Event ticket templates

How tickets get generated

Tickets are the category where the scannable code is the whole point. A ticket design that cannot carry a different code per copy is a poster. Here the QR or barcode is bound to a variable exactly like a text field, so a thousand rows produce a thousand tickets each holding its own ticket ID — CODE128, EAN-13, UPC, CODE39 or ITF-14 depending on what the scanner at the door expects. That matters more than it sounds: getting the barcode symbology wrong is discovered at the venue, not in the design review. Numbering is the other half of the job, and it is worth deciding the scheme before the first batch rather than after.

In practice: Booking systems generally call the API per purchase and attach the render to the confirmation email. Fixed-capacity events batch the whole allocation from a CSV up front.

Fields you'd usually bind

{{ticket_code}}

Bound to the QR or barcode element — unique per row, this is the field that matters.

{{attendee_name}}

For named tickets and conference passes.

{{seat}}

Section, row and seat, where the event is seated.

{{event_date}}

Usually constant across a batch, variable across a season.

Any text, image, QR code or barcode on the canvas can become a variable — these are just the ones this category tends to use.