Attendee management

Attendee management is where Easy Tickets shines for repeat-use customers - the event is the easy part, the attendees are the work.

Data capture modes

Per event, choose how attendee data is collected:

• From order. Pull the attendee from the Shopify order's contact (name, email). Used when one buyer = one ticket and you don't need extra details.
• On add-to-cart. The storefront popup collects details before checkout. Captures one entry per ticket in the cart, or one entry total, depending on event settings.
• Customer choice. Buyer picks at checkout which mode they want.

Most events use "On add-to-cart" because the storefront popup is the natural moment to grab details.

Standard fields

Every attendee has:

• First name.
• Last name.
• Email.
• Phone (optional - togglable per event).

These are the always-present fields; the popup collects them by default.

Custom fields

For event-specific data (meal choice, T-shirt size, dietary restrictions, accessibility needs, emergency contact):

1. Open the event settings.
2. Go to Attendee info.
3. Click Add field.

Each custom field has:

• Label - what the attendee sees ("Meal preference").
• Type - text, select (dropdown), checkbox, date.
• Required - must answer to complete checkout.
• Editable after purchase - can the attendee change their answer later via the ticket page.
• Sort order - drag-and-drop to reorder fields in the popup.

Custom fields are per-event. You can have unlimited fields. They appear in the storefront popup in your specified order.

Attendee list dashboard

From the event detail page, click Attendees (or Tickets - same thing). You'll see:

• One row per attendee.
• Search and filter (by name, email, status, custom field values).
• Sort options.
• Status badge per attendee (Active, Cancelled, Pending claim).
• Custom field values displayed inline.

Bulk actions across the selection:

• Manual check-in.
• Transfer.
• Refund / cancel.
• Resend confirmation email.

Per-attendee actions

Click into an attendee to see their full detail:

• All standard + custom field values.
• Ticket code, QR code data, public ticket URL.
• Transfer token (used by the transfer link).
• Check-in status and history.
• Edit custom field values (if allowed by event settings).
• Resend confirmation email.
• Cancel or refund (refund flows through Shopify, cancel just marks in Easy Tickets).

Statuses

• Active. Ticket bought, not cancelled.
• Cancelled. Refunded or manually cancelled. Doesn't show up at check-in.
• Pending claim. For bundle recipients - they haven't claimed yet, so no QR code is active.

Transfer

Attendees can transfer their ticket to another person without merchant involvement. The mechanism:

1. The confirmation email includes a transfer link with a unique token.
2. The original attendee visits the link.
3. They fill in the new attendee's details (name, email, optionally custom fields).
4. Easy Tickets reassigns the ticket and emails the new attendee a fresh confirmation.
5. The old QR/ticket page is invalidated; the new one is now valid.

Transfers are tracked - the attendee record shows original buyer plus the transfer history.

See Ticket transfer and bundle claims.

Refunds

When you refund an order in Shopify admin:

• A webhook fires to Easy Tickets.
• Easy Tickets marks the corresponding attendees as Cancelled.
• The QR codes and ticket pages become invalid.

If you only want to cancel an attendee without refunding through Shopify (rare - usually you do both):

• Open the attendee in Easy Tickets.
• Click Cancel attendee.
• The ticket invalidates. The order stays paid in Shopify (you'd refund manually if needed).

Resending emails

If an attendee says they didn't get their confirmation:

• Open the attendee.
• Click Resend confirmation email.
• The email queues immediately.

For mass resends (e.g. after a deliverability issue), select multiple attendees and use the bulk Resend action.

Editing attendee info

Customers may need to fix typos in their email or change a meal choice. Two paths:

• Customer-side. If the field's "editable after purchase" toggle is on, the ticket page exposes an edit form.
• Merchant-side. Open the attendee in admin, edit any field, save.

Email changes trigger a new confirmation send.

Multi-attendee orders

When one customer buys 4 tickets, you get 4 attendee records, one per ticket. The popup collects 4 sets of details (one per ticket in cart) - or just one set if the event is in "from order" mode.

For "from order" mode, the 4 attendees share the buyer's name and email by default, and you'd handle name collection at the door if needed.

For "on add-to-cart" mode, each attendee has unique details from the start.

What's next

• Ticket transfer and bundle claims - self-service transfer in detail.
• Web check-in PWA - using attendee data at the door.
• Storefront popup - the data capture UI.