> 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/usage-report.md).
# Usage Report
Maitre'D's Usage Report shows information based on real quantity used per item, based on beginning stock, purchases, transfers and ending stock for the time period requested. This report could be useful when planning your purchases. From the report filter window, select the appropriate period, suppliers, inventory items, categories, groups, locations and departments to be included in the report. The following is a sample of the usage report:
**Product:**
Description of the inventory item.
**Units:**
Format the item is used in recipes.
**Beginning stock:**
Quantity of inventory item, in usage units, at beginning of the time period.
**Purchases:**
Quantity of inventory item, in usage units, purchased during the time period.
**Transfer:**
Quantity of inventory item, in usage units, transferred during the time period.
**Ending stock:**
Quantity of inventory item, in usage units, at end of the time period.
**Real Used:**
Beginning stock plus purchases minus transfers and ending stock.
---
# 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/usage-report.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.