> 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/store-manager/manage-purchase-orders-and-transfers-out.md).

# Manage purchase orders and transfers out

- [Purchase order best practices](https://docs.rmhpos.com/store-manager/manage-purchase-orders-and-transfers-out/purchase-order-best-practices.md): This topic describes best practices for purchase orders (POs), such as setting up the reorder point and restock level, the sale and purchase units of measure, and the manufacturer pack quantity (MPQ).
- [Create purchase orders from purchase order requisitions](https://docs.rmhpos.com/store-manager/manage-purchase-orders-and-transfers-out/creating-purchase-order-requisitions.md): This topic describes how to automatically add items to purchase orders by creating a purchase order requisition and converting it to a purchase order.
- [Create or edit purchase orders](https://docs.rmhpos.com/store-manager/manage-purchase-orders-and-transfers-out/creating-purchase-order.md): This topic describes how to create a purchase order and add items to it manually.
- [Receive purchase orders](https://docs.rmhpos.com/store-manager/manage-purchase-orders-and-transfers-out/receiving-purchase-orders.md): This topic describes how to receive purchase orders from suppliers.
- [Create a transfer out](https://docs.rmhpos.com/store-manager/manage-purchase-orders-and-transfers-out/creating-transfer-order.md): This topic describes how to create a transfer out and add items to it manually.


---

# 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/store-manager/manage-purchase-orders-and-transfers-out.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.