Revenue overview

Who this is for: Manager, Owner, Read-only — the section opens on rms.analytics.read. Where: Revenue

CRS decides what you sell. Front Desk delivers it. Revenue is where you find out whether the price was right, and change it.

Everything on these screens is derived, not entered — with one exception. Occupancy, ADR, pace and the demand forecast are computed from the bookings your channels and the direct widget already delivered, on every request; there is no reporting database to load and nothing to reconcile at month end. What this section stores of its own is the decision trail on a rate recommendation (what was proposed, and whether you took it) and the competitor rates somebody typed in — benchmarking is the one screen here that is a record, not a computation.

หมายเหตุ

This section uses the default terminology. Your house may have renamed these terms under Settings → White-label — occupancy, ADR and RevPAR are all renameable, so the labels on your screens may not be the words on this page.

Who works here#

This is the one commercial section the default Manager bundle covers end to end: a Manager can read every report here and accept a rate recommendation, which is a real price change.

Role	Can	Cannot
Owner	Everything	—
Manager	Read every report, generate recommendations, accept or dismiss one, author budgets and forecast scenarios, define competitors and record benchmark rates	—
Read-only	Read the analytics, the forecast, the recommendation list and the competitor set/rates — and generate a fresh set of recommendations	Accept or dismiss one; author a budget or a scenario; add a competitor or record a rate
Front Desk, Accountant	Nothing — Revenue is not in their menu at all	—

หมายเหตุ

Generating recommendations rides on the read permission, so a Read-only role can refresh the list. That is deliberate: generating proposes, it does not price anything. Only accepting moves a rate, and only accepting is gated. Benchmarking follows the same read/manage split: rms.benchmark.read follows rms.analytics.read (everyone in this table has it), and rms.benchmark.manage follows rms.recommendation.manage — the same line that separates reading a recommendation from accepting one separates reading the comp set from editing it.

The contrast with CRS is worth understanding, because accepting a recommendation reaches further than it looks. A Manager may already price a room over there — the default bundle carries crs.rates.write — but not push availability, set restrictions or manage a channel, which stay Owner-level. Accepting here does both halves in one action: it writes the price and distributes it to every mapped channel. That is why it sits on its own permission, rms.recommendation.manage, rather than on the CRS write permissions a Manager does not hold.

Roles are configurable per organisation; the defaults are in roles and what each one can do.

สำคัญ

Revenue is off until someone switches it on. A new property starts with Front Desk, Reservations, Housekeeping, Accounting, Inventory and Point of Sale enabled — not Revenue. Until it is enabled for that property, nobody sees the Revenue group and every /rms screen answers "you don't have access", whatever their role — because a disabled app makes its permissions inert, rms.analytics.read included. If Revenue is missing, check the app before you check the role: why two people see different menus.

Opening the group takes you to Forecast & Pace, its first remaining feature — Analytics is not one of these screens any more. It became the Dashboard's Performance tab (Epic 59), a peer page at the app's front door rather than nested under Revenue. Portfolio isn't either — the cross-property roll-up moved further still, onto the portfolio home you land on before you even pick a property.

What's in this section#

• Revenue analytics — occupancy, ADR, RevPAR and the direct-versus-channel mix. Reached from the Dashboard, not from this menu. Every metric in this section is defined on that page. rms.analytics.read
• Forecast and pace — how the book is building, and where each date is expected to land. rms.forecast.read
• Planning: budgets and forecast scenarios — the targets a month is graded against. rms.analytics.read
• Grain and variance — the same book pivoted by segment, room category or booking window, against the budget. rms.analytics.read
• Rate recommendations — accept a price move and follow it out to the channels. rms.recommendation.read
• Competitor sets and benchmarking — who you price against, and what they were last charging. rms.benchmark.read

หมายเหตุ

Looking for the cross-property roll-up? It is not in this menu any more — see Workspaces, organisations and properties for the portfolio home you land on at sign-in.

How it connects#

Everything upstream is a booking. A stay ingested from an OTA and one taken by the direct widget are counted the same way; the only difference is which source segment it lands in. If a number here looks wrong, the question is almost always about the bookings, not the arithmetic — start at bookings from every channel.

Capacity comes from Front Desk. Available room-nights is the property's room count multiplied by the nights in the window, and that room count is the rooms on file in rooms and units. Add a room and every occupancy figure moves.

Accepting a recommendation writes back through CRS. It sets the rate plan's price — the same catalog described in room categories and rate plans — and queues an ARI change to every mapped channel, where you can watch it land in availability and ARI distribution. Revenue is not a read-only dashboard bolted on the side; it is one end of a loop that finishes at the channel.

Benchmarking is evidence, not an input to any calculation on this page. Nothing here averages your ADR against a competitor's rate automatically — benchmarking is a separate record you read alongside analytics and recommendations when you decide a price by hand.

The portfolio lives on the sign-in home now, not in this menu. Workspaces, organisations and properties covers every property you reach, per organisation — it needs more than one hotel to say anything interesting, the same as the screen it replaced.