A price rule prices the same way on every channel your guests buy through, with one exception. Capacity-based rules let you pick the channels, so you can run capacity pricing online and keep front counter prices flat.
Use this page to check where a rule prices before you build it, and to work out what a guest pays when a booking changes after it's sold.
Which channels each rule type prices
Sales channel | Quantity-based | Time-based | Early bird | Capacity-based (beta) |
|---|---|---|---|---|
Online checkout (and API) | Automatic | Automatic | Automatic | Your choice |
POS | Automatic | Automatic | Automatic | Your choice |
Venue Manager | Automatic | Automatic | Automatic | Your choice |
Legacy checkout | Standard rate | Standard rate | Standard rate | Standard rate |
Self-serve kiosks | Standard rate | Standard rate | Standard rate | Standard rate |
Automatic means you set the rule up once and it prices there with no further setup. Your choice means you select the channel on the rule itself.
Standard rate means the channel charges the product's normal price, ignoring the tiers. Guests can still buy. They just don't get tier pricing on that channel.
Where a price rule prices automatically
For quantity-based, time-based and early bird rules, you don't choose channels. Apply the rule to a product and it prices in the online checkout, at POS and in Venue Manager, in every case.
That's what keeps a single rule consistent. The same "Weekend pricing" rule gives a guest the same weekend price whether they book on their phone the night before or walk up to the counter.
Choosing channels on a capacity-based rule
Capacity-based rules are the exception. When you create one, you select which channels the tiers price on, under Sales channels:
Progressive Checkout & API
Point of Sale
Venue Manager
Select at least one. A channel you leave out charges the product's base price, whatever the capacity is.
The base price is what makes this work. You set it in the variations table alongside the tier prices, so every channel has a price to fall back on. See Create a capacity-based price rule (Needs verification).
Choosing channels is a property of the rule, not the product. A capacity-based rule reused across five products prices the same channels on all five. To price different channels, build a second rule.
What a guest pays when a booking changes
A booking that's already been paid for can still change. A guest reschedules, staff add a ticket at the counter, someone edits it in online accounts. What happens to the price depends on the rule type, and the four types do not behave the same way.
Rule type | Tickets added or removed | Booking moved to a new date or time |
|---|---|---|
Quantity-based | Moves to the tier the new quantity falls into | No change. Quantity tiers count tickets, not dates |
Time-based | Added tickets price at the tier for that session | Moves to the tier that date or time falls into |
Early bird | [CONFIRM: whether added tickets take the original lead-time rate or today's] | Holds the rate from the original booking date |
Capacity-based (beta) | Holds the price the booking was sold at, on any channel | [CONFIRM: whether the hold survives a change of date] |
The rule holds wherever the change is made. A booking edited by a guest in online accounts, by staff at POS or by staff in Venue Manager follows the same row.
The split is deliberate. Quantity-based and time-based rules price what's in the booking now, so changing the booking changes the price. Early bird and capacity-based rules price when the booking was made, so the original price is the one that counts.
This is separate from editing the rule itself. Changing a tier price updates new bookings only. Bookings already taken keep the price they were sold at, on every rule type.
FAQs
Can I run a price rule online but not at the counter?
On a capacity-based rule, yes. Clear Point of Sale under Sales channels and POS charges the base price. The other three rule types price every channel automatically, so the way to hold a counter price steady is to use a separate product rather than a rule.
Why is a guest at the kiosk paying a different price?
Self-serve kiosks and the legacy checkout charge the product's standard rate. They don't read price rule tiers, so a guest buying there pays the normal price while the same ticket in the online checkout follows the rule.
Does the API follow price rules?
Yes. The API prices alongside the progressive online checkout and is covered by the same channel selection on a capacity-based rule.
A guest added tickets to a booking and the price didn't change. Why?
Check the rule type. Early bird and capacity-based rules hold the original price by design. See the table above. On a quantity-based rule, tickets only count toward a tier when they're for the same product, date and session time.