This provides an overview of the Print Fields/Items/Variables available in Touch that can be included when printing to Floor/Kitchen/Label/Order/Raffle Ticket Barrel/Receipt printers.
Subjects ▼
- How To Access Print Fields/Items/Variables
- Conditional
- Custom Printer Commands
- Customer
- General
- Misc
- Orders
- Printer Commands
- Product Labels
- Raffles
- Tables
- Print Fields/Items/Variables
How To Access Print Fields / Items / Variables ▲ ▼
Print Fields/Items/Variables can be accessed via the Add Item button when editing anyone of the Printing Peripherals for Floor/Kitchen/Label/Order/Raffle Ticket Barrel/Receipt printers. For example:

Conditional ▲ ▼
Graphical ▲ ▼
Custom Printer Commands ▲ ▼
Graphical ▲ ▼
Customer ▲ ▼
Graphical ▲ ▼
General ▲ ▼
Graphical ▲ ▼
Misc ▲ ▼
Graphical ▲ ▼
- {EVENT AREA} - Refer to the Print Fields/Items/Variables section below for more specific information.
- {EVENT NAME} - Refer to the Print Fields/Items/Variables section below for more specific information.
Orders ▲ ▼
Graphical ▲ ▼
Printer Commands ▲ ▼
Graphical ▲ ▼
Product Labels ▲ ▼
Graphical ▲ ▼
Raffles ▲ ▼
Graphical ▲ ▼
Tables ▲ ▼
Graphical ▲ ▼
Print Fields / Items / Variables ▲ ▼
{Event Area} ▲ ▼
Select to include the name of the Area when printing Kitchen/Order/Receipt dockets using:
- Touch - The Area has been selected from the Event grid when the Order/Sale is commenced.
Notes...
The Area maybe overridden. For example, if a Table is added to an Order/Sale after selecting an Area, it will remove the Area from the Order/Sale.
- POS API - If the first character in the BookingName field has an open bracket "(", and then a closed bracket is also detected ")", it will use the data between the two brackets and determine the Area, by doing the following:
- Check if a Session is configured/scheduled at the date/time in the Location based on the TransactionDate in the POST/order request. If one is:
- NOT FOUND - Then the {SUITE NAME} or {EVENT AREA} Field/Item/Variable will NOT be populated.
- FOUND - If the data between the brackets () is:
- Numeric - It will attempt to locate an Area assigned to the Session based on the Area's ID (Id column) and return the Area's description (Area column) as the {SUITE NAME} or {EVENT AREA}.
- Apha-numeric - it will attempt to locate an Area assigned to the Session based on the Area's description (Area column) and return the Area's description (Area column) as the {SUITE NAME} or {EVENT AREA}.
- If neither of the above is located, then the {SUITE NAME} or {EVENT AREA} Field/Item/Variable will NOT be populated. This also means it won’t store the data within the brackets as the “SuiteId” in the raw transaction data.
- Check if a Session is configured/scheduled at the date/time in the Location based on the TransactionDate in the POST/order request. If one is:
Notes...
This was previously referred to as {SUITE NAME}. Venues that currently have {SUITE NAME} on their dockets do NOT need to change it. These will continue to function in the same way as it's replacement Field/Item/Variable functions, namely {EVENT AREA} .
{Event Name} ▲ ▼
Select to include the name of the Event when printing Kitchen/Order/Receipt dockets using:
- Touch - At the time the Order/Sale is finalised, if there is an Event configured/scheduled at the date/time in the Location the terminal is assigned too, then the Session's Name will be returned as the {Event Name}.
- POS API - The Session's Name will be returned as the {Event Name}, if a Session is located based on the “TransactionDate” in the POST/order request.
Notes...
For Orders/Sales posted via POS API for past or future Events , the correct Session Name will be returned based on the TransactionDate in the POST/order request, and NOT based on when it was submitted to SwiftPOS.
- Back Office API - It is recommended that if the incorrect {Event Name} is being returned, to switch to using POS API. This can be done by selecting the Submit orders directly to POS Terminal option when activating a Location.
End of article. ▲