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

# About backorders

This topic describes best practices for working with backorders. Your store may or may not offer backorders. Refer to your store's policies and procedures for backorders.

A **backorder** can be created at the request of the customer if the item or items they want to purchase are temporarily out of stock. Depending on the store's policies, a percentage deposit or full payment may be required at the time the backorder is created in POS.

Generally, backorders should only be created for items that are regularly in stock, or for items that the store is confident it will receive from the supplier in a reasonable amount of time. If backordered items are not available from the supplier (e.g., promotional or seasonal items), or the purchase order cannot be fulfilled by the supplier in a timely manner, the store may be required to cancel the backorder and issue a refund to the customer, if applicable. This can be disappointing for customers, and cause unnecessary administration for the store.

Depending on the store's policies, backorders may only be valid for a limited period of time such as 30 days. After this period, the store may opt to cancel the backorder and issue a refund to the customer, if applicable. The best practice is to identify the expiration period for backorders on the receipt, and any other store policies relevant to backorders such as whether the store honors backorder pricing and for how long.


---

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