> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/purchase-and-receivement.md).

# Purchase and receivement

## Introduction

Purchasing and receiving goods are essential steps in keeping your store stocked and running smoothly. In Flow Retail POS, these processes are designed to be simple, transparent, and fully integrated with your inventory.

This section will guide you through how to create purchase orders, register deliveries from suppliers, and ensure that stock levels are always accurate. By using the built-in purchasing and receiving tools, you can reduce errors, save time, and maintain full control of your inventory.

#### In this section you will learn how to

* How to create and manage purchase orders
* How to receive goods and update inventory
* How to deal with differences between ordered and delivered items
* How to set and use minimum and maximum stock levels
* How to add and manage suppliers in the system


---

# 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.flowretail.com/docs/day-to-day-operations/purchase-and-receivement.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.
