Turning a rule on, Apply or Skip

When it opens

The calendar

The calendar starts at your property's today and runs to the last night MAYA prices, 395 nights on, a small block per month: 13 to 15 months (15 only when today is late in January), Sunday first, as on the Calendar tab. A filled blue square is a day the rule will change, a dark one a day it will not, and today has a thin outline. Hover a blue square to read the day and how many room types change, such as "Sat 3 Oct 2026: prices change on 2 room types". A screen reader reads the affected days out as runs of dates.

What the days mean

Under the calendar is one line: "41 days will be affected by this rule.", "1 day will be affected by this rule.", or "0 prices will be affected by this rule." A "?" beside it explains the rest.

A day counts when the rule changes the price of at least one room type that night. The days come from a trial run of your pricing on your bookings as they are right now, once with the rule as you are about to save it and once as things stand (for an edit, the rule as it is saved now), compared night by night to the cent. So every other rule, your typed prices and your floors and ceilings are already taken into account: a raise on a night already at its ceiling moves nothing, so that day does not count. Nothing is saved while the window is open.

0 prices. "0 prices will be affected by this rule." means no price moves now: the rule is not true anywhere yet, or where it is, something else keeps the price where it is. With nothing to change, applying and skipping come to the same thing, so the window offers one button, Turn it on (Save changes for an edit to a rule that is on), and Cancel. Either one saves the rule on, as Apply price adjustments does, and from then on it acts on what becomes true.

A cut on low pickup with no booking window. When the rule is Decrease the rate with a Pickup count (advanced) row set to Less than and no Booking window (days to stay) row, two amber lines follow the count, worked out in the same trial run: "With no booking window condition, this rule reaches 396 of the 396 nights ahead. A night that gained under 1 room night over the 7 full days before counts as quiet, and a far-out night with no bookings yet always will, once your rules have run for 1 week." and "The cut repeats: each time its wait of 1 week is over and the night is still quiet, it cuts again, on top of the cut before." The first number is every night the rule can act on (fewer when it has a date range or weekdays), the second is the window your rules price, and the amount, lookback and wait are the rule's own. The count above can be "0 prices" while your rules have run for less than the lookback window, and these lines say what happens once they have. The rule builder fills a booking window row in for you when you build a rule of this shape. Read A cut on low pickup, far out.

Not enough similar nights. For a rule with a Booked so far vs usual row, a line follows the count on the nights where the rest of the rule is true but there aren't enough similar nights to compare with yet, worked out in the same trial run: "On 40 nights where the rest of this rule is true, there aren't enough similar nights to compare with yet, so it leaves them alone." When that is every night the rule can act on, as on a new property: "There aren't enough similar nights to compare with yet, so this rule won't change any night until there are." Read Booked so far vs usual.

Kept to far-out nights. The same two lines show for a cut on low pickup with a Booking window (days to stay) row set to Greater than a number of days, when a night stays that far out long enough to be cut more than twice. The furthest night your rules price is 395 days out, so a night stays in reach for 395 less that number of days, and the lines show when that is more than twice the rule's wait: 365 days with Greater than 30. The first line then starts "Kept to nights more than 30 days before arrival, this rule reaches 365 of the 396 nights ahead." With Greater than 381 and a 1-week wait it is 14 days: a night is cut 395 and 388 days out and no more, so no lines show. The builder fills nothing in for this one.

Apply price adjustments

The rule is saved and on. The days in blue are priced first on the next pricing run, usually within a minute and at most about five, and the rest of the window follows over the next runs. The days that change are the ones the calendar showed, unless something changes first. The Calendar tab and the change log show them as they land. In simulation nothing is sent. Live on Cloudbeds or ThinkReservations, the new prices are sent to your property system. On Mews, they change in MAYA only.

After an edit to its conditions, amount or room types, Apply judges every change the rule already has on the price against the edited rule: a standard rule's change moves to the new amount where the edited rule is true and comes off where it is not, and a booking speed or pickup rule's earlier changes come off. A new name or the undo box alone leaves the rule's changes where they are. Read A rule that is changed.

Skip price adjustments

The rule is saved and on, and the days in blue keep their prices: on each of them the rule leaves its part of the price as it is until the rule stops being true there and then becomes true again. From then on it acts on that day as on any other. Every day that is not blue works exactly as if you had clicked Apply price adjustments.

• A standard rule (a rule with no booking speed or pickup count condition): on a blue day where it was about to raise or cut, it is on with no change on the price. Once it stops being true there and later is true again, it adjusts.
• A booking speed or pickup rule: on a blue day it makes no change while it stays true. The first time it is true there after not being true, it adjusts, in that same run.

Whether the rule is true on a blue day is read from the night as it is now, whatever its undo box says: the rule made no change there for the box to keep.

After a Skip. Skip itself never changes a price. The prices on the blue days move later only once the rule has stopped and started being true there, or when something else moves them: a price you type, or another rule.

Counting. Skip never changes where a rule counts from: a booking speed or pickup rule counts every booking on the books, the ones made before you added it included, whether you applied or skipped. Read After you skip.

Changes already on the price. Switching a rule that has changes on the price back on, or saving an edit to a rule that is on, with Skip leaves its changes on the blue days where they are, each until the rule stops being true there and then becomes true again. They still come off when the night passes or when you delete the rule, and a price you type takes a booking speed or pickup change off and pauses a standard rule's change until you clear it. A rule that is changed says what then happens to each kind of change.

Off and on again. Switching the rule off freezes it, the skipped days included. Switching it back on opens the window again: Apply price adjustments ends the skipped days and judges every change the rule has on the price as Apply does, and Skip price adjustments leaves the days the window shows then as they are instead. An edit saved with either choice does the same.

Waits left by going live. Going live with Start from your current rates leaves a rule waiting on some nights, each until the rule stops being true there and becomes true again (Going live). A waiting night the rule would change is blue. Apply price adjustments, Turn it on and Save changes end every wait, and Skip price adjustments keeps them. Switching the rule off ends them on the next pricing run, once its changes there are off, so switched back on it starts as this window says for any rule. Deleting it removes them.

Cancel

Cancel, the Esc key or a click outside the window saves nothing. A rule you were switching on stays Off, and the rule builder keeps everything you typed, so you can change it and try again.

When something changes while it is open

Before anything is saved, the save checks whether anything that could move the days changed since they were worked out: a booking or a cancellation, a price typed, a pricing run, another rule, a room type. If the days come out the same, the rule is saved straight away. If not, nothing is saved, the window shows the new days with "Your bookings changed while this was open, so the days were checked again.", and you choose again. If they change yet again while it saves, one red line reads "Your bookings or prices changed again while this was saving, so nothing was saved. Try again in a minute."

When the days cannot be checked

If the check fails or takes too long, the line reads "We weren't able to calculate how many days would be affected by this rule.", and the window offers Try again, Skip price adjustments and Cancel, with no Apply price adjustments, since there is no count to apply. Skip then turns the rule on without changing any price now: with no days to go on, it leaves every day the rule could change as it is, each until the rule stops being true there and then becomes true again. When the check was refused because of too many checks at once, "That's a lot of checks at once. Give it a minute and try again." shows under that line.

How long it takes

While the days are worked out, the squares are grey and pulse, the line reads "Checking your calendar…", and the buttons wait. A standard rule is usually answered within a second or two. A booking speed or pickup rule takes longer, because every night it could act on is priced: its calendar is asked for in three parts at once, the nearest two months first, and the count appears only when all three are in, usually within a few seconds.

From the rule builder, often no wait

While you fill in the rule builder, MAYA works the days out in the background, the same way, so the window can open with them already there. It starts once the rule is complete (a name, a condition, increase or decrease, and an amount) and saving it would turn it on (a new rule, or a change to a rule that is on), when you have stopped changing the form for 0.6 seconds. Any change to the rule starts it again once you pause; a new name alone does not. Nothing runs while the browser tab is hidden or the window is open, and after a lot of changes in a few minutes it rests for a minute.

When you click Add Rule or Save changes, the window takes those days only if they were worked out for exactly the rule you are saving, within the last 2 minutes, and waits for them if they are still being worked out. Otherwise the window works the days out itself. Either way, Apply price adjustments and Skip price adjustments check them again before anything is saved. Nothing is saved while it runs, and it works out the days only, never any revenue.

Who can do this

Revenue Managers, General Managers and Hotel Admins. For a Viewer the window opens for a moment and closes again, and "Only a Revenue Manager or above can change this." appears under the rule's switch, or under the rule builder. Nothing is saved. Read Roles: who can do what.

Rules from PIE

Import from PIE adds its rules without this window. PIE has already changed the rates on the nights its rules match today, so rules that were on in PIE are added on as if you had clicked Skip price adjustments, and rules that were off in PIE are added off; switching one on later opens this window as for any rule. Read Adding them.

Messages you can meet