Should you sell food and drink vouchers before an event?

So you're selling tickets, the caterer wants a headcount, and you still don't know how many people will buy lunch. Selling food vouchers before the event sounds like a useful way to settle that question. You get money earlier, buyers know what they're spending, and the kitchen has something firmer than your best guess.

It can work. I'd start with a small, clearly described meal offer that people can collect without missing the event. Sell it only when the price covers delivery, your supplier agrees to the arrangement, and you can reliably record each redemption. A general food and drink balance accepted across several vendors needs a much more capable payment and settlement operation.

The part that deserves your attention is what happens after someone pays. Can they find the right counter? Does the voucher cover the meal they actually want? What happens if the vendor runs out? Advance sales help your event business when they improve the whole visit and leave more money after costs. Collecting tomorrow's bar money today doesn't establish either of those things.

Decide what the voucher actually buys

A food voucher can mean several different offers. You might sell one lunch, a drink token, or a cash amount that people spend across a changing menu. Those sound similar when you're writing the event page. They behave very differently when someone approaches a busy server.

An item voucher gives the buyer a defined entitlement. For example, one vegetable bowl and one soft drink, collected from a named counter during a specified service period. You can count those sales, reserve the ingredients and agree a supplier price. The buyer knows the meal, and the server knows what to hand over.

A value voucher gives the buyer an amount to spend. They might use part of it on coffee, save the rest for lunch and pay an additional amount if their order exceeds the balance. Now you need a reliable record of spending and remaining value. If several vendors accept it, their sales must reach the same balance record.

Physical drink tokens are another arrangement. A token might cover one item from an approved list, with no remaining balance. That's easier to explain than partial spending, but you still need controls over issuing, accepting and counting tokens. A distinctive colour alone doesn't stop someone passing around copies or a server accepting last month's stock.

Choose the offer around the problem you're solving. If you need an accurate lunch order, selling a specified meal tells you more than selling flexible credit. If you want buyers to explore independent traders, tying them to one dish might undermine the reason they came. You may be better off letting those traders take normal payments.

Write the entitlement in one ordinary sentence before choosing a system. If you keep adding exceptions, simplify the offer. Your team needs to explain it to someone who's hungry, holding a phone and trying to get back to the show. They won't appreciate discovering a complicated payment scheme at that moment.

Find a reason someone would buy early

The buyer needs a benefit beyond helping you forecast demand. A reserved lunch can mean they don't have to leave the venue between sessions. A family meal deal can make the day's cost easier to plan. A specified collection time can help someone arrange food around a performance they don't want to miss.

Start with questions people already ask. Are attendees checking whether there will be a vegetarian meal? Do they leave during the interval to find food? Are group organisers asking to pay for everybody's lunch on one invoice? Each question suggests a different offer. Selling everyone the same discounted drinks pack won't answer all of them.

Talk to the caterer about what advance knowledge changes. Can confirmed orders reduce a minimum guarantee? Can they prepare a popular meal in sufficient quantities? Will a simpler menu make collection faster? If the supplier orders the same amount regardless, your forecast benefit may be smaller than the sales pitch suggests.

Don't promise shorter queues simply because buyers have already paid. Prepayment removes one transaction, but the food still needs preparing, identifying and handing over. Someone who must join a collection queue and then another queue for a drink may reasonably wonder what they gained. Design the service before advertising the convenience.

An advance offer doesn't always need a discount. A reserved portion or a convenient collection arrangement can be valuable on its own. Explain that benefit honestly and let people decide. If you're relying on a reduced price, work out what the reduction costs you before announcing it.

There are also events where vouchers add very little. A small evening show with an established venue bar may already have quick service and predictable demand. Adding a separate purchase and redemption process could make that experience harder. Ask the venue whether a better staffed interval would solve your problem more directly.

Check what you keep when everyone redeems

The first thing you want to do is calculate the result assuming every voucher gets used. That makes you confront the promise you're selling. Don't build a profitable forecast around customers forgetting their purchases, leaving early or being unable to spend an awkward remaining balance.

For a specified meal, start with the amount you receive and subtract the supplier payment, transaction costs and extra delivery costs. Include additional servers, collection equipment, packaging and support work where they result from the offer. If you supply the food yourself, use the actual ingredient and labour costs rather than treating your existing team as free capacity.

Here's a hypothetical example in US dollars, excluding tax. Suppose you sell 200 meal vouchers at $18 each and pay the caterer $12 for every redeemed meal. Assume full redemption, payment costs of $120 and additional collection labour of $180. You receive $3,600, pay $2,400 for meals and have $900 left after those other costs.

Now suppose you reduce the price to $16 without changing sales or costs. Revenue falls to $3,200, leaving $500. At $14, it falls to $2,800, leaving $100. The following chart uses those invented planning assumptions. It shows money remaining after the stated offer costs, before the event's other costs, and is not an industry benchmark.

That comparison matters because a modest looking discount can remove most of what the offer contributes. In this example, reducing the price by $4 uses up $800 across the 200 sales. Your caterer still expects payment for the same meals. Earlier cash doesn't automatically compensate for that lost money.

The example assumes the organiser retains meal sales and pays the supplier. If your arrangement is a commission on a vendor's sales, calculate your commission instead. If the vendor receives the full voucher amount, your benefit may be operational rather than financial. Make that distinction before adding food revenue to your event forecast.

Our guide to pricing event merchandise and add-ons develops the cost calculation for optional purchases. For vouchers, add one further question. Who pays when the buyer receives something different from what you sold? A substitute meal or a refund can change a result that looked comfortable at launch.

Compare advance sales with what would happen anyway

The $900 in the example isn't necessarily $900 of extra money. Some customers would have bought lunch at the event without a voucher. If you would have retained the same amount from those purchases, selling in advance mainly changes the timing and the information available to you.

You need a reasonable estimate of what changes because you offer vouchers. Perhaps more attendees eat on site. Perhaps you reduce wasted preparation. Perhaps a vendor commits to a better price because of guaranteed orders. Those benefits can improve the result. Discounting meals that loyal buyers would have bought at full price can move it the other way.

Look at your previous food sales alongside attendance and service hours. If the event has changed its programme or venue, explain why the old pattern might differ. A conference moving lunch outside the paid area shouldn't assume the same purchase behaviour as one where the break and food counters shared a room.

Be careful with vendor guarantees. You may agree to pay for a minimum number of meals regardless of redemptions. Advance sales help you see whether you're approaching that minimum, but they don't remove the obligation. If sales stay below it, the event still funds the shortfall.

Keep the wider event result visible too. If collection needs a space you could otherwise sell to a trader, include that cost in the comparison. If an expensive food package makes admission harder to sell, investigate the effect on ticket sales. An attractive food sales report can hide a worse overall result.

You can use the event budget guide to keep those commitments together. Maintain a separate view of cash received, costs still owed and money you can safely use. A healthy account balance before the event doesn't mean the food operation has already made that amount for you.

Agree the vendor deal before taking orders

If someone else serves the food, they need to understand exactly what you've sold and how they'll get paid. Get their agreement before the first voucher goes on sale. A verbal promise to sort it out after the event leaves too many decisions for the busiest part of the day.

Confirm which products the voucher covers, the portion or serving size, the service window and any permitted substitutions. State whether there is a maximum quantity, an order deadline or a minimum guarantee. If you're selling a meal with several choices, ask whether the supplier needs the choices in advance or can manage them at collection.

Then work through the payment calculation using a sample order. Is the supplier paid per voucher sold or per meal actually redeemed? Does the agreed amount include tax, packaging and staffing? Who funds the discount? If you keep a commission, does it apply before or after refunds and other charges?

For a value voucher across several vendors, agree how each redemption identifies the vendor and the amount spent. You need to distinguish money accepted by the burger stall from money accepted by the coffee counter. A total showing all credit sold won't tell you what either business should receive.

Set a settlement date and a process for resolving differences. The vendor should receive a statement showing the accepted redemptions and any adjustments, rather than an unexplained transfer. Give them a deadline to flag discrepancies and name the person who can investigate. Keep enough records to trace a disputed transaction without sharing unrelated buyer details.

Also agree what happens when the supplier fails to deliver. If a stall closes early, do you have an approved alternative? Who authorises refunds? Can the vendor substitute an item without changing the buyer's purchase? These questions affect the terms you advertise, so answering them after sales begin is too late.

Make redemption work under actual event conditions

Walk through the whole purchase with the person who will serve it. The buyer receives a confirmation, finds the counter, presents the voucher and gets the food. At the same time, your record changes to show what has been used. Each step needs to work when the venue is loud and service is busy.

A QR code can identify a voucher, but displaying a code doesn't establish whether it remains valid. Your redemption process needs to check the entitlement and record its use. Otherwise two people can present screenshots of the same purchase at different counters, and both servers may believe they're doing the right thing.

For a specified meal, a single use record is often enough. For a voucher covering several drinks, the system needs to record each item used or provide separately controlled entitlements. For a cash balance, it must record the amount spent and the amount remaining. Don't make a general admission scan do a second job it wasn't designed to support.

Test the awkward cases before opening sales. Ask someone to present a used voucher, an order for several guests and a voucher from the wrong event. Try an unreadable screen and a purchase whose buyer has already received a refund. Staff need a clear answer for each case, including who can override a refusal.

Decide how group purchases work. If one person holds all the meals, can colleagues collect separately? Can a buyer transfer a meal to someone else? If your process requires the original buyer to be present, explain that before payment. Otherwise your collection desk becomes a place where colleagues search their messages for proof.

Keep admission and food entitlements distinct. A person can be admitted successfully and still have an unused meal. Someone might transfer their admission while retaining a separate purchase. Whatever rules you choose, the serving team needs the relevant entitlement and its current status, rather than assuming every admitted guest receives food.

Plan for connection problems without inviting duplicate use

Check connectivity at the actual service location, with the equipment and permissions vendors will use. A successful test beside the production office tells you little about a counter behind the stage. Ask the redemption provider how it handles an interrupted transaction and how staff can tell whether the purchase was recorded.

Offline operation needs particular attention. If several devices can accept the same voucher without communicating, each may accept it before learning another device already did. An offline feature can preserve service while still creating that risk. Ask what protection it provides and what decisions your team must make when devices reconnect.

For a small pilot, you might restrict a specified meal to one collection point with one controlled redemption record. That reduces flexibility but makes the process easier to supervise. A larger event needs a properly tested arrangement that matches its scale. Don't promise universal vendor acceptance and then improvise a shared spreadsheet during service.

Paper can be a fallback when you deliberately control it. Numbered, event specific tokens collected and retained at a designated point are easier to reconcile than photocopied emails accepted everywhere. Record any replacement so the original can't remain a second valid claim. Store unused stock securely and count what staff issue.

Name a supervisor who can resolve failures away from the main serving line. They need a way to find an order, check its status and document any replacement or refund. Set limits on exceptions so different vendors don't make contradictory promises. After service, reconcile those exceptions with the normal redemption records.

Sell only what the service can deliver

Your sales limit should reflect how many promised meals the team can supply in the advertised period. Food availability is only part of that calculation. The kitchen might have enough portions while the collection point lacks the space or staff to hand them over before the programme resumes.

Use a timed rehearsal with the caterer to estimate realistic service. Include reading the voucher, confirming the meal, retrieving it and answering ordinary questions. Then allow for people arriving together and for exceptions that take longer. A test with one cooperative colleague isn't a reliable promise of peak service speed.

If everyone has the same short lunch break, collection slots don't create more time unless you change the programme or the serving arrangement. You might extend service, add a counter or offer a meal that can be handed over more easily. Ask the catering lead which change removes the actual delay.

Stop sales at the quantity you can fulfil and leave a deliberate allowance for replacement meals or operational errors. Tell buyers the collection deadline before they pay. If the service closes while the event continues, repeat that time in the confirmation and at the venue. A paid meal nobody can find doesn't become successful fulfilment because a deadline existed somewhere.

Don't let voucher collection block general circulation or admission. Put clear directions in the confirmation and on signs near the food area. Keep a supported collection option for attendees who can't comfortably wait in the standard line. Discuss that arrangement with the venue and service team before making access promises.

Keep the food ordering deadline clearly separate from the voucher sales deadline. If the kitchen needs final quantities before your last ticket release, decide whether later attendees can still buy food on site. Reserve that stock separately rather than selling the same portions twice. For a cancelled order, check whether the caterer can reduce preparation or whether you still owe the agreed payment. That affects the cancellation terms you can afford to offer voluntarily. It also explains why a seemingly minor extension to advance sales needs the catering lead's agreement before your marketing team announces it publicly.

Explain unused value, refunds and changes before payment

Start with the ordinary cases. What happens if someone chooses not to collect? Can they cancel before the supplier deadline? Can they pass the voucher to a friend? What happens to a partial cash balance? Explain the answer where buyers choose the purchase and repeat it in the confirmation.

Don't assume that calling something an event voucher lets you choose any expiry rule. In Australia, the ACCC's gift card and discount voucher guidance describes minimum validity requirements and exceptions, including some offers available only for a specified period. Ask which rules apply to your actual arrangement before setting an event day expiry.

A buyer changing their mind is different from your event being cancelled or the promised food being unavailable. The ACCC's guidance for businesses selling event tickets explains Australian consumer rights when events are cancelled or significantly changed. Check the rights that apply to the separate food purchase too, rather than copying the admission policy and assuming it covers everything.

Operationally, make sure a refund also changes the voucher's status. Otherwise you can return the money and still hand over the food. A partial refund needs the same care if an order contains several meals. The person approving it should see what has already been redeemed and what remains.

Keep enough money available for the remedies you may owe. If you've already passed all voucher proceeds to a vendor, your agreement needs a way to recover money when that vendor can't supply the offer. Avoid leaving the buyer to negotiate between two businesses while each insists the other collected the payment.

Check food, alcohol and tax requirements separately

Food vouchers don't change the need for accurate food information and safe preparation. In England, Northern Ireland and Wales, the Food Standards Agency's allergen guidance for food businesses covers allergen information and staff responsibilities. Your supplier needs to confirm what information buyers receive before ordering and how staff handle questions at service.

Don't describe a meal as suitable for an allergy because a similar dish was suitable last year. Check the current recipe and preparation arrangement with the caterer. If a substitution becomes necessary, confirm suitability with the appropriate food lead. Our guide to dietary restrictions at events explains how to carry requests through to actual meal delivery.

Alcohol needs its own review with the licensed operator. For events in England and Wales, GOV.UK's alcohol licensing guidance explains the licensing framework. Prepayment doesn't replace the checks and service decisions required where you operate. Confirm how staff handle age verification, refusal of service and any resulting unused entitlement before promoting a drinks package.

Tax treatment can also differ between voucher arrangements. HMRC's guidance on vouchers and VAT distinguishes single purpose and multi-purpose vouchers and explains when VAT becomes due. Those are UK tax categories, not a shortcut based on whether your menu has one dish. Have your accountant classify the offer and the payments between organiser and vendors before launch.

Make the purchase description answer real questions

Imagine a buyer ordering lunch for a colleague who's arriving later. They need to know whether the purchase covers admission, whether they can forward the meal entitlement and whether their colleague must collect during a particular break. Those details affect the purchase now. A long set of general event terms won't help if the offer itself leaves them guessing.

For a specified meal, describe the dish and included drink, the collection point, the service time and the quantity covered by the displayed price. State whether a person needs a separate admission ticket. Explain dietary choices without promising a suitable meal until the caterer confirms the relevant request. Put the cancellation deadline where buyers can see it while choosing.

For a value voucher, explain what happens with ordinary menu prices. If someone has $20 remaining and orders $15 of food, can they spend the other $5 later? If they order $23, can they pay the additional $3 using a normal payment method? These are hypothetical amounts, but they're everyday transactions your system and participating vendors need to support or clearly exclude.

Show the eligible vendors and any excluded products before payment. If a voucher covers food but excludes alcohol, say so in the offer and on the redemption instructions. Explain where buyers can check a balance and who handles a missing confirmation. Ask someone outside the planning team to read the description and tell you what they think they're buying.

You can learn a lot from that conversation. If they think the voucher reserves a table, guarantees immediate service or works at every stall, you've found a misleading implication before it becomes a complaint. Correct the description or change the service. Repeating a restriction more loudly at the counter won't repair an expectation you created when they paid.

Close the accounts after service

Your final reconciliation should explain what happened to every issued entitlement. Separate sold vouchers, complimentary vouchers, refunds, replacements and redemptions. Complimentary meals might cost you the same supplier payment as paid ones, but they didn't produce the same revenue. Replacement codes must connect to cancelled originals so neither the meal count nor the money appears twice.

For a cash balance, reconcile the opening value, any legitimate additions, spending, refunds and the closing balance. Check the sum against the amount vendors accepted. A remaining balance can represent an obligation that hasn't ended, depending on the terms and applicable law. Ask your accountant how it should appear in your accounts rather than automatically moving it into event profit.

Investigate mismatches with the vendor while the team can still remember service. A counter may have recorded a replacement meal manually after a device failed. A refund may have reached the payment record without updating the vendor's report. Keep evidence of the correction and its approval. Quietly changing the total to make two reports match hides the problem for your next event.

Then pay against the agreed statement and date. If you dispute part of the amount, explain the specific transactions and follow the process you agreed. Don't hold the entire vendor payment indefinitely because a small exception needs checking. Equally, don't pay an unexplained total merely because everyone is tired and the event is over.

Keep the records in the places your team uses for event finance and customer support, with access limited to the people who need them. Decide who remains responsible for later buyer questions once temporary event staff finish. The purchase still needs an owner after the serving counter closes. Build that follow-up time into the offer's cost before deciding the pilot was profitable.

Run a small offer you can learn from

For your first test, choose one offer, one agreed collection arrangement and a sales limit the caterer can comfortably deliver. Keep the buyer explanation short enough to understand without a support conversation. You can expand choice later after you know where collection, reconciliation or refunds create work.

Set up admission sales clearly as well. Loopyah's ticketing tools support ticket types and QR ticket check-in, and you can sell drinks, merchandise and extras through Tap to Pay using your phone. Those capabilities help with ticketing and ordinary on site purchases. A prepaid balance accepted across vendors needs separately verified redemption and settlement capabilities before you promise it.

After the event, compare sales with actual redemptions and the amount paid to each supplier. Include extra labour, refunds and unresolved balances. Ask the catering team what the advance orders changed, and ask buyers whether the collection arrangement helped. A popular discount and a better lunch service are different findings.

Then decide whether to repeat the same offer, change it or stop. If full redemption leaves a worthwhile amount, buyers understand the terms and collection works, you have a sensible basis for another event. If the only attractive number is cash collected before you supplied anything, keep working on the offer before selling more.