A price looks wrong

Why did the price jump 50%?

Two rules acted on the same night, and percentages compound. Standard rules (no booking speed or pickup count condition) apply first, then each booking speed or pickup fire in the order it was made, then the floor and ceiling. A +10% followed by a +25% is not +35%: $200 becomes $220, then $275.

The change log shows each fire in the run that made it, from the price the night had just before. The second one reads:

"Hot-week surge" raised this night 25%, from $220.00 to $275.00. Bookings came in much faster than normal this past week: 12, against the 5 a night like this usually has by now. Busy nights' +10% still applies.

The first, "Busy nights" raised this night 10%, from $200.00 to $220.00, is the change of the run before it, further down.

Once three of one booking speed rule's changes are on the same night, the amber Rules that keep adjusting banner asks you whether to carry on or stop. Until you answer, it keeps going. Read Rules that keep adjusting.

If the jump is bigger than you want, set a ceiling. The default ceiling is $99,999.99, which stops nothing in the currencies MAYA works in. Read Floors and ceilings.

Why did a rule raise a night that is empty?

Because booking speed compares a night with what similar past nights had received at the same point before arrival, not with how full it is. A night 50 days out is compared with how its similar nights were booking when they were 50 days out. If those nights had received none at all by then, 2 or 3 bookings in a week read Much Faster Than Normal, or Faster Than Normal when there are fewer than 5 similar nights to compare with. If they had averaged a fraction of a booking, 0.4 say, it takes 3, because a difference of less than 2 bookings always reads Normal.

Press Show the numbers under the change. The panel that opens shows the count, the usual number ("nights like this one usually get almost no bookings over the same stretch") and which nights were compared. "Almost no bookings" covers anything under 1, none at all included. Read Booking speed reads oddly for why small counts read the way they do.

To keep raises off empty nights, add Sellable occupancy (%) Greater than as a second condition to your raise rules. A rule needs every condition true at once. Click Edit on the rule, click + Add condition, and click Save changes. The window then shows the nights that change. For a booking speed or pickup rule, Apply price adjustments takes off every raise the rule had made, on every night, and the edited rule then raises again only where it is true now, so stacked raises collapse to one and a night whose pace has gone back to normal loses its raise. Skip price adjustments keeps the raises on the days the window showed, and keeps new raises off. (A standard rule's change comes off just where the new condition rules it out.) Read Change a rule. An edited starter rule keeps its place above the rules you build.

Why did it cut a night that is nearly full?

A cut rule with only a booking speed condition does not look at occupancy. The two cut rules setup builds, "Slow-date rescue" and "Slow-date trim", come with an occupancy condition, Less than 70, so they leave a night 70% booked or more alone. Starter rules built before that, and cut rules you built, have only booking speed unless you add one. It counts bookings made in its window (past day, week or month, in full days up to yesterday) and compares them with similar nights over the same stretch. A night that filled up months ago and received one booking this month reads slower than a night like it usually books, and the cut fires.

A wedding or group booked as one reservation makes this more likely: for booking speed, a booking counts once however many rooms it holds. Twenty rooms in one reservation are 20 rooms for occupancy and one booking for booking speed.

Fix the night by typing a price on the Calendar tab. Read Start here for the wedding weekend case in full.

Prevent it by giving cut rules an occupancy condition (Less than 50, say), so a full night is never cut. Click Edit on the rule, add the condition and click Save changes. For a booking speed or pickup rule, Apply price adjustments takes off every cut the rule had made, on every night, and the edited rule then cuts again only where it is true now; with Skip price adjustments the cuts on the days the window showed stay, and no new cut lands on a full night. Read Change a rule.

Why did a raise ahead of usual come off again?

A booked so far vs usual rule counts every room on the books tonight, bookings that may still cancel or not show included, while earlier years hold only the bookings that stayed. So a night far out can read ahead of usual and be raised, then drop under the mark when some of those bookings cancel. The raise comes off at the next check, with the rule's undo box ticked or not. The change log says why: "this night no longer met its conditions".

To keep such rules to nights where your bookings are firmer, add a Booking window (days to stay) row set to Less than 60, say. Read What earlier years can't show.

We are sold out tonight. Why is the price still changing?

MAYA does not read how many rooms your system still has for sale. A full night is priced like any other: your rules run on it whenever its bookings change and once a day, and once you are live its price is sent whenever it changes (Cloudbeds and ThinkReservations). That is on purpose. A cancellation puts a room back on sale, and it sells at the rate your system has at that moment, which is MAYA's latest price once you are live.

On a sold-out night:

• An occupancy raise stays. A rule such as "Busy nights" keeps its one raise while the night stays above its mark, and, with its undo box ticked, takes it off if cancellations bring the night back down to the mark or under.
• A booking speed cut can still fire, unless the rule also needs the night under a share booked, as the starter cuts setup builds now do (under 70%). A full night takes no new bookings, so its recent count can read slow against similar nights that were still selling at the same point (the question above).
• Raises already made stay on the price, as they do on any night.

To keep cuts off full nights, add a Sellable occupancy (%) row set to Less than (70, say) to each cut rule: Edit on its row, + Add condition, Save changes. For an exact price on a sold-out night, type it on the Calendar tab.

Editing a starter rule keeps the rest of it exactly as it is, its rank above rules you built included, and "Slow-date trim" keeps its exactly Slower Than Normal unless you pick another speed. Read Change a rule.

Why is a price at $1?

That is the default floor, $1.00, and it stops nothing in practice. A cut rule that fires again after each wait, on a night that keeps reading slow, walks the price down until the floor catches it. With no floor set, the floor is $1.

Set a floor for each room type. Type it in the room type's Floor box on the review, or on the Rules tab press Get suggestions from my data. MAYA offers a floor only for a room type whose floor is still the $1.00 default. It also needs your answer to the floor question during setup, or at least 30 sold nights for that room type. Accept the amount, or type your own, then press Set it to. On the amber banner, Ask MAYA for a floor takes you to the Rules tab for the same button.

To change one room type's floor once it is set, type it in that room type's Floor box on the review, at maya-rms.com/onboarding/review. Answering the floor question from setup again writes the new floor to every room type that counts as a room at once, except one whose ceiling is lower than it. Read Set or change a floor or ceiling.

Once a floor is set, a cut rule stops firing on a night that is already at the floor, because it cannot move the price in its own direction. The price stays at the floor until you type a price, delete the rule, or bookings change what the rules read.

Why is a price at $99,999?

That is the default ceiling, $99,999.99. In the currencies MAYA works in it has the same effect as no ceiling at all. Raise rules that keep firing on a night that keeps reading fast climb until the ceiling stops them.

A property whose rooms sell for more than 99,999.99 (in yen, won, rupiah or dong, for example) cannot connect to MAYA yet, so no night of yours is held down by it. Read Floors and ceilings.

Set a ceiling the same way as a floor: in its Ceiling box on the review, or with Get suggestions from my data on the Rules tab, which Ask MAYA for a ceiling on the amber banner also takes you to. MAYA offers a ceiling only for a room type whose ceiling is still the $99,999.99 default. It also needs your answer to the ceiling question during setup, or at least 200 sold nights for that room type. The number is your answer or one built from the highest rates you have sold at, and you can type your own before pressing Set it to. As with a floor, you change a ceiling once it is set in its Ceiling box on the review.

Why is my price stuck at the floor?

Every price your rules work out is held between the room type's floor and ceiling, your own rate included. A price set by hand (a $0 comp night, a price typed before a limit changed, or a rate changed in your system and kept as yours) is published as it is. When the rules ask for less than the floor, the floor is published and the change log says "That would have dropped under your $80.00 floor for Standard, so it stopped there."

While the price sits at the floor, a cut rule does not fire again (it cannot move the price down), and a standard rule's cut holds while its condition holds. The price stays at the floor until something changes what the rules read, or until you act.

To lift it: type the price you want on the Calendar tab, or delete the cutting rule (which undoes its changes). Turning the rule Off keeps its changes, so the price stays at the floor. A typed price below the floor is refused rather than moved: "Below this room type's floor of $80.00." The one exception is 0, which is a comp night.

Why did a price change with no rule named?

Four shapes of entry have no rule name.

"Cloudbeds' rate went from $200.00 to $210.00, so the price moved to $231.00." No rule fired and none came off: your own rate changed in your property system, and the rules already on the night stayed on it, so the price followed. MAYA reads your rates about once an hour, and again when your property's date changes, and prices from that base. On a night MAYA has never sent to, a rate you change in Cloudbeds or ThinkReservations becomes the new starting point. Read Rates changed in your property system. A run that works the night out again to the price it already had gets no entry.

Mews: MAYA reads no rates from Mews, so a Mews night's starting price is always one someone typed, and this line does not appear there.

"The price moved from $200.00 to $210.00." Nothing on the night can be named, for example when MAYA has no record of the night's earlier run. A floor or ceiling you changed is named instead: "Your floor for Standard went from $80.00 to $90.00, so the price moved to $90.00."

"Sam set the base rate to $180.00." A person typed a price on the Calendar tab. The entry's bold line ends "Price set by hand". "A manager" appears when the name is not on file.

"The base rate was changed in Cloudbeds to $180.00." On a live property, a rate you changed in your system on a night MAYA had already sent to, an hour or more after the send, is kept as a manual price, while your setting is Keep the change as your price (as every property starts). The day card shows "Changed in Cloudbeds · $180.00". No name is attached. With MAYA's price wins on, the change log has an item of its own instead, such as "Fri, Nov 13, Standard: changed in Cloudbeds to $175.00. MAYA sent its price, $165.00, again."

For one night and room type, Why this price? on its day card lists the changes to it, newest first, with what is behind the price now (Why this price?).

A fifth shape names a rule you cannot find: "Pricing rule". That is a rule someone has deleted, in an entry from before October 2026. Newer entries keep a deleted rule's name. An older entry whose rule was changed since ends "The rule has been edited since." (Rules you change or delete).

Why did the price go back to the base rate?

Six reasons, and the change log names each.

• A standard rule stopped being true. A standard rule (no booking speed or pickup count condition) holds its change while the condition holds. With its undo box ticked, a cancellation that drops occupancy under the mark stops the condition holding, and the change comes off on the next run.
• A change came off after cancellations. "Cancellations meant "Warm-date bump" was no longer true, so its 10% raise came off." With a rule's undo box ticked, a booking speed or pickup change comes off when bookings it counted cancel and the rule is no longer true for the night, unless bookings made since keep it true. A cut made because a night was booking slowly never comes off this way, and nor does any change from a rule with its undo box unticked.
• A rule was deleted. Deleting undoes every change the rule made, from the next run.
• A rule was edited with Apply price adjustments. An edit to its conditions, amount or room types takes a booking speed or pickup rule's earlier changes off ("the rule was edited, so MAYA started it fresh"), and a standard rule's change off where the edited rule is no longer true. A rule that is changed
• You went live from your current rates. With Start from your current rates, every rule's change comes off, and each night goes back to your own rate. With Choose by rule and night, that happens to the changes of each rule you set to Skip, and on each room type left unticked under a night, those the list started unticked included. Going live
• A manual price was cleared. Clear on the room type card hands the night back to your rules. Standard rules that the typed price had paused apply again at once, if their condition still holds. Booking speed and pickup changes it took off stay off. Those rules change the night again only by firing anew, which they are free to do from the next run.

Read When a change comes off.

Why is a night unpriced?

The room type card shows "Current price" followed by a dash when no price has been published for that night and room type. Reasons, most common first:

1. Beyond 396 nights. Your rules price tonight and the next 395 nights, so a night further out gets no price. A price you typed further out is kept, and the night is priced and sent once it enters the window.
2. Closed in your system. A night whose rate is 0 in Cloudbeds or ThinkReservations, with no price typed in MAYA, is left unpriced. MAYA does not open a closed night at the floor. Type a price if you want the night priced.
3. No rate in your system for the night. A night Cloudbeds or ThinkReservations has no rate for, for example one further ahead than you have loaded rates, is not priced and nothing is sent for it, whatever its bookings paid. The card reads "No rate in Cloudbeds for this night yet" (or your system's name) under the dash. Load a rate for it in your system and the next hourly read picks it up, or type a price in MAYA, which is sent as typed. MAYA reads your rates as far ahead as your system returns them; a night past that is treated the same way until a read returns it. On ThinkReservations, a room type with every night like this may have no rate type MAYA reads at all: two rate types tie, or the one you picked is gone. The PMS tab says so under "MAYA reads and writes:", and so does the change log. Read Seeing and picking the rate type.
4. Rate removed in your system. A night MAYA had sent a price to whose rate was then removed in Cloudbeds or ThinkReservations, while your property keeps changes made there as its price. The card reads "Rate removed in Cloudbeds, so MAYA isn't pricing this night". Load a rate there and the next hourly read picks it up (a rate other than MAYA's last price is kept as your price), or type a price in MAYA. A rate removed in your system
5. Not run yet. A property that connected minutes ago has no runs until its first cycle. Give it about five minutes.
6. A past night. Past nights are never priced or changed.
7. A room type switched off in MAYA. A room type hidden during the review (an empty duplicate), one Cloudbeds or ThinkReservations no longer lists, or one we switched off after you removed it from Mews, is not priced and has no card on the Calendar tab. On Cloudbeds, MAYA's daily read of your room types switches a removed one off, and the change log says "Deluxe is no longer in Cloudbeds." On ThinkReservations the next cycle's read does. Until then, and on Mews until we switch it off, it stays priced, but nights that enter the 396-night window after you removed it have no rate to start from and show a dash. On Mews, email us its name and we switch it off. Read Room types and rooms out of service.

Mews: a Mews property has no rate read, so a night stays unpriced until you type a price for it.

Why did my rule fire three times and keep going?

Because it keeps going until you answer. Once three of a booking speed or pickup rule's changes are on the same night, the amber Rules that keep adjusting banner appears at the top of every tab: ""Hot-week surge" has 3 raises on Fri, Nov 13 2026." and "It keeps raising these nights until you stop it."

Answer Keep adjusting and MAYA stops asking about that night. Answer Stop for this night and the rule makes no more changes there. Only a Revenue Manager or above can answer. Read Rules that keep adjusting.

I answered Stop but the price did not go back

Stop means no more changes from that rule on that night. What it already did stays: "What it already changed there stays, unless cancellations mean the rule is no longer true." For a rule with its undo box unticked: "What it already changed there stays."

To put the price where you want it, type it on the Calendar tab. To undo everything the rule did on every night, delete the rule. Read Undo a price change.

Why does the same rule appear twice on one night?

""Slow-date trim" lowered this night 7%, from $200.00 to $186.00." in one run, then ""Slow-date trim" lowered this night 7%, from $186.00 to $172.98." with "Slow-date trim's -7% still applies." in a later one, is one rule that fired, waited its wait, and fired again. A booking speed rule can act on the same night more than once. After the first change it counts only bookings made in the full days since the newest cut still on the night by itself or a stronger rule, up to yesterday, compared with similar nights over the same days, and if those still read slow it cuts again. Three of its changes on one night bring the amber banner.

Why did my typed price disappear?

Four things clear or replace a manual price.

• Someone pressed Clear. The confirmation reads "Cleared. Your rules price this night again." Any Revenue Manager or above on the property can do it.
• Your system reported the night at 0. On a live property, a night MAYA has sent to that your system now has at 0 is read as you closing it. The night is left unpriced and the manual price there is cleared, unless MAYA's price wins is on, where your typed price is sent again over the 0. When you load a rate again, MAYA reads it as the starting point.
• Your system's rate was changed on a night MAYA had sent your typed price to. With Keep the change as your price, the new rate is kept as your price instead: the badge changes to "Changed in Cloudbeds".
• The night passed. Manual prices apply to tonight onwards.