Event Tickets
Unique scannable tickets in three clicks — sequential numbering + QR for gate check-in.
- Canvas
- 105 × 148 mm (A6 / Postcard)
- Bleed
- 3 mm
- Symbology
- QR Code, error-correction M (~15% damage tolerance)
- Sheet layout
- 4-up on A4 portrait
Step-by-step walkthrough
- 1Click the Tickets tile on the homepage. Pre-seeds the canvas to A6 / Postcard and primes the wizard with the tickets template hint.
- 2Drop your Eventbrite / box-office export CSV. Streaming parser shows the first 50 rows in <100 ms; full dataset finishes loading in the background while you map fields.
- 3Confirm the field mapping (auto-detect handles it). Order-ID columns become Text; ticket-URL columns auto-detect as QR; we suggest Code 128 fallback for short alphanumerics.
- 4(Optional) skip image library. Tickets rarely need per-row photos. The step auto-skips when no column resolves to image role.
- 5Verify A6 / Postcard is highlighted, click Open Editor. Wizard fills in a Cards step with 4-up A4 imposition + 3 mm bleed + crop marks. Counter and QR placements are pre-positioned on the lower-left third of the card.
- 6Drop your blank-PDF or designed template; export. Each row becomes one A6 page → 4-up arrangement on A4 sheets. 50 rows = 13 A4 sheets at 4-up.
What the output looks like
8 unique tickets (one per row). Each carries Ticket #0001…#0008 (counter) + a scannable QR linking to the unique check-in URL.
order_idattendee_nameemailsectionrowseatticket_urlPrepress pitfalls
- If your CSV's QR column is named confirmation_url or order_url instead of qr_url, the wizard still binds it — fuzzy matching covers 13+ synonyms.
- EC level M is fine for clean printers. Use H (~30% damage) if tickets are likely to be folded or stickered over.
- Sequential numbering uses the row index, not a CSV column — so an Eventbrite export's 'Order #' is decorative, not the counter source.
Pro tips from real print shops
- Add a composite field for `attendee_name + ' • Sec ' + section + ' Row ' + row` to print the seat assignment directly on the ticket.
- If you need duplex tickets (front = scannable, back = T&Cs), upload a 2-page source PDF — placements bind to sourcePageIndex 0 (front) by default; add a second batch on page 1 for the back.
- Print-shop reality: 4-up on SRA3 yields 8 tickets per sheet at zero bleed waste vs. A4's 4-up.