> 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-returns-report.md).
# Sales Returns Report
The Sales Returns Report in CW POS provides details of the returns made by customers. The report typically includes the following columns:
* Store: The store where the return was made
* Order Date: The date when the original sale was made
* SO Number: The sales order number of the original sale
* Product Catalogue: The catalog or category of the product returned
* Product: The name or SKU of the returned product
* Batch: The batch or lot number of the returned product
* UOM: The unit of measure of the returned product
* Return: The type of return made (e.g., defective, incorrect item, etc.)
* Order QTY: The original quantity of the product sold
* Return QTY: The quantity of the product returned
* Unit Price: The price of the product per unit
* Total Amount: The total amount of the return
This report can be useful in identifying the reasons for returns and in tracking the performance of the business in terms of customer satisfaction and product quality.
---
# 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-returns-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.