> 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/about-quotes.md).

# About quotes

This topic describes best practices for working with quotes. Refer to your store's policies and procedures for quotes.

Generally, **quotes** are created if customers are researching costs for a purchase, or if they are comparing the costs of purchasing the same or similar items at different stores (comparison shopping).

Quotes may include discounts or price changes that the customer has negotiated with a salesperson or manager. Depending on the store's policies, quotes may only be valid for a limited period of time, such as 30 days. After this period, the store is no longer obligated to sell the items to the customer at the prices identified in the quote.

For quotes, you enter all of the items in the quote, but you don't collect any payment when you tender the sale. The customer has the option to return to the store at a later date to complete the transaction. They may also choose not to complete the transaction.

If some items from the quote are available immediately, customers have the option to pick up those items and return at a later time to pick up the remaining items. However, customers must pay the total amount for all items they pick up. Quotes can also be converted to work orders if store employees require additional time to assemble the order for the customer.


---

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