> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/readme-1/advanced-transaction-tasks/transactions-putting-hold.md).

# Poner transacciones en espera

Este tema describe cómo los cajeros y vendedores pueden poner transacciones en espera para que puedan recuperarse y completarse más tarde.

Cuando pones una transacción en espera, POS guarda y luego sale de la transacción incompleta. Tienes la opción de recuperar la transacción más adelante para completarla y cobrar la venta. Por ejemplo, podrías poner una transacción en espera si un cliente olvidó su billetera en el auto y tiene que correr hasta su auto para recuperarla. Puedes seguir procesando transacciones para otros clientes en la fila hasta que el cliente regrese con su billetera y puedas cobrar la venta.

{% hint style="info" %}
Debe tener el **Permitido poner transacciones en espera** permiso para poner una transacción en espera en POS.
{% endhint %}

1. Completa la mayor parte posible de la transacción.
2. Toca **Transacción** | **Poner en espera**.
3. Si se te solicita, introduce un **Comentario de espera** y toca **Aceptar**.


---

# 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://docs.rmhpos.com/es/readme-1/advanced-transaction-tasks/transactions-putting-hold.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.