> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/item-wise-sales.md).
# Item Wise Sales
The **Item Wise Sales Report** provides detailed sales information for items sold during a selected period. This report helps users analyze item performance by displaying sales quantity, cost value, sales value, and discount value for each item.
## Steps to Open the Item Wise Sales Report
Step 1: Navigate to the **Point of Sale** module and click the **Advanced Reports** menu.
1. Select **Item Wise Sales**
* The **Item Wise Sales** screen will be displayed.
Step 2: Choose the additional options that you want to include in the report.
1. Select the required filter options based on your reporting needs.
Step 3: Sort the Report Data:
1. The system allows users to sort the report data for easier analysis.
2. Click on the required column heading or sorting option to arrange the data in ascending or descending order.
Step 4: After selecting the required filters and sorting options, click on the **Display** button.
1. The Item Wise Sales Report will appear on the screen.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/advanced-reports/item-wise-sales.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.
