> 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/readme-1/advanced-transaction-tasks/transactions-putting-hold.md).

# Put transactions on hold

This topic describes how cashiers and salespeople can put transactions on hold so they can be recalled and completed at a later time.

When you put a transaction on hold, POS saves and then exits the incomplete transaction. You have the option to recall the transaction at a later date to complete it and tender the sale. For example, you might put a transaction on hold if a customer forgot their wallet in their car and has to run to their car to retrieve it. You can continue to process transactions for other customers in line until the customer returns with their wallet and you can tender the sale.

{% hint style="info" %}
You must have the **Allowed to put transactions on hold** permission to put a transaction on hold in POS.
{% endhint %}

1. Complete as much of the transaction as possible.
2. Tap **Transaction** | **Hold**.
3. If prompted, enter an **On Hold Comment** and tap **OK**.


---

# 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/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.