In plain words
Your system and MAYA use different words for the same things. MAYA's is one of your rate plans (Cloudbeds) or rate types (ThinkReservations): the one per room type that MAYA writes to. A Cloudbeds reservation, a ThinkReservations reservation and a Mews reservation are all bookings in MAYA. A Cloudbeds room type, a ThinkReservations room type and a Mews room category are all room types in MAYA. This page is the translation table.
MAYA's screens mostly use MAYA's words: booking, night, room type, base rate, price. Your system uses its own. A few screens borrow your system's words. The connect screen, headed Connect your property system, talks about your "reservation history". The change log says "rates" for the prices MAYA sends, as in "Cloudbeds won't let MAYA change Deluxe rates". When a screen, a change log sentence or a docs page uses a word you do not use at the desk, this page says what it maps to.
The words that matter most
| MAYA says | Cloudbeds says | ThinkReservations says | Mews says | What it means in MAYA |
|---|---|---|---|---|
| Booking | Reservation | Reservation, holding one booking per room | Reservation, one room each | A stay. For occupancy each room counts. For a booking counts once however many rooms it holds. On Mews every room is its own reservation, so rooms booked together count once per room, unless you turn on Count bookings made together as one (3 or more for the same room type and dates, made within 3 hours) |
| Room type | Room type | Room type | Room category, space category or resource category | The kind of room a price is set for. Your rules set one price per room type per night |
| Units | Units | Rooms, counted per room type | Spaces (resources), counted per category | How many rooms a room type has. MAYA divides by it for . On ThinkReservations MAYA counts it from your list of rooms, and on Mews from your spaces. If Mews lists no spaces at all, it is one number for every room category, 100 until we set it with you |
| Room group | none | Room Group, on each room | none | Room types shown together under one name. On ThinkReservations a room type's group is the Room Group its rooms share. Each room type still has its own price. Read Room groups |
| The rate plan that follows nothing and has no public name (not derived) | The standard rate type called Best Available, or one picked on the PMS tab | none (not read) | The one rate per room type MAYA writes to and reads your own rate from | |
| Derived rate | Derived rate type | none | A rate that follows the base rate by your system's own rules. MAYA never writes to it. It moves when the base moves | |
| Package | Package, or any plan with a public name | Package, a standard rate type with rates of its own, one of your other standard rate types | none | On Cloudbeds, left alone by MAYA. On ThinkReservations, given the same change as your main rate on its own rate when ticked on the PMS tab (read the note below) |
| Night | Stay date, from check-in up to, but not including, check-out | Stay date, from start to end | Stay night, from arrival to departure | One night of a stay. A same-day booking is one night (on Cloudbeds, when Cloudbeds lists a room rate for that date) |
| Booking date | Date created | Created at | Created (UTC), read on your calendar | The date the booking was made, on your property's own calendar (on Cloudbeds, the date Cloudbeds records) |
| Rate (yours) | Rate | Price | none (not read) | The number in your system that MAYA reads as a night's starting point |
| Price (MAYA's) | Rate, once sent | Price, once sent | Shown only | The price your rules produce, which MAYA sends on Cloudbeds and ThinkReservations |
On ThinkReservations, each rate type is standard or derived (it follows another). A package or a non-refundable rate can be standard too. MAYA writes to the active standard rate type whose name contains Best Available. If none has that name, MAYA writes to the one active standard rate type that covers the most room types, even if it is a package. If two tie, MAYA writes to neither. Name your main rate type Best Available, or pick it on the PMS tab. Every other active standard rate type, a package or a wedding rate say, is one of your other standard rate types: MAYA gives it the same change as your main rate on its own rate when it is ticked on the PMS tab: all start ticked when you set up, and one first found once you are live waits for your tick. Read Your other standard rates.
Booking statuses and states
Your system marks each booking with a status. MAYA keeps some and removes others.
| Cloudbeds status | In MAYA |
|---|---|
| Confirmed | Counts as booked |
| Checked In | Counts as booked |
| Checked Out | Counts as booked (a past night) |
| Confirmation Pending | Counts as booked. It holds a room, and Cloudbeds' own occupancy counts it |
| Cancelled (Cloudbeds spells it "canceled") | Removed on the next read |
| No Show | Removed on the next read |
Two more Cloudbeds words: a booking in the unassigned list (not yet placed on a physical room) counts as a booked room, and a virtual room type (one that sells rooms from another type) is treated like any other room type.
| ThinkReservations status | In MAYA |
|---|---|
| Scheduled | Counts as booked |
| Checked in | Counts as booked |
| Checked out | Counts as booked (a past night) |
| Cancelled | Removed on the next read |
| No show | Removed on the next read |
ThinkReservations holds one booking per room inside a reservation. MAYA keeps each room's nights and room charge, and for the reservation counts once.
| Mews state | In MAYA |
|---|---|
| Confirmed | Counts as booked |
| Started | Counts as booked (the guest is in the house) |
| Processed | Counts as booked (a past night) |
| Optional | Counts as booked |
| Enquired | Counts as booked |
| Requested | Counts as booked |
| Canceled | Removed on the next read |
Only Canceled removes a booking. An option, an enquiry or a request counts like a confirmed booking until it is cancelled in Mews.
Each Mews reservation holds one room. A guest who books three rooms has three reservations in Mews, so for that stay counts as three bookings, unless you turn on Count bookings made together as one (3 or more for the same room type and dates, made within 3 hours of each other). On Cloudbeds and ThinkReservations the same stay counts once. MAYA does not read Mews reservation groups.
Comp, house-use and day-use bookings
Complimentary, house-use and owner stays. A booking counts by its status, not its rate. A comp or house-use booking at $0 counts as a booked room for sellable occupancy and , and as one booking for , like any other. On the calendar it adds $0 to the night's revenue, so it lowers the . There is no setting to leave $0 bookings out.
It never sets a night's starting price. A night starts from a price you typed, else your own rate from your system, and a night with neither is not priced, whatever its bookings are. Read How rules work together.
Day-use bookings (in and out the same day). They are not skipped. In ThinkReservations and Mews, a booking with check-out on its check-in date counts as one night on that date: a booked room for occupancy, and a booking for booking speed. In Cloudbeds, a booking counts on each date Cloudbeds lists a room rate for, so a same-day booking counts on its date when Cloudbeds lists a rate for it. Either way, a day-use room reads as booked that night, even though it can still be sold for the night.
Connecting words
| Word | Whose | What it means |
|---|---|---|
| Marketplace, Connect App, My Apps | Cloudbeds | Where you install MAYA and where you disconnect it. MAYA has no disconnect button of its own |
| Sign in with your Cloudbeds account, Sign in with your Think Reservations account | MAYA | The other way in: from the Connect your property system screen after paying |
| Access code | MAYA | A code that may be needed at checkout for some systems. Marketplace installs never need one |
| Client token, Access token, Enterprise ID | Mews | The keys MAYA uses to read Mews. We set them up with you |
| Group login | Cloudbeds, ThinkReservations | A login that reaches several properties. Through the Cloudbeds Marketplace it connects all of them. From inside MAYA it is refused |
| PMS tab | MAYA | The tab that shows the connection, its health, the last sync and your room type settings. "PMS" is the label. These docs say "property system" |
| Connected, Pending, Degraded, Error, Disconnected | MAYA | The connection words on the PMS tab. Read reconnecting and disconnecting |
MAYA's own words
These have no equivalent in your system.
| MAYA says | What it means |
|---|---|
| Cycle | One run for your property, about every five minutes: read bookings, refresh your rates if due, run rules, send changed prices |
| Window | Tonight and the next 395 nights. The nights your rules price and, once you are live, MAYA sends (Cloudbeds and ThinkReservations) |
| Rooms booked divided by rooms you can sell that night, counting room types ticked as rooms and any still tagged "needs your answer", and subtracting | |
| Counts as a room | The checkbox that says a room type is somewhere guests sleep |
| Rooms out of service | Units you take off sale for a stretch in MAYA. Your system's blocks are not read |
| , "Manual · $175.00" | A price you typed for a room type on a night |
| "Changed in Cloudbeds · $175.00" | A rate you changed in your system on a night MAYA had sent to, kept as a manual price. Also "Changed in Think Reservations" |
| "Rate removed in Cloudbeds" | Your system no longer has a rate for a night MAYA had sent to, so MAYA isn't pricing it until it has one again |
| MAYA's price wins | The setting that sends MAYA's price again over a rate changed or removed in your system, instead of keeping it |
| Simulation | The starting state. Everything runs and is written down. Nothing is sent |
| Live | After going live. Changed prices are sent every cycle (Cloudbeds and ThinkReservations) |
| "Prices not reaching Cloudbeds" | A change log item that says your system did not accept a price, and why |
| "Still happening", "Resolved", "Ended" | The state shown on a "Prices not reaching" item. Resolved: your system took the prices (on ThinkReservations, accepted them). Ended: something else closed it, such as a newer price replacing the failing one. Read when your property system does not accept a price |
For every other product word, read the glossary.
Example: One sentence, three vocabularies
The change log at The Harbour Inn says: "Cloudbeds won't let MAYA change Deluxe rates because that rate follows another rate plan". In Cloudbeds' words: the Deluxe room type's only rate plan is derived. In MAYA's words: Deluxe has no . The fix is the same in both: in Cloudbeds, give Deluxe a rate plan that follows nothing and has no public name. On ThinkReservations the change log shows a different sentence for a room type with no base rate: "MAYA can't find a base rate for Deluxe in Think Reservations, so its rates can't be changed". The fix there is adding Deluxe to your Best Available rate type, or picking a rate type that covers it on the PMS tab.