Transfer a ticket or move it to another date

When a guest cannot come, you can hand their ticket to someone else with a transfer link. On a recurring event you can also move the ticket to another date, or let customers change the date themselves.

Transfer a ticket to someone else

A transfer puts the ticket in a new person's name and gives it a new QR code. Only you can start one.

1. Open the event and go to "Attendees".
2. Open the ticket's menu (the pencil button) and click "Get transfer link". You see "Transfer link copied to clipboard!".
3. Send the link to the current holder or to the new person. The app does not send it for you.
4. The person opens the page "Transfer your ticket", which shows the ticket code, the current holder and the event date.
5. They fill in "New attendee first name", "New attendee last name" and "New attendee email", then click "Transfer ticket". On shops with several customer languages, they also pick "Language for the new attendee".

The page then says "Transfer complete" and the new holder gets the normal ticket email.

What changes and what stays

• The ticket gets the new name and email, a new QR code and a new ticket page link.
• The old QR code, PDF and ticket page stop working. The old link shows "This ticket link no longer works".
• The previous holder gets no email.
• Ticket code, type, date, seat, add-ons, refund protection and the Shopify order stay the same. No money moves and no ticket credit is used.
• The previous holder's phone number and answers stay on the ticket.
• The ticket's history records "Ticket transferred" and "Attendee details updated" with the old and new details. See Ticket history and staff notes.

Transfer limits

• "Get transfer link" shows on active tickets only. A ticket that is checked in, cancelled or refunded cannot be transferred: "This ticket can't be transferred (it's checked in or cancelled)."
• A link works once and has no expiry date. Clicking "Get transfer link" again makes a new link, and the earlier one stops working.
• Anyone holding the link can finish the transfer, and the page shows them the current holder's full name. Send it only to the right person.
• There is no on or off switch, no customer button and no bulk transfer.
• If you changed the event's QR code template so it no longer holds the check-in link, the QR code stays the same after a transfer.

Changing the name on the ticket page with "Update ticket details" is something else. The QR code and link stay the same, so an earlier copy of the ticket keeps working.

Move a ticket to another date

On a recurring event you can move a ticket to another date of the same event. The ticket keeps its QR code and link.

1. Open the series or one of its dates and go to "Attendees".
2. Open the ticket's menu and click "Move to another date".
3. Pick the "New date". Only today and later dates of the same event are listed, and cancelled dates are left out. Dates that cannot take the ticket are greyed out with the reason, such as "Sold out" or "No matching ticket type".
4. Leave "Send the ticket email again" ticked to email the guest the updated ticket.
5. Click "Move ticket".

You see "Ticket moved to" with the new date.

What a move does

• The ticket takes the ticket type with the same name on the new date, or the only type that date sells.
• The QR code and link stay. The ticket code stays too, unless the new date already uses it. Then you see "Ticket moved. Its new code is" with the new code.
• A check-in is undone, so the guest checks in again on the new date.
• A cancelled ticket becomes active again.
• Answers move to the questions with the same label on the new date.
• People on the old date's waitlist are emailed that a place opened.
• The "Ticket Moved" Flow trigger fires.

Capacity is checked, and a full date answers "That date is full." You can move a ticket as often as you like.

The Shopify order does not change. Its line item still shows the original date, and no price difference is charged or refunded. A move uses no ticket credit.

What cannot be moved

• Tickets on one-time events.
• Bundle tickets: "Tickets bought as a group can't be moved one by one yet."
• Refunded tickets, unclaimed bundle seats and class pack bookings.
• Seated tickets move only between seated dates, with a seat picked on the new date.

The app's block on the Shopify order page offers moves too: "Change date or time" for one ticket and "Move multiple tickets" for 2 to 20 tickets of one order. Those moves never send an email. Checked-in, bundle, seated and class-pack tickets cannot be moved there, and a bulk move moves every selected ticket or none.

Waiting for a date

Use this when a guest cannot make their date but does not know the new one yet. The place goes back on sale, while the ticket, its code and its order stay.

1. On the Attendees tab, open the ticket's menu and click "Keep ticket, remove from this date".
2. Read "Take this ticket off the date?" and click "Remove from this date".

You see "Ticket kept, waiting for a date", and the ticket gets the "Waiting for a date" badge. After that:

• any check-in is undone;
• the date's waitlist is emailed that a place opened;
• the guest gets no email;
• the ticket page shows "Waiting for a date" and "Date to be confirmed", with no QR code, PDF or calendar links;
• the door refuses the ticket with "This ticket is waiting for a new date".

Find these tickets with the "Waiting for a date" filter on the Attendees tab. The "Check-in" card on the event Dashboard counts them too.

To give the ticket a date, open its menu and click "Assign a date". The original date is offered as well. Putting a ticket back on its original date is not recorded as a move and fires no Flow trigger.

Keep "Send the ticket email again" ticked when you assign the date. The guest's ticket page says "The organizer will assign your new date and email you.", and that email goes out with the box ticked. If customer date changes are on, the page instead lets the guest pick the date.

This option exists on recurring events only, for active tickets. Bundle tickets, seated tickets and class pack bookings cannot wait for a date. A waiting ticket can be cancelled but not reactivated. Parking a ticket uses or returns no ticket credit.

Let customers change their own date

Customers can move their own ticket to another date of a series from their online ticket page. It is off by default.

1. Open the series and go to "Event settings" > "Tickets".
2. In "Customer date changes", turn on "Let customers change their date".
3. Pick when "Changes close". The choices run from "1 day before their date" to "3 weeks before their date", in steps of 1, 2 and 3 days and 1, 2 and 3 weeks. The default is "2 weeks before their date".

The setting sits on the series and covers all its dates. One-time events and a single date's settings do not have it.

The customer clicks "Change date" on their ticket page, picks a date in "Choose a new date" and clicks "Confirm change". Full dates show as "Sold out". The move works like yours: the QR code stays, capacity is checked and the old date's waitlist is told. When the ticket has an email, the updated ticket email goes out.

You get no email and there is no approval step. The ticket's history marks the change "Customer self-service", and the "Ticket Moved" trigger fires.

Customer date change limits

• A customer can move each ticket 3 times. After that the page says "This ticket has reached its date-change limit. Contact us to change your ticket." Your own moves do not count.
• The cutoff counts back from the start of the date the ticket is on now. After it the page says "Date changes are closed for this event. Contact us to change your ticket."
• A ticket waiting for a date skips the cutoff and can also pick its original date.
• Tickets that are checked in, cancelled, refunded or unclaimed get no "Change date" button. Neither do bundle tickets, or tickets on a series with no other future date.
• If you replaced the ticket page with your own HTML ("Edit code"), the "Change date" section does not show.

The Ticket Moved trigger in Shopify Flow

"Ticket Moved" fires whenever a ticket lands on a different date. That covers your moves, "Assign a date" to a new date, a customer's own change and moves from the Shopify order page.

It carries "Customer email", "Customer name", "Ticket code", "Event name", "Previous date", "New date", "Order name", "Event id", "Ticket number" and "Language". Use it to tag the order or tell your team. It does not fire for transfers, or when a waiting ticket goes back to its own date. The other triggers are listed in Shopify Flow triggers.

Bundles and table tickets

A bundle, such as a table of 10, gives each guest a claim link to put a seat in their own name. Claim links, group tickets and the group guest list are covered in Group tickets, tables and claim links. A bundle ticket can be transferred with a transfer link, but it cannot be moved or put on "Waiting for a date".