Write it down once.
It acts. It puts it back.

The move that undoes itself.

Setting a restriction is the easy half. You set a minimum stay for a strong week, the week softens, and the restriction stays there quietly turning away the bookings that would have filled it. The cost is rarely the setting — it is the forgetting.

A rule here carries the whole round trip. It runs every morning — and again whenever fresh data reaches the platform. When the situation arises, the restriction goes to your channel manager. When it passes, the original value comes back. You write down what you want once; nobody has to remember to undo it.

A two-night minimum makes sense in a normal booking window. Inside the last week, with half the house empty, it just turns away the one-nighters who would have filled it. The rule drops the minimum to one night, and puts the two back when the week recovers.

A Friday already past 85% a month out does not need one-night stays leaving the Saturday next to it empty — and it certainly does not need to sell the last rooms at a discount. One condition, two moves that do different jobs: the minimum shapes the length of stay, closing the discount plan shapes what those nights are worth.

When only a handful of rooms are left, the expensive channel is the one you least want them sold on. The rule closes the OTA group for the endgame and leaves your own booking engine open. When inventory grows back, the group reopens on its own.

An event in town and a compset that has already moved up: that is the day you do not want sold cheap. Watching both sources every day, on every date, is the kind of check that rarely survives a busy week.

Every rule starts by only telling you.

A new rule cannot touch anything, and that is not a setting you have to remember to check — it is where every rule begins. It watches, it matches, it writes to the log, and it notifies whoever you named: "this would have matched six days." Nothing moves.

Run it that way for a week or a month, next to the dates you know well. Read what it would have done. When you find yourself agreeing with it, arm it — and the platform asks for your password again at that moment, because switching a rule from watching to acting is not something that should happen by a stray click.

How many rooms are genuinely still yours to sell. It is not floored at zero either — a negative number is the overbooking signal, not a broken reading.

How far your own rate sits from the competitors you track — above or below, as a percentage. The condition reads the same competitor data the rate reports are built on.

Tentative and optional business as a share of the whole night — the soft part of the book. A day that looks full on paper can be mostly options that have not turned into anything yet.

Whether the date carries something from your Event Calendar — a public holiday, a local festival, a fair, a match. The pricing side already reads that calendar; now a rule can too.

Not last year's finished number — last year's same day as it looked a year ago, at this same distance from arrival. That is what makes it a real pace comparison instead of a flattering one.

Two filters narrow every rule: which weekdays it may touch (Fridays only, weekends only, any set you like) and how close to arrival it applies — anywhere from tomorrow out to two years ahead.

It only says what actually happened.

If the log says it happened, it happened. A change is recorded only once your channel manager has confirmed it back — so a refused change never shows up as done. You get a failure you can act on instead.

That matters most on the days you are not looking. Even a quiet run reads back cleanly: what changed, on which dates, and which rule asked for it.

When the reason goes away, the move goes with it.

The reversal is the half that decides whether you trust the thing. Once the condition has stopped matching, the platform puts back the value that was there before the rule touched it — not a default, not a guess, the actual previous value it recorded on the way in.

And it does not rush. A number sitting right on your threshold can drift across it and back within a day, so the rule waits for a second run to agree before it undoes anything. No flip-flopping on your channels.

A change you make in Peaqplus is never written over.

This is the one that decides whether a revenue manager can live with automation. The rule set a two-night minimum on a Saturday; you opened the Pricing Calendar, knew something the data does not, and set three. From that moment the rule has no claim on that date. It does not push your three back to two, and when the condition passes it does not "restore" a one either. It steps back and says so in the log.

One thing worth knowing: the rule looks at what Peaqplus has on file, not at your channel manager. If someone edits a restriction straight in the extranet, the rule cannot see it. Keep the changes in Peaqplus and the protection holds.

The same principle settles rules arguing with each other. If two rules would touch the same setting on the same date and scope, the higher-priority one takes it and the other logs the collision and moves on. Two rules can still work the same date on different settings — a minimum stay and a channel group are not in each other's way.

11 rules written for you. Pick one, tune it.

You do not start from a blank condition builder. Eleven rules cover the patterns most hotels want first, grouped by what they are for: minimum stay, pace and deviation, events, competitors, channels. Pick one, move the threshold to your own numbers, choose who gets notified — and it starts watching.

Anything your channel manager cannot do is marked before you pick it, not after you save it.

Change the condition, the moves, the date range or the priority on a live rule and the platform reverses what that rule did and hands it back to you in notify-only. Renaming it, or changing who gets notified, does not count as a change of substance.

A rule can ask for something your channel manager cannot do — a minimum stay it supports, an arrival block it does not. When that happens the platform stops the whole rule instead of doing the part that would fit — and tells you, once a day rather than once an hour.

With moves still standing, the switch is refused — turn the rules off first, so the reversal happens on the system that made them. With nothing outstanding it goes through, and every acting rule drops back to notify-only, so a person deliberately re-arms them on the new connection.

A period you have excluded — a renovation window, a manual-strategy stretch, a booking stop — is skipped whole. Moves already standing inside it are left exactly where they are.