Turning a rule off, deleting it, or changing it

The On/Off switch

Each rule on the Rules tab has a switch under Status that reads On or Off.

Switching Off is at once, with no confirmation, from the next cycle. Off means the rule stops acting. It does not undo anything:

• a standard rule's change that was on a night stays on that night, and does not come off when the rule stops being true, because the rule is no longer being checked
• a booking speed or pickup rule's raises and cuts stay on the price, and they are not checked for cancellations while it is off
• on the day cards and in your property system, nothing moves

Two things still reach them, as they reach any rule's changes. A price set by hand on a night and room type (typed in MAYA, or changed in your property system and kept as your price) takes a booking speed or pickup change off there for good and pauses a standard rule's change while the price stands (Your rules after your price). 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).

Switching On first opens a window, headed "Turn on "Busy nights"?", with a small calendar of the days the rule will change and "X days will be affected by this rule." Apply price adjustments lets it act on every night it matches from the next cycle, and a standard rule that was keeping a change lets it go where it is no longer true. Skip price adjustments switches it on but leaves the days the window showed as they are, each until the rule stops being true there and then becomes true again. Cancel leaves it Off. Read Turning a rule on, Apply or Skip.

A rule cannot be switched On while 40 others are on (read How many rules you can have).

Delete

The red Delete button at the end of a rule's row opens a dialog headed "Delete "Busy nights"?". It says: "Deleting this rule also undoes the price changes it has already made. Any night it adjusted goes back to what the price would be if this rule had never run." and "If you only want it to stop acting from now on, turn it off instead — the prices it has already set stay exactly as they are." Then, in amber: "Deleting cannot be undone." Three buttons:

• Delete Rule and Undo Its Changes: removes the rule and every change it made, from the next cycle
• Turn It Off and Keep Its Changes: switches the rule off and closes the dialog
• Cancel: the dialog opens with it selected, and it or the Escape key closes the dialog with nothing changed

If a delete does not go through, the reason shows in red under the rule's switch and the rule stays. A rule you were editing stays open in the rule builder with your changes.

The change log keeps its price entries, and each one keeps the deleted rule's name, reasons and amount as they were when it ran. Entries from before October 2026 did not keep them: there the rule's moves read "Pricing rule", with no sentence saying why. Your answers to the rule's keeps-adjusting banner (the "Your answer" entries) are removed along with the rule. The next run that prices each night it was on says so: "Busy nights" was deleted, so its 10% raise came off. That took this night from $165.00 to $150.00. Read The change log.

Changing a rule

Click Edit beside Delete at the end of the rule's row. The rule builder opens under the list, headed "Edit "Busy nights"", with the rule as it is saved: its name, its conditions, the direction and amount, the room types it measures and changes, and the undo box, Take this change back if cancellations remove the bookings that triggered it. The rule's row is highlighted while you edit. Change what you want and click Save changes:

• Only the name changed: saved at once. A name moves no price.
• The rule is On: the window opens first, headed "Save changes to "Busy nights"?", with the days the edited rule will change. Apply, Skip or Cancel, as for switching a rule on. Cancel keeps what you typed in the builder.
• The rule is Off: saved at once, and no price moves. Its changes stay as they are, and the window shows what the edited rule does when you switch it on.

Cancel editing, under the form, empties the builder without saving. A rule's date window (a rule imported from PIE with dates has one), weekdays and priority are not in the builder, and an edit keeps them as saved. If someone changed the rule's conditions, amount or room types in another tab after you opened it, the save stops with "This rule changed in another tab. Reload it to edit." and a Reload button that fills the builder with the rule as it is now.

What an edit does to the rule's changes. After an edit to its conditions, amount or room types, Apply price adjustments judges every change the rule 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. With Skip price adjustments, the changes on the days the window showed stay until the rule stops being true there and then becomes true again. Such an edit also clears the rule's "Stop for this night" answers. A new name or the undo box alone leaves the rule's changes where they are, and keeps its answers. Read A rule that is changed for every case.

Waits left by going live. If you went live with Start from your current rates, a rule may still be waiting on some nights until it stops being true there and becomes true again (Going live). Saving the rule with Apply price adjustments ends those waits: it acts on every night it matches now, and the window's days include them. Skip price adjustments keeps them, and leaves the window's days as they are. Turning the rule Off ends them on the next pricing run, once its changes there are off, so switched back on it starts as any rule switched on does, with Apply or Skip. Deleting it removes them.

The change log keeps what the rule was. Its older entries still tell each change as the rule was when it ran, under the name it had then. Entries from before October 2026 work differently: Rules you change or delete.

The "Tune ... ?" card after Get suggestions from my data is an edit too: Make that change moves the occupancy threshold of a standard rule, through the same window when the rule is on. Read Getting suggestions later and Change a rule.

The list

The rules table has six headed columns, Name, Fired, Conditions, Room Types, Price Change and Status, and a seventh with no heading that holds each rule's Edit and Delete buttons. On a narrow screen it scrolls sideways, with Status and the buttons kept in view.

If the list can't be read, "Couldn't load your rules." shows above the table with Try again. An empty table under that line means your rules couldn't be read just then, not that they are gone, so press Try again rather than building them again.

Order. Most fired in the last 90 days first, then rules that are on before rules that are off, then by name.

Filter. The pills above the table, All, Enabled and Disabled, show every rule, only the ones that are on, or only the ones that are off.

Fired. How many pricing runs the rule acted in over the last 90 days. The "?" beside the heading says: "Each pricing run where the rule acted in the last 90 days counts once, however many nights and room types it changed." So a rule that raised 7 room types in one run reads "1×". It goes on: a booking speed or pickup rule can act on the same night again in a later run, when its wait is over and it is still true, and that counts again; and a change that came off later still counts. So the count can be higher than the changes you can see on the calendar now. A dash means not once in that time. A plain dash you can't click means the counts couldn't be read just then: reload the tab. A fire older than 90 days drops out of the count, so a rule that has not acted lately can go down, or back to a dash. Click the number to see each fire it counts (The fire log).

Conditions. In words, joined with a dot: "Sellable occupancy above 80%", "Rooms left fewer than 5", "Booking window below 7 days", "Current rate below $150", "Pickup above 5 room nights (past 3 days), then waits 3 days", "booking speed at least Faster Than Normal (past week), then waits 1 week", "Recent bookings at least 10 (whole property, last 7 full days)", "ADR above $180", "Booked so far ahead of usual by at least 25%". A rule that covers only some nights has a "?" after its conditions: some days of the week (a starter rule copied from your own Friday and Saturday moves, say) or some dates (a rule imported from PIE with dates). Hover it, or click it, for "Days: Friday and Saturday nights only." and "Dates: Oct 15, 2026 to Nov 30, 2026.", whichever apply, and "It leaves every other night alone. Editing the rule keeps these." A rule with no "?" covers every night.

Room Types. The types the rule changes, or "Watches Standard, Deluxe · Changes Suite" when it measures different ones.

Price Change. "+10%", "-15%", "+$25", "-$25". A fixed amount shows your property's own currency symbol, as the calendar and the change log do: "+€25" for a property in euros, "-£25" in pounds. Until MAYA has read your property's currency the symbol is $. The rule builder's fixed amount box carries the same symbol: Adjust by fixed amount (€) for a property in euros.

Stopped on N nights. An amber chip under the switch when you have told the rule to stop on some upcoming nights, with a "?" and a Let it run again link. Read Rules that keep adjusting.

The fire log

Click a rule's number in the Fired column ("12×") and a window opens with the rule's name at the top, "12 fires in the last 90 days" under it (just "Fires in the last 90 days" if the count couldn't be read), and a "?" that explains the count as the list's does and says the times are your property's. It lists exactly the fires the number counts, newest first, up to 25 at a time (fewer when fires changed many nights and room types). A fire is one run the rule acted in, one row each:

• when it fired, in your property's time zone, with the zone: "Oct 3, 2:05 PM EDT", with the year when it was not this year. Hover it for the exact second. The change log shows the same run on your browser's clock, so the two differ when you are not in your property's zone.
• the nights and room types it changed: "Nov 13 · Queen", "Nov 11 to 12 · 7 room types", or "5 nights, Nov 11 to 18 · 7 room types" when the nights are not in a row. Nights that cross into another year carry the year on both ends: "Oct 10, 2026 to Nov 9, 2027". On a phone the room types are cut short first.
• what it did, in your currency: "+10%", "+$15". A small amber Simulation tag sits beside it when your property was simulating at the time.

If a fire landed since the rules list loaded, the window's count is the newer one, and the list's number changes to match it.

Under the title, Why didn't it fire? asks about a night the rule left alone, and a dash in the Fired column opens it for a rule that hasn't fired at all (Why didn't it fire?). Under each night's room types, Why this price? opens that night's price and the changes to it.

Click a row to open it, and click again to close it. It shows:

• Where the price went, in the change log's words, once when every room type says the same, otherwise beside each room type. A fire made while simulating says "Simulation: these are the prices it would have set." and "Nothing was sent to Cloudbeds.", and "Nothing was sent to Cloudbeds at the time." once you are live. If its price is still the night's latest then, a second line says what going live did with it: "Sent to Cloudbeds after you went live.", "Waiting to be sent to Cloudbeds now that you're live.", "Couldn't be sent to Cloudbeds after you went live." or "Held back after you went live, not sent to Cloudbeds." A live fire whose price is still the night's latest says "Sent to Cloudbeds.", "Waiting to be sent to Cloudbeds.", "Couldn't be sent to Cloudbeds." or "Held back, not sent to Cloudbeds.", from MAYA's record of its sends. On ThinkReservations, a sent price reads "Accepted by Think Reservations, checking." until MAYA's hourly read of your rates finds it there. A fire whose price a later run replaced has no such line: MAYA's record keeps only each night's latest send, so it cannot say. Nor does an unsent price while MAYA cannot send it (back in simulation, work paused over your subscription, a Disconnected connection, a night beyond the window): "Waiting" would not be true. On Mews a live fire says "Nothing was sent to Mews. MAYA doesn't send prices there yet." With no record of which mode your property was in at the time, nothing is said about sending.
• Each night, such as "Fri Nov 13", with every room type the fire changed on it and that room type's price before and after the run: "Queen $150.00 to $165.00". It is the night's whole price, so another rule acting in the same run is in it too, and it starts from the price the night had just before that run, as the change log does. With no earlier price on record (a night new to the window) it reads "$165.00 after this run". "at your ceiling" (or floor) follows when your limit held the price, and "Prices not on record" shows when the record of that run is not there. A fire across more than 200 nights and room types lists the first 200 and ends "Show 50 more of 50 nights and room types left.": click it for the rest, 200 at a time, until every one is listed.
• Why it fired on that night, in the change log's sentences with the numbers it saw: "It was 72% full, past the 70% mark you set." For a booking speed or pickup rule the numbers come from the run that fired it, and if that record is missing, from what the fire kept itself, numbers only: "6 room nights booked in its count." If you have edited the rule since, only the numbers show, then "The rule has been edited since.", because its marks at the time are not on record.
• What happened later, when anything did, oldest first, under the night when it happened on every room type there, otherwise under the room type: "Came off Oct 5, 9:10 AM EDT." (a standard rule's change, when its conditions stopped holding or an edit took it off), "Came off Oct 5, 9:10 AM EDT: bookings behind it cancelled.", ": a price was set by hand.", ": the rule was edited." or ": you went live starting from your Cloudbeds rates." (a change taken off when you went live from your current rates), "Moved to the rule's new amount Oct 5, 9:10 AM EDT." (an edit kept the change at the rule's new amount), "A price set by hand took over Oct 5, 9:10 AM EDT." and "Told to stop on this night Oct 5, 9:10 AM EDT.", each with your property's time zone. A rate changed in your property system on a night MAYA sent counts as a price set by hand when MAYA keeps it as your price; with MAYA's price wins on in Settings, MAYA usually sends its own price over it instead (Rates you change in your property system). Each is worded for the mode at its own time: a change that came off while simulating "Would have come off".

When the rule is off, "This rule is off. Its changes stay where they are." shows under its name. A rule with no fires in the last 90 days shows a dash in the list instead of a number, and the dash opens Why didn't it fire? rather than this window.

Older under the rows adds up to 25 fires before them. While they load it reads "Loading…", and if they cannot load, "Couldn't load older fires." shows beside it. Once the oldest is on screen, "Nothing older. The fire log shows the last 90 days." shows instead. If the window cannot load at all it says "Couldn't load this rule's fires." with a Try again link. Close it with the × at the top right, the Escape key, or a click outside it.

What a fire is. The count and the window read the same list, so they always agree: each pricing run, in the last 90 days, in which a standard rule's change went on at least one night and room type, or a booking speed or pickup rule made a raise or cut. That is how long MAYA keeps the record that explains a fire. Nothing is read until you click, so the rules list loads as fast as before. Everyone who can see the rules list sees the same window, whatever their role, and there is nothing in it to change.

How many rules you can have

At most 40 rules can be On at once on a property. Rules that are Off do not count, and a rule saved from the Rate Simulator arrives Off. At 40, the window with the calendar opens for a moment when you add a rule or switch an Off rule on, then closes, and "This property already has 40 active rules, which is the maximum." shows in red under the form or under the rule's switch. Nothing is saved. Turn a rule off or delete one first. Import from PIE says so before adding anything, such as "That makes 43 rules on, and a property can have 40. Untick 3 to fit."

Every standard rule (a rule with no booking speed or pickup count condition) that is true applies, and their changes stack. Booking speed and pickup rules take turns: at most one acts on a night and room type per run. Read How rules work together.

Who can do this

Revenue Managers, General Managers and Hotel Admins can switch, edit and delete rules. A Viewer sees the switch and the Edit and Delete buttons, and can open a rule in the builder to read it, but switching, saving or deleting changes nothing and shows "Only a Revenue Manager or above can change this." in red under the rule or the form. Read Roles: who can do what.

Who did what

The app does not show who on your team added, switched or deleted a rule. If you need to know, email us with the rule's name and roughly when.

The change log has no entry for adding a rule, editing it, switching it on or off, or deleting it, or for which of Apply or Skip was chosen: it shows only what those steps did to prices. The people the change log does name are whoever typed a price ("Priya set the base rate to $180.00.") and whoever answered the keeps-adjusting banner (the "Your answer" entries). MAYA support is the exception: a rule our staff add, change, switch or delete for you shows as a "Changed by MAYA support" item, such as "Removed the pricing rule "Busy nights"." Read Changes by MAYA support.