> 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/tickets/ticket-types.md).

# Ticket Types

### **Overview** <a href="#overview.1" id="overview.1"></a>

The Ticket Types setting allows you to manage the different types of tickets used in the system. You can add, edit, delete, and sort ticket types. While creating or editing a ticket type, you can configure its general settings, associate entity types, and map the ticket type to specific terminals and menus.

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

### **Screen Elements** <a href="#screen-elements.1" id="screen-elements.1"></a>

| **Screen Element**        | **Description**                                                                      |
| ------------------------- | ------------------------------------------------------------------------------------ |
| Ticket Type List          | Displays the available ticket types.                                                 |
| Search                    | Allows you to search for a specific ticket type.                                     |
| Add Ticket Type           | Opens the screen to create a new ticket type.                                        |
| Edit Ticket Type          | Opens the selected ticket type for editing.                                          |
| Delete Ticket Type        | Deletes the selected ticket type after confirmation.                                 |
| Sort Ticket Types         | Allows you to change the order of the ticket types.                                  |
| Ticket Type Name          | Specifies the name of the ticket type.                                               |
| Transaction Type          | Specifies the transaction type associated with the ticket type.                      |
| Ticket Number Generator   | Specifies the number generator used for tickets.                                     |
| TicketInvoiceNumerator    | Specifies the numerator used for ticket invoices.                                    |
| Order Number Generator    | Specifies the number generator used for orders.                                      |
| Promotion Numerator       | Specifies the numerator used for promotions.                                         |
| FullTaxInvoiceNumerator   | Specifies the numerator used for full tax invoices.                                  |
| QueueNumerator            | Specifies the numerator used for queue numbers.                                      |
| Tax Included              | Determines whether tax is included for the ticket type.                              |
| Pre Order                 | Determines whether the ticket type is configured for pre-orders.                     |
| Allow Zero Price Products | Determines whether zero-price products can be used with the ticket type.             |
| Entity Type List          | Allows you to select and configure the entity types associated with the ticket type. |
| Menu Mapping              | Allows you to map the ticket type to the required terminals and menus.               |
| Save                      | Saves the ticket type configuration.                                                 |
| Close                     | Closes the current screen.                                                           |

### **Working** <a href="#working.1" id="working.1"></a>

#### **Add a Ticket Type** <a href="#add-a-ticket-type" id="add-a-ticket-type"></a>

1. Select "Add Ticket Type".

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

2. Enter the required details in "Ticket Type Name" and configure the required settings.

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

3. Open "Entity Type List" and select the required entity types.

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

4. Select “Select” and configure the entity type settings as required.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-7733df7a8fa65a20f462ba6ccc4c972c79afd3aa%2Fatt_13_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

5. Open "Menu Mapping" and select the required terminals and menus.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-3555952d41ada213e95b5c9bcd932534effeb4bf%2Fatt_14_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

6. Select "Save" to create the ticket type.

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

#### **Edit a Ticket Type** <a href="#edit-a-ticket-type" id="edit-a-ticket-type"></a>

1. Select the ticket type that needs to be modified.
2. Select "Edit Ticket Type".

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

3. Update the required settings, entity types, or menu mappings.
4. Select "Save" to save the changes.

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

#### **Delete a Ticket Type** <a href="#delete-a-ticket-type" id="delete-a-ticket-type"></a>

1. Select the ticket type that needs to be deleted.
2. Select "Delete Ticket Type".

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

3. In the confirmation message, select "Yes" to delete the ticket type.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-5111145fbc4ae528b76661d19c8e2880ac0493ff%2Fatt_19_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Sort Ticket Types** <a href="#sort-ticket-types" id="sort-ticket-types"></a>

1. Select "Sort Ticket Types".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-8ba8ab79e08766dbda78f0b8360cc9a307cc16d2%2Fatt_20_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Arrange the ticket types in the required order.

#### **Search for a Ticket Type** <a href="#search-for-a-ticket-type" id="search-for-a-ticket-type"></a>

1. Enter the required text in "Search".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-18c84d6eefcf6108ba490e2a97096dc7bc6820c0%2Fatt_21_for_3423698947.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Select or review the matching ticket type from the list.

### **Use Case** <a href="#use-case.1" id="use-case.1"></a>

* Create ticket types based on different transaction requirements.
* Configure ticket and order number generation for each ticket type.
* Define tax and pre-order settings for specific ticket types.
* Allow zero-price products where required.
* Associate relevant entity types with a ticket type.
* Configure entity-related settings before creating tickets.
* Map ticket types to the required terminals and menus.

### **Notes** <a href="#notes.1" id="notes.1"></a>

* Ensure the required fields are configured before selecting "Save".
* Review the selected entity types before confirming the configuration.
* Verify the terminal and menu mappings for the ticket type.
* Deleting a ticket type requires confirmation.
* Use "Search" to quickly locate a ticket type.
* Use "Sort Ticket Types" to arrange ticket types in the required order.


---

# 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/tickets/ticket-types.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.
