How to handle refunds when an event add-on becomes unavailable

Your event is still going ahead. The meal package isn't. Now you've got buyers who paid for both, a caterer who can't deliver, and a support team asking whether to refund the whole order.

Start by checking exactly what each buyer purchased and how the missing extra affects their ability to attend. Where admission still delivers the promised event and the extra can reasonably be separated, resolve the extra without cancelling valid tickets. Where the loss changes the substance of the purchase, review the wider remedy before deciding that a partial refund is enough.

That distinction matters more than what you called the item at checkout. A souvenir shirt and the only transport to a remote venue are both possible add-ons. Losing them creates very different problems. Your response needs to follow the actual promise, the buyer's circumstances and the rules applying to the sale.

This guide works through the incident itself. We'll cover stopping new sales, identifying affected purchases, pricing the refund, offering replacements and keeping admission and payment records accurate. The dollar examples are fictional USD calculations, not typical prices or legal refund formulas. Use them to test your own process before anyone starts clicking refund.

Find out what has actually failed

The first thing you want to do is get a clear answer from whoever was delivering the extra. "There's a problem with lunch" isn't enough to make a decision. Are all meals unavailable, one dietary option missing, or deliveries running late? Can the supplier still deliver before the advertised break? Has anything already been provided?

Ask for written confirmation of the affected product, date, quantity and delivery commitment. Record when you learned about the failure. You need enough certainty to stop making an offer you can't fulfil, while avoiding an announcement that cancels more than necessary.

Suppose a supplier can provide standard lunches but cannot provide the advertised allergy accommodation. Don't mark the whole meal service as available and expect the affected buyer to improvise. Work out whether an appropriate alternative can actually be delivered, with the necessary specialist checks. Someone's dietary requirement doesn't become less important because most orders are unaffected.

Stop new sales of the failed extra through every route you control. Check the event page, upgrade links, partner offers and event-day sales instructions. Preserve the original description and terms for existing buyers before you replace them. The updated page tells future customers what is available; the saved version helps you understand what earlier customers bought.

Give one person authority to coordinate the incident. That person can bring together supplier confirmation, customer decisions and finance without personally doing every task. Otherwise, production may announce a replacement while support is promising refunds and the sales page continues offering the original item.

Your first internal note should say what failed, who is affected so far, what sales have stopped and when the team will decide the next action. If the facts are incomplete, name the uncertainty. "We are confirming whether the evening collection is affected" gives staff a useful limit. "Please reassure everyone" doesn't.

Keep a record of late purchases too. An order placed while the website was being corrected still needs resolving. Check the final affected list against the actual time sales stopped, rather than assuming that everyone who paid after the supplier's phone call saw the warning.

Decide whether the extra can be separated from admission

Look at the event as the buyer understood it. Could they still receive the advertised main experience without the extra? Was the extra genuinely optional? Does removing it create an access problem, a substantial change or a purchase the buyer would reasonably see very differently?

A missing collectible poster will often be easier to separate from concert admission than a cancelled artist meeting sold as the main attraction of a premium package. You still need to resolve the poster, but the concert itself may remain unchanged. With the premium package, the wording of the offer and the importance of the missing element deserve closer review.

Transport is another useful test. If a remote event sold a coach from the nearest station, refunding the coach price may leave buyers unable to reach the venue. Check practical alternatives and any wider obligations before saying their admission is unaffected. A ticket can remain technically valid while the journey needed to use it has disappeared.

The Australian Competition and Consumer Commission explains that remedies depend on the kind of purchase and the seriousness of the failure. Its guidance on repair, replacement, refunds and service cancellation also addresses material changes to services. That is Australian guidance, rather than a rule you can automatically apply to every country or every event contract.

Use that distinction to identify cases requiring legal review in your market. Don't turn it into a private test that overrides the buyer's rights. An event continuing on its original date does not settle every refund question. Equally, one unavailable optional item doesn't automatically mean every unaffected purchase must be cancelled.

Ask support to flag the specific consequence. "Buyer cannot attend without the cancelled coach" is useful evidence. "Buyer unhappy with extra" hides the reason the case may need a different response. Staff should escalate the consequence, alongside the original sales description, to someone who can decide the remedy.

For the ordinary case where the extra is separable, make the decision explicit. The extra is cancelled, the proposed repayment covers that extra, and the admission remains valid. Our wider event refund policy guide helps with the underlying policy. This incident needs a decision about the particular missing promise.

Identify every affected purchase

Don't make a buyer explain a failure your own order records already show. Start with completed purchases of the affected item and match each to its order and payment. Then use replies to resolve exceptions, rather than treating whoever emails first as the complete list.

Count units, buyers and orders separately. One person may buy lunches for several colleagues. Two people may attend on one order. Someone may purchase admission first and an extra later. A refund list based only on unique email addresses can miss quantities or attach the repayment to the wrong transaction.

For each affected purchase, record the order reference, item, quantity, amount paid after discounts, payment reference, any previous repayment and the proposed action. Keep admission identifiers separate from the extra's collection or access identifier. Those distinctions will matter when you update fulfilment and entry.

Check whether some units have already been delivered. If shirts were collected on the first day but the remaining sizes never arrived, a list of every shirt sold is too broad. Compare paid units with actual handover records. Investigate unclear collections before deciding that a scan or a staff recollection proves delivery.

Be careful with third-party purchases. A sponsor may have bought a block of meals, or a company may have paid for staff. Establish who paid and who needs the practical update. The attendee may need to know there is no lunch service, while the purchaser receives the payment confirmation. Don't promise the attendee a personal refund from a company-paid order.

Use the existing ticketing or order system as the main record where it supports the work. Add an incident register only for decisions or follow-up that the system doesn't hold. You don't want staff maintaining an entire second order database that drifts out of date during the event.

Limit access to personal information. The UK's Information Commissioner's Office describes data minimisation under UK GDPR as keeping information adequate, relevant and limited to the purpose. That guidance is under review. For this task, a payment reference and action record are usually more useful than a forwarded inbox full of unrelated personal details.

Check the list against total units sold before approving payments. If sales show more affected units than your incident list, find the missing orders. If your list shows more, investigate duplicate entries, already resolved cases and purchases that were never completed.

Calculate the refund from what the buyer paid

For a separately priced extra that you cannot deliver and have decided to refund in full, start with the actual amount paid for that extra. Your supplier's cost is a different number. Keeping the difference because the supplier won't reimburse you transfers your delivery problem to the buyer.

Take a fictional order with two admission tickets at $60 each and two lunch packages at $25 each. The buyer paid $170, with no additional tax or fees in this simplified example. If both lunches are cancelled and refunded in full, $50 returns to the buyer and $120 remains paid for valid admission.

Check that the proposed payment action does exactly that. A button labelled "refund order" may do more than you intend. A payment-only partial refund may return money without changing any ticket or lunch entitlement. Confirm the relationship between the financial action and the items before applying it to real customers.

Now suppose this buyer already received a $10 refund relating to the same lunches. A further $50 would overpay the agreed $50 lunch repayment. Verify why the earlier refund happened, then calculate the amount still due. If the $10 related to a separate admission correction, it should not quietly reduce the lunch remedy instead.

Discounts make the calculation less obvious. Imagine the same order used a disclosed 10% discount across all items. Admission becomes $108 and lunches become $45, for a $153 total. Refunding the fully cancelled lunches returns $45 under that recorded allocation, leaving $108 for admission. The buyer didn't pay the undiscounted $50 lunch total.

That example is arithmetic, not permission to choose whichever allocation produces the smallest refund. Follow the actual sale, the agreed terms and the applicable rights. If the checkout did not allocate a package discount, record a defensible method and have the decision reviewed before processing a batch.

For mixed quantities, work at item level. If only one of the two lunches failed, identify which entitlement is cancelled and calculate that unit's repayment. Don't halve the entire order. Both admission tickets and the unaffected lunch may still need to work exactly as sold.

Keep tax and fee handling outside the simplified example until you have checked them. If your real receipt includes tax, payment charges or delivery, reconcile the full customer total with finance. The confirmation should show the actual amount returning, rather than making the buyer reconstruct it from a percentage.

Resolve bundles and fees before you process a batch

A bundle can be easy to buy and awkward to unwind. The ticket and the extra may have been sold at one price, with a discount that never appeared against individual items. You need to establish the value of the missing part without inventing a less generous deal after purchase.

Suppose you advertised a $72 admission-and-shirt bundle alongside separate prices of $50 for admission and $28 for the shirt. Your internal planning might have treated the shirt as the remaining $22. That planning assumption doesn't automatically establish the buyer's remedy when the shirt is unavailable.

If the sales terms clearly and lawfully allocated $50 to admission and $22 to the shirt, you have a starting point to review. If they didn't, don't announce "$22 is all we owe" because it preserves the ticket price you wanted. Consider the offer, applicable consumer rights and the package's remaining value. Escalate uncertainty before sending amounts to every buyer.

Our guide to pricing event merchandise and ticket add-ons explains the original pricing decision. Here, the useful lesson is to preserve the allocation and wording buyers actually saw. A finance model can help explain the sale, but it cannot retroactively rewrite it.

Check compulsory charges and optional charges separately. Was there a shipping payment solely for the missing shirt? Was there an order charge that also covered valid admission? Was a charge attached specifically to the extra? Those details help finance identify the amount to review. They don't, by themselves, decide what the law permits you to retain.

For covered US live-event ticket sales, the Federal Trade Commission's fee rule questions and answers address total-price disclosures and misleading statements about fees, including refundability. The guidance doesn't provide a universal formula for allocating a failed add-on. Use it to check that your descriptions are accurate, then establish the remedy for the transaction.

A processor retaining an original fee is a cost to your business. It doesn't automatically mean you can deduct that fee from a refund owed to the customer. Make the commercial cost and the customer entitlement separate decisions, with the applicable terms and law checked.

Approve a worked example for each real pricing pattern before processing multiple orders. Full-price extras, discounted extras and bundles may require different calculations. Once the rule is settled, give staff the approved method and a route for orders that don't fit. Avoid asking each support person to make their own interpretation.

When only some extras can still be delivered

A partial shortfall creates another decision before the refund calculation. Who gets the remaining supply? If you sold more than you can now deliver, avoid letting the loudest email or earliest arrival quietly determine the outcome. Check the promise and any allocation rule buyers accepted, then approve a fair, explainable response.

Imagine a fictional event sold 40 lunch packages and the supplier can now deliver only 30. Those are 40 individual meals, possibly spread across fewer than 40 orders. First verify which meals remain available and whether they meet the actual orders. Thirty standard meals do not necessarily cover a list containing different dietary needs.

If the missing ten meals can be identified against specific purchases, contact those purchasers with the appropriate remedy. If the shortfall has no natural allocation, establish the approach before communicating. You might invite volunteers to take a suitable replacement or refund, provided that choice is real and doesn't limit anyone's rights. Have a reviewed plan for any remaining shortage.

Don't announce that ten people will receive refunds while leaving everyone uncertain about whether they are among them. Give each affected buyer a definite outcome as soon as it is confirmed. If you need replies to allocate replacements, explain that stage and when individual confirmation will follow.

Preserve group arrangements where they mattered to the purchase. A family ordering meals together may not find one replacement collected elsewhere useful. A company buying a shared session may need the group kept together. Ask what the proposed split would change before treating every unit as interchangeable.

Also check who actually sold the extra. An independent food vendor may have taken a separate payment under its own terms, while your event sold admission. In another setup, you collected both payments and contracted the caterer yourself. Those arrangements need different handling. Establish the contracting parties from the checkout and receipt, rather than sending customers to the supplier because you would prefer them to resolve it.

Where another seller owns the payment, help the buyer reach the right route and explain what your event team is doing about the practical disruption. Don't promise that you have refunded a payment you cannot access. Where your business sold the extra, don't describe your subcontractor as the buyer's seller without a basis in the actual agreement.

Tell every delivery point the final allocation. Remaining stock at a merchandise stand or meal desk should match the people still entitled to collect it. Keep replacement acceptances and refunds in the same incident record so a buyer doesn't accidentally keep both a refunded entitlement and a confirmed replacement.

After the decisions, count again. In the simple 40-meal example, 30 meals delivered and ten fully refunded would explain all 40 paid units, if no other remedy or replacement applies. Where the numbers differ, find the unresolved purchases before the service opens. A total that balances only because staff guessed who received what is not a completed reconciliation.

Offer a replacement people can actually use

A replacement can be the best outcome when it provides the promised benefit in time and the buyer accepts it where required. It can also become another failure if the team agrees to something that looks similar on a supplier quote but doesn't work for attendees.

Consider a cancelled sit-down meal. A food voucher may seem equivalent in dollars, yet require a long queue during the only short break. A replacement shirt may cost the same but have a different design or arrive after the event. A coach leaving from another city is not the same journey because its seat costs the same amount.

Start with the buyer's use. What were they paying to do, when did they need it, and what restrictions mattered? Then compare the replacement against those conditions. Confirm actual supply before offering it. "We should be able to source something" is an investigation update, not an offer ready for acceptance.

Explain changes plainly. Name the replacement, timing, location, any price adjustment and the action the buyer needs to take. Where a refund is available, make that choice easy to understand. Don't hide it behind a long description of why the replacement is better for your budget.

If the alternative costs less, decide the difference before announcing it. If it costs more, decide whether you will absorb that cost or offer an optional paid choice. Don't impose a new charge on someone simply to receive the remedy already owed. Any new purchase should be a deliberate agreement.

Use credits with the same care. A credit for a future event has restrictions and depends on another purchase or visit. It isn't interchangeable with money returned to the original payment method. Offer it voluntarily where appropriate, describe expiry and redemption conditions, and don't use it to avoid a refund the buyer is entitled to receive.

Give an honest response deadline when operations require one. A caterer may need replacement numbers before a real cutoff. Explain what happens if the buyer doesn't respond, using a reviewed default that respects their rights. Silence shouldn't become manufactured acceptance of a materially different service.

Keep the decision alongside the order. A short record of the offer, buyer's acceptance and final fulfilment instruction prevents staff offering the original refund again after the replacement has been provided. It also helps the event team know what to deliver when the buyer arrives.

Tell buyers what changes and what still works

The buyer's first practical question may be whether they can still come. Answer it explicitly for the case you have reviewed. Then explain the unavailable item, the remedy, the amount and the next update. A vague subject line such as "Important information" makes them search for the actual problem.

For the fictional $170 order, a suitable message after approval but before submission might read: "Your two admission tickets remain valid. We can't provide the two lunch packages in order A104. We've approved a $50 refund for those lunches and will send confirmation when it has been submitted to the original payment method. You don't need to cancel your admission."

That wording describes the real stage. Once submitted, change the message to say it has been submitted, with the verified provider timeframe and reference where available. Don't say the money is already back in the buyer's account because someone clicked a control. Payment processing and a customer's bank statement are different evidence.

Tell people what to do on the day. Should they ignore the old meal voucher? Will a replacement have a different collection location? Does their original admission QR remain the one to use? Give the correct instruction for the actual system, rather than assuming that every partial refund preserves or replaces tickets in the same way.

Check who receives the notice. The purchaser needs the payment information; the people attending need delivery instructions. Where you can only contact the purchaser, ask them to share the relevant practical update with their group. Keep personal financial details out of a message meant for everyone holding a ticket.

Refund terms affect buying confidence more broadly. In Loopyah's 2025-2026 US event attendee report, 33.8% of 500 respondents selected better refund policies as something that would motivate earlier buying. The survey was fielded through Pollfish on November 11, 2025, and allowed multiple selections. It didn't test add-on failures or prove that a particular refund response increases sales.

Source: Loopyah Event Attendee Insights Report, Q9, Pollfish survey of 500 US respondents, November 11, 2025. These are three selected options from a multiple-choice question, using unweighted respondent shares. They are not a complete ranking and should not be added together.

The reason to explain the incident well is already clear without promising a sales result. People have paid for something you cannot provide. They need an accurate answer that lets them plan their visit and understand what will happen to their money.

Process the payment without cancelling the wrong thing

Before the first refund, confirm what your platform supports for the actual purchase. Can staff refund a selected extra? Can they enter a partial payment amount? Does either action invalidate tickets, remove the extra, change stock or send an automatic email? Ask for a demonstration or check the supported instructions when that relationship is unclear.

A payment provider can support partial refunds without your ticketing platform exposing an item-level refund control. Those are different capabilities. Don't promise that your current event setup can do something because the underlying payment service documents an API for it.

Loopyah's ticket-selling tools include a buyer refund window for a set time after purchase. That voluntary window doesn't decide the remedy for an unavailable extra. Confirm the supported order-level action with the provider before processing a partial remedy or describing how it changes admission.

For a payment-system example, Stripe's documentation on refunding payments describes partial refunds and the handling of pending and failed refunds. It also explains that refund funding depends on available balance. Those are Stripe-specific details; check the equivalent process and funding requirements for the payment route used by your event.

Prepare the approved list, then have someone check the first real case against the order and the intended result. After processing, inspect the payment record, admission status, extra entitlement and customer message. Only continue with similar cases once that outcome matches the decision.

Use a clear marker for a case being processed so another staff member doesn't act at the same time. Before retrying a request after a slow screen or error message, check whether the first action succeeded. Returning to the dashboard and clicking again can create a duplicate repayment where the system permits multiple partial refunds.

Keep individual amounts within the approved remedy and the payment's remaining refundable balance. A customer may already have received money for another reason. Match that history carefully, and don't use an over-broad bulk action to force a collection of different partial refunds into one convenient operation.

A refund isn't finished because the request was submitted. Assign someone to review pending and failed outcomes and update the buyer. Where a refund fails, follow the provider's supported recovery process, verify the original status before another payment route, and record the eventual resolution against the same case.

Update collection records and brief the door team

The finance action and the delivery action need to agree. A refunded lunch still shown as collectable can be handed over accidentally. A cancelled lunch causing an admission ticket to fail can leave a legitimate attendee arguing at the entrance. Check both before event day.

Tell the door manager exactly which entitlement changed. "Lunch cancelled, admission valid" is useful. "Order refunded" may be interpreted as no entry, even when most of the payment remains for valid tickets. Staff should see enough information to admit the right person without seeing the entire financial dispute.

For the fictional order A104, keep two valid admissions and cancel the two lunch entitlements after approving the separable lunch remedy. If your system represents these differently, translate that decision into its supported controls. Don't improvise new QR codes or ask buyers to rely on screenshots that staff cannot verify.

Check downloaded lists and printed collection sheets. A live update may not change a list prepared earlier. Record which version the team should use and withdraw obsolete copies. If offline working is necessary, assign a controlled record for exceptions and a person to reconcile it with the main system.

A replacement creates its own handover. If the buyer accepts an alternative meal, the collection team needs the alternative entitlement, quantity and any appropriate suitability information. They don't need the buyer's entire email conversation. Share the minimum useful instruction through the approved route.

Keep support away from the admission queue when a case needs investigation. Frontline staff should know who can check a refund case and where the buyer can wait without blocking entry. That person should be able to distinguish a cancelled extra from invalid admission before asking someone to pay again.

Rehearse an affected order. Ask a staff member who wasn't involved in the incident to explain what the buyer can do with it. If they read "partial refund" and conclude that one admission is cancelled, the handover needs fixing. The money alone doesn't communicate which rights remain.

Our guide to ticket management covers the wider connection between orders and entry. For this incident, test the exact boundary you changed. A meal refund should produce the meal outcome you approved, with the reviewed admission decision carried through to the actual entrance.

Fund the remedy while you resolve the supplier claim

When the supplier fails, it is tempting to wait for their repayment before refunding buyers. That may leave you unable to meet obligations when due. Establish the customer remedy and its timing, then pursue the supplier position under the relevant agreement as a separate piece of work.

Use a cash calculation to understand the immediate need. Suppose 40 fictional lunch packages at $25 each must be fully refunded. The customer repayments total $1,000. That is the amount to fund before considering any additional processor cost or other remedy that applies.

Assume you paid the supplier $600 and they confirm a $400 return, leaving $200 unrecovered. If that $400 arrives after the customer payments, you still need access to the full $1,000 when you initiate them. A promised recovery isn't cash already available in the payment balance.

Now assume a further $30 of incident-related charges and $120 of additional support time at fully costed rates. After the $400 supplier recovery, the example's net cash outflow from this point is $750: $1,000 refunded, plus $30 and $120, minus $400 recovered. This excludes the earlier supplier payment because it has already left the account.

To understand the whole failed add-on activity, include that earlier $600 too. You originally collected $1,000, paid $600, then returned $1,000 and incurred $150 more, before recovering $400. The final result is a $350 loss. That is a different calculation from the $750 still leaving the business after the incident began. Neither figure is a suggested deduction from the buyer's refund.

Keep those views separate in the event budget. If you count the $400 recovery as both reducing the original supplier expense and adding new income without an offset, you'll make the result look better than it is. Ask finance to reconcile the reporting treatment, including any tax correction or credit note.

Review your refund cash reserve against the payment timing. The relevant question is whether money is available through the required route when repayments need to happen. An event can look solvent in a budget and still have too little available in the payment account on the day.

Save the supplier correspondence and claim deadline. Recover what your agreement and applicable law allow, without delaying the buyer's remedy to improve your negotiating position. Your customer shouldn't have to manage the dispute between your business and its supplier.

Handle exceptions without reopening every decision

Some buyers will ask for something outside the ordinary partial refund. They may have paid for travel to collect a limited item, relied on the cancelled transport, or already bought a replacement meal. Record what happened and route the request to someone authorised to assess it. Don't promise that the add-on price is always the maximum remedy.

At the same time, keep a clear record of what was already agreed. A buyer who accepted a suitable replacement and received it is a different case from someone still waiting for a decision. Staff need the offer and outcome before answering another request, otherwise the same case gets reconsidered differently across email and social messages.

An open payment dispute needs special care. Check the current payment status and follow the provider's dispute process before sending a separate repayment. Stripe's guidance on responding to disputes explains that the response must follow the case and its deadline. Use your provider's instructions for the actual disputed transaction.

Keep the evidence relevant. Preserve the original offer, the supplier failure, what admission remained available, the proposed remedy, the buyer's response and the payment record. A long narrative about how hard the team worked doesn't establish what was delivered or what money was returned.

For group purchases, don't let one attendee's reply silently decide for everyone. Establish the purchaser's authority and the items covered by the response. A company buyer accepting replacement lunches for named colleagues may be straightforward. A guest saying "refund all of ours" without being able to identify the order needs clarification before financial action.

If the buyer says a promised refund hasn't appeared, investigate the actual stage. Check whether it was approved but never submitted, remains pending, failed, or succeeded in the provider's records. Where available, provide the supported reference for their bank. Avoid submitting a second payment merely to end the conversation quickly.

Make the online status understandable too. W3C's guidance on accessible status messages explains how important status changes can reach assistive technology without requiring focus to move. If your own form displays a refund outcome, test that the message is available to people using screen readers, as well as visible on the page.

Agree an escalation route that stays available after the event. Supplier settlement and payment problems may continue after the production team leaves the venue. Keep an accountable contact and an update date until each unresolved case has a verified next step.

Close the incident only when the records agree

Before closing the incident, reconcile affected units with delivered replacements, cancelled units and unresolved cases. Reconcile approved repayment amounts with the amounts actually submitted and their current outcomes. The totals should explain every affected purchase without counting the same item twice.

For each case, check the buyer communication too. A correct financial record doesn't fix an email telling someone their whole event was cancelled. Confirm that the final message describes the admission and extra status accurately, with a usable route for any remaining question.

Review what made the failure expensive. Was supply promised before a contract was confirmed? Did your preorder cutoff leave no time for recovery? Did one bundle hide the item allocation? Did staff lack a supported way to remove an extra while preserving admission? Those are useful changes for the next on-sale.

Update the offer and operating instructions before selling the extra again. Set a realistic confirmation date, preserve the agreed pricing allocation and establish who can approve a replacement. If the supplier remains uncertain, reduce the commitment or pause the offer until you can deliver it.

The next practical step is to choose one real affected order and walk it through with support, finance and the person running collection. Have each explain the refund amount, what the attendee can still use and what happens next. Resolve any disagreement there before applying the same decision to the rest of your buyers.