Skip to content
yaReserva

Search the site

Go to

Searches the 78 features, the 36 guides, the documentation and the frequently asked questions.

Book
Rooms and rates

Revenue rules

Automatic price adjustments — by occupancy, by lead time, by length of stay — with a floor, a ceiling and a daily movement cap.

What it solves

Changing the price by hand every night does not scale, and letting a rule change it on its own is rightly scary: a badly set rule can empty a weekend or price the hotel out of the market. The guardrails are what make automation something you can switch on without watching it.

You notice it in things like these

  • A rule runs away over a weekend and nobody notices until Monday.
  • There is no way to tell which layer left the night at that price.

How it works

  1. Rule guardrails

    In the "Action" step of creating or editing a rule there is a guardrail block: minimum price, maximum price and maximum change per night as a percentage. All three are optional, and a rule with no guardrails behaves exactly as before.

  2. A guardrail stops, it does not push

    If the night was already below the floor — a hand-written price, a low season — a rule that lowers it leaves it where it was, instead of raising it to the floor. Same with the ceiling. The guardrail trims the rule's movement; it never moves the price on its own.

  3. Applied in the engine, not in the screen

    They are applied to the rule's complete step — all its tiers together — inside the price resolver, so they hold equally for the calendar, checkout, quotes, the simulator, the preview and the audit trail.

  4. The explanation says what stopped it

    The price breakdown shows a "· guardrails" layer that says in words what happened: "capped at maximum $3,500", "to ±15% per night". You do not have to guess why the rule did not get where it should have.

  5. With history and duplication

    Guardrails go into the rule's history ("Minimum price" changed), duplicating a rule inherits them, and the summary states them: "between $1,200 and $3,500, no more than ±15% per night". The database rejects a floor above the ceiling even if someone bypasses the domain layer.

Where it lives in the panel

  1. Rooms & rates
  2. Rates
  3. Revenue rules

What it needs first

  • A base price and the rates the rule acts on.

    Base price

Carry on here

Shall we walk through it with your hotel on screen?

Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.