How to split a multi-pass ticket

Slice a multi-pass's remaining entries across multiple new tickets, each with their own recipient.

Last updated 25 April 2026

Split takes a multi-pass ticket's remaining entries and reallocates them across multiple new tickets. Useful when a buyer wants to share their class pack with a friend, or a team wants each member to have their own QR.

When the Split button appears

Split is only available when ALL of these are true:

  • The ticket is a multi-pass (e.g. 5-class pack)
  • Status: Issued (not consumed, refunded, or voided)
  • More than 1 remaining entry β€” if only 1 is left, use Reissue instead

Steps

  1. Owner Portal β†’ Ticket Hub β†’ open the multi-pass ticket
  2. Click Split
  3. Modal shows: N remaining entries to split
  4. Two recipient rows appear by default. For each row:
    • Attendee name
    • Email
    • Passes β€” how many entries this recipient gets
  5. + Add recipient to add more rows (up to 10)
  6. Γ— next to a row to remove it
  7. Watch the Allocated X / N counter β€” total must exactly equal the remaining entries
  8. Click Split into N tickets

Examples

Original Remaining Split as Result
5-pass, 2 used 3 2 + 1 Recipient A gets a 2-pass, Recipient B gets a 1-pass
10-pass, 4 used 6 2 + 2 + 2 Three recipients each get a 2-pass
5-pass, 0 used 5 1 + 1 + 1 + 1 + 1 Five single-use tickets

What happens

  • Original ticket β†’ voided
  • N new tickets minted, each with:
    • Fresh QR + short code
    • Its own attendee name + recipient email
    • The pass count you allocated
    • Same source (event / product), expiry, and host as the original
  • Each recipient receives their own ticket email
  • Every replacement links back to the original via reissuedFromTicketId

Rules enforced

  • Minimum 2 recipients (otherwise use Reissue)
  • Maximum 10 recipients
  • Each recipient gets at least 1 pass
  • Total allocated must exactly equal remaining β€” Split button stays disabled until balanced
  • Each email must be a valid format

Audit trail

  • Original history logs the split with all replacement codes listed
  • Each replacement has reissuedFromTicketId pointing to the original β€” chain is traceable via the Ticket Hub detail modal on either side

Related