Online ticket pages

The online ticket page lives at /tickets/<token> and is the canonical "show this at the door" view. Every attendee gets a unique URL.

What customers see

A clean page with:

• The event name, date, time.
• The venue (with a Google Maps link if address-based).
• The attendee's name and ticket type.
• The QR code, scannable at check-in.
• A Download PDF button.
• An Add to Calendar link (iCal export).
• A check-in status badge (live-updates after a scan).
• Any add-ons selected (e.g. T-shirt size, meal choice).
• A refund-protection badge if the attendee opted in.

How customers reach it

Most commonly:

• From the confirmation email - the email links to the ticket page.
• From the order thank-you page in Shopify, via the Thank You Tickets block.
• From a saved bookmark or the link forwarded to a phone.

URL format

https://<your-shop>/tickets/<unique-token>

The token is a long, unguessable string. So even though the URL is public, it's effectively unlisted - only people with the link can view the ticket.

Customisation

Same editor system as emails and PDFs:

• Visual editor with block-level toggles.
• Custom blocks (rich text, image, two-column).
• Raw HTML code editor with template variables.

You can change:

• Logo, colours, fonts.
• Which blocks appear (QR, event info, attendee details, calendar export, add-ons, refund protection).
• Header and footer copy.
• Per-block field selection (e.g. show date but not start time).

See Emails and PDF tickets for the editor reference.

Calendar export

The "Add to Calendar" button generates an iCal file with:

• Event name as the calendar title.
• Start/end time.
• Location (address or "Online" with the meeting link).
• Description (your event description).
• A reminder set for an hour before (configurable per event).

Works with Apple Calendar, Google Calendar, Outlook, anything that accepts iCal.

Check-in status display

When a staff member scans the QR or marks the attendee manually, the ticket page picks up the change in real-time (or on next refresh):

• A "Checked in" badge appears.
• The check-in count shows for multi-entry tickets.
• The time of check-in is displayed.

Useful for customers who want to confirm their entry was recorded.

Custom data display

Custom attendee fields can be configured to show on the ticket page:

• Meal preference.
• Seat number.
• Workshop session selected.
• Any per-attendee data the customer or staff might need to see.

Per-field, choose whether it's visible on the ticket page in the event's attendee field settings.

Editing attendee info from the ticket page

If the event allows post-purchase edits ("editable after purchase" flag on the field), customers can update their custom field values directly on the ticket page. Useful when:

• They typoed their meal preference at checkout.
• The original buyer wasn't sure of details and now is.

Email changes trigger a fresh confirmation send.

Transfer button

If the ticket is transferable, the ticket page exposes a Transfer ticket button that opens the transfer flow at /tickets/transfer/<token>. See Ticket transfer and bundle claims.

Mobile-first design

The page is built to look correct on phone screens first. QR codes are sized for screen-display reading by another phone's camera. Customers showing tickets at the door typically pull up the page on their phone.

The PDF is the backup for when the customer prefers paper or has a phone-dead emergency.

What's next

• Emails and PDF tickets - the editor system.
• Ticket transfer and bundle claims - the related transfer flow.
• Web check-in PWA - what the staff side does with the QR.