> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-inventory/purchase-order.md).
# Purchase Order
Maitre'D's purchase order report allows to print a previously created purchase order so it can be mailed, faxed or read over the phone to the supplier. From the report filter window, select the dates, suppliers, locations, items and categories to be included in the report. The following is a sample of the purchase order report:
This report is divided in two sections. The first section provides you with:
**>Billing address**
Address where the invoice will be mailed.
**>Purchase Order**
**Date:**
Date of creation of the purchase.
**P.O.#:**
Purchase order sequential number.
**Supplier:**
Address of supplier for this purchase.
**Ship To:**
Address where the merchandise will be shipped.
The second section provides you with:
**Quantity:**
Quantity of items ordered.
**Unit:**
Format of items ordered.
**Code:**
Code of the inventory item.
**Description:**
Inventory item description.
**Price:**
Price paid by purchase format.
**Amount:**
Total $ amount of the ordered item.
**Total:**
Total $ amount of all items on the purchase order.
---
# 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.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-inventory/purchase-order.md?ask=&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.