Refund Shouldn't Be Plan A
When one of our partners had to cancel an 80-ticket event, we helped them transfer customers instead of refunding them. Only 4 out of 80 needed a refund. Here's what happened.
One of our partners called us on a Tuesday. They'd sold 80 tickets to a Saturday dinner — $150 each — and the event had to be cancelled. They needed help processing refunds for all 80 orders.
We said: let's not do that yet.
The call
The partner's instinct was understandable. Event cancelled, 80 people expecting dinner, the right thing to do is give everyone their money back. They'd already started drafting the apology email.
But we asked a question before they hit send: what else do you have coming up? Turns out, quite a bit. The following Saturday had about 30 seats left. A new date two weeks out was wide open. And they ran a completely different event — a wine tasting series — that some of these customers might actually prefer.
So instead of an apology-and-refund email, they reached out to each customer with options: move to next Saturday, move to April 12th, switch to the wine tasting, or get a full refund. Most people replied within hours.
Then we got to work on our end.
What we actually did
This wasn't a simple "move everyone to the same date." Each customer picked something different, and we handled each order accordingly.
Some transferred to the following Saturday. Some moved to the April date. A few switched to the wine tasting series entirely — different event, different ticket type, different price point. Cohost handled all of it the same way: open the order, pick the target event, map the ticket types, execute. The attendees moved automatically — removed from the cancelled event, created on the new one with the right assignments. The original orders stayed intact. No cancellations, no new purchases, no re-charging anyone's card.
The whole thing took about twenty minutes across all 80 orders, even though we were scattering people across three different events.
Out of 80 customers, 76 landed somewhere they were happy with. Some replied to say thanks. Most didn't reply at all — which, in customer service, is the best possible outcome. It means there was nothing to complain about.
Four people couldn't make any of the alternatives. We refunded those four. Clean, fast, no friction.
Four refunds instead of eighty. That's the difference.
The money
Let's talk about what would have happened if we'd processed all 80 refunds.
$12,000 in ticket revenue — gone. But that's just the headline number.
Payment processing fees aren't refundable. Stripe, Square, whatever processor you use — they charge on the original transaction (typically 2.9% + $0.30) and keep it when you refund. On 80 tickets at $150, that's roughly $370 in fees paid for transactions that no longer exist.
Platform fees make it worse. If you're selling through a platform like Eventbrite, fees are even steeper. Eventbrite charges 3.7% + $1.79 per ticket plus 2.9% processing per order. On a $150 ticket, that's about $9.84 — roughly 6.6% of the ticket price. And when an event is cancelled, Eventbrite requires a full refund including all fees. The organizer absorbs the entire cost.
On 80 tickets at Eventbrite rates, that's roughly $787 in platform and processing fees that vanish on refund. And here's the kicker: when you resell those same 80 seats for the rescheduled date, you pay the full fees again. You've now paid platform fees twice for the same customer attending the same event.
Our partner paid zero in lost fees. Because the orders were transferred, not refunded, the original transactions stayed intact. No fees lost. No fees re-paid. The only refund costs were on those four orders that genuinely needed it.
The customer experience
Here's the part we didn't expect to matter as much as it did.
When we transferred the orders, Cohost issued new e-tickets automatically. Every customer got an email with their corrected ticket — the right date, the right event, the right details, updated QR code. Whether they'd moved to next Saturday's dinner or switched to the wine tasting entirely, each person got exactly the right ticket for where they'd landed. Open the email, see the new event, done.
But we also knew that not everyone reads their email carefully. Some people would show up with their original ticket — the one for the cancelled Saturday — saved in their phone or printed out at home. They might not have noticed the new email, or they might have just grabbed the first ticket they found.
So the scanner at the door honored both tickets. The old barcode still worked. No one got turned away because they showed the wrong QR code. No friction at check-in, no confused door staff explaining that "you need the new one."
This is the kind of detail that separates a resolution from a good resolution. The transfer handled the logistics. The backwards-compatible scan handled the human reality that people don't always update their saved tickets.
What it cost to not refund
Let's put numbers on it. Our partner kept 76 orders intact at $150 each. That's $11,400 in retained revenue. The processing fees on those 76 orders — already paid — stayed attached to real revenue instead of becoming a loss. No marketing spend to resell those seats. No second round of platform fees.
The four refunds cost roughly $18.50 in processing fees. Compare that to the $370+ they would have lost refunding all 80.
But the number that matters most isn't on a spreadsheet. It's 76 customers who had a seamless experience — no refund to process on their end, no re-purchase, no re-entering payment details. They got an email, they got a new ticket, and they showed up. Some of them probably don't even know the event was cancelled and rescheduled. They just went to dinner.
Why this matters beyond one event
This wasn't a special case. Events get cancelled. Dates shift. Venues fall through. Artists get sick. Weather happens. Every organizer faces this eventually — most face it several times a year.
The question is what tools you have when it happens. If your platform's only answer is "refund," then every disruption follows the same expensive path: cancel, refund, eat the fees, remarket, resell, pay fees again, hope people come back. That's Plan A, B, and C.
If you can transfer orders between events, the calculus changes completely. The first question stops being "how do we process these refunds?" and becomes "where can we move these people?" Refund is still there for the customers who need it. But it's Plan B, not Plan A.
Our partner ran the numbers after this incident. Over a year of events, they estimated they'd face three or four situations like this — cancellations, major date changes, venue swaps. At 50-80 affected orders each time, the difference between refund-everything and transfer-first was roughly $30,000-$40,000 in retained revenue annually. And that's a conservative estimate that doesn't account for the customers they would have lost permanently to the rebooking friction.
The upgrade play
While we were working through the transfers, something else happened that's worth mentioning.
A handful of customers — maybe six or seven — replied to the rescheduling email with some version of "actually, I was already on the fence about this." Not angry, not demanding a refund, just... lukewarm.
Our partner called a few of them and offered an upgrade. "How about we put you at a better table for the new date?" Two of them took it immediately. One asked for VIP seating and got it. The other three ended up keeping their original tickets after the conversation.
Zero refunds from that group. The upgrade cost our partner almost nothing — the better tables weren't sold — but it turned six potential refund requests into six retained customers, three of whom now had a better experience than what they'd originally bought.
This is the other side of having options. When your only tool is a refund, every hesitant customer becomes a lost sale. When you can upgrade a ticket type on the spot, every hesitant customer becomes a conversation.
What we learned
We've helped enough partners through situations like this to notice a pattern. The organizers who refund by default lose more than revenue. They lose momentum, they lose the relationship, and they lose the compounding value of a customer who was already committed.
The organizers who reach for a transfer first — who pick up the phone, offer an alternative, and make the move easy — keep nearly everything. The revenue, the fees, the customer, and the goodwill.
The refund button should be the last thing you reach for. Not because refunds are wrong — sometimes they're exactly right — but because there's almost always a better first move.
Handle it better with Cohost
Cohost's Advanced Order Management gives you transfers, ticket upgrades, voids, and full or partial refunds — all from one dashboard with a complete audit trail. Your old tickets still scan. Your new tickets go out automatically. Stop treating every problem like a refund.