> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/envios-y-entregas/preparar-y-despachar/etiquetas-de-entrega.md).

# Etiquetas de logística

Cuando el pedido esté listo para enviar, se debe seleccionar en la columna de entrega el estado "Listo para enviar". Según la configuración del módulo de Logística, este cambio puede activar automáticamente la generación de la etiqueta. En algunos casos, el sistema de gestión realiza este cambio de estado de forma automática.

El cliente recibirá notificaciones por email sobre el estado de su paquete, configurables desde el módulo de [Notificaciones al Cliente](https://guia.fenicio.help/clientes-y-comunicaciones/notificaciones-a-clientes.md).

El código de tracking se completa automáticamente con la información del proveedor de envío.

La etiqueta se puede obtener desde el [Panel de ventas](https://guia.fenicio.help/ventas-y-pedidos/panel-de-ventas.md) o desde el [Detalle de una venta](https://guia.fenicio.help/ventas-y-pedidos/gestionar-una-venta/detalle-de-una-venta.md).

{% hint style="info" %}
Para integración con Mercado Libre, se habilita una etiqueta oficial de envío lista para imprimir.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guia.fenicio.help/envios-y-entregas/preparar-y-despachar/etiquetas-de-entrega.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
