Event tickets
How to create Apple Wallet event tickets in bulk
Turn one event design and an attendee CSV into personalized Apple Wallet tickets with mapped names, seats, ticket IDs, and barcodes.
What you’ll leave with
- Design and test one event-ticket template before multiplying it across the guest list.
- Give every attendee a stable ticket ID and unique barcode payload in the CSV source.
- Preview mapped rows and test the finished passes with the real admission scanner before distribution.
1. Design the master event ticket
Start with one event ticket that represents the whole run. Set the event name, venue, relevant date, artwork, colors, field hierarchy, and barcode format before importing attendee data. Shared values belong in the design; guest-specific values belong in the spreadsheet.
Install a test copy on iPhone and check the information visible at the door. Staff usually need the event, attendee or ticket holder, admission level, section or seat, and a scannable credential. Move policies, support details, and longer instructions to the back of the pass.
- Shared: event name, venue, date, doors time, artwork, and terms
- Personalized: attendee name, ticket ID, section, row, seat, and barcode
- Operational: entrance, ticket type, accessibility note, or admission group
2. Prepare a clean attendee CSV
Use one header row and one attendee per row. Keep column names short and unambiguous, export dates consistently, and make every ticket ID unique. If the barcode carries a credential, generate that value in the ticketing system rather than deriving it from a visible row number.
Remove merged cells, totals, blank header columns, and duplicate records before importing. A compact source file makes mapping easier to audit and prevents a formatting artifact from becoming hundreds of incorrect passes.
attendee_name,ticket_id,ticket_type,section,row,seat,barcode
Mina Patel,EVT-2026-0041,General Admission,Floor,,,EVT:2026:0041
Owen Brooks,EVT-2026-0042,Reserved,Orchestra,B,14,EVT:2026:00423. Map columns and preview real rows
In PassMaker, open the event ticket template or saved draft, import the CSV, and map each column to its destination field. Map the credential column to the barcode message and keep human-readable recovery text short enough for staff to enter manually when a scanner fails.
Preview rows from the beginning, middle, and end of the file. Include the longest attendee name, the most complex seat assignment, and any optional blank values. Fix the template or source data once, then preview again before generation.
- Confirm every required pass field receives a value.
- Check long names and labels for truncation.
- Verify the barcode and alt text belong to the same attendee.
- Confirm relevant dates and venue details use the right timezone.
4. Generate, test, and distribute the passes
Generate the batch, review the output names and count, then open several finished passes on a physical iPhone. Scan them with the same hardware and admission software used at the venue. Test duplicate scans, invalid IDs, offline behavior, and the staff lookup fallback before sending tickets to guests.
Distribute each pass only to its intended attendee through the event workflow you control. If details change after distribution, a static replacement file must reach the guest again; live remote updates require a Wallet web service and device registration infrastructure.
Put it into practice
Build the JSON, then verify the package.
Use the free browser tools to turn the rules in this guide into a clean starting file and an actionable validation report.
Skip the hand-assembly.
PassMaker does every step on this page on your iPhone — field editor, artwork, manifest, PKCS#7 signing and Add to Wallet — without wiring up a signing environment.
Download on the App StorePrimary references
Related guides
Getting started
How to create an Apple Wallet passA practical end-to-end guide to designing, packaging, signing, testing, and distributing a real Apple Wallet pass.
8 min readBarcodes
Apple Wallet barcode formats and compatibilityChoose between QR, PDF417, Aztec, and Code 128, set message encodings, and design barcodes that scan reliably from an iPhone display.
8 min readSemantics
Apple Wallet semantic tags for boarding passes and eventsUse structured semantic information while preserving compatible visible fields across Wallet versions and pass layouts.
9 min read