Pricing — global vs station overrides
A product has a global price that every station uses. Any station can set its own price for that product instead. These two cover almost every event.
flowchart LR
G["<b>Global price</b><br/><small>set on the product</small>"] --> Q{"Station uses<br/>global prices?"}
Q -- Yes --> A["<b>Global price</b><br/><small>charged at this station</small>"]
Q -- No --> B["<b>Station price</b><br/><small>override for this station</small>"]
class G start
class Q decision
class A,B result
Products sold as part of another product (modifiers, for example the side in a meal) can have their own price in that context. See Modifier pricing below.
Global catalog prices
Set on each product under Global prices: one amount per event credit/token currency (not virtual credit).
These are the prices every station uses unless the station overrides them.
Station overrides
| Setting | Effect |
|---|---|
| Use global catalog prices (on) | Station sells at the product’s global prices |
| Use global catalog prices (off) | Enter per-currency station price overrides |
The products table shows an Override badge when a station is not using globals.
Taxes are not overridden at the station—tax rates come from the product’s catalog tax picks when Taxes are enabled.
Station overrides apply to that station’s sellable products. Modifier group prices are separate: see below.
Modifier pricing (meals and add-ons)
Modifiers are not a step between global and station prices. A modifier has its own price inside its group, which applies only when it is chosen on a parent product.
flowchart LR
M["<b>Modifier chosen</b><br/><small>for example, the side in a meal</small>"] --> Q{"Group uses<br/>catalog prices?"}
Q -- Yes --> P["<b>Product's own price</b><br/><small>global or station</small>"]
Q -- No --> G["<b>Group price</b><br/><small>for example £0.00 or +£1.00</small>"]
class M start
class Q decision
class P,G result
Modifier group prices
On a modifier group, each modifier product can:
- Use product catalog prices (same as selling it alone), or
- Set group catalog prices for all currencies — including £0.00 (included) or a smaller add-on amount.
Group prices apply on every parent product that attaches that group. There is no separate “per parent” modifier price in Dashboard.
Worked examples: Burger + Fries
A. Independent products (à la carte)
Create two standard products and sell them separately (or ring both lines on the same ticket):
| Product | Mode | Global price | How it is sold |
|---|---|---|---|
| Burger | standard | £10.00 | Own POS button |
| French Fries | standard | £5.00 | Own POS button |
Basket: Burger £10 + Fries £5 = £15.00.
Each line uses its own catalog (or station) price. No modifier group is required.
B. Burger Meal combo (price on the parent; sides included or topped up)
Keep Burger and French Fries as catalog products so Fries can still be sold alone. Add a meal product that carries the combo price, and attach a side-choice modifier group where Fries is priced for the meal context—not at its standalone price.
| Product | Mode | Global / role |
|---|---|---|
| Burger Meal | standard (parent) | £12.00 — price of the meal |
| Burger | standard or used as structure | Often not charged again as a separate line when the meal is the sellable parent |
| French Fries | standard (also used as modifier) | Standalone £5.00; in the meal group £0.00 (included) |
| Onion Rings | standard / modifier | Standalone e.g. £4.00; in the meal group +£1.00 (upgrade) |
Modifier group: “Choose your side” (purpose choice, min 1 / max 1)
| Option | Catalog standalone price | Price in this group |
|---|---|---|
| French Fries | £5.00 | £0.00 (included in meal) |
| Salad | £4.00 | £0.00 |
| Onion Rings | £4.00 | £1.00 (add-on / upgrade) |
On Touch
- Cashier taps Burger Meal → basket line £12.00.
- Must pick one side. Fries or Salad add £0; Onion Rings add £1.00.
- Optional extras (cheese, bacon) live in a separate
addongroup with their own group prices (e.g. Cheese +£1.00).
Mental model
- Parent product = what the guest is buying (the meal) and usually where the main price lives.
- Modifiers = choices and extras. Their group price is what matters on that parent—not the product’s shelf price.
- Reuse the same Fries SKU for à la carte and meals; only the modifier-group override changes the meal price.
C. What not to do
- Do not create “Fries (meal)” as a second product just to get a £0 price—use a group price override on the shared Fries product.
- Do not put the full meal price only on Fries/Burger children if the parent is what cashiers tap; guests and reporting expect the meal line to carry the combo amount.
Recommended pattern
- Set correct global prices for every product you sell alone (Burger £10, Fries £5).
- For combos, put the meal price on the parent and override modifier prices inside the group (£0 included, or small add-ons).
- Override at the station only for venue-specific menus (VIP bar premium, etc.).