> 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/pos-analysis-popularity-analysis.md).
# Popularity Analysis
The **Popularity Analysis Report** helps users analyze the popularity and profitability of menu items within the restaurant. This report provides valuable insights into item performance by identifying which menu items are selling the most and generating the highest profit.
## Steps to Open the Popularity Analysis Report
Step 1: Navigate to the **Point of Sale** module and click the **Analysis** menu.
1. Select **Popularity Analysis**
* The **Popularity Analysis** screen will be displayed.
Step 2: Choose the required **Advance Filter** options for the report.
* The filter options help users generate reports based on specific business requirements.
Step 3: After selecting the required filters and options, click on the **Display** button.
* The Popularity Analysis 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/pos-analysis/pos-analysis-popularity-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.
