> 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/work-with-quotes/cancel-quotes.md).

# Cancel quotes

This topic describes how cashiers, salespeople, and floor managers can cancel quotes.

If you look up the customer, when you recall the quote, POS only displays quotes belonging to the selected customer. If you do not look up the customer, when you recall the quote, POS displays all open quotes and you will have to search for the customer's quote.

1. (Optional) Look up the customer. Refer to [**Look up customers**](/readme-1/work-with-customers/customers-looking-up.md) for more information.
2. Tap **Orders** | **Recalls** | **Recall a Quote**.
3. To select the customer's quote, do one of the following:

* Tap the quote and tap **Add**.
* Tap the quote twice.

4. Tap **Orders** | **Cancel Order**.
5. (Optional) On the **Deposit to Keep** screen:
   1. Enter the amount of the customer's deposit that the store is keeping (not refunding to the customer). If the store is returning the full deposit to the customer, enter zero (0).
   2. Tap **OK**.
6. Enter the refund amount next to the appropriate tender type.
7. Tap **OK**.
8. (Optional) Print or email the customer's receipt.


---

# 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/work-with-quotes/cancel-quotes.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.