In plain words
On the Calendar tab, open the night and click Why this price? under a room type's price: it shows the price, what is behind it, and the changes to it, newest first. Or open the Change Log tab. Each lists what it changed, one bold line per change on a night across the room types it moved, followed by a sentence that names what changed, from the price just before, and the reason. For a change, click Show the numbers under the entry to see the counts behind it. The change log opens on your 10 most recent runs that changed a price, and Older at the bottom adds the 10 before them, back through 90 days. For a change older than that, check the night on the Calendar tab: a badge means the price was typed in MAYA or changed in your system, and Current price shows where your rules have taken your rate.
Why this price?
On the Calendar tab, click a night, then Why this price? under a room type's price. It opens on that night and room type. Night and Room type at the top pick another. It also opens from the Change Log (under each room type of a change, and under a change on one room type) and from a rule's fire log (under each night's room types).
- The price. "$150.00 → $165.00": where the night started and where your rules took it, when MAYA last worked it out, with the time under it. While your property is simulating it reads "$150.00 → MAYA would send $165.00". Under it, a chip for each thing behind the price, in the order they apply: where it started ("Cloudbeds' rate" with your system's name, "Your price" for a price you typed, or "Changed in Cloudbeds" for a rate changed there that MAYA kept), each rule's change ("Busy nights +10%", with "×2" when one rule's changes stacked), and "Your ceiling" or "Your floor" when one held it. A price you typed over your ceiling or under your floor is the limit itself, so that chip reads "Stopped at your $500.00" ("Stopped at the $500.00 set in Cloudbeds" for a rate changed there). A rule's chip opens its fire log. When the calendar now shows another price than the one last worked out, it says so: "How this price was worked out isn't kept."
- Its changes. The changes to the night, newest first, with sentences saying what changed and why. Where the Change Log's bold line counts the room types a change moved ("3 room types"), this one names the room type, and its sentence gives this room type's own prices. Other items for the night sit among them by time, for example a rate changed in your property system or your Stop for this night answer. An item for a rate MAYA sent its price over again says what became of that send, in the Change Log's words (Rates changed in your property system). Older adds 10 more at a time.
- The rules on the room type. Rules on Standard (with your room type's name) lists each rule that changes it, with where it stands on the night: "+10% on", "Off" (or "Off · +10% stays" when its change is frozen on the price), "held" (by a Skip, by going live from your rates, by a price you typed, or, for a raise, by a night given away at $0) or "not on". On a night MAYA isn't pricing, no rule reads "on" and an Off rule reads "Off": there is no price for a change to be on. Why not? beside one opens Why didn't it fire? for it.
Everyone on the property can open it. A night MAYA isn't pricing also says why: it has passed, it is past your window, or your property system has no rate for it, removed it or has it at $0. Its last price and changes still show while they are kept.
What is kept
A reading is kept each time a night's price changes, the changes on it or their order change, your floor or ceiling starts or stops holding it, or a price is typed. Readings are kept for 90 days, and the newest reading of a night still ahead is always kept. A run that changes nothing keeps no reading, so a night whose price hasn't moved can go a long time without one, and the price shown is from its last reading. Once you reach the oldest, "Nothing older is kept." shows under the list.
Open the change log
- 1
Go to the Change Log tab
It opens on changes only. Each entry is headed Pricing run with the time of the run in your browser's local time, such as "Sat, Nov 14, 2026, 3:05 PM PST", and how long ago it was, such as "(12 min ago)". Ongoing problems, headed Prices not reaching Cloudbeds (or your system's name), sit above every run.
- 2
Find the night
Inside a run, each change starts with a bold line in the shape "Nov 14 · 7 room types · Busy nights +10%": the night, the room types the run changed that way, and what changed. Look for the night. One change covers every room type moved the same way; Each room type under it lists each one with its own price before and after. In a run made while your property was simulating, the bold line starts "Simulation:", because nothing was sent.
- 3
Read the sentence under it
The first sentence names what changed and the move, from the price the night had just before the run: "Busy nights" raised this night 10%, from $150.00 to $165.00. The next sentence gives the reason in your own numbers: It was 85% full, past the 80% mark you set. Changes that were already on the price are named only in grey: "Warm-date bump's +10% still applies." The run that made that one has its own change further down.
- 4
Show the numbers for a booking speed change
When a rule acted, a Show the numbers link sits under the entry. It shows how many bookings the night received, how many a night like it usually has by that point, and the level that reads as. Which nights were compared? lists which past nights were compared and why, and List the nights lists them one by one.
What the sentences mean
| You read | It means |
|---|---|
| "Busy nights" raised this night 10%, from $150.00 to $165.00. | That rule fired in this run, on the room types in the bold line. $150.00 is the price the night had just before the run. |
| "Hot-week surge" raised this night 25%, from $165.00 to $206.25. with "Busy nights' +10% still applies." | A second rule fired on top of the first, in a later run. Percentages compound, so the 25% is applied to $165.00. |
| Cloudbeds' rate went from $150.00 to $160.00, so the price moved to $176.00. | Your own rate changed in your system. The rules already on the night stayed on it, so the price followed. |
| on 7 of 8 room types | The prices most of the change's room types share. Each room type has every one. |
| It was 85% full, past the 80% mark you set. | The condition that made an occupancy rule true. |
| Bookings came in faster than normal this past week: 9, against the 5 a night like this usually has by now. | The count behind a rule. It counts bookings, not rooms. Once the rule, or a stronger booking speed or pickup rule, has raised the night, it counts only the bookings made since the newest of those raises still on the night, and the sentence reads "in the 3 days since this rule or a stronger one's latest raise still on this night". Those bookings alone have to beat what a night like this usually gets in the rule's whole window. A raise from a (a rule with no booking speed or condition) does not change what it counts. A rule that cuts counts full days only, ending yesterday, and the sentence says "up to yesterday" or "after this rule or a stronger one's latest cut still on this night". |
| That would have gone past your $300.00 ceiling for Standard, so it stopped there. | The rules asked for more, and the ceiling held the price. |
| Cancellations meant "Warm-date bump" was no longer true, so its 10% raise came off. | Guests cancelled and the rule was no longer true for the night, so its change came off. The next sentence gives the numbers. |
| "Weekend nudge" was deleted, so its 10% raise came off. | You deleted the rule, which takes its changes off. |
| That took this night from $165.00 to $150.00. | The move, from the price the night had just before. The sentences before it say what came off or what changed. |
| Sam set the to $180.00. | A person typed a price on the Calendar tab. No rule is named because no rule acted. |
| The base rate was changed in Cloudbeds to $180.00. | The rate was changed in your property system on a night MAYA had already sent to, and MAYA kept that rate. |
| Fri, Nov 13, Standard: changed in Cloudbeds to $175.00. MAYA sent its price, $165.00, again. | An item of its own, not under a run: your setting is MAYA's price wins, so MAYA sent its own price over a rate changed in your property system. Before the send goes it reads "MAYA's price, $165.00, is waiting to be sent again." |
| Simulation: Nov 13 · Standard · Busy nights +10% | A run made while your property was simulating, tagged Simulation. Nothing was sent, and the sentences under it say what would have happened. |
| "Pricing rule" raised this night 10%. | The rule that acted has since been deleted, and the entry is from before October 2026, when entries did not yet keep a rule's name. Newer entries keep it. |
| It was 82% full. The rule has been edited since. | The entry is from before October 2026 and you have changed the rule since, so your marks at the time are not on record: it shows the numbers the run saw. Newer entries keep the marks. |
How far back the log goes
The tab opens on the 10 most recent runs that changed a price, however long ago they ran. On a busy day that may be the last hour, on a quiet week several days. Click Older under the last entry to add the 10 runs before them, and again for the 10 before those, back through the 90 days MAYA keeps. Once there is nothing older, "Nothing older. History is kept for 90 days." shows instead. The runs in between that changed nothing are counted into one quiet line per stretch, shown under Show All Cycles.
To see every night one rule changed, click its number in the Fired column on the Rules tab: its fire log lists each time it acted in the last 90 days, with the price before and after and why. Read The fire log.
If no run has changed a price yet, no runs are listed. Within a run you see the 40 biggest moves. When a run had more, a line under them counts the rest, such as "And 23 more changes in this run." (or "And 23 more prices would have changed in this run." in simulation).
If nothing is listed for the night
When the price moved before the oldest run on screen, click Older until its run shows (see above). A change older than 90 days is gone from the log, and you can still narrow it down yourself. Open the night on the Calendar tab and check three things:
- A badge on the room type's card. "Manual · $180.00" means someone typed that price in MAYA. "Changed in Cloudbeds · $180.00" (or your system's name) means the rate was changed in your property system and MAYA kept it. Either way, the starting price did not come from your rules. Hover the badge for the time it was set (or, for a rate changed in your system, when MAYA read it).
- Current price against your own rate. Current price is your rate for that night after your rules and your floor and ceiling. A gap between the two is what they added or took off. (MAYA reads no Mews rates, so on Mews the starting point is always a price you typed.)
- Which of your rules could apply. On the Rules tab, hold each rule that is On up against the night: how full it is, how many days away it is, and whether the rule changes that room type.
The detail behind every change is kept for 90 days, the same time the log reaches back. If you cannot find a change within that time, email us the night and room type and we can read it for you.
If the price did not move, most runs change nothing. Click Show All Cycles to include the quiet lines, such as "Prices checked 47 times from Sep 24, 10:05 AM to 1:55 PM, nothing needed to change". That is normal: about every five minutes MAYA reads your bookings and runs your rules on the nights that changed, and a price only moves when a rule's condition changes.
A night 396 or more nights away, past tonight and the next 395, is not priced yet, so it has no entries. A night before today is never priced.