> 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/dineplan/pos/merge-tickets/faqs.md).
# FAQ's
## 1. How do I combine bills from multiple tables into a single ticket when a customer wants to pay together?
To combine tickets from multiple tables into a single ticket for a customer paying altogether, follow the two-stage merge process:
1. **Stage 1 — Bring Tables Together:** Open the POS module and select the first table. Click **"Change Table"** in the top-left corner of the screen to open the **Table Selection Screen**, then select the next table to bring its orders into the same view. Repeat **"Change Table"** if additional tables need to be added.
2. **Stage 2 — Select and Merge Tickets:** Open the merged table to view all available tickets individually on the **Ticket List**. Click the specific **Ticket Number** on the left side of the ordering screen for each ticket that needs to be combined. Once all required tickets are selected and highlighted, click the **"Merge"** button to unite them into a single ticket.
**Note:** Always verify the combined ticket, items, and total amount before proceeding to final payment.
## 2. What checklist should I verify before starting to merge tickets for a customer party?
Before initiating the **Merge Tickets** process in DinePlan POS, complete the following pre-merge checklist:
* Verify that all tables to be combined currently have active tickets in the system.
* Identify all table numbers that the customer wants to group into a single bill.
* Ensure you are logged into the appropriate POS terminal with permissions to access the **"Change Table"** option.
* Confirm directly with the customer which specific tables and orders should be included in the combined bill.
**Note:** Confirming table numbers with the customer beforehand prevents accidentally merging orders from unrelated tables.
## 3. Where do I find the "Change Table" option to start bringing separate tables together?
The **"Change Table"** button is located directly on the POS ordering screen.
To locate and use it:
1. Open the **POS** module.
2. Select the first table involved in the group order (for example, "Table 3").
3. The ordering screen for that table opens.
4. Look at the **top-left corner of the screen** to find and click **"Change Table"**.
**Result:** Selecting **"Change Table"** opens the **Table Selection Screen**, allowing you to associate the current order view with another table.
## 4. How do I bring a second or third table into the same view using "Change Table"?
To group multiple tables together into one display view, use the **"Change Table"** function sequentially:
1. On the ordering screen of your first table, click **"Change Table"** in the top-left corner.
2. The **Table Selection Screen** opens, displaying all available tables on the POS screen.
3. Select the next table to be included (for example, "Table 7").
4. The selected table is brought into the current table view.
5. If a third table needs to be added (for example, "Table 4"), click **"Change Table"** again.
6. Select the next table from the **Table Selection Screen**.
7. Repeat this sequence until all required tables are brought together.
## 5. How do I select specific individual ticket numbers to combine once tables are brought together?
After bringing the required tables together, select the exact tickets to be merged:
1. Open the merged table to view the ordering screen.
2. Locate the **Ticket List** displaying individual **Ticket Number** entries on the left side of the ordering screen.
3. Click the specific **Ticket Number** for the first table (e.g., Table 3).
4. Click each additional **Ticket Number** for the other tables (e.g., Table 7 and Table 4).
5. Verify that each selected ticket is highlighted on screen, indicating it is marked for the merge.
**Note:** Carefully review the ticket details to ensure only the customer's requested tickets are highlighted.
## 6. Why is the "Merge" button grayed out or inactive, and how do I activate it?
The **"Merge"** button remains inactive until all required tickets have been explicitly selected.
To activate the **"Merge"** button:
1. Ensure you have opened the merged table view.
2. Click on the specific **Ticket Number** entries on the left side of the ordering screen.
3. Once the required tickets are selected and highlighted, the system automatically activates the **"Merge"** button.
4. Review the selected tickets one final time, then click **"Merge"** to execute the combination.
## 7. How do I use Order Details and Ticket Amount to verify that I am selecting the correct ticket?
To ensure you do not merge an incorrect or unrelated ticket, review the details displayed on screen before merging:
* **Order Details:** Displays the individual items and order information associated with a selected ticket. Check the item names and quantities to confirm they match what the customer ordered.
* **Ticket Amount:** Displays the financial total associated with the selected ticket. Cross-check the amount to confirm the ticket belongs to the correct party.
**Note:** Always check both **Order Details** and **Ticket Amount** prior to clicking **"Merge"** to confirm that no unrelated ticket is included.
## 8. What are the exact steps to finalize combining selected tickets after tapping "Merge"?
Once the **"Merge"** button becomes active, follow these steps to finalize the merge and verify the output:
1. Review the highlighted **Selected Ticket** entries one more time.
2. Click **"Merge"** to combine the selected tickets into a single ticket.
3. Review the newly updated ticket displayed on the ordering screen.
4. Check that all expected items from the separate tickets are now listed on the combined ticket.
5. Verify the combined **Ticket Amount**.
6. Confirm that no unrelated tickets or items were accidentally included.
## 9. How do I handle a scenario where a customer wants to merge orders across three different tables (e.g., Tables 3, 4, and 7)?
When a party seated across three tables (such as Tables 3, 4, and 7) requests a single bill, execute the following step-by-step workflow:
1. **Open Table 3** from the POS table screen.
2. Click **"Change Table"** in the top-left corner.
3. On the **Table Selection Screen**, select **Table 7**.
4. Click **"Change Table"** again.
5. On the **Table Selection Screen**, select **Table 4**.
6. Open the table containing the merged tickets.
7. Review the displayed tickets from Tables 3, 7, and 4.
8. Click the required **Ticket Number** entries on the left side to select them.
9. Click **"Merge"**.
10. Verify the combined ticket items and total amount before processing payment.
Refer this link - [Merge Ticket](https://help.rbsgo.com/dineplan/pos/merge-tickets/pages/HUBf8g3DEsaVKFPAUtSa#merge-tickets.1)
## 10. How do I process the final payment after successfully merging the tickets?
After merging the required tickets into a single ticket, proceed with payment settlement:
1. Review the combined ticket on the ordering screen and verify the total bill amount.
2. Select **"Pay"**.
3. Select the payment method requested by the customer (e.g., Cash or Card).
4. Complete the transaction.
5. If the customer requests to split the combined bill among party members, select the applicable split-payment option on the payment screen.
## 11. What should I do if a table has multiple individual tickets listed on the merged ordering screen?
When multiple tickets appear on the ordering screen after using **"Change Table"**, follow these selection rules:
1. Review the **Ticket List** on the left side of the screen, where tickets from the merged tables are displayed individually.
2. Click on each individual **Ticket Number** to inspect its **Order Details** and **Ticket Amount**.
3. Select **only** the ticket numbers that belong to the customer requesting the combined bill.
4. Ensure unselected tickets (belonging to other guests) remain unhighlighted.
5. Verify that all required tickets are highlighted as **Selected Ticket** entries before clicking **"Merge"**.
## 12. How does the Table Selection Screen work when associating orders from different tables?
The **Table Selection Screen** is an intermediate selection window in DinePlan POS:
* It opens automatically after clicking **"Change Table"** on an active ordering screen.
* It displays all available tables across the POS layout.
* Selecting a table from this screen brings that table or order into association with the active table view.
* This allows staff to group separate seating locations together so their individual tickets can be selected and combined.
## 13. What checks should I perform after clicking "Merge" to ensure no incorrect items were merged?
Immediately after clicking **"Merge"**, perform the following verification check on the ordering screen:
* **Review the Ticket:** Inspect the single combined ticket displayed on screen.
* **Verify Items:** Check that all expected menu items from the original tables are present.
* **Verify Amount:** Check the combined total ticket amount for accuracy.
* **Confirm Exclusion:** Ensure no unrelated ticket or item from another table was accidentally included.
**Note:** Always perform this verification check before tapping **"Pay"**.
## 14. Can a customer split the payment after all their table tickets have been merged into one?
Yes. Once tickets from multiple tables have been combined using **"Merge"**, the system creates a single merged ticket.
To process payment:
1. Verify the total amount on the combined ticket.
2. Click **"Pay"**.
3. If the customer wishes to split the payment across multiple payment methods or party members, select the applicable split-payment option on the payment screen.
4. Complete the payment process.
## 15. What critical mistakes should I avoid during the Merge Tickets workflow to prevent wrong billing?
To prevent billing errors and accidental order merging, follow these documented guidelines:
* **Never skip customer confirmation:** Always confirm with the customer which tables and orders need to be combined before starting.
* **Verify each table selection:** Check the table selected at every stage of the **"Change Table"** process.
* **Review all displayed tickets:** Do not select tickets blindly; review the **Ticket List**, **Order Details**, and **Ticket Amount** for every table brought into view.
* **Select only required tickets:** Ensure only the customer's specific ticket numbers are highlighted before clicking **"Merge"**.
* **Always verify before payment:** Check the final combined ticket and total amount before clicking **"Pay"**.
---
# 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/dineplan/pos/merge-tickets/faqs.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)