> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/suppliers-and-purchasing/purchase-orders.md).

# Purchase Orders

Purchase Orders, the orders you place with your suppliers in order to replenish stock, are the reverse side of the coin to Sales Orders.

The workflows for *Purchase Orders* are quite similar to those for *Sales Orders* as many of the concepts are shared, so be sure to study the "Sales Order Workflow Mega Tutorial" **before**reading this one - in particular, you should understand *Item Types* well. Since a lot of shared ground is covered in that tutorial, this one is a little less "mega", so you should breeze through it!

### Receipts, Invoicing and Payments: All Together

Just as is the case for *Sales Orders*, the receipts, invoice and payments are all created and live **inside** the main *Purchase Order* record rather than being separate entities unto themselves.

### Order Status <a href="#order-status" id="order-status"></a>

Purchase Orders have their own status axes:

* received
* invoiced
* paid

Just like *Sales Orders*, these axes can vary independently and can be in one of three states: *not at all*, *partially* (except in the case of 'invoiced') or *fully*.

\ <br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pakk.io/suppliers-and-purchasing/purchase-orders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.