Overview
The Availability tab answers four questions: when a product runs, how far ahead and up to when it can be booked, how a booking confirms, and how much capacity there is. All times are interpreted in the product’s timezone (defaulting to your organization’s), shown throughout the tab.
Booking Window
- Advance Booking (Days) — how far into the future the calendar is open for booking (defaults to 90 days).
- Booking Cutoff — how long before the start time bookings close (defaults to 0, i.e. right up to start).
How a Booking Confirms
The Capacity/Inventory choice decides whether a booking is accepted automatically:
- Free & Unlimited — no capacity limit; every booking confirms.
- Limited — confirmed only while capacity remains. This is the usual choice for tours and timed entries.
- On Request — a tentative booking that you confirm manually.
For Limited products, set a Ticket Issue mode — when the ticket is actually issued: Immediate (automatic, ~5 minutes), 1 Hr or 24 hrs (both manual), or Post Documentation.
Capacity
For anything other than Free & Unlimited, capacity is resolved in layers, each taking precedence over the one before it:
- Default Capacity — the baseline number of spots. If a booking matches nothing more specific, this applies. With no Default Capacity set, the product is unavailable.
- Rules — replace the default when their conditions match (see below).
- Overrides — a dated override wins over both the default and any rule for the dates it covers. Set its quantity to 0 to close out those dates entirely (a sold-out weekend, a maintenance day).
A linked schedule can also carry its own capacity, which overrides the Default Capacity for the days that schedule governs.
Within that capacity, a pax type or variant item can carry its own Capacity per date / slot (set in the item dialog on the Price tab): 100 male and 90 female places, 40 front-row seats. An add-on item can draw on another product’s stock (Draws stock from), e.g. 10 rental bikes a day shared by several tours. See Setting Up Product Pricing.
Capacity Rules
Capacity rules give one product different capacity in different circumstances — a smaller group size on a particular time slot, more seats on a schedule, a cap when a specific option is chosen. Open Add a Rule under the Default Capacity and define:
- Conditions — one or more tests, each a field, an operator and a value, with whether all or any must be met.
- Result — the capacity (Qty) to use when the rule matches. It replaces the Default Capacity; it is not added to it.
Fields you can test
| Field | Applies to | What it holds |
|---|---|---|
| Option | any | The variant or package item(s) selected. |
| Schedule | Experiences with schedules | A schedule covering the booked date or slot. |
| Time Slot | Experiences booked by Date & Time | The booked start time. |
These are selection fields, so the operators are All of / Any of / None of.
Which rule wins: when more than one capacity rule matches a booking, the one giving the highest Qty wins. Write conditions that do not overlap so the intended rule is the one that applies. A rule’s result that comes to 0 makes that booking unavailable.
The editor also lists a Store field, but store-based capacity is not yet applied at booking time — use a dated Override or a per-schedule capacity to vary capacity by store for now.
Scenarios
Smaller group on the sunset tour. Time Slot Any of “Sunset” → Qty 8, while the rest of
the day runs at the Default Capacity.
More seats on a weekend schedule. Schedule Any of “Weekends” → a higher Qty than the weekday default.
Cap a premium option. Option Any of “VIP box” → Qty 10, limiting how many of that
variant can be sold even though the general capacity is larger.
Close a slot without touching dates. A rule whose result is 0 (e.g. Time Slot Any of a
retired slot) makes that slot unavailable. For a date-bounded close-out, use an Override of
0 instead.
Schedules and Calendars
- Applicable Calendars — link a central calendar to control closed days and special days across products.
- Applicable Schedules — link one or more schedules to limit which days and months the product runs. If none are linked, the product is available on all days and months.
Each linked schedule carries:
- Operating Hours — one or more windows (Start/End time), or 24 Hours for an all-day window.
- Capacity — overrides the Default Capacity for this schedule.
- Closed — marks the schedule as accepting no bookings.
Booking Slot
The Booking Slot mechanism sets how a customer picks a time:
- Pass — no date selection; open on any day, subject to the schedule and rules. Use this for passes, open-dated tickets and multi-day rentals.
- Only Date — the customer picks just a date.
- Date & Time — the customer picks a date and a start time.
Daily Slots (Date & Time only)
When the mechanism is Date & Time, define the start times under Daily Slots. Each slot has:
- Name — an internal label (e.g. “Morning departure”).
- Start Time — in the product timezone; can be a departure or door-opening time.
- Duration — measured from the start time.
- Applicable Schedules — which schedules the slot belongs to. Leave empty to make it available to all schedules (e.g. restrict a sunset slot to a summer schedule).
A slot’s dialog does not set its own capacity. To give a specific slot a different capacity, use a capacity Rule (by time slot) or a dated Override in the Capacity section above.
