Easy Tickets & Events docs

Features

Ticket transfer and bundle claims

How customers self-serve transfer tickets to other people, and how bundle purchases (Table of 10, group buys) work with claim links.

Two related but distinct flows: transferring an existing ticket to a new person, and distributing a bundle of tickets you bought for a group.

Ticket transfer

For "I bought a ticket but can't attend - my friend will go instead":

  1. The original attendee opens the ticket page or the confirmation email.
  2. They click Transfer ticket.
  3. The transfer flow opens at /tickets/transfer/<token>.
  4. They fill in the new attendee's name, email, optionally phone.
  5. Submit.
  6. The ticket is reassigned: old QR invalidated, new QR issued.
  7. New attendee receives a fresh confirmation email.
  8. Old attendee receives a "ticket transferred" confirmation.

No merchant involvement needed.

Transfer settings

Per event, you can configure (under attendee fields):

  • Transfer enabled. On/off per event. Default on.
  • Editable fields after transfer. Which custom fields the new attendee can fill in versus inherit from the original.

If transfer is off (e.g. for VIP-only events with strict access lists), the transfer button doesn't appear and the URL returns a forbidden message.

Transfer history

Each attendee record tracks transfer history:

  • Original buyer name and email.
  • Each transfer's old and new attendee, timestamp.

Useful for fraud investigations and door staff questions ("but the email says someone else's name").

Bundles - the "Table of 10" pattern

For "buyer purchases 10 tickets, sends nine claim links to friends":

Setup

  1. Create a ticket type for the bundle.
  2. Toggle Is bundle on.
  3. Set Bundle size to the number of tickets (10).
  4. Set the price (one bundle purchase = price for all 10).

The bundle is a single SKU/variant in Shopify, but expands to 10 attendees on purchase.

Purchase flow

  1. Customer adds 1 bundle to cart, completes checkout.
  2. Easy Tickets creates 10 attendee records.
  3. One attendee (the buyer) is the primary - status Active, QR active.
  4. The other 9 are status Pending claim - QR inactive until claimed.
  5. The buyer receives:
    • Their primary ticket.
    • 9 unique claim links to forward.

Claim flow

For each of the 9 secondary attendees:

  1. The friend receives the claim link from the buyer (via email, text, whatever).
  2. They click the link, landing at /tickets/claim/<token>.
  3. They fill in their name, email, optionally custom fields.
  4. Submit.
  5. The attendee record flips from Pending claim to Active. QR is now valid.
  6. They receive their own confirmation email.

The buyer doesn't have to know all 9 friends' details. The friends self-serve.

Unclaimed bundles

If a claim link is never used:

  • The attendee stays in Pending claim status.
  • The QR never activates.
  • At the event, that "ticket" is effectively unused.
  • Inventory was already debited at purchase, so there's no oversell risk.

The buyer can re-share the claim link if they sent it to the wrong person - the link doesn't expire.

Combining transfer and bundles

A bundle's primary attendee can transfer their primary ticket like any other attendee. The bundle's claim links are issued at purchase and are not affected by transfers - they remain valid until claimed.

A claimed secondary attendee can also transfer their ticket after claiming.

Use cases

Transfer:

  • "I bought a workshop pass but got sick - giving it to my friend."
  • "I bought concert tickets but my partner is going with someone else - the second ticket needs to be in their name."

Bundle:

  • "Buy 10 tickets at a corporate discount, distribute to team members."
  • "Hen do / bachelor party - one organiser buys, sends claim links to the group."
  • "Family pack - one parent buys, sends claim links to kids/spouse."

Refund handling

When a bundle is refunded:

  • All 10 attendees (primary + secondaries) are cancelled.
  • Unclaimed slots are cancelled automatically.
  • Already-claimed secondaries receive a cancellation email.

If only the buyer wants a refund (without affecting the claimed friends), that's not currently supported in one click - refund the order, then re-issue tickets manually to the friends who'd already claimed. A future enhancement may make this smoother.

What's next