How do you restrict an event add-on to the people entitled to buy it?

Someone buys a Saturday workshop for your event. They've paid and received a confirmation, but their admission ticket is for Sunday. Now your team has to contact them about a booking the checkout should have questioned before accepting it.

You can explain the restriction when they arrive, but by then you've already sold them something they can't use. The better time to catch that mismatch is before payment, while they can still choose the right admission or another activity.

To restrict an event add-on properly, define which admission, attendee and date qualify, then make the buying process check those conditions alongside quantities and availability. Repeat the checks when someone buys later, changes a ticket or transfers a booking. A sentence saying "ticket holders only" helps explain the offer, but your sales process also has to enforce it.

The interesting part is that the person paying isn't always the person using the extra. One buyer might book for four colleagues, only two of whom want the workshop. Another might buy admission today and lunch next week. Rules that look fine in a simple test can reject legitimate customers or accept impossible bookings once those ordinary situations appear.

We'll work through those decisions using a fictional paid weekend event. All quantities, times and USD amounts in the examples are invented planning assumptions. They aren't recommended limits, customer results or evidence of how any particular ticketing platform works.

Start with the reason for the restriction

Before changing your checkout, write down why an extra needs a restriction. A workshop inside the event requires admission because the participant must enter the site. A parking pass needs a vehicle allocation. A limited tasting may have an age condition. Those are different problems, even if you currently sell everything under a heading called "extras".

Start with a plain sentence about the purchase. "One Saturday admission holder can buy one place in the Saturday printmaking workshop." That tells you who qualifies, which date matters and how many places they may buy. "Workshop available with selected tickets" leaves all three decisions unfinished.

Then ask whether the restriction is necessary. Does a shirt buyer really need an admission ticket if you're willing to ship the shirt? Does someone attending an evening performance need daytime admission for an activity held in a separately accessible foyer? You might choose either arrangement, but it should follow the experience you're selling.

Unnecessary restrictions can block sales you could fulfil perfectly well. Equally, removing a genuine admission requirement can create customers who own an activity booking but have no way to reach it. Agree the physical access arrangement with the venue before deciding what the checkout should allow.

Keep the commercial decision separate from the booking rule. Our guide to which event extras to charge for separately helps you decide what belongs in admission and what can support a separate price. Here, we're deciding who can purchase that separate offer once you've chosen to sell it.

Write one rule for each extra. Copying the workshop rule onto meals, parking and merchandise can create strange results. A driver might need one parking pass for a car carrying four attendees. Those same attendees could legitimately need four lunches. An order-wide maximum of one would be wrong for at least one of those purchases.

Finally, name the person who owns the rule. Sales can explain it, but the activity lead needs to confirm the participation conditions and operations needs to confirm access. Resolve disagreements before the offer goes live, while changing a sentence doesn't require contacting people who have already paid.

Match the extra to the right admission and date

For our weekend event, imagine Saturday admission, Sunday admission and a weekend pass. A Saturday workshop accepts Saturday admission or the weekend pass. Sunday admission alone doesn't qualify. The weekend pass qualifies because it includes Saturday, not because it happens to be the most expensive ticket.

That distinction matters when you introduce discounted releases, sponsor tickets or complimentary admission. Two tickets with different prices may provide exactly the same access. If the cheaper release is excluded accidentally, you've created a restriction that contradicts what those buyers were promised.

Build the qualifying list from admission rights. Include legitimate earlier releases and agreed allocations. A person who received valid Saturday admission from a partner may be entitled to purchase the same Saturday activity as a public buyer. Decide that explicitly rather than letting the route through which they received their ticket determine the answer by accident.

Also distinguish a ticket selected in the current order from admission bought previously. A rule that checks only today's basket might work for the initial sale and fail for every returning customer. Conversely, finding an old order under an email address doesn't establish that the relevant admission remains valid or belongs to the intended participant.

For multi-day offers, use the actual dates and access periods in the customer wording. "Saturday printmaking workshop, 14:00" is more useful than "Day one upgrade" when the event includes an opening night or changes its programme order. Keep the date consistent in the event page, purchase selection and confirmation.

Our guide to ticket types for a multi-day event develops the admission structure. Check that structure first. An add-on rule can't repair a weekend pass whose description never makes clear which days it covers.

If the activity is outside ordinary opening hours, confirm how participants enter. Saturday admission might end before an evening extra begins, or the usual gate might be closed. The purchase needs both a qualifying admission and a workable arrival instruction. Otherwise, the rule succeeds at checkout and the customer still gets stuck outside.

Decide whether the rule applies to an attendee, an order or a vehicle

Suppose one buyer purchases four Saturday admissions. Does that permit one workshop place, four places or as many as the buyer wants? The answer depends on your offer, not on the fact that all four admissions share an order number.

For a workshop with one place per eligible attendee, four qualifying admissions can support up to four places. Each place should be assigned to a different qualifying attendee before it becomes a confirmed participation booking. Having four admissions somewhere in the order doesn't explain who is booked into which activity.

Now imagine two of those attendees buy a workshop today and the other two decide next week. Your rule needs to count earlier workshop purchases against the same attendees. A maximum of four per transaction would allow another four on the next visit. That's a transaction limit, not a continuing limit per person.

There are legitimate order-based rules too. A group delivery charge might apply once to the whole order. A parking pass might cover one vehicle, with the advertised vehicle conditions. A merchandise purchase could allow several items per buyer without connecting each shirt to an attendee. Name the unit people are actually buying.

Be especially careful with family and group admission. One family ticket may represent several people, while an individual ticket represents one. Multiplying the number of ticket documents by an add-on allowance will produce the wrong answer if those documents cover different numbers of participants.

Decide what happens when attendee names aren't known yet. A company may buy places before choosing its team. You could allow provisional assignments within the purchased allowance, with a clear deadline and a supported way to name participants. Don't advertise confirmed individual activity places if the booking remains only an unassigned expression of interest.

This isn't a reason to collect more information than you need. It's a reason to identify the correct relationship. Staff should be able to answer "Which admission allows this person to attend this workshop?" without assuming that every person sharing a purchaser is interchangeable.

For popular extras, explain your limit in customer language. "One place per Saturday attendee, including places bought earlier" is clearer than "maximum quantity one". The latter could mean one per order, one per transaction or one per person, and customers shouldn't have to discover your interpretation through a rejected payment attempt.

Count benefits already included before selling another one

A premium admission might already include a workshop place or a meal. Those included benefits need to count when you decide what else the attendee may buy. Otherwise, your checkout can sell the same person a second entitlement without making clear that they're paying for something they already have.

Suppose the fictional weekend pass includes one Saturday workshop choice. A standard Saturday ticket doesn't include a workshop, but its holder can purchase one. Both attendees might finish with one confirmed workshop place. Their routes to that place differ, and the records need to preserve that difference.

Be clear about whether "includes a workshop" means a guaranteed place in a named activity or permission to choose from remaining availability. Those promises carry different obligations. If you guarantee a particular session, protect its places when selling the premium pass. If a choice is required later, explain the booking step and the limits before the pass purchase.

Don't silently convert an included benefit into a paid extra when someone chooses a different option. Explain any permitted upgrade, its additional price and what happens to the original benefit. A buyer shouldn't finish with two bookings because one department calls the second purchase an upgrade while another treats it as an additional activity.

Likewise, a complimentary ticket doesn't automatically include or exclude extras. A speaker may have admission and lunch included but no workshop entitlement. A sponsor guest might have the same admission as a standard buyer. Record the actual package, including earlier promises made outside the current public ticket page.

Check whether additional quantities are genuinely useful. Someone may want two shirts and one workshop. Rejecting every second purchase because it is called an add-on would lose a legitimate merchandise sale. Allowing two workshop places for one participant could withhold a scarce place from another buyer for no useful reason.

When you change packages between releases, preserve the promises attached to earlier purchases. Current public wording isn't enough to establish what an early buyer owns. Keep a dated description or another reliable record of each sold package, so support can resolve a question without relying on somebody's memory of launch week.

Keep eligibility and availability as separate checks

An eligible attendee can still find that an activity is full. An available activity can still be unsuitable for a particular ticket. The buying process needs both answers before it confirms a place.

Imagine our Saturday workshop has 24 sellable participant places after the responsible team has set its actual operating limit. Six are already reserved by premium-pass holders, 14 have been sold separately, and two are protected in active checkouts. Two remain available. A returning buyer with three qualifying admissions can book at most two places at that moment, not three.

Those figures describe an invented sales position. They don't establish how many people can safely use your room. Great Britain's Health and Safety Executive explains that organisers need to assess the venue's suitability and safe capacity. Its guidance concerns safety planning in Great Britain. Set the real limit with the relevant venue and activity specialists under the requirements where you operate.

Then make every route use the same remaining allowance. A premium package, public add-on link and staff booking cannot each promise the last two workshop places independently. If different products draw on the same activity, the stock relationship must remain accurate across all of them.

Our guide to shared capacity across linked sessions covers that inventory problem in depth. The important connection here is that passing the admission check doesn't reserve stock. The required place also has to be secured through the supported booking process.

Recheck the final selection before confirming the purchase. A buyer may remove their Saturday admission while leaving its workshop in the basket. Another may switch to Sunday while an old Saturday extra remains selected. The earlier successful check mustn't become permanent permission after the qualifying purchase has disappeared.

When the last place goes during checkout, explain the result before the customer receives an unsupported promise. The provider needs a documented process for a payment that remains unresolved while availability changes. Ask how the booking is protected and how exceptions are handled, rather than assuming that a paid receipt always means every requested place was secured.

If your tools cannot protect the relationships reliably, simplify the offer. A smaller number of clearly defined packages or fixed allocations can be easier to fulfil than a flexible selection that staff must repair afterwards. Compare the lost flexibility with the actual work and risk of accepting incompatible purchases.

Check session clashes for the person attending

Two activities at the same time aren't necessarily an invalid order. One buyer could be booking different activities for different colleagues. The conflict appears when the same attendee is promised both.

For our example, suppose printmaking runs from 14:00 to 15:00 and a studio tour runs from 14:45 to 15:30. One person cannot attend both in full. If your descriptions promise full participation, don't accept both bookings for that person and expect them to negotiate an early departure on the day.

Now suppose the tour starts at 15:10 instead. A ten-minute gap may or may not work. Include the actual route, departure instructions and any preparation needed. An accessible route could take longer than the route used by the person building the schedule. Ask the delivery team to test the journey before presenting the combination as practical.

Record the rule against the participant. One attendee could take printmaking while a colleague takes the overlapping tour. A basket-level block would prevent that valid purchase. An order that allows everything without assigning participants would conceal the invalid case.

You also need to decide what counts as a clash. Is the attendee required for the entire activity? Is a drop-in genuinely flexible, or does it have a fixed induction? Does an equipment collection time need the participant present? The answer follows the service promise, rather than a blanket rule that any matching start times are incompatible.

Some combinations are possible but unattractive. An attendee might miss a talk to attend an optional workshop, and choosing between them may be exactly how the programme works. Explain the trade-off instead of banning every overlapping item automatically. Reserve hard restrictions for combinations you cannot honestly deliver or that the applicable conditions prohibit.

When the programme changes after purchase, find the affected participants rather than emailing every customer the entire timetable. A revised start time can create a clash that didn't exist when they booked. Offer a supported way to resolve it, taking account of what they bought and their rights, before asking staff to enforce the new schedule.

Treat age conditions as a separate responsibility

Admission to your event doesn't prove eligibility for every activity inside it. A family event might include an adults-only tasting. An activity may also have a minimum age set by the supplier or another participation condition that differs from general entry.

State the relevant age, when it is measured and what evidence is required. For an age condition based on the event date, the purchaser's current age isn't the only question. The participant could be someone else, and their birthday might fall between purchase and attendance.

Work with the responsible licence holder or specialist to establish the actual rule. Don't copy an age threshold from a different country or assume that calling something a private add-on changes the rules applying to it. A box ticked during checkout doesn't settle every duty at the point of service.

Accepted evidence can change too. In September 2026, the UK government announced that licensed businesses in England and Wales could choose to adopt certified digital proof of age for alcohol sales. That doesn't mean any phone image is acceptable, or that every venue must accept every digital service. Confirm the current policy with the person responsible for your event's alcohol service.

Tell buyers what they need to bring, and brief the serving team on the same policy. If somebody else can buy on the participant's behalf, say that the participant still needs to satisfy the stated conditions. A purchaser supplying their own age does nothing to establish the age of the person receiving the tasting.

Separate legal or safety restrictions from your preference about the audience. An advanced workshop may require prior knowledge, but a vague statement that it is "for professionals" isn't a usable check. Explain the prerequisite and decide whether a declaration is sufficient or approval is genuinely necessary.

Where approval is required, make its status clear before taking a non-refundable payment or promising a confirmed place. An application, a temporary reservation and an accepted booking are different outcomes. Use wording and payment arrangements that match the actual stage, and have the conditions reviewed for your market.

Our guide to event age verification covers the arrival and identification process more fully. Connect that process to the purchase rule, while keeping the responsibilities distinct. Being allowed to buy an activity doesn't remove the checks the team must make when delivering it.

Keep access arrangements out of ordinary upselling rules

An arrangement that enables someone to attend may need different treatment from an optional commercial extra. Don't automatically process companion access or accessible seating as if it were another paid upgrade with a one-per-order limit.

Start by understanding the person's access requirement and the obligations applying to the venue and event. A rule built around a single named purchaser can fail when someone buys on another person's behalf. A blanket block on an extra companion can also conflict with the actual accommodation the customer needs.

For assigned seating in the United States, the Department of Justice's ADA ticket sales guidance addresses accessible seating, companion purchases and purchasing on another person's behalf. It also says sellers cannot require proof of disability before selling accessible-seat tickets. Those are specific US requirements; don't turn a generic fraud-prevention setting into a reason to disregard them.

This doesn't mean every event must use one universal companion policy or that every optional experience is free. It means you need to identify which part of the purchase concerns access before applying your usual commercial restrictions. Get the appropriate advice for your location and the specific service.

Make the ordinary purchase route usable, and provide a clear way to discuss requirements that the standard choices don't cover. If the only way to obtain an accessible option is to wait for an unanswered email while public tickets sell out, an explanation buried in your terms won't resolve the practical disadvantage.

Staff also need a decision route for exceptional cases. Give them the person responsible for access arrangements and enough information to refer a request promptly. Don't ask a frontline seller to make medical judgments or improvise a new companion policy while the buyer waits.

Test the supported purchase with someone who wasn't involved in building it. Can a customer buying on behalf of another person understand the choices? Can they distinguish optional paid activities from an access arrangement? Fix the unclear wording or unsupported restriction before adding another explanatory paragraph to the terms.

Let existing attendees buy later without opening the offer to everyone

Later purchases can be useful. A buyer may need to speak to friends before choosing lunch, or a workshop might go on sale after admission. You can support that behaviour while still checking that the person using the extra holds qualifying admission.

Start with a supported route that finds the current admission and its remaining allowance. A forwarded public link isn't proof of eligibility. Neither is knowing somebody's order number. Ask your provider how an authorised buyer or attendee is recognised and what information the process reveals before a purchase is accepted.

Don't force the purchaser to attend if the offer allows individual attendees to buy their own extras. A company administrator may have paid for admission, while a colleague makes a personal activity choice. Decide how the colleague is authorised to use that admission's allowance without giving them access to everyone else's booking.

Returning buyers should see benefits already included or purchased. If a person has one workshop included in their pass and has already reserved it, a later link shouldn't offer a second identical booking as though the allowance were unused. If additional purchases are permitted, explain what the new purchase adds.

Set a real deadline around delivery. A meal choice may need to close before the caterer's final order, while a workshop can remain available if places and staff capacity remain. Don't use one closing time merely because all the offers share a page. Tell the buyer whether the deadline concerns ordering, assignment or attendance.

When automated checking isn't supported, a managed route can be reasonable for a small number of purchases. Staff can verify qualifying admission before issuing the supported payment or booking invitation. Be honest about response times and availability. An inquiry should not look like a confirmed place while somebody is still checking it.

Avoid building that review process from a shared document full of unnecessary personal information. The UK's Information Commissioner's Office explains why businesses should collect and hold only the personal data they need. The guidance is under review following UK legislative changes, so check current requirements when designing the process. For this task, start by asking what staff need to verify the admission, rather than requesting a copy of every identity document.

Explain a refusal while the buyer can still fix it

A restriction is easier to accept when the customer understands it before they invest time choosing. Put the qualifying admission, date and quantity rule beside the extra. Repeat the important condition in the selection step where it affects the purchase.

For our workshop, useful copy might say, "For Saturday admission and weekend-pass holders. One place per attendee. Saturday, 14:00 to 15:00." That gives people enough information to decide whether the offer fits before they try to pay.

If a selection fails, explain the actual reason. "This workshop requires Saturday admission. Your selected admission is Sunday" identifies a fixable mismatch. "Not eligible" makes the buyer guess whether the problem is their age, ticket, payment or a technical error.

Give a legitimate next action where one exists. That might be choosing Saturday admission, assigning the workshop to another qualifying attendee or selecting a different time. Don't automatically add a more expensive ticket and take payment without the buyer knowingly choosing the revised purchase.

W3C's form notification guidance recommends understandable feedback that identifies the error and helps people correct it. Apply that to the actual purchase interaction, including keyboard and assistive-technology use. A disabled button with no accessible explanation leaves some buyers unable to discover why they cannot continue.

Make the final review show which person receives which activity. A group buyer should be able to spot that one colleague has printmaking and another has the tour. Clear assignment at this stage also gives support better evidence if someone later says they thought everyone had the same booking.

Then confirm the result accurately. If payment succeeded but an activity remains under review, don't send a message that calls it confirmed. If the entire selection was accepted, show the date, participant and extra without requiring the buyer to reconstruct them from several unrelated emails.

Important restrictions also belong in the offer itself. Australia's competition regulator says ticket sellers must not hide costs or conditions of entry from consumers. That is Australian guidance, but it illustrates why a hidden term is a poor substitute for a clear purchasing decision. Check the obligations applying to your own sale and describe the offer before accepting payment.

Recheck affected extras when a booking changes

An admission can be valid when the extra is purchased and change afterwards. Your process needs an answer when a Saturday ticket moves to Sunday, an attendee is replaced or the original admission is cancelled.

Start by listing the affected extras before completing the change. Moving admission to Sunday should not silently leave a Saturday workshop attached to somebody who can no longer enter that day. Equally, it shouldn't cancel an unrelated shirt order that can still be delivered under its original terms.

Explain the available choices before confirming the amendment. Perhaps the buyer can retain Saturday admission, select an available Sunday activity or request the applicable remedy for an affected extra. Check the terms, circumstances and local obligations. Don't assume that writing a dependency rule gives you a universal right to keep the money for an unusable purchase.

For an attendee substitution, decide which extras move with admission and whether the replacement meets the conditions. A tasting attached to an adult's admission can't simply be handed to a replacement who fails its age requirement. A named workshop reservation may also need a supported reassignment so the delivery team knows who to expect.

Keep unused quantities accurate. If an authorised change removes one of four eligible attendees, work out which dependent booking is affected. Don't arbitrarily cancel the last workshop sold if the group can identify another attendee who will use the place legitimately and your terms permit that reassignment.

Refunds need their own checks. Returning money doesn't always end a booking, and ending a booking doesn't automatically mean every cost or payment has reversed. Identify the admission and activity rights that remain before returning a scarce place to sale. Otherwise, the original customer and a new buyer could both hold apparently valid confirmations.

If the extra itself becomes unavailable, use a separate incident process. Our guide to refunds for unavailable event add-ons works through that response. Here, the priority is spotting when an admission change has made an otherwise available extra impossible for a particular person to use.

Keep a brief history of what changed, who approved it and what the buyer was told. The useful record explains the current booking and the earlier promise. It shouldn't require the activity lead to read an entire support conversation at the workshop door.

Ask your ticketing provider to demonstrate the whole purchase

Turn the rules into a short demonstration brief. Describe your admissions, included benefits, extras and legitimate group purchases. Ask the provider to show what happens through the supported buyer and staff processes, including a returning purchase and an amendment.

Loopyah's ticket-selling tools support ticket types and releases with their own prices and quantities, with confirmation emails linking to QR tickets. Use those capabilities to make the admission offer clear. For a more involved add-on rule, confirm the exact supported setup before promising it to customers.

Creating two ticket types doesn't, by itself, establish that one can only be bought by a holder of the other. A provider needs to show the qualifying-admission check, the per-attendee allowance and the current availability together. Ask to see the result after the buyer removes the required admission or comes back using a later link.

Check the staff view too. Can support explain why a purchase was refused? Can they tell which attendee owns an extra and whether that person still has qualifying admission? If changing the booking requires a managed process, who may perform it and what prevents another seller accepting a conflicting purchase during the change?

The same distinction applies to arrival. A valid event QR scan establishes admission under the supported check-in process. It doesn't automatically prove age eligibility, workshop participation or whether lunch has been collected. Match each delivery task to the record the team actually needs.

Our guide to delivering pre-booked extras covers that handover. Connect it to the purchase rules so staff receive the confirmed participant, item and quantity, with any necessary conditions. The door team shouldn't have to reconstruct whether somebody was entitled to purchase the extra months earlier.

Rehearse the cases most likely to fail

Use your provider's test or demonstration environment, or its approved testing process. You want to learn whether the offer works without creating live charges, false bookings or messages to real customers. Write the expected outcome before running each case, so a plausible-looking screen doesn't become your definition of success.

Start with the ordinary purchases, then change one condition at a time. A useful rehearsal includes these cases:

• Saturday admission with one Saturday workshop succeeds when a place is available; Sunday admission alone is refused with the reason shown.

• A weekend pass qualifies for Saturday, including a legitimate earlier price release with the same access.

• Four admissions support four eligible attendee assignments, while a repeated purchase cannot exceed each person's remaining allowance.

• Two colleagues can book overlapping activities separately, while one participant cannot book an impossible combination under your stated rules.

• Removing qualifying admission from the basket prevents an unsupported dependent purchase.

• A returning attendee can buy through the authorised route, while a forwarded public link doesn't establish eligibility.

• Included benefits, partner allocations and active checkout holds all affect the availability shown.

• An admission date change or permitted transfer identifies affected extras and produces accurate replacement confirmations.

Continue through an unavailable activity, a failed payment and any supported delayed-payment case. Confirm that staff can identify what happened without guessing from a receipt. Where your team cannot simulate a condition safely, ask the provider to demonstrate it and record the limits of what you verified.

Test the words as well as the counts. Ask someone unfamiliar with the setup to explain why their selection was refused and how to correct it. If they can't, revise the explanation. Making the button redder won't tell them that their admission is for the wrong day.

Then run one booking all the way to the activity team. They should find the correct participant, date and entitlement, including an earlier change. Keep the expected and observed results with the operating notes. Repeat affected tests when you change a package or add another selling route.

Measure mistakes as well as add-on sales

Once sales open, watch completed valid purchases alongside refusals and support requests. A blocked purchase can mean your rule prevented a mistake. It can also mean the rule rejected somebody who should qualify. Look at the reason before changing the setting.

For a fictional USD example, suppose 20 mismatched bookings would each require 12 minutes of paid support work. That's four hours. At an assumed staff cost of $30 an hour, including the employer's associated costs, the work costs $120. If the corrections also cause $40 of non-recoverable transaction charges in this example, the direct cost is $160. Those charges are invented assumptions, not a statement about your payment provider's refund policy.

A proposed improvement with a one-time cost of $250 wouldn't pay for itself from that direct cost alone. It might still be worthwhile because it prevents an unfulfillable sale or protects scarce activity places, but explain that decision honestly. If the same 20 mistakes recur across four comparable editions, the assumed direct cost becomes $640, provided the workload and charges genuinely repeat. Check whether the improvement can be reused without further cost before comparing the four-edition saving with that initial price.

Don't count all released staff time as cash saved. If employees remain paid for the same hours, the immediate benefit may be time available for other work. Compare any actual change in staffing, tools and support costs separately from the value of reducing inconvenience and avoiding broken promises.

Also investigate lost legitimate purchases. If weekend-pass holders keep contacting support because the workshop rejects their tickets, repairing that rule could recover sales without weakening the underlying restriction. If customers abandon a valid choice because the explanation is confusing, improve the explanation before removing a necessary check.

Choose one extra and trace it through the whole process before extending the same arrangement to the rest. Confirm who can buy it, how many they can buy, what availability limits it and what happens after a change. Open sales when the buying process, confirmation and delivery team all support that same promise.