In plain words
A 's change (a rule with no or condition) comes off when the rule stops being true. With its undo box unticked, cancellations usually don't take it off through its Greater than occupancy and Fewer than rooms left lines. A booking speed or pickup rule's change comes off when cancellations mean the rule is no longer true, as long as its undo box is ticked, which it is on every new rule. More bookings never take it off. The slow pace itself never takes a cut off, because cancellations only make a night slower. Your typed price takes booking speed and pickup changes off that night and pauses the standard rules there. An edit to the conditions, amount or room types that you apply judges a standard rule's changes against the edited rule and takes a booking speed or pickup rule's changes off, and one you save with Skip leaves them on the days the window showed until the rule stops being true there and then becomes true again. Deleting a rule undoes everything it did. Switching a rule off undoes nothing, though a price you type still does to its changes what it does to any rule's, and going live from your current rates still takes them off.
The undo box
Every rule has one box, Take this change back if cancellations remove the bookings that triggered it, under Rate adjustment in the rule builder. It starts ticked on every new rule, and and accepted suggestions are ticked too. The rules list does not show it. To change it on a saved rule, click Edit on the rule, tick or untick it and click Save changes. On a rule that is on, the window with the calendar opens first: ticking can take off a change whose rule is no longer true, and unticking can keep one that would have come off. The new box applies from the next cycle, and the rule keeps its changes and its count. The "?" beside the box sums up this page.
- Ticked. When bookings a change counted are cancelled, MAYA checks the rule again. If, without them, the rule wouldn't have made the change, it comes off. If bookings made since keep the rule true, the change stays. More bookings never take a change back.
- Unticked. Cancellations alone don't take the change off through occupancy, rooms left, or pickup. A 's recent bookings or condition is still read as the night is now, so a cancellation there can still end its change. And when you apply an edit to a standard rule's conditions, amount or room types, its changes are judged once on every condition as the night is now, box or not. A change still true then is kept through cancellations again (A rule that is changed).
The box is not an end date. It only takes a change back when cancellations remove the bookings behind it. A booking speed or pickup raise made while a night was under an occupancy line, for example, stays when more bookings take the night over that line.
The box works the same way for a raise or a cut. Cancellations can only make a rule untrue through a Greater than occupancy or pickup line, a Fewer than rooms left line, a booking speed level the rule needs to reach, or, on a standard rule, an At least recent bookings line or an average rate booked line. Unticked, the box keeps the change through all of these except a standard rule's recent bookings or average rate booked line, which is read as the night is now. A , anything Less than and a slow pace only get truer as guests cancel, so a cut made because a night was booking slowly stays when cancellations slow it down further.
Once a change has come off, its rule can change the night again when it is true again and its wait is over. The wait still runs from the change that came off, so a night on the edge does not go up and down every cycle. A standard rule has no wait, so it goes back on as soon as it is true again.
Either way, a change also comes off when the night passes, when a price is set by you (or changed in your property system on a night MAYA has already sent to, while you are live and keep such changes as your price), when you delete the rule, when you go live from your current rates (with Start from your current rates, or with Choose by rule and night for a rule you set to Skip or a room type left unticked under a night), and when you apply an edit to its conditions, amount or room types (read A rule that is changed). A price set by hand pauses a standard rule's change rather than taking it off (read A price you type).
Standard rules
A (any of , rooms left to sell, booked so far vs usual, , current rate, recent bookings and average rate booked, and no or row) keeps one change on a night and room type while it is true, and takes it off on the first cycle where it is not. With the undo box ticked, that includes a night that drops under its occupancy line because guests cancelled.
Example: A cancellation at The Harbour Inn
"Busy nights" raises 10% when a night is more than 80% full. Friday is 17 of 20 booked (85%): Standard is $165. Two guests cancel, so Friday drops to 15 of 20 (75%). On the next cycle, about five minutes later, the raise comes off and Standard goes back to $150. If a new booking lifts Friday over 80% again, the raise goes back on.
With the box unticked, a Greater than occupancy condition and a Fewer than rooms left condition count as met while the change is on, as long as the room types the rule measures have rooms to sell, so cancellations alone don't take the raise off through them. An edit you apply to the rule's conditions, amount or room types is judged once on every condition as the night is now, so a raise kept through cancellations comes off if the edited rule isn't true. Where it is true, the raise moves to the new amount, and from then on the box keeps those two conditions met again (A rule that is changed). The rest of the rule is read as the night is now: a booking window condition still runs out as the night gets closer, a Less than occupancy rule or a More than rooms left rule still switches off when bookings come in, and booked so far vs usual, recent bookings, the current rate and the average rate booked are read as they are, because they move with time and rates as well as with cancellations. So on an unticked booked so far vs usual rule, a cancellation that takes the night under the mark still takes the change off. On a day that Skip price adjustments left as it was, the box keeps nothing, because the rule made no change there: a night that falls under the line ends the skip, and the next time it is over the line the rule adjusts (read Skip price adjustments).
The How rules behave panel on the Rules tab animates both. Ticked: "Occupancy falls to 65%, so the rule is no longer true and its raise comes off." Unticked: "Occupancy falls to 65%. The box is unticked, so the raise stays."
Changes after cancellations
A or pickup rule's change stays on the price after the rule acts, until the night passes, a price is set by hand for that night, you apply an edit to its conditions, amount or room types or delete it, you go live from your current rates (with Start from your current rates, or with Choose by rule and night for a rule you set to Skip or a room type left unticked under a night), or, with the undo box ticked, cancellations make the rule no longer true. More bookings never take it off. The check starts once a room that was booked for the night when the change was made has cancelled. It recounts what the change counted, not the night as it is now:
| The rule's condition | What the check looks at |
|---|---|
| Booking speed | The bookings the change counted that are still booked, against what a night like it usually got over those days, as read when the change was made. The rule's own level is the bar |
| Greater than | The pickup the change counted, less the bookings from that stretch that have cancelled since |
| Greater than | The night's sellable occupancy now |
| Rooms left to sell Fewer than | The night's rooms left to sell now |
Booked so far vs usual, recent bookings, the current rate and the average rate booked on a booking speed or pickup rule are judged when the rule acts, and never by this check: they move with time and rates as much as with cancellations.
If the change's own count falls short, MAYA reads the rule once more the way it would count with the change off, bookings made since included. If that keeps the rule true, the change stays and every rule keeps counting from when it was made. Only when both fall short does the change come off.
Each stacked change is checked on its own numbers. A change is never checked in the cycle that made it, never while its rule is switched off, never once the rule measures a different set of room types from the one it measured when it acted, and never while Skip price adjustments holds it on a day the window showed (until the rule stops and starts being true there). Switch the rule back on with Apply price adjustments and the check resumes.
Example: Two cancellations, then one more
On Monday, October 12, 2026, "Hot-week surge" raised Saturday, November 14, 2026 by 25%, after 12 bookings arrived in a week when a night like it usually gets 5. Two of those 12 cancel: 10 are still booked, still much faster than normal, so the raise stays. One more cancels: 9 left read only faster than normal, short of the Much Faster Than Normal the rule needs. Unless the Saturday's week, read as it stands now, still reads Much Faster Than Normal, the raise comes off on the next cycle.
The change log then says: Cancellations meant "Hot-week surge" was no longer true, so its 25% raise came off. Of the 12 bookings it counted, 9 are still booked, where nights like it usually get about 5, and the rule needs a booking speed of at least much faster than normal. The entry then ends with the move, such as "That took this night from $250.00 to $200.00.", and any change still on the night is named in grey under it. For a rooms left line it reads, for example, "Rooms left to sell had risen to 7, and the rule needs fewer than 5."
Example: A raise under an occupancy line
"Early buzz" raises 10% when booking speed reads Faster Than Normal and Sellable occupancy (%) is Less than 60. It raises Friday, November 13, 2026 at The Harbour Inn while Friday is 52% full. Then more bookings take Friday to 70%. The raise stays: more bookings never take a raise back. And the rule can't act on Friday again while Friday is over 60%. A works the other way: "Quiet-night nudge", which raises 5% while occupancy is Less than 60, takes its raise off as soon as Friday goes over 60%.
Cuts
A cut rule whose conditions are a slow pace, a Less than or a never comes off because of how the night books. Guests cancelling only make it truer, and new bookings are what the cut was for: a cut that switched off the moment a booking arrived would undo the thing that brought the booking in. If bookings have recovered and you want the price back up, type the price you want on the calendar, or delete the rule, which undoes every cut it made.
"Bookings recovered, so why did the cut not come off?" Because bookings arriving never take off a or pickup cut, or a standard cut on a booking window alone. (A standard cut with a Less than occupancy, More than rooms left or Fewer than recent bookings line does come off once bookings take the night across that line.) A cut rule can keep cutting the same night after each wait, down to your floor. Once three of its cuts are on the night the amber banner asks whether it should keep going, and until you answer, it does. Read Rules that keep adjusting.
A price you type
When you type a price for a night and room type, every and pickup change already on it comes off ("this night's price was set by hand" in the change log), and the already there are paused on that night: they stay on but stop moving the price until they stop being true and become true again. Your number becomes the base, and rules that act later stack on it. Clearing your price brings the paused standard rules back, but the booking speed and pickup changes that came off stay off. Read Your rules after your price.
A rule that is changed
You change a rule with Edit and Save changes, or by accepting a "Tune ... ?" card after Get suggestions from my data, which moves a 's occupancy threshold. What happens to the changes the rule already has on the price depends on how the edit is saved:
| The rule | Saved with Apply price adjustments | Saved with Skip price adjustments |
|---|---|---|
| A standard rule | Whether the edited rule is true is read from the night as it is now, undo box ticked or not: each change stays where it is true, at the new amount, and comes off where it is not. That includes room types you took off the rule and nights it no longer covers. Nights that now meet the edited rule gain the change. After that, an unticked box keeps the changes that stayed as it kept them before | On the days the window showed, each change stays at its old amount until the edited rule is next true there after not being true, then moves to the new amount (or comes off, on a room type or night the rule no longer covers). Every other night is judged as with Apply |
| A or pickup rule | Its earlier changes come off. The edited rule reads its whole window again, with no wait, so it can change the night again at once | On the days the window showed, its earlier changes stay and are not checked for cancellations. Once the rule has stopped and started being true on such a day, they come off and the edited rule can act there in that same run. Every other night is judged as with Apply |
With Skip, price changes that were on the price stay on the days the window showed, and:
- whether the rule is true there is read from the night as it is now, undo box ticked or not;
- 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, which comes back when you clear the price;
- saving the rule again with Apply price adjustments ends the skip, and its changes are judged as Apply judges them.
Read Skip price adjustments for Skip in general. The window before the save shows the days Apply would change.
A new name or the undo box alone leaves the rule's changes where they are (the new box applies to cancellations from the next cycle). An edit saved to a rule that is Off changes no price: its changes stay as they are, still cover the rules they covered, and the window when you switch it on shows what the edited rule does. Changing the conditions, amount or room types also clears the rule's "Stop for this night" answers.
"Why did the change log say the rule was edited?" A booking speed or pickup change that comes off because its rule was edited with Apply reads ""Warm-date bump" stopped applying an earlier 10% raise here: the rule was edited, so MAYA started it fresh." A standard rule's change that comes off reads as any standard rule letting go, and one that is still true moves to the new amount: ""Weekend nudge" was edited, so its raise went from 10% to 15%." A change that Skip price adjustments left at its old amount reads "the rule was edited, so MAYA started it fresh" when it moves to the new amount, then the rule's new raise.
The night passes
Once your property's date moves past a night, every change on it is left as it was and nothing touches it again. Past nights are never re-priced.
A deleted rule
Deleting a rule removes every change it made, whether from a or a or pickup rule, from the next cycle. Every night it adjusted goes back to what the price would be if the rule had never run. The delete dialog says so and offers Turn It Off and Keep Its Changes beside Delete Rule and Undo Its Changes. Read Turning a rule off, deleting it, or changing it.
Switching a rule off undoes nothing: its changes stay as they are, and cancellations do not take them off while it is off. Two things still reach them, as they reach any rule's. A price set by hand on the night takes its booking speed and pickup changes off there for good and pauses its standard changes while the price stands (A price you type). And going live from your current rates takes changes off whether their rule is on or off: every rule's with Start from your current rates, and with Choose by rule and night, those of each rule you set to Skip and those on each room type left unticked under a night (Going live).
The change log sentences
| What happened | What you read |
|---|---|
| A switched off | "Busy nights" stopped applying an earlier 10% raise here: this night no longer met its conditions. That took this night from $165.00 to $150.00. Any other change still on the night is named in grey: "Hot-week surge's +25% still applies." |
| A booked so far vs usual rule switched off only because there weren't enough any more | "Weekend pace" stopped applying an earlier 10% raise here: there weren't enough similar nights to compare with. When anything else in the rule stopped being true too, it reads "this night no longer met its conditions". Read Booked so far vs usual |
| A change came off for cancellations | Cancellations meant "Warm-date bump" was no longer true, so its 10% raise came off. Then the numbers the check found, and the move, from the price the night had just before |
| You typed a price | A line naming who set the price, then: "Warm-date bump" stopped applying an earlier 10% raise here: this night's price was set by hand. |
| A or pickup rule was edited, with Apply | "Warm-date bump" stopped applying an earlier 10% raise here: the rule was edited, so MAYA started it fresh. |
| A rule was deleted | "Weekend nudge" was deleted, so its 10% raise came off. That took this night from $462.00 to $420.00. Older entries keep the rule's name and reasons; in entries from before October 2026 it is called "Pricing rule" with no reason given |
"Why did the price go back to the base rate?" One of: a standard rule stopped being true, cancellations meant a rule was no longer true, you or a colleague cleared a typed price, an edit to the rule was applied, the rule was deleted, or you went live from your current rates (with Start from your current rates, or with Choose by rule and night for that rule or night). The change log lists the night in the run that did it: it names what came off and why, then "That took this night from" the old price to the new one. Any change still on the night is named in grey as still applying.