> 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/stock-value-by-category.md).
# Stock Value by Category
Maitre'D stock value by group report shows you both how much your stock has cost you, as well as how much it is worth now, divided by inventory categories. From the report filter window, select the time period to be included in the report. The following is a sample of the stock value by category report:
For each inventory category, and for all inventory categories, the report provides you with:
**Inventory Category:**
Description of the inventory category.
**Average Cost:**
Value of inventory items that belong to that category according to their average cost. This number shows how much the stock you have in hand has cost you.
**Last Cost:**
Value of inventory items that belong to that category according to the last price paid. This number shows how much the stock you have in hand would likely cost to replace.
---
# 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/stock-value-by-category.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.
