Set up ticket printing with QZ Tray

TripWorks supports printing physical tickets through QZ Tray, a lightweight application that runs on your computer and connects TripWorks to a locally attached or networked printer. This is separate from receipt printing — ticket printing uses custom-formatted commands and merge fields to generate tickets for individual bookings.

How it works

When a ticket is printed from TripWorks, the system:

  1. Retrieves the raw printer command you configured.
  2. Merges booking data into the command using the fields you defined.
  3. Sends the result to QZ Tray, which forwards it to the selected printer.

QZ Tray must be running on the device you are printing from. It connects to TripWorks automatically when present.

Configure ticket printing

  1. In TripWorks, go to Settings > Ticket Printing.
  2. In the Raw Printer Command field, enter the command your printer expects. This is specific to your printer model — consult your printer's documentation for the correct command syntax.
  3. Use merge field tokens (in the format %Field Name%) anywhere in the command to insert booking data at print time. See the available fields below.
  4. Under Default Printer, select the printer you want to use. QZ Tray must be running for printers to appear in this list. Your selection is saved to this device.
  5. Click Save.

Available merge fields

Insert these tokens into your raw printer command. TripWorks replaces them with the booking data at print time.

Customer

  • %First Name%
  • %Last Name%
  • %Full Name%
  • %Email%
  • %Phone%
  • %Confirmation #%

Ticket

  • %Booking ID%
  • %Ticket Type%
  • %Ticket Price%

Activity

  • %Experience Name%
  • %Experience Internal Name%
  • %Experience Date%
  • %Experience Time%
  • %Experience Date & Time%

The label used for "Experience" may differ in your account if you have configured a custom activity label under account settings.

Troubleshooting

No printers appear in the Default Printer dropdown
QZ Tray is not running. Start QZ Tray on the device, then reload the page.

Ticket prints but data fields are blank
Check that your merge field tokens match the exact field names above, including capitalization and spaces. For example, %First Name% will work but %firstname% will not.

Printer command produces unexpected output
The raw command is sent directly to the printer without modification (after merge field replacement). Verify the command syntax against your printer manufacturer's documentation.