Read the rate & availability grid

Who this is for: Revenue, Reservations, Manager, Owner — requires crs.rates.read. Where: CRS → Rate & Availability

Everything you sell for a date lives in three separate places: how many rooms are left, what each rate plan charges, and which restrictions are switched on. CRS → Rate & Availability puts all three on one grid, one column per date, so you can read a month of selling in a single screen instead of opening three.

Reservations is now CRS#

The app group that used to be called Reservations is now called CRS — the central reservation system.

The old name was the problem: Front Desk already has a Reservations screen, and it means something different. Front Desk's reservations are the bookings you are servicing today. CRS is the outward-facing side — the rates, availability and restrictions you publish, and the channels that read them.

Nothing moved. Every screen is where it was, every address still works, and nobody gained or lost a permission. Only the word on the group changed.

The breadcrumb is the page title. Select the app crumb to jump between CRS screens.

The screen that used to be listed as Rates is now Rate & Availability, because that is what it shows.

Read the grid#

Room categories on top, rate plans underneath, dates across. The first column stays put while the dates scroll.

The grid has two blocks, and they answer different questions.

Room categories is inventory. Each number is how many rooms of that category are still sellable on that night — the same truth Front Desk works from, so the grid can never offer you a room that is already occupied or blocked.

Rate plans is price. Each cell is what a guest pays on that night under that plan, in the property's currency, plus any restriction that applies. A plan sells a room category, so its cells sit under the availability that limits them.

The first column is sticky: scroll the dates sideways and you keep the category and plan names in view.

Choose the period#

Set Period to the number of days you want to see — anything from 14 to 90. Type a number outside that range and it snaps back to the nearest end rather than showing you a window the grid cannot answer for.

• ‹ and › move a whole window at a time. The windows are contiguous: the next one starts on the day after the last column of this one, so nothing falls between two views.
• Today returns to a window starting today.

The colours#

Red beats orange. A closed-out date is not sellable at all, so its stay restrictions are beside the point.

Red — close out. Not sellable that night. There are two independent ways to get there: someone set stop-sell on the rate plan, or the room category has no availability left. Either way, a guest cannot book it.

Orange — a stay restriction applies. Still sellable, but not to every stay. Minimum stay, maximum stay, no check-in, no check-out.

No tint — open. No restriction. Sell it.

Colour is never the only signal. Every restricted cell also carries a glyph, and hovering it names the restrictions in words:

Marker	Means
A crossed circle	Close out — not sellable
≥3	Minimum stay of 3 nights
≤5	Maximum stay of 5 nights
An arrow pointing into a door	No check-in — a stay may not start on this date
An arrow pointing out of a door	No check-out — a stay may not end on this date

Catatan

A minimum stay is not a block. A date marked ≥3 still sells — to a guest arriving for three nights or more. If it looks like nothing is booking on a date, read the marker before you assume the rate is wrong.

Where each number comes from#

The grid holds no figures of its own. It reads them, which is why it never disagrees with the screen that owns them.

• Availability is derived from Front Desk — stays, holds and blocked rooms. Take a room out of order and the number here drops on the next load.
• Price is the rate plan's price for that night: its standard price, replaced by a date-specific rate wherever one has been set. A cell reading a different amount from its neighbours is a date someone priced deliberately. It renders in the property's currency, formatted the property's way — the words on this screen follow your language, but the money follows the hotel.
• Restrictions are resolved in three layers, each one overriding the one below: the plan's weekday defaults, then any restriction template applied over a date range, then a single-date setting. What you see in the cell is the answer after all three — not something you have to assemble yourself.

That last point is worth holding on to. If a cell shows a restriction you did not expect, it came from one of those three layers, and the most specific one wins.

When the grid is empty#

A property with no room categories or no rate plans has nothing to show, so the grid says so rather than drawing an empty table. Add a room category and a rate plan, and it fills on the next visit.

What's next#

• Reservations overview — how rates, availability and channels fit together
• Take a room out of order — the other reason an availability number falls
• Analytics — what the rates you set here earned