Coupon stacking rules are the venue-side settings that decide whether more than one discount, promo code or voucher can apply to a single booking. The safe default is stacking off, with exceptions turned on only for tightly controlled cases like an approved corporate rate. Some platforms enforce this through usage limits and arrival window checks, not guesswork.
TL;DR:
- Most systems treat “stackable” as a binary setting, with “no” blocking any second promotion from applying and “yes” allowing multiple discounts, which increases risk.
- Gift cards generally stack with coupons by applying to the final balance, while vouchers tend to be exclusive, and bundle discounts require caps to prevent excessive combined discounts.
- Proper promotion setup involves configuring purchase and arrival windows, usage limits, and priority order, with staging tests essential before going live.
- Per-transaction caps and strict policy controls help protect margins by preventing overly large discounts from stacking beyond acceptable levels.
- Regular monitoring and reporting are crucial to catch unexpected promotion combinations, especially ones left enabled after campaigns end.
Table of Contents
- How booking systems process stacking and promotion priority
- Coupons, vouchers and bundle discounts don’t behave the same way
- Setting up stacking, windows and usage caps correctly
- Three worked examples for escape room bookings
- Testing stacking rules in staging before you go live
- Protecting margin while still using promotions strategically
- What running promotions across escape room venues actually teaches you
- Manage stacking safely with Riddlio
- Where to check the settings yourself
- Sources
- FAQ
How booking systems process stacking and promotion priority
Most booking engines treat “stackable” as a binary setting attached to each coupon or promotion. Set it to “No” and the system blocks a second code from applying once one is active. Set it to “Yes” and multiple discounts can combine on the same booking, which is powerful and risky in equal measure.
Behind that toggle sits a validation sequence. A code gets checked for existence, then whether it is currently enabled, then against usage limits, then against activity or equipment eligibility, and finally against the booking’s timing windows before the discount is applied, as Resytech’s coupon documentation describes it.
Where things get complicated is priority order. Some platforms use a “stop if matched” rule: once a promotion matches a booking, the engine either consumes the matched items or halts further promotion checks entirely, depending on configuration, according to BookingLive’s promotions documentation.
- A “No” stackable setting blocks any second code from applying to the same booking.
- The validation order runs code lookup, enabled check, usage limits, eligibility match, then window checks.
- “Stop if matched” processing means the first promotion attempted can prevent later ones from firing, so the order you set promotions in changes the outcome.
Coupons, vouchers and bundle discounts don’t behave the same way
Not every discount type interacts the same way with others, and treating them identically is where most stacking errors start.
Gift cards typically act as a payment method rather than a discount. They apply to the balance left after coupons and other discounts have already reduced the price, so they commonly stack with coupons without any special configuration.
Vouchers are different. A voucher that functions like a pre-paid ticket is usually built to be exclusive: it cannot be combined with coupons or manual price overrides, and Resytech’s activity voucher documentation treats it as its own redemption flow rather than a discount layered on top of others. Bundle or bulk-booking discounts sit somewhere in between. They can often run alongside a coupon, but per-transaction limits are what stop that combination from producing an outsized discount on a large group booking.
- Gift cards apply to the final balance after other discounts, so they usually stack by default.
- Vouchers behave like pre-paid tickets and are best treated as exclusive, not stackable.
- Bundle or bulk discounts can coexist with coupons, but need a per-transaction cap to limit exposure.
Getting this distinction wrong in your promotion setup is the fastest way to turn a marketing campaign into a margin problem.
Setting up stacking, windows and usage caps correctly
Coupon editors give you a specific set of fields, and each one changes how a promotion behaves at checkout.
- Set a purchase window for when a customer can apply the code, and a separate arrival window for when the booked session must occur. Resytech’s coupon rules guide treats these as distinct checks, so a code bought in December can still be restricted to sessions in January.
- Use negated windows to block out holidays or peak dates instead of building dozens of narrow allowed windows. Negated windows take precedence and are simpler to maintain.
- Decide on per-code versus overall usage limits. A per-code cap limits how many times one specific code is redeemed; an overall limit caps total redemptions across a campaign.
- Choose whether the promotion is stackable and whether it should stop if matched once applied, which prevents a second promotion checking against the same booking.
- Set priority order so corporate or partner codes are evaluated before public campaign codes, since the first match can determine what else is allowed to apply.
Pro Tip: Build every new promotion in a disabled state first, then enable it only after a staging test confirms the windows and limits behave as intended.
Three worked examples for escape room bookings
Numbers make stacking rules concrete faster than settings screens do.
Early-bird plus group discount. A booking for six players at a session priced at $30 per player totals $180. With stacking off, only the larger of the two discounts applies. With stacking on, an early-bird 10% code and a group 15% code both apply, taking the total down further, which is exactly the scenario platforms flag as needing per-transaction limits to control.
Gift voucher plus promo code. A $50 gift card is not a discount, it is a payment method. A coupon reduces the room price first, then the gift card balance is deducted from what remains, following the sequence Zuddl’s coupon documentation describes for stackable and per-transaction-limited discounts.
Corporate booking with approved stacking. A venue may allow a negotiated corporate code to stack with a seasonal promotion for a single approved client, provided a per-transaction limit caps the combined discount.
- Early-bird and group discounts multiply fast once stacking is on, so a cap matters more than the individual rates.
- Gift cards apply after coupons, not before, which is why final totals often surprise front-desk staff.
- Corporate stacking should always carry a documented approval and a cap.
A per-transaction limit is one of the clearest levers venues have for controlling how many units a single coupon can touch, and Zuddl’s documentation notes that platforms allocate the discount to the highest-value units first when that limit is in place.
Testing stacking rules in staging before you go live
A new stacking rule should never meet a paying customer before it meets a staging environment.
- Mirror your live pricing, slots and active promotions in staging so test results reflect real conditions.
- Run every realistic permutation: single coupon, stacked coupons, coupon plus gift card, voucher alone, and corporate combinations.
- Check the resulting transaction logs and invoices line by line, including what a refund looks like once a stacked discount has been applied.
- Run a short pilot on a small slice of real bookings before a full rollout.
- Track discount rate and average order value during the pilot to catch anything the test cases missed.
Pro Tip: Keep a written record of every test case and its expected outcome, so a future rule change can be checked against the same baseline instead of starting from scratch.
Protecting margin while still using promotions strategically
The policy layer matters as much as the technical settings.
- Default every new coupon and promotion to non-stackable; document any exception and who approved it.
- Apply both a per-transaction cap and an overall usage limit so a single booking or campaign cannot erode margin beyond a known ceiling.
- Require managerial sign-off before enabling stacking on any code that exceeds a set discount threshold.
- Set up automated reports that flag bookings with unusually high combined discounts so issues surface within days, not at month-end reconciliation.
None of this requires turning down promotions altogether. It just means every stacked discount should be a decision someone made on purpose, not a default the system fell into.
What running promotions across escape room venues actually teaches you
The surprises rarely come from the discount itself. They come from a promotion left stackable by default months after the campaign that needed it ended, quietly combining with a new one nobody tested together.
The fix isn’t cleverness, it’s habit: stage every rule change, check the transaction log, and let a report flag anything unusual before a customer or a manager finds it first. Reporting tools exist to catch a discount pattern before it becomes a quarter’s worth of lost margin.
— Iosif Beraru
Manage stacking safely with Riddlio
Riddlio gives escape room venues coupon rules, voucher sales and redemptions, and usage limits in one dashboard, so a stacking decision does not have to be a guess.
You can build a promotion in a disabled state, test it against real slot data, and check the reporting before it ever reaches a customer. Gift vouchers are sold and redeemed through the same system that runs your booking calendar, and dynamic pricing tools sit alongside promotions rather than fighting them. If you are ready to see how this fits your venue, check Riddlio’s pricing for the Starter, Pro, Unlimited and Enterprise plans.
Where to check the settings yourself
For the exact fields behind these rules, see Resytech’s guide to purchase and arrival windows, BookingLive’s promotion priority documentation, and a partner guide on stacking ticket discounts in 2026 for live-event examples.
Sources
- Coupons | Resytech Docs
- BookingLive Promotions: Add / Configure Discounts & Vouchers : Helpdesk
- Coupons | Zuddl Docs
FAQ
What does “coupon stacking” mean for a booking system?
Coupon stacking means allowing more than one discount code, voucher or promotion to apply to the same booking at once. Most systems control this with a stackable toggle set per coupon, and the safe default is to leave it off unless a scenario is deliberately approved.
Do gift cards count as stacking with coupons?
Gift cards usually act as a payment method applied to the balance left after coupons reduce the price, so they commonly combine with coupons without triggering stacking restrictions. Vouchers that work like pre-paid tickets are typically treated as exclusive instead, following Resytech’s voucher documentation.
What is a purchase window versus an arrival window?
A purchase window controls when a customer can apply a code at checkout, while an arrival window controls when the booked session itself must fall for the discount to count. Both are checked separately, and Resytech’s configuration guide recommends negated windows for blackout dates rather than many narrow allowed windows.
Should escape room venues ever allow stacking?
Stacking works best as an exception rather than a default, reserved for approved cases like a negotiated corporate rate with a documented cap. Outside that, per-transaction limits and overall usage caps keep any single booking from combining discounts beyond what the venue intended.
How should a new stacking rule be tested?
Test it in a staging environment that mirrors live pricing and slots, running every realistic combination of coupons, vouchers and gift cards before publishing. Check the resulting transaction logs and run a short pilot while tracking discount rate and average order value.