Charge a room per part of day
Example: a room is rented per part of day: morning (09:00–13:00) € 120, afternoon (13:00–17:00) € 150 and evening (17:00–21:00) € 180. A customer books the afternoon.
What does the customer see?
| Description | From date | From time | To time | Quantity | Subtotal |
|---|---|---|---|---|---|
| Room hire afternoon | Thu 23 Jul 2026 | 13:00 | 17:00 | 1 | € 150.00 |
| Total | € 150.00 |
When to use this
- The customer books a fixed block of the day, not a loose number of hours.
- Each part of the day has its own time window and rate.
There are two ways to set this up. Choose the variant that fits best.
Variant 1 — Three periods with period price
You create three 4-hour periods, each with its own price. In the price schema you let the price come from the period (Period price).
Period
Go to Views → Period and create three periods:
| Setting | Value |
|---|---|
| Morning | Minutes, timespan 240 (4 hours), price € 120 |
| Afternoon | Minutes, timespan 240 (4 hours), price € 150 |
| Evening | Minutes, timespan 240 (4 hours), price € 180 |
Price schema
Create a schema row per part of day and link the matching period:
| Setting | Value |
|---|---|
| Period | morning / afternoon / evening (the right one per row) |
| Price type | Period price (price comes from the period) |
| From / To | 09:00–13:00, 13:00–17:00, 17:00–21:00 |
| Calculation | Total price |
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.
Sub-variant: more expensive evening
Want to simply make the evening a percentage more expensive than the period price? For the evening row set Price type to % Period price and enter 125 under Price (= 125%). With a period price of € 150 the evening becomes € 150 × 1.25 = € 187.50.
Variant 2 — One period, price in the schema
You use one period and alternate the parts of day with time windows in the schema. You enter the price directly in the schema (not via the period).
Period
| Setting | Value |
|---|---|
| Unit | Minutes |
| Length (timespan) | equal to the part of day (240 = 4 hours) |
Price schema
Create a schema row per part of day with a time window and the amount:
| Setting | Value |
|---|---|
| Price type | Actual price (you enter the amount yourself) |
| Calculation | Total price |
| From / To (morning) | 09:00 / 13:00 → € 120 |
| From / To (afternoon) | 13:00 / 17:00 → € 150 |
| From / To (evening) | 17:00 / 21:00 → € 180 |
Good to know
The From and To fields in the price schema are not opening hours. They only decide for which time window a price row applies. Covering the whole day ensures every booking always has a valid price — even when an administrator places a reservation outside the regular opening hours. The moments a customer can book online are set separately via the opening hours/bookable times.
The moments a customer can start (the bookable times) are set in the product's opening hours and bookable times, not in the price schema.
