> 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/banquet/banquet-module/analysis/faq-on-analysis/how-can-i-analyze-item-wise-sales-and-market-segment-performance.md). # How can i analyze Item-Wise Sales and Market Segment Performance ? To analyze item-wise sales and market segment performance, you should use the tools located within the Analysis and Queries menus of the system. Analyzing Item-Wise Sales • **Item Wise Sales Tool:** Navigate to the Analysis menu and select Item Wise Sales to identify which products are generating the most interest and revenue . • **Filtering Data:** You can refine this analysis by filtering for specific Product Groups, Menu Items, or Open Items to get a granular view of your sales . • **KOT Details:** For a more operational perspective on item usage, you can also review the Kot Details report under the main Reports menu . Analyzing Market Segment Performance • **Banquet Sales Performance:** This specific tool in the Analysis menu allows you to compare different market segments side-by-side, which is essential for identifying growth opportunities and high-performing client types . • **Grouping by Segment:** In the general Banquet Sales analysis, you can use the Grouped By function and select Market Segment to see a breakdown of revenue generated by each category . • **Future Performance:** To analyze upcoming performance by segment, use the Business On Book query, which can be filtered by Business Filters to see what is currently on the books for different market categories . --- # 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/banquet/banquet-module/analysis/faq-on-analysis/how-can-i-analyze-item-wise-sales-and-market-segment-performance.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.