Skip to content

Occupancy looks wrong

8 min readWhen something looks wrongUpdated October 10, 2026

In plain words

is rooms booked divided by rooms you can sell that night, counting room types ticked as rooms and any still tagged "needs your answer", and taking off first. It differs from Cloudbeds' headline number because Cloudbeds keeps blocked rooms in its count while MAYA removes only rooms you enter as out of service. It can read over 100%. On Mews, where Mews gives no count, a room category is counted as 100 rooms until we change that number, so email us your counts. On ThinkReservations the counts come from your list of rooms there.

Why does MAYA's occupancy differ from Cloudbeds'?

Two reasons. Both can make MAYA's number higher than Cloudbeds', and the second can also make it lower.

Blocked rooms. Cloudbeds' own headline occupancy keeps blocked rooms in the count it divides by. MAYA does not read room blocks, allotments or out-of-order rooms from Cloudbeds. It divides by the room type's room count minus any rooms you have entered as out of service in MAYA. So a block you enter in MAYA can only make MAYA's number higher than Cloudbeds', and a block you hold only in Cloudbeds does not make them differ.

Which room types count. MAYA counts only room types ticked as Counts as a room on the PMS tab, and any still tagged "needs your answer". If Cloudbeds lists a meeting room or a parking space as a room type and MAYA has it unticked, the two numbers divide by different room counts. MAYA's number reads higher when those types are emptier than your rooms, and lower when they are fuller.

Which bookings count is the same in both: bookings with the status confirmed, checked in, checked out or Confirmation Pending count as booked. Cancelled bookings and no-shows do not.

Read Sellable occupancy for the definition.

Why is my occupancy wrong when rooms are out of order?

Because nobody has told MAYA. Rooms out of order in your property system are not read. Enter them in MAYA: on the PMS tab, under the room type, press + Rooms out of service, fill in From, To, Units and an optional Reason (optional), and press Save. Those rooms come off the sellable count for those nights only, and your rules run on those nights again from the next cycle if they fall within the 396-night window. Nothing is sent to your property system about the block.

Standard has 12 rooms, 3 are out of service, 8 are booked: 8 of 9, which is 89%. Without the block it reads 8 of 12, which is 67%.

Read Tell MAYA rooms are out of service.

Why is occupancy over 100%?

Because more rooms are booked than MAYA reads as sellable. It happens when you mark after they were already sold (12 rooms, 3 out of service, 10 booked reads 111%), or when your property system has overbooked the night. MAYA does not cap the number. A room type with every room out of service that night is left out instead, its bookings with it, on the day card as in your rules.

A rule's threshold cannot go above 100, so a rule set to Greater than 100 acts on a night when the room types it measures are, together, booked past what you can sell. To catch one overbooked room type, measure only that type.

Why is my occupancy tiny on ThinkReservations or Mews?

On Mews, MAYA counts each room category's rooms from your spaces in Mews. Occupancy reads low when a category holds spaces you do not sell: switch them off in Mews, and the next cycle leaves them out.

If Mews lists no spaces at all, every room category gets the same number of rooms, one number for your whole property, 100 until we change it. A category with 6 rooms and 5 booked then reads 5% instead of 83%, and occupancy rules that need a full night never fire. If every category shows the same units on the PMS tab, email us your room categories and their room counts. Read Mews.

rules are not affected. counts bookings, not rooms, but it compares within seasons read from how full past nights were. Put the counts right before relying on booking speed too.

On ThinkReservations, MAYA counts each room type's rooms from ThinkReservations' list of rooms. Occupancy reads low when that list holds rooms you do not sell: mark them there as inactive, as not a room, or as not included in occupancy, and the next cycle leaves them out. Read ThinkReservations.

Why does a room type show 100 rooms?

The PMS tab's Room types list shows "100 units" for a room type whose room count MAYA does not have. On Cloudbeds the count is read from your system on every cycle, so this is rare and means Cloudbeds reported none. On ThinkReservations it is read from your list of rooms on every cycle, so it shows only when MAYA could not read that list when the room type first appeared, and the next cycle that reads the list puts the real count in. On Mews it is counted from your spaces in Mews on every cycle, so it shows only when MAYA could not read your spaces when the category first appeared (the next read that works puts the real count in), or when Mews lists no spaces at all and we have not set the one number for your property yet: email us the real count. While a room type ticked as a room shows 100, MAYA measures no room count for your bill, so it never raises your bill.

The day card says 85% but the log says 92%

They are reading different room types. The day card's percentage is the whole property: every room type ticked as a room, and any still tagged "needs your answer". A change log sentence such as "It was 92% full, past the 80% mark you set." is the occupancy over the room types that rule measures. A rule measuring only Standard reports Standard's occupancy.

When a rule's measured list includes a type that is not a room, MAYA leaves it out of the figure and says so: "That 92% leaves out Meeting Room." Read A rule did not fire for how a rule reads its own room types.

Does a group of 10 count as 10 rooms?

Yes, for occupancy. A booking that holds 10 rooms is 10 booked rooms on each of its nights. That is different from , where a booking counts once however many rooms it holds. Read Booking speed reads oddly.

Why does day revenue include my meeting room?

The day card's revenue figure sums every room type, including ones you have unticked as rooms. Occupancy and the "12/20 rooms" line use only the ticked ones, and any still tagged "needs your answer". So a meeting room booking adds to revenue and not to occupancy.

Why does day revenue differ from a revenue pickup rule?

Both value a booked night at the booking's rate as your system last reported it. They part only on a booking your system reported with no rate on MAYA's latest read: the day card counts the rate MAYA first read for that booking, and a rule set to Revenue (currency) counts it as 0. A booking your system has never reported an amount for is 0 in both. Neither figure is sent anywhere.

Why does day revenue not match my property system's revenue report?

MAYA adds up the nightly rates your system reports for booked nights. It never adds tax or takes off a booking site's commission, and what the rate includes depends on your system: in Cloudbeds and ThinkReservations it is the room rate on the same basis as your own rates, and in Mews it is the booking total, taxes included, split across its nights. A report that adds taxes, fees or extras, or takes off commission, will differ. The calendar has the detail for each system.

Was this page helpful?

Not answered here? Email us. We aim to reply within one business day.