High and low season (calendar prices)
Example: a party room costs € 200 per part of day in low season (Jan–May) and € 300 per part of day in high season (Jun–Aug). A customer books a part of day in July.
What does the customer see?
July is in high season, so the rate of the High schema group applies:
| Description | From date | From time | To time | Quantity | Subtotal |
|---|---|---|---|---|---|
| Room hire (high season) | Wed 15 Jul 2026 | 13:00 | 17:00 | 1 | € 300.00 |
| Total | € 300.00 |
When to use this
- You want prices to depend on the date, not only on the weekday or time.
Step 1 — Period
| Setting | Value |
|---|---|
| Unit | Minutes (or Days for day rentals) |
| Length (timespan) | length of the bookable block |
Step 2 — Price schema
Note: in time mode the system automatically turns each price row you add into 7 rows — one per weekday (Sun–Sat). Each row defaults to the whole day (0:00–24:00) at price 0. You then only adjust the price (and optionally the time window) on the days you need.
Create two schema groups (field Schema group), each with its own price rows:
| Setting | Value |
|---|---|
| Schema group Low | price row(s) with € 200 |
| Schema group High | price row(s) with € 300 |
Step 3 — Calendar
Go to Views → Calendar and link date ranges to a schema group:
| Setting | Value |
|---|---|
| 01-01 to 31-05 | Schema group Low |
| 01-06 to 31-08 | Schema group High |
| other dates | Schema group Low |
The calendar now determines which price group applies for each booking date. Want to vary per day or time within a season too? Just add more rows inside the schema group.
