The Pricing tab on the event editor controls everything about what customers pay: the pricing model (per-person or flat), one or more pricing categories with tiered rates by participant count, per-category min/max/default participant rules, and optional deposits. Deposits can be a fixed amount or per-participant, and you can require only a deposit at checkout with the balance collected later.
Getting started
Open Events > Event settings, pick an event, and switch to the Pricing tab in the event editor.
How it works
The Pricing tab is organized into three sections:
- Pricing model: pricing type (per-person or flat) and four global toggles that affect how prices show on the booking site
- Pricing categories: one or more named categories (e.g., Adult, Child) with tiered rates by participant count plus per-category min/max/default participant rules
- Deposits: optional deposit amount that can be required at checkout, with the remainder collected later
Pricing on a booking slot can override these event defaults. See Booking slots for slot-level overrides.
Step-by-step guide
Pick a pricing model
On the Pricing tab, find the Pricing model section. Pick a Pricing type from the dropdown:
| Option | Behavior |
|---|---|
| Per person | Each participant in a category multiplies the per-person rate. Common for ticket-style events |
| Flat | A single fixed price for the entire booking, regardless of group size. Common for private experiences |
Configure the global toggles below the dropdown:
| Toggle | Effect |
|---|---|
| Category pricing is cumulative | Combines participant counts across categories when picking a tier. With it on, 2 adults + 2 children = 4 total for the tier match. With it off, each category's count is evaluated alone |
| Hide pricing rate on booking site | Hides the per-ticket rate from customers and only shows the line total. Useful when you don't want to advertise per-person prices |
| Limit to one category per purchase | Forces customers to pick a single category per booking instead of mixing categories. With it off, customers can combine multiple categories in one booking |
Click Save at the bottom of the editor.
Add a pricing category
- On the Pricing tab, find the Pricing categories section
- Click Add new category
- A new category row appears with a Name input and one tier row underneath
- Set the Name (e.g., "Adult", "Child", "Senior")
- Configure the first tier (see below)
- Click Save
Configure tiered pricing within a category
A pricing category can have one or many tiers. Each tier covers a range of participants and sets a price that applies when the participant count falls in that range.
Inside a category row, find the tier row(s) under Per participant pricing and set:
| Field | Description |
|---|---|
| Minimum participants | The smallest group size this tier covers (auto-validated against the previous tier's max) |
| Maximum participants | The largest group size this tier covers |
| Price | The price applied at that tier (per participant for Per person, or as the flat price for Flat) |
Click the + at the right end of the last tier row to add another tier, or the - on any tier (other than the first) to remove it. Save the event when you're done.
Tiers run in order: a 1-2 participant tier at $40, a 3-4 tier at $35, and a 5+ tier at $30 means a group of 4 pays $35 each. With Category pricing is cumulative on, all categories' counts combine when matching the tier.
Set per-category participant rules
Each category has three additional fields that constrain bookings:
| Field | Description |
|---|---|
| Minimum required | Minimum number of participants in this category for the booking to be valid (e.g., "at least 1 adult") |
| Maximum allowed | Maximum participants of this category per booking (e.g., "no more than 4 children") |
| Default | The number of this category preselected when the customer opens the booking flow |
Set these on each category row and save the event. The customer's booking flow enforces these rules at checkout.
Remove a pricing category
- On the category row, click the three-dot menu
- Click the remove option in the menu
- Save
If a category is in use on existing bookings, removing it doesn't retroactively change those bookings, but no new bookings can use the removed category.
Configure deposits
On the Pricing tab, scroll to the Deposits section and toggle Allow deposit on. The deposit fields then appear:
| Field | Description |
|---|---|
| Require only deposit amount during checkout | When on, customers can pay only the deposit at checkout and the remainder is collected later (typically at the venue). When off, customers can pay either the deposit or the full price |
| Deposit type | Per booking (a single fixed deposit per booking, regardless of participants) or Per participant (deposit multiplied by participant count) |
| Deposit amount | Numeric value with currency prefix. Min 0, precision 2, step 0.1 |
Save the event when you're done.
Disable deposits
- Toggle Allow deposit off
- Save
- Customers can no longer pay a partial amount; the full price is required at checkout
Reference
Pricing model section
| Field | Type | Notes |
|---|---|---|
| Pricing type | Dropdown | "Per person" (id: 1) or "Flat" (id: 2) |
| Category pricing is cumulative | Toggle | Combines participant counts across categories for tier matching |
| Hide pricing rate on booking site | Toggle | Hides per-ticket rate from customers |
| Limit to one category per purchase | Toggle | Forces single-category bookings |
Pricing categories section
| Element | Description |
|---|---|
| Add new category | Adds a new category row with one initial tier |
| Name | Required category label (e.g., Adult, Child, VIP) |
| Tier row | Minimum participants, Maximum participants, Price |
| Add tier (+) | Adds another tier to the same category |
| Remove tier (-) | Removes a tier (only on tiers other than the first) |
| Minimum required | Per-category floor: minimum participants of this category |
| Maximum allowed | Per-category ceiling: maximum participants of this category |
| Default | Pre-selected count when the booking flow opens |
| Three-dot menu (per category) | Includes the Remove category action |
Deposits section
| Field | Type | Notes |
|---|---|---|
| Allow deposit | Toggle | Master switch for deposits. Off hides the rest of the deposit fields |
| Require only deposit amount during checkout | Toggle | When on, customer can finish checkout with only the deposit |
| Deposit type | Dropdown | "Per booking" (id: 0) or "Per participant" (id: 1) |
| Deposit amount | Number | Currency prefix, min 0, precision 2, step 0.1 |
Validation behavior
Saving the event validates pricing categories. If any tier has min greater than max, missing fields, or invalid prices, the form blocks save and surfaces the errors inline.
Good to know
- Per-person vs Flat: per-person pricing is best when group size matters to your costs (more people = more wear, more facilitator effort). Flat pricing is best when you're selling a private experience that doesn't scale with group size.
- Tiered pricing is a powerful way to reward larger groups. A 1-2 tier at $40, 3-5 tier at $35, 6+ tier at $30 makes the experience cheaper per person as the group grows.
- Cumulative pricing is most useful when adults and children should count the same for tier matching. Without it, 2 adults + 2 children might land in different tiers from 4 adults, which is rarely what you want.
- Hide pricing rate is useful for premium experiences where you'd rather show "Total: $200" than "$50 per person × 4". Customers see the cleaner total and don't fixate on the rate.
- Limit to one category per purchase simplifies checkout for venues where mixing categories isn't valid (e.g., adults-only events that still want a separate "VIP" category for higher-paying customers without combining with regular adult tickets).
- Per booking vs Per participant deposit: per booking is simpler ("$50 deposit, period"). Per participant scales with group size and is better when your costs scale with people.
- Require only deposit at checkout lets you collect a small commitment online and the balance at the venue. This is great for high-value experiences where customers might be more comfortable paying a partial amount up front.
- Pricing on a specific booking slot can override the event-level pricing. Use slot overrides for one-off promotions or special pricing on holidays.
FAQ
Q: When does the customer pay the remainder of a deposit?
A: When Require only deposit amount during checkout is on, the remainder is recorded as outstanding on the transaction. Collect it at the venue with Take payment on the booking, or send a payment link from the transaction page.
Q: Can different events have different pricing categories?
A: Yes. Categories are configured per event. An "Escape Room" event can have Adult / Child / Senior; a "Private Hire" event can have just one Flat category.
Q: Can the same customer mix categories in one booking?
A: Yes, unless Limit to one category per purchase is on. Without that toggle, a customer can book 2 adults, 1 child, and 1 senior in one transaction.
Q: What does "Category pricing is cumulative" do exactly?
A: It changes how tiers are matched when there are multiple categories. With it on, 2 adults + 2 children counts as 4 total participants when picking which tier of the Adult category applies (and the same for Child). With it off, the Adult tier is picked based on the 2 adults alone, and the Child tier based on the 2 children alone.
Q: What's the difference between Minimum required and Minimum participants on a tier?
A: Minimum required is per-category and means "this category must have at least N participants in any booking". Minimum participants is per-tier and means "this tier covers groups of this size". They're independent rules.
Q: How do deposits show on the customer's transaction?
A: The transaction records the deposit as paid and the remainder as outstanding. The full price is captured as the transaction total. The customer's receipt shows both.
Q: Why is my pricing not showing on the booking site?
A: Make sure you've added at least one pricing category with at least one valid tier and saved the event. Also confirm the event is enabled on the booking site template.