> 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/sales-cost.md).
# Sales Cost
Maitre'D's Sales Cost Report shows information on the sales cost per inventory item and the differences between the real and the theoretical used quantities. This report is available on a weekly, periodic and monthly basis for the current and past time period. 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 sales cost report:
**Product:**
Description of the inventory item.
**Units:**
Format the item is used in recipes.
**Theoretical Sales Cost:**
Total cost of inventory item sold.
**Variance:**
Quantity of inventory item variation in usage units.
**Variance Value:**
Total value of inventory item variation.
**Variance %:**
Percentage of variance value compared to total of sales cost added with variance value.
---
# 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/sales-cost.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.