> 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/primeros-pasos/conoce-el-panel-de-gestion/ordenes-a-atender.md).

# Órdenes a atender

> **🔑** Rol requerido ➡ **Ventas (cualquiera de ellos)**

<figure><img src="https://2747103182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6IaVQbKlcXY7PQrymzlw%2Fuploads%2FxTu3sgClSeQhpW64Cxe1%2Fimage.png?alt=media&amp;token=ee9f1926-4969-4754-8042-9dea84c951c6" alt=""><figcaption><p>Indicadores de órdenes a atender</p></figcaption></figure>

Los recuadros indican las órdenes que pueden requerir atención o seguimiento por parte del comercio. En los recuadros se indican:

* **Nuevos pedidos** que deben ser preparados.
* **Pedidos cuyo pago debe ser revisado**, debido a inconsistencias entre el monto cobrados al comprador y el monto nominal de la orden.
* **Órdenes con pago pendiente**. Son aquellos en los que el pago aún no se ha hecho efectivo. Suelen ser pagos que se realizan offline, como ser los pagos en redes de cobranza.
* **Sin entregar**. Son las órdenes que están preparadas pero aún no han sido entregadas al cliente. Es recomendable revisar periódicamente las órdenes sin entregar para verificar que no exista ninguna atrasada o fuera de los plazos prometidos a los compradores.

{% content-ref url="/pages/-MAS37wYItpNRU\_SkcO3" %}
[Ventas y pedidos](https://guia.fenicio.help/ventas-y-pedidos/panel-de-ventas.md)
{% endcontent-ref %}


---

# 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/primeros-pasos/conoce-el-panel-de-gestion/ordenes-a-atender.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.
