Event ticket bundles: when to sell several events together

Sell event ticket bundles when the same buyer has a good reason to attend several named events and the combined purchase improves what those dates earn. Keep tickets available individually, reserve a place at every included event, and decide how you will handle one cancelled date before you take anyone's money.

So you've got several events coming up. One has strong demand, another needs a push, and your regulars keep asking what's next. You could sell each date separately. Or you could give someone a clear reason to put several of them in their calendar today.

That second option can work beautifully. It can also turn your best event into a discount machine for your quietest one. The difference starts with what the buyer wants, then runs through your pricing, capacity and delivery.

Here, an event ticket bundle means one purchase covering specified, distinct events. Think a Friday concert and a Sunday listening session, or a business conference and a separate evening dinner. It isn't a flexible class pass, a subscription, or several people buying tickets to the same event. We'll work through choosing the events, setting the price, protecting places and delivering the purchase across dates. Every financial example is hypothetical, uses USD and excludes tax unless stated otherwise.

Give the buyer a reason to want every event

Start with the person buying, rather than the dates you want to fill. What makes the events better together for them?

A film screening followed by a separate conversation with the director has an obvious connection. The buyer sees the work, then gets to discuss it. A conference followed by a paid networking dinner can suit someone travelling to make business contacts. Two concerts by unrelated artists may still work together if the same local audience follows both.

But the link needs to survive a simple question. If someone asks, "Why would I go to both?", can you answer without mentioning the discount?

"They're both ours" isn't much of an answer. Neither is "The second event has loads of tickets left." Your sales problem doesn't become the buyer's reason to attend.

Talk to people who bought a previous event. Ask which upcoming dates interest them, whether they can attend both, and what would make deciding now worthwhile. Show the actual names, locations and times. Someone who likes the idea of a weekend package may change their mind when they notice the Sunday event starts before their train arrives.

The Australian government's pricing strategy guidance recommends testing offers with customers and considering what they value. For a bundle, that means testing the combination as well as the price. Find out whether the events belong together before asking how much cheaper you should make them.

Look at past purchases where you have appropriate records. Did the same people already attend these types of events? Did buyers of one event ask about the other? Treat those observations as reasons to investigate, rather than proof that a new package will sell.

I'd start with two events. You can explain the relationship quickly, the buyer has fewer dates to check, and your team has fewer things to untangle if one changes. Add another event when it adds something people actually want. A longer list can make the decision harder, especially when every date involves travel or childcare.

Choose a fixed bundle people can understand

For a first offer, name exactly what one purchase includes. One admission to the Friday concert and one admission to the Sunday listening session is clear. "Access to selected events" leaves too much work for the buyer.

A fixed bundle commits both sides. The buyer knows their dates. You know which events owe them a place. If they must choose from a menu later, you're selling a different offer with a booking process, availability rules and potential disappointment to manage.

Specify the ticket level at each event. A premium concert ticket and standard listening session admission are different from standard admission to both. State whether seating is reserved, whether any food is included, and whether the events have different age restrictions. Don't let a single package name hide restrictions that would stop someone attending.

Keep the individual tickets available unless the experience genuinely requires the complete package. Someone who can only attend Friday should still have a sensible purchase. It also gives buyers an honest comparison and helps you see whether the bundle attracts additional Sunday attendance or merely changes how Friday buyers pay.

Be careful when the two events have overlapping times. Even a short overlap can make the promise impossible for someone relying on public transport. Include travel time between venues and realistic arrival requirements. If people need to leave the first event before its main attraction, you haven't created a useful pairing.

Different organisers add another decision. Who is selling the package, who holds the buyer's money, and who handles a complaint about either date? Agree the answers with your partner before promotion starts. A buyer shouldn't have to work out which company owes them a refund because your organisations never discussed it.

Write the offer in a sentence your door team could repeat. "This purchase gives one person standard admission to these two named events on these dates." If that sentence needs a paragraph of exceptions, simplify the offer before writing better sales copy.

Price the package without giving away your strongest date

You don't have to discount a bundle. Buying several events at once can have value through a clear programme, confirmed plans and a convenient purchase. If those benefits are enough, keep the combined price at the sum of the individual tickets.

Suppose your concert costs $60 and your listening session costs $40. A $100 bundle preserves both prices. You can still describe the connected experience and make it easy to choose. Call it a package, and avoid promising a saving that doesn't exist.

If you test a lower price, write down what you expect it to change. Perhaps concert buyers will add the listening session when the combined cost is $90. Perhaps people interested in both will commit earlier. Those are different outcomes, and the first is usually the stronger reason to give away revenue.

Now separate buyers who would attend both anyway from buyers who would otherwise attend only one. You can't know this perfectly, but you can build a realistic assumption and test it. Giving an existing two-event buyer a $10 discount loses $10 without selling another admission. Getting a concert-only buyer to purchase the $90 bundle adds $30 of ticket revenue compared with their $60 purchase.

That extra $30 isn't all profit. The Sunday admission has a cost. For this example, assume serving an additional listening session attendee costs $8, with no additional payment fee or staffing change. The bundle then adds $22 compared with that person's concert-only purchase. Your own payment terms and delivery costs may give a different answer.

The US Small Business Administration's break-even guidance separates selling price, variable costs and fixed costs. Apply that distinction to each event. Include the costs that increase with another attendee, and keep the whole event's fixed bills in your budget.

Your event budget still needs to cover the concert, the listening session and the extra work of selling them together. A useful sale can contribute towards those bills without making the complete programme profitable. For wider price decisions, our ticket pricing guide covers how this offer sits alongside the rest of your ticket structure.

Compare the bundle with what would happen without it

Let's put those assumptions together. Imagine twenty people would already buy both events individually. Another ten would buy only the concert. Without a bundle, those purchases bring in $2,600. The first group pays twenty times $100, and the second pays ten times $60.

Suppose all thirty choose the $90 bundle. Ticket revenue becomes $2,700. You've added $100, but you've also committed to ten more listening session admissions. At the assumed $8 attendance cost, those admissions cost $80. The improvement is $20 before any extra promotion, administration or other costs.

That is much less exciting than thirty bundle orders might look on launch day. If creating and supporting the offer costs another $50, the result is $30 worse than selling individually. A healthy order total can hide a poor pricing decision.

Now suppose twenty concert-only buyers upgrade instead, while the same twenty existing two-event buyers receive the discount. The upgrades add twenty times $22, or $440, after the extra Sunday attendance costs. The discounts given to existing two-event buyers cost $200. Subtract the same $50 offer cost and the improvement is $190.

This example assumes those upgraded buyers were going to buy concert tickets anyway. If someone would have purchased neither event, the comparison changes. If someone gives up a full-price Sunday ticket to buy the package, it changes again. Don't classify everyone who bought a bundle as a new customer.

Use a few scenarios before launch. In one, most purchases replace two individual tickets. In another, more people add the second date. In a third, the package attracts buyers who weren't going to attend either. You don't need a complicated forecast. You need to know which assumption makes the offer worthwhile and whether it sounds believable.

Include any full-price sale you expect to lose because a bundle occupies the place. If Sunday has spare capacity, that cost may be small. If Friday was heading for a sellout, discounted Friday admissions can replace tickets you would have sold at $60. Don't quietly treat that space as free.

Allocate the price to each event before selling

One checkout creates a combined payment. Your event records still need to show how much of it belongs to each date. Decide that allocation before launch and use it consistently across reporting, partner settlements and the buyer information that matters.

A simple management approach is to split the bundle price in proportion to the individual ticket prices. Our $60 concert and $40 listening session make a $100 individual total. At a $90 package price, allocate $54 to the concert and $36 to the listening session. The amounts add to $90 and apply the same proportional reduction to both.

This is a worked management example, rather than a universal accounting or refund rule. Your accountant should confirm revenue recognition, tax and settlement treatment for your business. Your cancellation policy needs its own legal review for the markets you sell into. A convenient spreadsheet split doesn't settle either question.

Avoid allocating almost everything to the event least likely to be cancelled just to reduce potential refunds. Buyers bought two real admissions. A token value against the main attraction will be difficult to explain when that attraction disappears.

Keep the allocation attached to the original order. If the individual concert price rises later, don't rewrite the earlier buyer's package values. Their purchase happened under the price and terms shown at that time. You need to be able to reconstruct those details when responding to a question months later.

Fees deserve a separate check. Does your provider charge per order, per admission, or both? Can it refund one event within the purchase? Who absorbs a processing fee when one date is cancelled? Confirm the actual behaviour before building savings into your calculation. One payment doesn't automatically mean one ticketing charge.

If another organiser runs Sunday, agree their share and when you'll pay it. Decide who bears the cost of a refund, including one issued after their settlement. The partnership needs a workable cancellation process, not just an agreeable split of launch revenue.

Let the tightest event set your bundle limit

Every bundle uses capacity at every included event. That sounds obvious until a package counter keeps selling after one of the dates runs out of space.

Imagine Friday has eighty places available and Sunday has thirty. You can sell no more than thirty of this bundle before reserving space for other sales. The extra Friday availability doesn't give you permission to promise a Sunday admission you can't deliver.

Now suppose you want to keep fifteen Sunday places available for individual buyers. That leaves fifteen for bundles. Whether that reservation is sensible depends on demand and the price each option leaves you, but the capacity arithmetic is straightforward. Count the places you have actually committed, including invitations, accessible seating arrangements and partner allocations.

A bundle cap should also protect a strong date from excessive discounting. If Friday normally sells well, you might make a small quantity available in the package while keeping the rest for individual tickets. Set a real quantity and explain availability honestly. Don't invent a deadline or claim the package is nearly sold out when it isn't.

Availability must update when a bundle sells. A package purchase needs to reserve the concert place and the listening session place, even if two separate event records sit behind it. If your ticketing setup can't do that reliably, resolve the setup before launch. Staff shouldn't have to discover an oversell while comparing reports after a campaign.

Returns and transfers can change the count. A partial cancellation might release Sunday space while Friday remains held. A refund for the complete package may release both. An admission already used cannot become an unused place again. Write those rules down and test them against what the system does.

Never plan around an assumed number of people failing to attend unless your operating model, safety rules and buyer terms support it. Someone who bought both dates is entitled to the places you promised. A quiet Sunday forecast doesn't make it safe to oversell Sunday.

Make the purchase clear before payment

Your sales page should answer the questions that affect whether someone can buy. Put the event names, dates, venues, admission types and total price where people can see them while deciding. Add the cancellation and transfer information that could materially change their choice.

Explain whether the same attendee must use both admissions. If transfers are allowed, say whether someone can transfer Sunday while keeping Friday, how they do it and when the deadline falls. If the package belongs to one named person throughout, say that before purchase. Don't leave the door team to introduce a restriction the buyer never saw.

Show the price people actually need to pay under the applicable rules. In the United States, the FTC's live-event ticket fee guidance requires covered businesses to display the total price including calculable mandatory fees upfront. It allows specified exclusions, including government charges, with further disclosure requirements before payment. Follow the guidance for your offer rather than advertising a package price that grows through unavoidable charges.

Your saving comparison also needs to be true. Compare the same admissions under the same relevant purchase conditions. If individual prices changed, update a new offer's comparison. If one event is unavailable individually, don't present its invented standalone price as a saving.

Keep a record of the terms and offer shown when each buyer purchased. A shared page can change. The order needs to preserve the relevant version, price and included dates. This protects your team from guessing which announcement a buyer saw.

Read the page on a phone. Can someone tell which dates they are committing to without expanding several panels? Can they find the transfer rule before they pay? A beautifully written programme description doesn't compensate for a hidden restriction.

Finally, ask a colleague who wasn't involved in creating the bundle to explain it back to you. Listen for the assumptions they make. If they assume dinner is included or that they can choose either date, the page needs fixing even if the detail exists somewhere below.

Give each date its own admission and reminder

One order shouldn't require the buyer to solve your ticket structure. They need to find the right admission for the right event, know when to arrive and understand what happens after they use the first one.

You may deliver separate tickets for each date or use a supported credential with distinct event permissions. Either way, the door process must identify the event being checked and record only that admission as used. A Friday scan must leave Sunday admission available. A Sunday scan must not create another Friday entry.

Don't assume a QR code can do this because it scans successfully once. Ask your ticketing provider to demonstrate the complete sequence in your actual setup. Buy the package, open the delivery message, check in to Friday, then inspect Sunday. Test a second Friday scan as well.

Our event confirmation email guide covers the purchase details buyers need. For a bundle, add a clear list of the included dates and the way to retrieve each admission. If a buyer purchases for another person, make sure that attendee can receive the information they need.

Send practical reminders for each date. Friday's arrival time doesn't tell someone where to go on Sunday. Mention the relevant venue, doors time, access requirements and support route. Keep the message tied to that event so buyers don't mistake a reminder for a new purchase request.

Prepare the door team for the wording buyers will use. Someone may show a package receipt, the wrong event ticket or an older message. Staff need a way to look up the order and confirm the current admission without admitting someone twice or refusing a valid buyer.

If you allow partial transfers, test the messages to both people. The original buyer should know which admission they retain. The recipient should receive Sunday information without gaining Friday access. A transfer is complete when the records, credentials and communication all agree.

Decide what happens when one event changes

This is the part I'd settle before spending anything on promotion. You sell a connected experience, but the two dates can still have separate problems. A venue closes on Friday. A speaker withdraws on Sunday. A buyer attends the first event and then the second is cancelled.

Your policy needs to distinguish a buyer changing their plans from you failing to deliver an included event. It also needs to distinguish a minor programme adjustment from a cancellation or significant change. Local consumer law can affect the remedy, so have the actual wording reviewed for your selling markets.

The Australian Competition and Consumer Commission's event ticket guidance explains that refunds after cancellations or significant changes depend on the circumstances. Where the organiser chooses to cancel or makes a major change, consumer rights can require a refund. That guidance is specific to Australia. Don't turn it into a single worldwide package policy.

For our hypothetical $90 bundle, the records show $54 against Friday and $36 against Sunday. If Sunday is cancelled after Friday happens, your planned process might refund the $36 allocation while preserving the Friday attendance record. Whether that amount satisfies the buyer's rights depends on the contract, circumstances and applicable law. Allocation makes the process explainable; it doesn't override those rights.

A cancellation before either date can be more complicated. If the connection was the main reason someone bought, losing one part may affect the whole purchase. Don't assume everyone must keep the remaining ticket just because its event is still happening.

State what your policy offers and how buyers request any choice they have. Include when you'll communicate the change, what happens to the affected admission, how refunds are calculated and when buyers should expect processing. Only promise a timeline you can deliver.

The UK's Competition and Markets Authority publishes guidance on fair and transparent consumer terms. For UK sales, use the current guidance when reviewing your conditions. Writing "no refunds" in bold doesn't make a term fair or remove applicable consumer protections.

A practical policy draft can start with the actual purchase. "Your package includes one standard admission to the Friday concert and one standard admission to the Sunday listening session. Both places are reserved when payment completes." Then insert the confirmed dates, venues and entry conditions. Those details must match the event records.

Next, describe the cancellation process using the allocation you've agreed. "We record the package payment against each event separately. If an included event is cancelled, we will contact you with the available remedy, the amount involved and the processing timetable." Replace that general sentence with your reviewed terms before selling. It is a drafting prompt, not finished legal wording.

Include a support route that stays available between dates. Assign one person to approve exceptions and record the reason. A door supervisor shouldn't improvise a new refund promise while dealing with arrivals. Equally, a support agent shouldn't transfer an admission without checking whether it has already been used.

Keep buyer communications attached to the order. If you offer a refund choice, record what the buyer selected and when you completed it. That gives your team a shared answer when the person contacts you again. It also helps a partner understand why their expected settlement changed, without forwarding a messy collection of private messages or guessing which version of the policy applied.

Test the ugly cases before inviting buyers

Run a complete purchase using the same journey customers will use. Follow it through delivery, both event records, capacity and payment reporting. Ask someone outside the setup team to do it, because the person who built the offer already knows where everything is.

Check the normal case first. One purchase reserves one place on each named date. The buyer sees the promised admission types and total paid. Your reports show the agreed revenue allocations, and the original order can be found from either event's attendee record.

Then test a duplicate scan at the first event, arrival at the second after using the first, and the wrong ticket shown at the door. Check what staff see and which action they can take. A vague error message can turn a solvable lookup into a queue.

Try cancelling Sunday only. Confirm the refund amount, the remaining Friday status, the released Sunday capacity and the message to the buyer. Try the same change after Friday admission has been used. The record of an attended event should survive the refund of another.

Try a complete refund before either date, and a permitted transfer of only one admission. Look for duplicate refunds, stale credentials and places that remain unnecessarily blocked. If a partner is involved, verify that their settlement records change correctly too.

You should also know what happens if delivery fails or the buyer can't find the message. Your support person needs a repeatable way to retrieve the order without issuing additional valid admissions. Record the result of each test and fix failures before opening sales.

If the package requires unsupported workarounds that nobody can reliably repeat, simplify it. Separate purchases with clear cross-promotion may be a better offer until your ticketing setup can deliver the bundle you want. A tidy checkout is only useful when every promised admission works afterwards.

Launch a small offer and review every date

Start with a limited quantity and a defined review point. Decide which buyers will see the offer and why they are likely to want both events. An existing audience interested in the programme is a more useful first test than a broad campaign aimed at anyone who likes discounts.

Write down what would persuade you to repeat it. You might want more paid Sunday attendance, enough additional money after costs, and a delivery process your team can handle. Set those numbers using your own event budget.

During sales, watch individual tickets alongside packages. If bundle purchases rise while full-price purchases fall by the same amount, investigate who changed their purchase. Ask a short question where appropriate, but treat self-reported intent as supporting evidence. People don't always know what they would have done without an offer.

After each event, reconcile allocated revenue, refunds, attendance and additional costs. Review the final result after the last included date, not just the cash collected at launch. Earlier receipts still come with later delivery obligations. Keep enough funds available to meet those obligations and your planned refund process.

Listen to support conversations as well. Repeated questions about ticket access or transfer rules show where the offer confused people. Fix the relevant page or workflow before expanding the package. More sales will multiply the same confusion.

Repeat a bundle when buyers want the combination, each date keeps enough capacity and the additional purchases justify the price reduction and work. If the strongest event merely became cheaper, change the offer. The right bundle gives people a reason to attend more of your programme while leaving your event business better off when those dates are over.