> 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-report.md).
# Sales By Product Report
Sales by Product Report is a report generated by CW POS that shows the sales performance of products in a particular store or across multiple stores. The report typically includes the following columns:
* Store: The store(s) where the products were sold
* Product Category: The category to which the product belongs
* SKU: The Stock Keeping Unit (SKU) or unique identifier for the product
* Product: The name or description of the product
* QTY: The total quantity of the product sold
* Sales: The total sales amount generated by the product
The report can be filtered by date range and can provide valuable insights into the performance of individual products or product categories, helping retailers identify their best and worst performing products and make informed decisions about inventory management and marketing strategies.
---
# 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-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.