> 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/pos-analysis/stewardwise-sales-analysis.md).
# Stewardwise Sales Analysis
The **Stewardwise Sales Analysis** report helps users analyze and review sales data efficiently. This report allows users to apply advanced filters, display the required data, and export the report to Excel for further analysis.
## Steps to Open Stewardwise Sales Analysis
Step 1: Navigate to the **Point of Sale** module and click the **Analysis** menu.
1. Select **Stewardwise Sales Analysis.**
* The **Stewardwise Sales Analysis** screen will open.
Step 2: On the **Stewardwise Sales Analysis** screen, click the **Advanced Filter** option.
1. Select the required filter values based on your reporting needs.
Step 3: After selecting the required filters, click the **Display** button.
* The system will generate and display the sales analysis report on the screen.
If the user wants to export the report to Excel:
1. Click the **Excel Export** icon/button available 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/pos-analysis/stewardwise-sales-analysis.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.
