Pricing Rules
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
Pricing rules automatically change a single ticket type's price without manual editing — raise the price as an event fills up, or move to a higher tier once an early-bird window closes.
What you can do here
- Add a rule to any one ticket type, either Time-Based (price changes during a date/time window) or Demand-Based (price changes once a percentage of capacity has sold).
- Set its priority relative to other rules on the same ticket type.
- Activate, deactivate, edit, or delete any existing rule.
How to add a rule
- Choose the Ticket Type the rule attaches to.
- Pick Time-Based or Demand-Based.
- Enter either a New Price (a flat override) or a Discount % (a percentage off) — at least one is required.
- For Time-Based, set a start and/or end; for Demand-Based, set the Demand Threshold %.
- Set a Priority if this ticket type has more than one rule, then save.
Settings explained
- New Price — replaces the ticket's price outright. If both New Price and Discount % are filled in on the same rule, New Price wins.
- Discount % — a percentage taken off the ticket's base price.
- Priority — the tie-breaker when a ticket type has more than one active rule at the same moment. Lower numbers are evaluated first, and only the first matching active rule is applied — rules never stack with each other (a flash sale is the one thing that stacks on top of a rule; see below).
- Start / End (Time-Based) — leaving either blank means no limit on that side.
- Demand Threshold % (Demand-Based) — the rule activates once this percentage of the ticket type's own capacity has sold. A ticket type with no capacity limit can never trigger a demand-based rule, since there is no percentage to compute.
How the final ticket price is worked out
Wherever a ticket type's price is shown — the event page, checkout, or the “current price” hint on Ticket Types — it is calculated in this order:
- Start from the ticket type's base price.
- Apply the one active pricing rule with the lowest priority number, if any (a New Price override, or a Discount % off the base price).
- If an active flash sale also covers this ticket type, take its discount percentage off the result of step 2 — flash sales and pricing rules stack, one on top of the other.
- Whatever the combined discount, the final price is floored at 10% of the original base price — no combination of a rule and a flash sale can discount a ticket by more than 90%.
That is the exact amount charged when a ticket type is bought individually. It is not what is charged when the same ticket type is bought inside a bundle — a bundle has its own flat price, set on the Bundles page, unaffected by pricing rules or flash sales on its component ticket types. Finally, a discount code entered at checkout is applied last, on top of whichever subtotal results — the combined price of individually bought tickets, or the bundle price.
Good to know
- A rule attaches to exactly one ticket type — to give several types the same time-based or demand-based treatment, add the rule to each one.
- Deactivating a rule, rather than deleting it, is reversible and keeps its settings for later.
- Demand-based thresholds are compared against the ticket type's own capacity, not the event's overall capacity.
Troubleshooting
- Price did not change even though the threshold was passed — check the rule is Active; also confirm the ticket type has a capacity limit set, since unlimited-capacity types never trigger demand-based rules.
- A rule seems to be ignored — another active rule on the same ticket type has a lower priority number and is winning instead. Only one rule ever applies at a time.
- New Price field seems to do nothing — if both New Price and Discount % are set on the same rule, New Price always takes effect; clear it to use the percentage instead.
- Combined discount looks smaller than the rule and flash sale percentages added together — the two apply multiplicatively, one on top of the other rather than added, and the result is capped at 90% off the base price.