> 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/banquet-sales.md).

# Banquet Sales

The **Banquet Sales** used to analyse banquet sales data within a selected date range. This analysis helps users review sales performance based on different grouping options, market segments, and contribution filters for better business insights and reporting.

## **Steps to View Banquet Sales Analysis**

Step 1: Log in to the system and navigate to the **Banquet Module**.

* Click on the **Analysis** menu.
* Select **Banquet Sales** from the available options.

Step 2: After selecting **Banquet Sales**, the system will open the analysis screen.

* By default, the system displays banquet sales details based on a **predefined day/date range**.
* This view provides an overview of banquet sales transactions for the selected period.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-9ab53ee7377a9b91b33589b1b90eab6464307eba%2Fm21%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

Step 3: Click on the **Group By** option.

* Select the required grouping method to organise the sales data accordingly.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-4ef6d46bf07cdfa99bd4288db573bbd7180153c1%2Fm21.1%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

Step 4: Click on the **Market Segment** option.

* Choose the required market segment(s) for analysis.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-e4ab992c2afa78a4cc7ddf2931675a9603405076%2Fm21.2.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 5: Click on the **Contribution Filter** option.

* Select the required filter criteria to refine the analysis results.
* This filter helps users focus on specific sales contributions or categories.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-6cb2cbd086b9b5e390f07dd9a554ef74d2e91a7a%2Fm21.3.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 6: After applying all required filters and selections, click on the **Display** button.

* The system will generate and display the **Banquet Sales Analysis Report** based on the selected criteria.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-aa62d8172b4acfb08d2d7d2a54acbc4ffe609a42%2Fm21.4.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/banquet-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.
