When a ticket qualifies for more than one discount, Entase needs a rule to decide what the buyer actually pays. This article explains the default behavior and the exception for coupons created with price policy stacking.
On the Price Policies and Coupons pages, you can click
Default behavior: greatest discount wins
By default, discounts do not stack. When multiple discounts apply to the same ticket, Entase applies only the single greatest discount.
What counts as a discount?
- Reductions defined in your price policy rules (for example, an early-bird or member rate)
- A coupon the buyer enters at checkout
Example — no stacking
| Discount source | Value |
|---|---|
| Price policy — Early Bird | 15% off |
| Coupon — SUMMER10 | 10% off |
When the buyer applies the coupon, the price policy discount is cleared. The buyer gets 10% off from the coupon only.
If the coupon were 20% off instead, the buyer would get 20% off from the coupon only.
This prevents accidental over-discounting when buyers hold both a promotional coupon and an already-reduced ticket type.
Price policies vs. coupons
When a buyer applies a coupon, any discounts from price policies are cleared. Only the coupon discount applies, even if the price policy discount would otherwise be greater.
The exception is a coupon created with the with price policy stacking option. With this option, the coupon discount is calculated on top of any applicable price policy discount.
When stacking is enabled:
- Entase first applies any matching price policy discount to the base ticket price.
- The coupon discount is then calculated on the already-reduced price.
The two discounts are applied sequentially, not added together as a flat sum.
Example — stacking enabled
Base ticket price: €100
| Step | Discount | Resulting price |
|---|---|---|
| 1 | Price policy — Member rate: 20% off | €80 |
| 2 | Coupon — LOYALTY5: 5% off | €76 |
The buyer pays €76, not €75 (which would be the result of naively adding 20% + 5% = 25% off €100).
Example — stacking enabled, coupon is percentage vs. fixed
Base ticket price: €50
| Step | Discount | Resulting price |
|---|---|---|
| 1 | Price policy — Student rate: 10% off | €45 |
| 2 | Coupon — EXTRA3: €3 fixed off | €42 |
The fixed-amount coupon deducts from the post-policy price, so the buyer pays €42.
Choosing the right approach
| Goal | Setting to use |
|---|---|
| Protect margins; do not combine coupon and price policy discounts | Create the coupon without price policy |
| Reward loyal buyers who also qualify for a rate | Create the coupon with price policy |
| Run a targeted promotion on top of existing pricing | Create the coupon with price policy |
Tip: Use stacking sparingly and always preview the final price before publishing a campaign. A stacked percentage coupon on an already-heavily-discounted price policy can result in a lower price than intended.
How to enable stacking on a coupon
Choose the with price policy option when you create the coupon. For the full coupon creation process, see Creating a coupon.
From that point on, any ticket that qualifies for both a price policy discount and this coupon will have both applied in sequence.