Nerveเอกสาร

รายได้

Revenue overview

Occupancy, ADR, pace and rate recommendations, all derived from bookings you already took — and the one commercial section a Manager runs end to end.

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

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

Reservations 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. 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. The only thing this section stores of its own is the decision trail on a rate recommendation: what was proposed, and whether you took it.

หมายเหตุ

This section uses the default terminology. Your house may have renamed these terms under Settings → Terminology — 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 —
Read-only Read the analytics, the forecast and the recommendation list — and generate a fresh set of recommendations Accept or dismiss one; author a budget or a scenario
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.

The contrast with Reservations is deliberate rather than accidental. Editing a rate there is Owner-level; accepting a recommendation here changes the same price, and a Manager may do it. Accepting a generated move inside guardrails is a smaller act of trust than typing an arbitrary number, so it sits on its own permission — rms.recommendation.manage — which the Manager bundle carries.

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 an Owner enables it for that property (which needs apps.manage), nobody sees the Revenue group, whatever their role. If it is missing, check the app before you check the role: why two people see different menus.

There is no Revenue landing screen. Opening the group takes you to Analytics, which is the report the rest of the section is read against.

What's in this section#

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 Reservations. 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.

The portfolio is per organisation. It rolls up every property you can read revenue for, which is why it needs more than one hotel to say anything interesting.