In plain words
MAYA runs about every five minutes, prices again each night whose bookings changed, and prices every night from tonight to 395 nights ahead once a day. A rule has up to nine conditions. A or pickup rule waits 1 day to 2 weeks after it acts (a pickup rule up to its 30-day lookback); a doesn't wait. Booking speed compares with up to eight from the last three years. The tables below give every other number, with the page that explains it. Only one of them can be changed from the app: how many bookings a group counts as, in Settings.
The cycle
| What | Number | Read |
|---|---|---|
| How often MAYA reads your bookings and runs your rules on the nights that changed | About every five minutes | |
| How often every night in the window is priced again | Once a day, in the first cycles after midnight at your property, nearest nights first | |
| When a rule's wait ends, and a pickup lookback moves on | At your property's midnight: they count whole days | After a rule acts |
| How often your own rates are read (Cloudbeds and ThinkReservations) | About once an hour, and again when your property's date changes | What MAYA picks up from your system, and how soon |
| How often the whole is read again | Once a day | What MAYA picks up from your system, and how soon |
| When a read fails | Tried again 10 minutes later, then about every 15 minutes | Connection lost |
The window and prices you type
| What | Number | Read |
|---|---|---|
| Nights your rules price and MAYA sends | 396: tonight and the next 395, about 13 months | How rules work together |
| How far ahead you can type a price | Up to 399 days, from tonight | Setting a price yourself |
| Nights in one price save | At most 366 | Setting a price yourself |
| Nights in one block of | At most 366 | Room types and rooms out of service |
| Highest price you can type | $99,999,999.99, and never above the room type's ceiling | Setting a price yourself |
Rules
| What | Number | Read |
|---|---|---|
| Conditions in one rule | 1 to 9, at most one of each kind (8 on Mews, without rooms left to sell) | The rule builder, field by field |
| Amount of a rule's change, percent or fixed | Above 0, with no upper limit you would meet (anything under 1,000,000 saves), except that a percent cut must be under 100%. A fixed cut to 0 or below publishes the floor | The rule builder, field by field |
| Occupancy threshold | 0 to 100 | Sellable occupancy |
| Booked so far vs usual threshold | 0 to 100, percent of the rooms measured | Booked so far vs usual |
| Measured over for | Past day, Past week or Past month | Booking speed |
| Then waits (advanced) | 1 day to 2 weeks, 1 week when unset; a pickup row can also wait its lookback window, up to 30 days | After a rule acts |
| lookback | 1, 3, 7, 14 or 30 days | Pickup count (advanced) |
| Counted over for recent bookings | Yesterday, or the last 3, 7, 14 or 30 full days, starting on Last 7 full days; the threshold starts at 10 bookings | Recent bookings (advanced) |
| Rounding | A rooms left or recent bookings threshold to whole rooms or bookings, a to whole days, a current rate or threshold to the cent, a booked so far vs usual percent to two decimals. Prices are rounded to the cent, never to whole numbers | The rule builder, field by field |
| Adjustments before the amber banner asks you | 3 on the same night | Rules that keep adjusting |
| Rules switched On at the same time | 40. Rules switched Off do not count | How many rules you can have |
Booking speed
| What | Number | Read |
|---|---|---|
| compared | Up to 8, or up to 3 for a night near a holiday | Which past nights your rules compare with (advanced) |
| How far back they come from | The last 3 years | Which past nights your rules compare with (advanced) |
| Similar nights before MAYA widens the search | 4, away from holidays (with fewer, the search widens a step) | Which past nights your rules compare with (advanced) |
| Similar nights needed for the full range of levels | 5 (with fewer, the reading stays within one step of Normal) | Booking speed |
| Bookings needed to read Faster Than Normal | 9 when 5 are expected, 27 when 20 are expected | Booking speed |
| Bookings made together, counted as one (off as it starts) | 3 or more, same room type and dates, all made within 3 hours of each other, stays of up to 30 nights | What is counted |
| Count a group as up to | 1 to 10 bookings, 1 as it starts | Settings |
Booked so far vs usual
| What | Number | Read |
|---|---|---|
| compared | The same as 's: up to 8, or up to 3 for a night near a holiday | Booked so far vs usual |
| Similar nights it needs | 3 with bookings (with fewer, it isn't true) | Booked so far vs usual |
| The usual | To 0.1 of a room, the highest and lowest left out at 5 or more | Booked so far vs usual |
Floors and ceilings
| What | Number | Read |
|---|---|---|
| Floor until one is set | $1.00 | Floors and ceilings |
| Ceiling until one is set | $99,999.99 | Floors and ceilings |
| A floor of 0 | Not allowed. A typed 0 is a instead | Make a night free |
Your history
| What | Number | Read |
|---|---|---|
| History read when you connect | Up to about 10 years, as far as your system holds (not for Mews yet) | The history import |
| History and use | The last 3 years | The history import |
| History the review reads | First results from 3 years, then refined from everything imported | The history import |
| Bookings read ahead | About 13 months | The history import |
| History needed before MAYA builds | About 60 days of past stays | Your starter rules |
The change log and the PMS tab
| What | Number | Read |
|---|---|---|
| Runs on screen | The 10 most recent that changed a price, and 10 more each time you click Older | The change log |
| How far back the change log goes | 90 days | The change log |
| Changes shown per run | The 40 biggest moves, then a line counting the rest | The change log |
| Sending problems and your banner answers shown | Up to 20 of each per page | The change log |
| How long the detail behind a change is kept | 90 days, as far back as the change log goes | Find out why a price changed |
| A rule's Fired count and fire log | Fires in the last 90 days; the log shows 25 at a time | The fire log |
| Requests listed on the PMS tab (Cloudbeds) | The last 50, kept for 7 days | The PMS tab |
How often you can do things
When you go past one of these, the screen asks you to wait a few minutes and try again. Nothing is lost.
| What | Limit | Read |
|---|---|---|
| Saving or clearing typed prices, and room type changes | 30 per person in 10 minutes | Setting a price yourself |
| Checking the days a rule will change (the window before it starts acting; a or pickup rule's check counts three times) | 60 per person in 5 minutes | Turning a rule on, Apply or Skip |
| Import from PIE (Add and Try again) | 10 per person on a property in 10 minutes | Import your rules from PIE |
| Floor and ceiling boxes on the review | 120 per person in 10 minutes | Checking what MAYA found |
| Rate type pick and Also moves with MAYA ticks (ThinkReservations) | 6 per person in 5 minutes | Seeing and picking the rate type |
| Get suggestions from my data | 5 runs in 15 minutes | Getting suggestions later |
| Checking a code | 20 per person in 10 minutes | Codes and the free trial |
| Starting checkout | 10 in 10 minutes | Setting up payment |
| Invitations | 20 an hour on one property | Inviting and removing people |
Billing and your team
| What | Number | Read |
|---|---|---|
| Rooms you can sign up for yourself | 1 to 500 (above 500, email us) | What it costs |
| Free trial (Cloudbeds Marketplace only) | 7 days | Codes and the free trial |
| Second card check after checkout | 48 hours | Cards, payments and invoices |
| Time to set your room count after the room count email | 7 days | Your room count and what you pay |
| People on the team | 2 up to 20 rooms, 4 up to 40, 5 up to 60, 6 up to 80, 8 up to 500 | Inviting and removing people |
| Password | At least 8 characters | Create an account and sign in |
| Send the link again for a new confirmation email | Once a minute | Create an account and sign in |
| Telling us about a charge you dispute | Within 60 days | Cards, payments and invoices |
| Notice before a price change | At least 30 days | What it costs |
| Deleting your data after a verified request | Within 90 days | Cancelling, restarting and leaving |
| A Cloudbeds Marketplace property that never paid, unused | Its history may be removed after 180 days | Cancelling, restarting and leaving |
The connection
| What | Number | Read |
|---|---|---|
| The Cloudbeds Marketplace hand-over link | Good for 24 hours | Cloudbeds |
| The sign-in link from inside MAYA | Good for 15 minutes | How to get started |
| A rate you change in your system is kept as yours | When changed 60 minutes or more after MAYA's send landed | Rates you change in your property system |
| Changes that look like another pricing tool | 20 or more rates in one read, or changes on 3 or more days within 7 days; said at most once every 7 days | When something else seems to change your rates |
| The overwrites email, with MAYA's price wins on | At most once a day, listing up to 40 nights and room types, then how many more | Emails MAYA sends |
| Overwrites in the change log | The newest 50 within each page of runs, back through the log's 90 days (MAYA keeps its record of them for 180 days) | The change log |
| An unfinished Cloudbeds job is sent again | After 45 minutes | How prices reach your property system |
| A price that will not land is tried again | Every cycle, up to 10 times at one price, then once a day | When your property system does not accept a price |
| You are told about a problem that usually clears itself | After 2 hours and at least 5 tries | When your property system does not accept a price |