CRS

Reservations overview

The commercial side of the house: what you sell, at what price, with what restrictions, through which channel — and who is allowed to change it.

อัปเดตล่าสุด

Who this is for: Owner and Manager — reading needs crs.booking.read or crs.rates.read; what reaches a channel — availability, restrictions, connections — is Owner-level by default. Where: Reservations

Front Desk owns what you deliver. Reservations owns what you sell: the catalog, the price, the restrictions, and every channel the property sells through. It is the module a revenue manager lives in.

One fact runs through all of it — the direct booking engine and every connected OTA sell the same inventory and the same restrictions. There is no second copy to keep in step.

หมายเหตุ

This section uses the default terminology. Your house may have renamed these terms under Settings → White-label.

Who works here#

The line the default bundles draw here is not the one people expect. It does not fall between reading and writing — it falls between changing what you sell and changing what the channels are told.

Role Can Cannot
Owner Everything —
Manager Read bookings and take or amend them; edit room categories, rate plans and prices; save distribution settings; manage listings; answer messages; reply to reviews; edit property content Push availability, set restrictions or stop-sell, connect and manage channels
Read-only Read bookings, rates, messages and reviews Any change

So a Manager may reprice a room — the default bundle carries crs.rates.write — but cannot push that price out, close a date, or connect a channel. Those need crs.availability.write, crs.restrictions.write and crs.channel.manage, and the default Manager bundle carries none of them.

That split is deliberate, and the reason is retraction: a price sitting in your catalog is easy to change again, while a price or a stop-sell that has reached an OTA is not. The permission sits with the act of distribution rather than the act of pricing.

One consequence worth knowing: a price a Manager edits does not reach a channel on its own. It sells through the direct booking engine immediately and waits for someone who can distribute it — or for an accepted rate recommendation, which does both halves at once (see rate recommendations and parity).

Roles are configurable per organisation — see roles and what each one can do. Where a screen needs a permission the Manager bundle does not carry, its page says so on the header line.

What's in this section#

When something else is the master#

If your property runs an external channel manager and it is connected on the Integration Hub, it masters the facts it owns — mappings, ARI, or both. Nerve renders those screens read-only and refuses server-side writes to them, and a banner on the affected screen says which facts are involved.

There is never more than one writer to a fact. Whatever the arrangement, the front desk stays the system of record for stays.

How it connects#

A booking becomes a stay. Anything that arrives here — from a channel or from the direct booking widget — materialises as a Front Desk stay on the right room type and rate, with taxes and the payment-collection method carried onto the folio. From that point it is an ordinary arrival: see the Front Desk overview.

Revenue pushes back through here. Accepting a rate recommendation in the Revenue module updates the rate plan and queues an ARI change to every mapped channel — it does not stop at the price. That is also the one path by which a Manager's decision reaches a channel without an Owner: see the Revenue overview.

The booking widget sells the same truth. A stop-sell applied here closes the direct widget as well as the OTA, which is the whole reason restrictions live in one place.

หมายเหตุ

On staging, every channel connection runs against an in-process stub. Connections, mappings, ARI pushes, messages and reviews all behave as specified and delivery states are real — but nothing reaches a live OTA.