> 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/backoffice/settings/terminals.md). # Terminals ## **Overview** The Terminals section is used to configure and manage the terminals used in the system. Users can create terminals based on their restaurant setup and manage existing terminals by editing, deleting, or changing their display order.

### **Screen Elements**

| **Screen Element** | **Description** | | ------------------ | ---------------------------------------------------------- | | Terminal List | Displays the terminals configured in the system. | | Search | Used to search for a specific terminal. | | Add Terminal | Used to create a new terminal. | | Edit Terminal | Used to modify the selected terminal. | | Delete Terminal | Used to remove the selected terminal. | | Change Sort Order | Used to change the order in which terminals are displayed. | | Close | Closes the Terminal screen. | ### **Working** #### **Create a Terminal** 1. Select "Add Terminal" from the Terminal List.

2. Enter the required "Code Name" and "Terminal Name".

3. Select the required "Report Printer", "Transaction Printer", and "Parent Terminal".

4. Enter the required "Opening Cash" and "Tolerance" values.

5. Enable the required terminal options, such as "Default Terminal" or "Collection Terminal". 6. Enter the required "Terminal Identification" and "SerialNumber".

7. Select "Save" to create the terminal.

#### **Edit a Terminal** 1. Select the required terminal from the Terminal List. 2. Select "Edit Terminal".

3. Update the required terminal information. 4. Select "Save" to apply the changes.

#### **Delete a Terminal** 1. Select the terminal to be deleted. 2. Select "Delete Terminal".

3. Confirm the deletion when prompted.

#### **Change Sort Order** 1. Select "Change Sort Order".

2. Arrange the terminals in the required order. 3. Save the new order as prompted. ### **Use Case** * Configure separate terminals for different billing counters within the restaurant. * Set up dedicated terminals for different service areas, such as the restaurant floor, takeaway counter, or drive-through counter. * Assign specific report and transaction printers to terminals based on the printing requirements of each counter or service area. * Configure a terminal as the "Default Terminal" when it needs to be used as the primary terminal for the operation. * Set up a "Collection Terminal" when a particular terminal is responsible for handling collections. * Define "Opening Cash" for terminals that handle cash transactions at the beginning of their operation. * Configure multiple terminals when the restaurant requires separate billing points for different operational areas. * Organize the configured terminals in a preferred order to make them easier to identify and manage in the Back Office. ### **Notes** * Configure each terminal with the appropriate terminal code and name. * Select the correct printers for reports and transactions. * Configure "Opening Cash" according to the terminal's operational requirements. * Enable "Default Terminal" or "Collection Terminal" only when required. * Enter the correct "SerialNumber" and terminal identification details. * Review the terminal before deleting it, as deletion removes it from the configured Terminal List. --- # 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/backoffice/settings/terminals.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.