> 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-queries-1/table-wise-sales.md).
# Table Wise Sales
The **Table Wise Sales** feature allows users to view sales details for each table along with the total collection amount. Follow the steps below to access and view the Table Wise Sales report.
## Steps to View Table Wise Sales
Step 1: Navigate to the **Point of Sale** module and select **Queries** menu.
1. Click on **Table Wise Sales**.
* After clicking **Table Wise Sales**, the Table Wise Sales screen will appear.
Step 2: The Table Wise Sales screen will display the available sales details.
1. Users can review sales information related to different tables.
* This screen helps users analyse sales activity table by table.
Step 3: After clicking the Display button, the system will show the sales report.
Step 4: View Total Collections.
1. The report will display the sales details for each table.
2. Users can also view the **Total Collection Amount** from the displayed report.
* This helps users monitor overall sales performance and table-wise collections.
---
# 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-queries-1/table-wise-sales.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.
