Ticket types

What a ticket must have before it can be sent or paid — a customer, an address, a scheduled time, or an entity such as a captain or a table.

Who can do this: Owner
Permission needed: «Manage Settings»

Settings → Ticket Types controls the required fields and the numbering of each kind of ticket:

Each type shows what it needs (Customer Req., Address Req.) and Default for the type new tickets get.

Edit a type

Code (fixed), the Arabic Name and English Name, Color, Icon and the Sort Order.
Scheduled Time — Hidden, Optional or Required (a pre-order for a set time).
Ticket Numerator — Tenant default, or a numbering of its own.
Requires Customer — the ticket cannot be sent or paid without a customer.
Requires Address — and the customer must have an address (needs Requires Customer too).

At the till, a missing field opens the ticket details to fill it in.

Requires linking

Under Requires linking you tick the entity types a ticket of this type must be linked to before it can be sent or paid — for example a Captain who serves the order and the Table it is served at. Every active entity type is listed; you add entity types and their entities (the captains, the tables) in Settings → Layout (Floor plans).

The order counts. The number beside each ticked type is the order the till asks in: the first one you tick is asked first. To change the order, untick a type (or press Remove … beside it) and tick it again — it goes to the end.
An inactive entity type you required earlier stays in the list, greyed, marked Inactive. The till does not ask for it until it is active again; remove it here if you no longer want it.
In the list, each type shows what it requires, such as Captain required.

The Dine-In type requires a Captain and a Table

A ticket that is missing one of them is refused with this message. At the till, Major asks for the entity before that happens — see The till. The customer and address requirements above are asked first; the entities after them.