> 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/faq-on-advanced-reports/how-to-check-item-wise-sales.md).

# How to check item-wise sales?

To check item-wise sales, you can use the specialized Item Wise Sales report or the Outlet Item Audit found in the Advance module.

**Item Wise Sales Report**

The Item-wise Sales report provides comprehensive information for a selected period, allowing you to identify which items are the most popular. It lists all items sold during that timeframe along with their:

* Net quantity.
* Cost value.
* Sales value.
* Discount value.

**Steps to access the report:**

1. Navigate to **Advance Reports > Item Wise Sales.**
2. Select any additional options or filter settings you want printed in the report.
3. Apply any necessary sorting based on your requirements.
4. Click the display button to generate the report.

**Outlet Item Audit**

Alternatively, you can use the Outlet Item Audit to monitor and verify item-wise sales and usage at a specific outlet. This audit ensures correct item configuration, pricing, and billing accuracy while helping to prevent discrepancies or misuse.Steps to access the audit:

1. Navigate to **Advance Reports > Outlet Item Audit.**
2. Click the display button to view the report


---

# 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/faq-on-advanced-reports/how-to-check-item-wise-sales.md?ask=<question>&goal=<user_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.