Book a demo Sign in
Selling online

The revenue engine: a recommended rate with its reasons

Every night of every room type is scored against what is on the books; the engine proposes a price with the reasons, a manager approves or rejects it, and an approved price goes to the channel manager the same minute.

# The revenue engine

The revenue engine: the Proposed tab — one row per room type and night with the tariff, the proposed price, the change, the confidence and the reasons — and Approve on each.
The revenue engine: the Proposed tab — one row per room type and night with the tariff, the proposed price, the change, the confidence and the reasons — and Approve on each.

Do this

  1. Proposed — every night of every room type the engine wants to move, under its stay date, with what is on the books against what is expected.
  2. Tick rows and Approve the ticked, or read one row: the tariff, the proposed price, the change, the confidence, and why in plain words.
  3. Approve writes the price on every plan of the type and queues it for the channel manager; At… writes another price with a reason; Reject records why and rests that night for a week.
  4. Policy is where it is switched on and its guardrails set.

Menu → Revenue engine. Every night of every room type, for the next ninety days (the horizon is yours to set), scored against what is on the books.

What it looks at. How full the room type is against what a hotel usually has on the books this far out (the engine learns your own curve once it has a month of days; until then it uses a default and says so); how many rooms were picked up in the last week; whether the last rooms are going; whether a night is close and empty; the events you have told it about; and how far out the night is — far nights move less.

What it proposes. A price, and beside it the reasons in plain words: *78% of Deluxe on the books at D-21, against 50% expected*. A confidence from 10 to 90 says how much to trust it. Nothing is published by the engine: Approve writes the price, Approve at… writes another price with a reason, Reject records why (a reason picked from a list). An approved price goes to every plan of the room type and every type priced from it, and the channel manager's push queues the same minute — see it on Operations → Log.

Guardrails. On Policy: a floor and a ceiling per room type, the largest move in one step (15% by default), the rounding (₹50), the smallest change worth asking about (2%). A night can be locked — the engine proposes nothing there. An event (a wedding week, a festival) adds a percentage on those nights.

The tariff is yours. The engine starts every proposal from the price you set, never from its own last proposal, so approvals do not stack. Retype the tariff on a night and the engine starts again from the new number.

Off by default. Switch it on per hotel on Policy. Autopilot — publishing without a person — is not in this release.

The Policy tab

Policy: the mode, the horizon, the target occupancy, the step limit, the rounding; per room type a floor, a ceiling and its own step; and the button that saves it.
Policy: the mode, the horizon, the target occupancy, the step limit, the rounding; per room type a floor, a ceiling and its own step; and the button that saves it.
  1. Mode — *Off* or *Recommend*. Autopilot is not offered in this release.
  2. Per room type: a floor, a ceiling, its own largest step, and *leave this type alone*.
  3. Save the policy. Events and locks are on their own tab: an event adds a percentage on its nights, a lock keeps the engine off a night a person has fixed.

More in Selling online

What the channel manager doesAxisRooms carries the OTAs. We send it rates and availability; it sends us bookings. Mapping room types and rate plansNothing is sent for anything unmapped. Map the hotel, then each room type and rate plan. When an OTA booking arrivesIt lands on the chart by itself, at the OTA price. What cannot be applied waits on a list with the reason. What the channel sent, and what became of itThe CM Log on Operations reads in four tabs — reservations, inventory, rates, cancellation — the bookings the channel delivered and the pushes we sent it, each with its fate. The Channel sync log report is every exchange with AxisRooms, both ways, hotel by hotel.