The calendar, in three layers
Price, restrictions and availability over the same grid of days. It is the screen you open every morning.
What it solves
A hotelier does not think in terms of a "price screen" and an "allotment screen": they think about 14 July. The three questions about a day — what do I sell it for, on what conditions and how many are left — live on the same grid, and are changed where they are read.
You notice it in things like these
- Changing one long weekend takes thirty clicks spread across four screens.
- A wrong price gets saved and there is no way back.
- Closing one date on six rates has to be done six times.
How it works
Price layer
The price of each rate and each day, with its layer-by-layer explanation, bulk change, gap detection and undo. Changes are held in a tray and ship together: different prices across several rates and dates in one call and one transaction.
Restrictions layer
Every rate on one grid, with a single change covering several rates, room types and weekdays at once. Each field is left as is, set, or cleared. If a single cell ends up impossible, none are saved: it all goes in or none of it does.
Availability layer
Free rooms by type and day: physical minus sold minus blocked, from the same source as the inventory matrix. Opening a day shows its reservations — the ones arriving first — and its blocks.
Seasons layer
The fourth, which arrived later: which season rules each day, with its adjustments, its priority and which rates receive it from their parent. Read here, edited on its own screen.
The cell opens and explains itself
Opening a night shows the full breakdown and, below it, the price for each number of people on the same plan and what the extra adult costs versus the previous occupancy, flagging the hand-set one. Also how children and the extra bed are charged. The numbers come from the same grid already drawn, so they cannot contradict the cell.
What changes goes out to the agencies
Every screen that changes price, restrictions or availability writes through the queue that publishes to channels, with its exact kind: price, restrictions or availability separately. A price is never sent when only a restriction changed.
Where it lives in the panel
- Rooms & rates
- Rates
- Calendar
The calendar stays at the top of the Rates block even though it is the last thing you configure: it is the screen you open every day once the hotel is set up.
What it needs first
A base price and at least one rate: the calendar shows what already exists, it does not create it.
Rate plansRooms already created, so the Availability layer has something to count.
Physical inventory
What it does not do yet
The limits, told by us
- The restrictions layer cannot be filtered by channel: Channex receives restrictions per rate, not per channel, so such a filter would promise something that never reaches the agency.
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.