In plain words
You don't need this page to build rules. It is the fine print on what happens after a rule changes a night. A (a rule with no or condition) keeps its change on while it is true and takes it off when it isn't, with no wait. With its undo box unticked, cancellations usually don't take it off through occupancy or rooms left. A booking speed or pickup rule keeps its change on the price, waits, and then looks at the night again, counting only the bookings made since the newest change there by itself or a stronger rule that moves the price the same way. Each room type is judged on its own.
Standard rules, step by step
For each night and room type, a does one of three things in a :
- Switch on. The rule is true where its change was not on. The change goes on the price.
- Stay on. The rule is still true. Nothing changes, and it doesn't act again.
- Come off. The rule is no longer true. The change comes off and the price goes back.
So a cancellation that drops a night from 82% to 78% takes a "Greater than 80" raise off on the next cycle, and a late booking that lifts it back above 80 puts it on again. There is no wait.
With the rule's undo box unticked, cancellations usually don't take it off through a Greater than occupancy condition or a Fewer than rooms left condition. The rest of the rule is read as the night is now: a condition still runs out as the night gets closer, and a cancellation that moves recent bookings, the average rate booked or booked so far vs usual can still end the change. Read The undo box.
Booking speed and pickup rules, step by step
- Act. The conditions are true, the rule is not waiting on that night and room type, and it beats any other or pickup rule ready to act there (Which one fires when several match). The change goes on the price.
- Wait. The rule leaves that night and room type alone for its Then waits (advanced) setting: 1 day to 2 weeks, or a pickup row's lookback window, up to 30 days. A booking speed row starts on 1 week. A row starts on Same as the lookback window, or on 1 week once you pick a 14- or 30-day lookback. A rule with both waits the longer of the two. The "?" beside the wait says: "Waits count whole days at your property. A 2-day wait from a change made at any time on a Monday is over as Wednesday begins." MAYA reads the night again on that day's daily pass, in the first cycles after midnight, nearest nights first.
- Read again. When the wait is over, the rule reads the night again, counting only the bookings made since the newest change on that night by itself or by a stronger rule that moves the price the same way, while that change is still on the price. If those bookings keep the rule true, it acts again and the new change stacks on the earlier one. Read Counting after a change.
- Asks you at three. Once three of a rule's changes are on the same night, an amber banner asks you whether to keep going. Read Rules that keep adjusting.
The change log shows a repeat as a change of its own, in the run that made it: "Hot-week surge" raised this night 25%, from $250.00 to $312.50, with "Hot-week surge's +25% still applies." under it for the earlier raise.
- Monraised
- Tue
- Wedreads
- Thu
- Fri
- Sat
- Sun
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
- Mon
After a 2 days wait from a raise on Monday afternoon, the rule reads the night again as Wednesday begins, and through that day, and counts only the bookings made since the raise: Monday after the raise, Tuesday and Wednesday. A rule that raises on a fast pace needs those bookings alone to beat what similar nights get in a whole week.
If the bookings since the raise read the rule's level or beyond, it raises again and the wait starts over. If not, the price holds at one raise. A stronger rule's raise in between moves the start of the count up to that raise.
A 2-day wait after a raise on Monday afternoon: the rule reads the night again as Wednesday begins, and through that day, and counts only the bookings made since the raise, Monday afternoon through Wednesday. A rule that raises on a fast pace needs those alone to beat what similar nights get in a whole week.
An illustration with made-up numbers, not your property.
Example: A 2-day wait after a Monday raise
The "Hot-week surge" is Much Faster Than Normal or faster over Past week, waits 2 days, raises 25%. It raises the Saturday's price on Monday afternoon.
Tuesday: waiting. Wednesday, just after midnight: the wait is over. The rule now counts the Saturday's bookings that came in after Monday's raise, from Monday afternoon on, and through Wednesday as they come. Because it raises on a fast pace, those bookings alone have to read Much Faster Than Normal or faster against what similar Saturdays get in a whole week. It never counts the bookings that made it act on Monday again.
If Monday's burst was the whole story, the bookings since the raise read Normal and the price stays at one raise. If bookings keep coming, it raises again on Wednesday, waits until Friday, and so on. At three raises on that night, MAYA asks you.
"My rule's wait is over and the night still reads faster, so why did it not act again?" Because the whole-window reading you see in an older log entry includes the bookings the rule already acted on. After a change, the rule only counts what arrived since. If those bookings alone do not keep it true, it does nothing. That is by design: a rule never raises twice on the same bookings, and neither does a weaker rule after a stronger one's raise. A stronger rule still counts the bookings a weaker rule raised on.
Counting after a change
Once a or pickup rule, or a stronger one that moves the price the same way, has changed a night, the rule usually counts only the bookings made since the newest such change, while that change is still on the price. A rule that has never changed the night itself counts from a stronger rule's change too, as "Five" does in the example below.
- A weaker rule's change never moves where a stronger rule counts from.
- Raises and cuts never move each other's count.
- A 's change never moves it either.
- A change that has come off, for cancellations or because you typed a price, no longer counts as a starting point.
- A change that going live from your current rates took off (with Start from your current rates, or with Choose by rule and night for a rule on Skip or a room type left unticked under a night) still counts as a starting point for weaker rules that move the price its way: the bookings it acted on stay spent (Going live).
- A change made by a rule you have switched off still counts, because it stays on the price.
- A change still on the price from before its rule was edited (one Skip price adjustments kept, or one of a rule edited while it was off) is judged as the rule was when it made it, so an edit that lowers the amount or changes the speed doesn't by itself change which rules that change covers.
The "?" panels in the rule builder say what stronger means: "A stronger rule is one that changes the price by more. If two change it by the same amount, a rule that watches booking speed is stronger than one that doesn't, and of two that do, the one set to the faster speed is stronger (the slower speed, for rules that cut)." Which one fires when several match has the full order.
Another rule can act on the same day. If a stronger raise rule acted on the night earlier today, a weaker raise rule can still act on that night today, but only on the bookings that arrived after that raise. The stronger rule holds the night through its wait only while it would be true again on what it counts itself.
Example: Two tiers at The Harbour Inn
"Five" raises 10% on 5 or more of pickup in a week. "Ten" raises 20% on 10 or more. Standard starts at $100. On Monday 10 book at once. Both rules are true, and "Ten" changes the price by more, so it raises: $120. "Five" does not add its 10% on the same bookings.
On Tuesday 3 more book, and on Wednesday one of Monday's guests cancels. "Ten" still has 12 in its week, so its raise stays, and both rules keep counting from Monday's raise. On Thursday 2 more book: 5 since the raise, so "Five" raises 10% on top: $132. "Ten" still counts from its own raise, 5 so far, because a weaker rule's raise never restarts a stronger rule's count.
Booking speed
A rule that raises counts from the raise itself: on the day of the raise, only the bookings that first reached MAYA from your property system after it, then every day since. A rush later that day is still counted, and nothing from before the raise is counted twice.
A rule that raises on a fast pace (Faster Than Normal, Much Faster Than Normal or Surging) needs those bookings alone to beat what get in its whole window. Any other booking speed rule compares them with the similar nights over the same days of their own booking curves. Those nights had no change that day, so for them the first day counts in full.
A rule that cuts counts full days only, up to yesterday, on the night and on the nights it is compared with. After a cut it counts the full days after the day of the cut, so it has nothing to count until one of those has passed.
Example: Hot-week surge at The Harbour Inn
"Hot-week surge" measures Past week, acts on Much Faster Than Normal, raises 25% and waits 2 days. On Monday, October 12, 2026 it raises Standard for Friday, November 13. On Tuesday it is waiting. On Wednesday, October 14 the wait is over.
MAYA now counts three days: the bookings that arrived after Monday's raise, then all of Tuesday's and Wednesday's. Because the rule raises on a fast pace, those three days on their own have to read Much Faster Than Normal against what similar Fridays get in a whole week, 5 bookings. With 10 or more, it raises again.
If it does, the change log says: "Bookings came in much faster than normal in the 3 days since this rule or a stronger one's latest raise still on this night: 12, against the 5 a night like this usually gets in a whole week."
The exact sentences under Show the numbers after a change are in When the reading shows.
Pickup count
A Greater than pickup rule, while its lookback window still reaches back to its change, counts only the room nights (or revenue) booked after the change and still booked. A booking from before the change cancelling takes nothing from that count. So a wait shorter than the window never counts the same burst twice: a 3-day rule with a 1-day wait can raise again the next day only on new pickup. Once its window has moved past the change, it counts its whole window again.
- Greater than counts today so far and the days before it in its lookback window.
- Less than counts full days only, up to yesterday, so its last change counted the full days before its own. It judges again only once a whole lookback window of full days, starting with the day of that change, has passed, because a short stretch always looks slow.
A count over the whole window (every Less than count, and a Greater than count once the change is behind it) is net pickup: room nights booked minus room nights cancelled, so a cancellation of a booking made before the change lowers it.
Read Pickup count (advanced).
After you skip
Skip price adjustments moves no rule's count. A rule you add, switch on or edit counts as it would with Apply price adjustments: a new rule counts every booking in its window, the ones made before you added it included, and an edited booking speed or pickup rule reads its whole window again. On the days the window showed, the rule makes no change until it stops being true there and then becomes true again, and it is judged there on that same count. Skipping starts no wait. Read Skip price adjustments.
After a typed price
A price you type takes the booking speed and pickup changes off that night and starts those rules over: each waits its wait, in whole days from the day you typed, then reads its whole window again, bookings from before your price included. Read Your rules after your price.
When cancellations hit a kept change
When cancellations hit a change and bookings made since keep its rule true, the change stays, and every rule keeps counting from when it was made, not from when it was checked. Counting starts again only when a price changes. Read Changes after cancellations.
Per room type
Everything above happens separately for each room type the rule changes. Waits run per night and room type, and floors and ceilings are per room type. So a rule can act on Deluxe and not on Standard on the same night: Standard may still be waiting, sitting at its ceiling, or counting from a newer change of its own.
The Fired column counts , not nights or room types: a run in which the rule changed 7 room types on 3 nights counts once. Read The list.