Skip to content
PassMaker

Event tickets

Send Event Tickets to Apple Wallet in Bulk (CSV)

Send event tickets to Apple Wallet: design one ticket, import your guest CSV, map names, seats and barcodes, then share a pass to each attendee.

By Swapnanil Dhol8 min read

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:0042

3. 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.

5. Check guests in at the door

PassMaker creates the tickets; it does not include a door scanner. Use the check-in tool you already have, or any barcode scanner app that reads your format, and match each scanned ticket ID against the same CSV you imported. A shared spreadsheet with a checked-in column works for small events.

Mark each ID as used when the guest enters, so a forwarded or screenshotted copy is caught on the second scan. Keep a printed or offline copy of the guest list in case the venue has no signal.

  • Under about 200 guests: a scanner app plus a shared spreadsheet
  • Larger events: a check-in app that imports your CSV and flags duplicate scans
  • Ticket sales, live updates or remote revocation: a hosted Wallet platform such as PassKit or Passcreator

Frequently asked questions

How do I send event tickets to Apple Wallet?
Build the ticket and import your attendee CSV in PassMaker, generate a personalized pass for each row, then share each .pkpass file with its attendee. They open it on an iPhone and tap Add to Wallet.
Can I create Apple Wallet tickets from a spreadsheet?
Yes. Export the sheet as a UTF-8 CSV with one attendee per row, map its columns to ticket fields and the barcode, and preview rows before generating. PassMaker also accepts JSON.
Do free accounts support bulk generation?
Free accounts include two passes per day, so a full guest list needs Pro for higher volume.
Will tickets update if the event details change?
Static passes do not update remotely. If the venue or time changes, send attendees a replacement pass file.
How do I scan Apple Wallet tickets at the door?
Use your check-in app or any scanner app that reads your barcode format, and match each ticket ID against the CSV you imported. Mark IDs as used so duplicate scans are caught. PassMaker makes the tickets but does not include a door scanner.

Try it

Make your pass in PassMaker.

PassMaker is free to download and runs on iPhone with iOS 17 or later. Free accounts include two passes per day.

Primary references