Glossary

A to C

ADR (screen: ADR $160.00). Average daily rate: a room type's room revenue for a night divided by the rooms of that type booked that night. It is on the room type cards in the calendar's day detail. With nothing booked it shows a dash: "ADR –". A calendar day can also show the whole night's ADR, when your property picks it in Settings: the room revenue of the room types ticked as rooms, and any still tagged "needs your answer", divided by the rooms booked in them. Read The calendar and Settings. A rule can act on it too, with the Average rate booked, ADR (advanced) condition, which leaves out rooms booked with no rate or at 0: read Average rate booked, ADR (advanced).

Apply price adjustments (screen). One of the two choices in the window that opens before a rule starts acting (switched on, added, or saved with changes while on): the rule changes the days the window showed from the next pricing run. Read Turning a rule on, Apply or Skip.

Base price. The price a rule starts from on a night and room type. It is your typed price if you set one, else your own rate as read from your property system. Nothing else: a night with neither is not priced. Read How prices reach your property system.

Base rate (screen, Cloudbeds). The one rate plan per room type that MAYA writes to in Cloudbeds: the plan that does not follow another plan and has no public name. Derived plans follow it by Cloudbeds' own rules. In ThinkReservations, the Best Available rate type, or the one picked on the PMS tab. The change log also says "set the base rate" for a price someone typed. There it means the night's starting price. Read What MAYA reads and writes.

Best Available (ThinkReservations). The active standard rate type whose name contains "Best Available". One named exactly "Best Available" or "Best Available Rate" comes first. It is the rate type MAYA sends its prices to in ThinkReservations. If no active rate type has that name, MAYA uses the one active standard rate type that covers the most room types. If two tie, neither is used and nothing is priced or sent until you name one Best Available or pick one. A General Manager or Hotel Admin can pick any active standard rate type on the PMS tab instead, and the tab says "MAYA reads and writes:" with the one in use. Read ThinkReservations.

Booking. For booking speed, one reservation for one night, however many rooms it holds: a 20-room wedding booked as one reservation in Cloudbeds or ThinkReservations is one booking. In Mews each room is its own reservation, so each room counts as a booking. Separate reservations made from one Cloudbeds allotment block, or in one ThinkReservations group or group block, are one booking. On any system, so are bookings made together: 3 or more separate reservations for the same room type and dates, made within 3 hours of each other, once you turn on Count bookings made together as one in Settings (it starts off). Under its Advanced, Count a group as up to lets a group count as up to 10 bookings. For sellable occupancy each room counts, so the same wedding is 20 booked rooms, and pickup count counts every room too, a group's included. Read Booking speed.

Booking speed (screen). How many bookings a night received in the past day, week or month, compared with how many similar past nights had received by the same point before arrival. Seven levels, from Stalled to Surging. Read Booking speed.

Booking speed and pickup rules. Any rule with a Booking speed or Pickup count condition. It acts, the change stays on the price, and after its wait it can act again on the same night, so raises stack on raises and cuts on cuts. At most one of them acts on a night and room type per run. Read After a rule acts.

Booked so far vs usual (screen). A rule condition: every room booked for a night so far, on the room types the rule measures, against what similar past nights had booked at the same number of days before arrival. Ahead of usual by at least or Behind usual by at least a percent of the night's rooms to sell. The calendar's day card says it as "12 booked, usually 7 by now". Read Booked so far vs usual.

Booking window (screen: Booking window (days to stay)). The number of days until the stay, on your property's own calendar. Tonight is 0, tomorrow night is 1. Read Booking window.

Ceiling (screen). The highest price MAYA will publish for a room type. Setup fills it from your answer to the five questions where it fits, or else from your own rates if the room type has at least 200 room nights sold. Otherwise it stays at $99,999.99 (a number in your own currency), which stops nothing in the dollar, euro and pound style currencies MAYA works in, until you set one (Which currencies MAYA works in). Read Floors and ceilings.

Change Log (screen). The tab that shows your pricing runs that changed a price, the 10 most recent first and 10 more each time you click Older, back through 90 days, and for each change, which rule acted and why. The quiet runs between them are counted into lines, shown under Show All Cycles. Read The change log.

Changed in Cloudbeds (screen: Changed in Cloudbeds · $123.00). The badge on a room type card for a rate you changed in your property system on a night MAYA had already sent to. MAYA keeps it like a manual price, while your setting is Keep the change as your price. The same words head a change log item when MAYA sent its price again over such a change. Read Rates changed in your property system.

Closed period. A stretch when the whole property was shut, confirmed on the setup review. Its nights are left out of every comparison. Read Checking what MAYA found.

Code. A signup code we give you that opens self-serve signup for a property system, or grants a trial or a discount. One code per property. A code's own free days replace the Marketplace trial rather than adding to it, while a discount code with no free days keeps the trial and discounts the invoices after it. Read Codes and the free trial.

Colour key (screen). The small key on the left of the calendar: "Strong night" beside green, "Typical night" beside amber and "Weak night" beside red, or the reverse on a property that reversed its colours in Settings. Its ? says how a night is judged. Read The calendar.

Comp night. A night with a manual price of 0. No rule raises it. MAYA does not send 0 to any property system, so you set it there yourself. Read Make a night free.

Connected (screen, on the PMS tab). The connection to your property system is working: MAYA reads your bookings and, once you are live, sends prices. The other words the Connection card can show are Pending, Degraded, Error and Disconnected, each defined here. Read The PMS tab.

Counts as a room (screen). The checkbox on the PMS tab that says a room type is somewhere guests sleep. Ticked types are what MAYA divides by for sellable occupancy, and what you are billed for. A type tagged "needs your answer" has not been ticked or unticked yet: it counts in occupancy but not in your bill until you answer. Read Room types and rooms out of service.

Current price (screen). The price MAYA has worked out for a room type on a night, after rules and limits. It is what the calendar shows and what is sent. Read The calendar.

Cycle. One run of MAYA for your property, about every five minutes: read bookings, refresh your rates if due, run your rules on every night whose bookings changed or that a change of yours reaches (and on every night once a day, after midnight at your property) and, once you are live, send the prices that changed. For Mews, MAYA does not read rates or send prices yet. Cycles run on MAYA's side, day and night, whether or not anyone has MAYA open, and your own internet being down does not stop them. Only MAYA being unable to reach your property system's service does, or a stopped subscription. Read How rules work together.

D to H

Degraded (screen, on the PMS tab). Two meanings. On the Connection card (Cloudbeds and ThinkReservations only): MAYA is still reading and sending, and one calm line says "Your Cloudbeds connection needs a refresh soon. Prices are still updating." It usually clears by itself on the next read. If it is still there in an hour, a General Manager or Hotel Admin reconnects, which does no harm. On the Health (last 24 hours) card: 80% to under 98% of MAYA's requests to your system succeeded. Read Reconnecting and disconnecting.

Derived rate plan. A rate plan in your property system that follows another plan by a rule of its own, such as 10% off the base rate. MAYA never writes to one. It moves when the base rate moves, by your system's own rules. ThinkReservations calls it a derived rate type. Read How prices reach your property system.

Disconnected (screen, on the PMS tab). MAYA's access to your property system is gone: the app was uninstalled, its permission was removed, or your system refused it. Nothing is read or sent until a General Manager or Hotel Admin reconnects. Nothing is deleted. Read Reconnecting and disconnecting.

Error (screen, on the PMS tab). Your property system refused MAYA's saved access, so reading has stopped for now. MAYA keeps trying about every 15 minutes, and the card goes back to Connected by itself once a try works. If it does not clear, a General Manager or Hotel Admin reconnects. Read Connection lost.

Fired (screen). The number of pricing runs a rule acted in over the last 90 days, each run counted once however many nights and room types it changed, including changes that later came off. A booking speed or pickup rule can act on the same night again in a later run. Click the number for the rule's fire log, which lists each one. Read The list and The fire log.

Floor (screen). The lowest price MAYA will publish for a room type. Setup fills it from your answer to the five questions, or else from your own rates if the room type has at least 30 room nights sold. Otherwise it stays at $1.00, which stops nothing, until you set one (a floor cannot be 0). Read Floors and ceilings.

General Manager (screen, a role). Everything except managing Hotel Admins: pricing, going live, the property system connection, billing and the team. Read Roles.

Go live. Switching a property from simulation to live, so its changed prices are sent to Cloudbeds or ThinkReservations every cycle (nothing is sent to Mews yet). A General Manager or Hotel Admin does it with Go live on the amber simulation strip at the top of the dashboard. The review screen has no Go live. Mews has no button: email us and we switch the property live. One way in the app: only we can switch a property back. Read Going live.

Guardrails (screen, in the Rate Simulator). A room type's floor and ceiling, shown together as a range.

Hold My Hand / Let Me Drive (screen). The two setup paths. Hold My Hand asks five optional questions and walks you through the review. Let Me Drive goes straight to the dashboard, and the review stays available. Read Hold my hand or let me drive.

Holiday. One of 17 US holidays MAYA uses to pick similar nights: a night near Thanksgiving is compared with the same position around Thanksgiving in earlier years. No other holidays exist yet. Read Time, weekends, currency and holidays.

Hotel Admin (screen, a role). Everything, including managing General Managers. The person who creates the account and pays is a property's first Hotel Admin. Read Roles.

Hotel day. A calendar date in your property's own time zone. The window, booking windows, "past week", pickup count lookbacks and rule waits all count in hotel days. Read Time, weekends, currency and holidays.

L to P

Keep the change as your price (screen, in Settings). The choice every property starts on for a rate changed or removed in Cloudbeds or ThinkReservations on a night MAYA sent to: a changed rate is kept as your price, and a removed one stops MAYA pricing the night until your system has a rate again. The other choice is MAYA's price wins. Read Rates changed in your property system.

Last sync (screen, on the PMS tab). The last time MAYA read your bookings from your property system successfully, about every five minutes on a healthy connection. It says nothing about sending prices. Read The PMS tab.

Level. One of the seven booking speed readings: Stalled, Much Slower Than Normal, Slower Than Normal, Normal, Faster Than Normal, Much Faster Than Normal, Surging. Read Booking speed.

Live. The state after going live. Every cycle, prices that changed are sent to Cloudbeds or ThinkReservations. Nothing is sent to Mews yet, so a Mews property only shows as live. Read Simulation mode.

Manual price (screen: Manual · $123.00). A price you typed for a room type on a night on the Calendar tab. It becomes the night's base price. Once you are live, it is sent as typed to Cloudbeds or ThinkReservations (a night beyond the 396-night window goes when it enters the window). Nothing is sent to Mews yet, and a price of 0 is never sent. Rules already on that night pause for that room type, and rules that fire later stack on top. Read Setting a price yourself.

Marketplace. The Cloudbeds Marketplace, where a Cloudbeds property installs MAYA with Connect App. Properties that arrive this way get the free trial and can come in as a group. Read Cloudbeds.

MAYA's price wins (screen, in Settings). The choice for a property that also runs another pricing tool: a rate changed or removed in Cloudbeds or ThinkReservations on a night MAYA sent to is not kept, and MAYA sends its own price again, logs each night in the change log and emails your General Managers and Hotel Admins at most once a day. Prices typed in MAYA are never replaced. Read When MAYA's price wins.

Measure / Change (screen). The two room type lists of a rule that watches one set of room types and prices another, shown when Change prices on different room types is ticked. Read Measure one set, change another.

Measured over (screen). The booking speed window: Past day, Past week or Past month, counted in booking dates on your property's calendar, today included. A rule that cuts counts full days only, ending yesterday. Read Booking speed.

Momentum (in explanations). The fallback reading when a night has no similar past nights: how nearby dates of the same kind (weekend or weekday) are filling now compared with the same dates a year earlier. Always treated as thin evidence. Read Similar nights.

Not a fair comparison? (screen). The link on a compared night that lets you set it aside with a reason. Read Not a fair comparison.

Other standard rate types (ThinkReservations; screen: Also moves with MAYA). Your active standard rate types with rates of their own besides the one MAYA reads and writes, such as a wedding, group or package rate. Each one ticked on the PMS tab or the review gets the same change as your main rate on its own rate, so its usual gap stays. All start ticked when you set up; one first found once you are live is held out, marked New, until you tick it. Floors and ceilings don't apply to them. Read Your other standard rates.

Package. A rate plan that sells the room together with something else, such as breakfast or parking. On Cloudbeds MAYA never writes to a package. A package built on the base rate moves when the base rate does, by your system's own rules. On ThinkReservations a package rate type with rates of its own is one of your other standard rate types. Read What MAYA reads and writes.

Paused. A word with four meanings, so these docs keep them apart. A rule you set to Off on the Rules tab is "switched off": it stops acting and its changes stay on the price (the switch says On and Off, and the list's filter says Enabled and Disabled). Rules on a night where you typed a price are "paused" there, as the save's confirmation says ("Paused 2 rules on this night for this room"): a booking speed or pickup rule's changes come off that night, and a standard rule stops moving the price until it stops being true and becomes true again. "MAYA has paused work on this property" is the banner shown while the subscription is not active, and "Paused" as a status on the Billing page means the subscription is on hold in Stripe. Read Turning a rule off, deleting it, or changing it, Setting a price yourself and The billing page.

Pending (screen, on the PMS tab). Connected but not paid for yet, or set up and not switched on yet. Nothing runs until then. Finish payment, or wait for us. Read The PMS tab.

Pickup count (screen: Pickup count (advanced)). How many room nights, or how much revenue, a night gained over 1, 3, 7, 14 or 30 whole days at your property, cancellations subtracted: today so far and the days before it, or for a rule that looks for low pickup, the full days up to yesterday. Read Pickup count.

PMS (screen). Your property management system: Cloudbeds, ThinkReservations or Mews, where your bookings and rates live. In these docs, "property system". Read Which systems work.

Price and rate. In these docs, a price is what MAYA works out and sends. A rate is what lives in your property system, such as your base rate or a rate you changed there.

Pricing run (screen). One evaluation of every night and every rule for your property. The change log shows those that changed a price, one entry per run, 10 at a time. Read The change log.

R to S

Rate Simulator (screen). The tab where you make up a night and see what your rules would do to it. Nothing there is saved or sent unless you click Save This Rule, and a rule saved from there arrives switched Off. Read The Rate Simulator.

Revenue Manager (screen, a role). Day-to-day pricing: rules, typed prices, floors and ceilings, room types and rooms out of service, answering the Rules that keep adjusting banner, setting dates aside, and what the calendar shows and what MAYA does with rates changed in your property system, in Settings. A Revenue Manager cannot go live, reconnect the property system from MAYA, or open the Billing or Team pages. Read Roles.

Revenue on the books (screen). Room revenue from bookings already made for that night, shown on the calendar day card. Read The calendar.

Reversed (screen, in Settings). The other choice for the calendar's colours: green marks a weak night worth working on and red a strong night you can leave. Amber is a typical night either way. Standard is where every property starts. Read Settings.

RevPAR (screen). Revenue per available room: a night's room revenue from the room types ticked Counts as a room, and any still tagged "needs your answer", divided by the rooms you can sell that night (the rooms in those room types, less rooms out of service). A calendar day shows it when your property picks it in Settings, and the calendar's colours rank your nights by it (the ? by the colour key says "revenue per room"). Unticking a room type takes its rooms and its revenue out of it. Read The calendar and Settings.

Room count. The number of rooms you are billed for. MAYA measures it from your property system every cycle, counting only room types ticked as rooms. Read Your room count.

Room group. Room types your property system shows together under one name. On ThinkReservations it is the Room Group column: when you sell rooms by name, each room is its own room type and its Room Group puts them together. MAYA shows room types under their groups and gives each group a button in the rule builder. Each room type keeps its own price. Read Room groups.

Room night. One room for one night. A booking of 2 rooms for 3 nights is 6 room nights. Pickup count and the import's progress bar count room nights. For a single night, room nights are the rooms booked.

Rooms out of service (screen). Rooms you take off sale for a stretch, entered on the PMS tab. They come off the sellable count for those nights only. Nothing is sent to your system. Read Room types and rooms out of service.

Rough estimate (screen). The last line of the change log: what MAYA's prices added, from bookings already made. On a raised night each room booked while the raise is on adds MAYA's price less your rate. On a cut night each booking beyond the usual pace adds what an average booking paid. Nothing is subtracted. For time MAYA's prices weren't sent (in simulation, on Mews, or with sending switched off), it says what you would have added. It counts bookings, never nights still to sell. Read The rough estimate.

Rule. One sentence you write once: when a night looks like this, change its price by that much. MAYA checks every rule on a night within about five minutes of its bookings changing, and on every night once a day. Read What a rule is.

Rules that keep adjusting (screen). The amber banner that asks you what to do once three of a booking speed or pickup rule's changes are on the same night. Read Rules that keep adjusting.

Skip price adjustments (screen). The other choice in that window: the rule is on, but the days the window showed keep their prices, each until the rule stops being true there and then becomes true again. Every other day works as with Apply, and a booking speed or pickup rule counts every booking on the books, the ones made before it included. Read Turning a rule on, Apply or Skip.

Season. A stretch of your year that books differently, found from your own history and never set by hand. It only ever appears inside an explanation. Read Similar nights.

Seats. How many people can be on a property's team, members plus pending invitations: 2, 4, 5, 6 or 8, following your room count. Read Inviting and removing people.

Sellable occupancy (screen). Rooms booked divided by rooms you can sell that night, counting only room types ticked as rooms, and any still tagged "needs your answer", with rooms out of service taken off first. Twelve rooms, three out of service, eight booked: 89%. Read Sellable occupancy.

Set aside (screen: Set this date aside). Marking a past night as not a fair comparison so it is left out of comparisons from the next run. Read Not a fair comparison.

Settings (screen). Opened from the gear at the top right of the dashboard. What each calendar day shows and which way its colours read, for everyone on the property, and your own text size. Read Settings.

Show the numbers (screen). The link under a change, in the change log or in Why this price?, on a night that kept a booking speed or booked so far vs usual reading. It opens the counts behind the change, the nights MAYA compared with, and the way to set one aside. Read The numbers behind a change.

Similar nights. The up to eight past nights MAYA compares a night with, from the last three years: same weekday (or, near a holiday, the same position around it) and same time of year. When too few match, other nights of the same kind are added: weekend nights (Friday and Saturday) for a weekend night, the other weekday nights for a weekday night. A night near a holiday has at most three, one a year. Read Similar nights.

Simulation mode. The starting state of every property. Everything runs and is written to the change log, and nothing is sent to your property system. Read Simulation mode.

Standard rule (screen, in the How rules behave panel). A rule with no booking speed or pickup count condition: its conditions are any of sellable occupancy, rooms left to sell, booked so far vs usual, booking window, current rate, recent bookings and average rate booked. It keeps one change on while it is true and takes it off when it isn't (with its undo box unticked, cancellations usually don't take an occupancy or rooms left change off: The undo box). It never stacks on itself. Read Two kinds of rule.

Starter rules. The rules MAYA adds at setup when your property has about two months of history and no rules yet. Which ones depends on your answer to the last of the five questions: usually five booking speed rules (Slow-date rescue, Slow-date trim, Warm-date bump, Hot-week surge and Sudden-spike catcher), with bigger raises where your nights filled early, and possibly a raise for nearly full nights, after "Find money I'm leaving on the table", or, after "My pricing works", rules copied from the raises and cuts your own rates made. Read Your starter rules.

Stopped on N nights (screen). The chip under a rule's switch that counts the nights still to come on which you told it to stop, with Let it run again beside it. Read Rules that keep adjusting.

T to Y

Text size (screen, in Settings). Standard, Large or Larger: how big MAYA shows its text for you, on every device you sign in on. Read Settings.

Then waits (screen: Then waits (advanced)). How long a booking speed or pickup rule leaves a night alone after acting on it: 1 day to 2 weeks, or a pickup row's lookback window, up to 30 days. A booking speed row waits 1 week when unset, and a pickup count row waits its lookback window (Same as the lookback window) unless you choose another; picking a 14- or 30-day lookback starts it on 1 week. A rule with both waits the longer of the two. A pickup row looking for low pickup (Less than) never acts again before its whole lookback window has passed. Read Booking speed and How long a pickup rule waits.

Three-times question. Another name for the Rules that keep adjusting banner.

Turn it on (screen). The one button in that window, beside Cancel, when it reads "0 prices will be affected by this rule.": the rule is saved on and changes nothing now. For an edit to a rule that is on, the button reads Save changes and does the same. Read Turning a rule on, Apply or Skip.

Trial. Free days before your first charge. Properties that arrive from the Cloudbeds Marketplace get a 7-day free trial at their first signup, never on a restart. A code can carry its own trial, which replaces the Marketplace one rather than adding to it, and also counts at the first signup only: a restart gets no trial of any kind. A card is taken and nothing is charged until the trial ends. Read Codes and the free trial.

Usual number (in explanations). What similar past nights had received over the same stretch of their own run-up, averaged with the highest and lowest dropped once there are five or more. It can be a fraction, such as 0.4. On screen it reads "nights like this one usually get about 5 bookings", or "almost no bookings" under 1, and is rounded to a whole number otherwise. Read Similar nights.

Viewer (screen, a role). Can look at everything and change nothing. Read Roles.

Wait. See Then waits. The wait is counted per rule, night and room type, from that night's last counted change, or from a price you typed if it came later, in whole days at your property: a 2-day wait from a change made any time on Monday is over as Wednesday begins.

Weekend. Friday and Saturday nights. Used when similar nights are chosen and seasons are read. Rules have no weekday control yet. Read Time, weekends, currency and holidays.

Window (396 nights). Tonight and the next 395 nights on your property's calendar, about 13 months: the nights your rules price and, once you are live, the nights whose prices are sent to Cloudbeds or ThinkReservations. A price you type further ahead is sent when its night enters the window. Read How prices reach your property system.

Your corrections (screen). The panel at the top of the change log that lists every date you have set aside, each with Undo. Read Not a fair comparison.

Words from other revenue tools

If you have used another revenue tool, these are the words you may be looking for, and what MAYA calls them.

Comp set (competitive set). Not used. MAYA reads no competitor rates and no data from other hotels, only your own bookings and rates. Read What MAYA does.

Lead time. MAYA calls it the booking window: the number of days from today until the night. A rule uses it through the Booking window (days to stay) condition. Read Booking window.

Length of stay (LOS). Not used by rules. There is no condition for how long a guest stays, and MAYA writes one nightly rate per room type. Keep length-of-stay prices and minimum stays in your property system. Read What rules cannot do yet.

Pace. MAYA calls it booking speed: how many bookings a night received in the past day, week or month, compared with what similar past nights had received at the same point before arrival. Where a night stands overall, its rooms on the books against where similar nights stood at the same point, is booked so far vs usual. Read Booking speed and Booked so far vs usual.

PIE (Price Intelligence Engine). Cloudbeds' own rule-based pricing. Its occupancy rules and price limits can come into MAYA from a screenshot. Read Import your rules from PIE.

STLY (same time last year). There is no STLY report. The nearest thing is similar nights: each night is compared with similar past nights from the last three years, read at the same distance before arrival. A rule on booked so far vs usual compares the rooms on the books with them, and the calendar's day card shows it for a night such a rule covers. When none can be found, momentum compares nearby nights now with the same nights a year ago. Read Similar nights.

Yield rules. MAYA calls them rules: one sentence you write once, such as "when a night is more than 80% full, raise every room type by 10%". If your property system has yield rules of its own that change the base rate, switch them off before you go live. Read What a rule is.