> For the complete documentation index, see [llms.txt](https://docs.cwsuite.com/pos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cwsuite.com/pos/product-guides/reports/sales-by-product-category-report.md).
# Sales By Product Category Report
The Sales By Product Category Report in CW POS provides a summary of sales performance by product category. It typically includes the following columns:
* Store: The location where the products were sold.
* Parent Product Category: The higher-level product category that the product belongs to (if applicable).
* Product Category: The specific product category that the product belongs to.
* Sold QTY: The total quantity of the product sold in the given time period.
* Total Amount: The total sales amount generated by the product category in the given time period.
This report is useful for understanding the sales trends and performance of different product categories across stores, and can help identify areas of strength or areas for improvement.
---
# 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.cwsuite.com/pos/product-guides/reports/sales-by-product-category-report.md?ask=&goal=
```
`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.