What rules cannot do yet

Each limit and what to do instead

A weekend-only rule. Every rule you build runs every day of the week. There is no weekday choice in the builder, and MAYA has no setting for which nights are your weekend. (In these docs, and in how similar nights are chosen, weekends are Friday and Saturday nights.) Outside the demo property, whose rules were set up with days and dates, the one kind of rule limited to some days is a starter rule copied from your own rates after you answered "My pricing works": when your move happened only on Friday and Saturday nights or only on the others, or was different on each (a different size, step or window), its name ends in "(Fri and Sat)" or "(Sun to Thu)", and the "?" after its conditions in the rules list names the days. Read Your starter rules. What to do instead: for a weekend price, type a price on those nights on the calendar. It becomes the base for that night, and the rules already on it pause there (their changes come off). Read Setting a price yourself. For a rule that reads weekend busyness on its own, remember that booking speed already compares each Friday with other Fridays and each Saturday with other Saturdays, so a booking speed rule does not need a weekday switch to behave differently on weekends.

A date range, a season or an event. Every rule you build runs for every night in the 396-night window, all year. The builder has no dates. Outside the demo property, the one exception is a rule imported from PIE with a START DATE and END DATE: it covers only those nights, the "?" after its conditions in the rules list shows them ("Dates: Oct 15, 2026 to Nov 30, 2026."), and an edit keeps them. Read Import your rules from PIE. What to do instead: for a wedding weekend or a festival, type a price for the range with through… on the calendar (up to 366 nights in one save, from tonight to 399 days ahead). Rules already on those nights pause there (their changes come off), and rules that act later stack on top, so switch off the rules that would move those nights until the weekend has passed. Switching a rule off stops it on every night, so switch it back on afterwards. Read Hold a price for a wedding or event weekend. For seasons, booking speed already compares inside the season your history shows, so a booking speed rule adjusts to the season by itself.

Priority. There is no priority control: when two booking speed or pickup rules are true on the same night, the stronger one acts, in the order Which one fires when several match lists, and every true standard rule applies.

Either/or. Conditions on one rule are always "and": "Matches when all of the following are true." For "busy or last-minute", make two rules. Both can act on the same night, and their changes stack.

One night only. A rule cannot be limited to one night. Type a price for that night instead.

Both a percent and a fixed amount. A rule has one amount: type a number in one box and the other greys out. For "10% plus $5", make two rules. They stack.

An exact price, like $199. A rule changes the price by a percent or a fixed amount, up or down. It cannot set the price to a number. For an exact price, type it on the calendar for that night, or for a run of nights with through…. It is published as you typed it, and rules that act later stack on top of it. Read Setting a price yourself.

Copy or duplicate a rule, or copy rules to another property. Not yet. Build the rule again. Rules belong to one property.

An occupancy threshold above 100. The measured number can go above 100% (rooms out of service after a night sold, or overbooking), but the rule builder stops a threshold above 100 (your browser points at the box). Greater than 100 acts on a night when the room types the rule measures are, together, booked past what you can sell.

Two conditions of the same kind. One of each: at most one row of each of the nine kinds per rule (one fewer on Mews, where rooms left to sell isn't offered yet). For a band such as "between 60% and 80%", the builder cannot say it. Use two rules: one at Greater than 60, and a second at Greater than 80 that makes the change you want above the band. The two stack, so choose the second amount with the first already applied.

A current rate per changed room type. A current rate condition reads one number for the rule: the rate of the room types it measures, their average by rooms to sell when it measures several. It cannot act only on the room types that are under the mark. What to do instead: measure one room type, and tick Change prices on different room types to change others, or make one rule per room type. Read Current rate.

A cap on how far or how fast prices move. There is no setting such as "never more than 20% below my base rate" or "at most one change a day", and a floor or ceiling cannot be a percentage. Floors and ceilings are fixed amounts, one pair per room type, the same on every night.

To keep Standard ($150) within 20% of its usual rate, it needs a $120 floor. Type it in Standard's Floor box on the review to set it for Standard alone. On Cloudbeds, importing from PIE also sets each room type's own floor and ceiling from PIE's price limits, if you keep them there. Answering the floor question again would put $120 on every room type, Deluxe and Suite included. A floor is one amount for every night, so it does not follow a base rate that changes through the year. Read Floors and ceilings.

What keeps prices in check today:

• the floor and ceiling of each room type
• a standard rule makes one change while it is true, and takes it off when it isn't (unless its undo box is unticked, which usually keeps an occupancy or rooms left change on through cancellations)
• a booking speed or pickup rule waits after each change on a night (its Then waits (advanced) setting) before it can change that night again, and then counts only the bookings made since
• in each cycle, at most one booking speed or pickup rule changes a given night and room type
• once three of a booking speed or pickup rule's changes are on the same night, an amber banner asks you whether it should keep going

A price can still change more than once in a day. A standard rule switches on and off as bookings come and go, and a stronger rule can step in while a weaker one waits. Read How rules work together and Floors and ceilings.

A smallest change, such as "do not send moves under 1%". There is no minimum-change setting. Any price that changed, even by a cent, is sent to Cloudbeds or ThinkReservations once you are live. What to do instead: use larger amounts, or fewer rules that stack.

No changes in the last few days before arrival, or at certain hours. There is no freeze window and no quiet hours. Cycles run about every five minutes, day and night, and tonight is always priced. What you can do:

• On a booking speed or pickup rule you build, add a Booking window (days to stay) row set to Greater than 2. The rule then makes no new change on tonight or the next two nights. What it already did there stays, though with its undo box ticked a change still comes off when cancellations mean the rule is no longer true. When you add the row to a rule that is on, save the edit with Skip price adjustments: with Apply price adjustments, the rule's changes on tonight and the next two nights come off and, the rule no longer true there, don't come back.
• On a standard rule, the same row takes the rule's change off as the night comes within those days, and that is itself a price change. A standard rule cannot be kept still near arrival this way.
• On a starter rule, click Edit and add the row the same way, and save it with Skip price adjustments. Two things on starter rules can't be built new, and editing keeps them: Slow-date trim's exact level (in the builder, Slower Than Normal also matches the slower levels) and a copied rule's days, "(Fri and Sat)" or "(Sun to Thu)". A Last-minute starter rule already has a booking window row and acts only near arrival, so the row can't be added to it: switch it off instead.
• A price you type for those nights is published as typed, but rules that act later still stack on it, so it is not a freeze either.

Only direct bookings, or leaving out booking sites. There is no channel filter. Every booking counts the same, whatever channel it came from: direct, through an online travel agency (a booking site), or made at the front desk. That goes for sellable occupancy, booking speed and pickup count alike.

Length of stay (LOS) pricing, such as cheaper for a 7-night stay. There is no condition for how long a guest is staying, and no minimum stay setting. MAYA writes one nightly rate per room type on Cloudbeds. On ThinkReservations it writes one to your main rate type, plus the same change to each other standard rate type ticked under Also moves with MAYA on the PMS tab (Your other standard rates). It writes nothing to Mews. What to do instead: keep length-of-stay prices and minimum stays in your property system. A long-stay or discounted rate plan set up there to follow your base rate moves by your system's own rules when MAYA changes the base. On ThinkReservations, untick a long-stay standard rate type with its own prices on the PMS tab, or set it up as derived, if MAYA should not move it. Read Prices are not reaching your property system for how a plan that follows the base rate behaves.

A setting for how bold MAYA is. There is no aggressiveness setting and no slider from careful to bold. How far and how often prices move depends only on what you set: the rules, their amounts, the speed levels, the waits, and each room type's floor and ceiling. To be bolder, pick larger amounts, levels nearer Normal (such as Faster Than Normal), shorter waits or a higher ceiling. To be gentler, do the opposite or raise the floor. The last of the five questions picks your starter rules: copies of the raises and cuts your own rates made, or the usual five with bigger raises where your nights filled early. It sets no boldness for rules you build. Read The five questions and Your starter rules.

Room counts from before, and bookings that came and went. Booked so far vs usual reads earlier nights against today's room counts, because MAYA keeps no history of them: a room type that grew (10 rooms to 14) makes its earlier nights look emptier than they were, for up to three years. Earlier nights also hold only the bookings that stayed, on the night and room type they ended on, while tonight still holds bookings that may cancel. Mostly, these make a night read further ahead than it is. What to do instead: pair it with a Booking window (days to stay) row to keep it to nights nearer arrival, and set aside nights that weren't normal. Read Booked so far vs usual.

A rule that raises only when a night is nearly full and booking fast. This one you can do: put a Sellable occupancy (%) row and a Booking speed (recommended) row on the same rule. Both must be true.

Things that are settings, not rules

• Floors and ceilings are per room type, not per night, season or weekend. Read Floors and ceilings.
• Rooms out of service take rooms off the sellable count for a stretch of nights, which changes what occupancy rules see. Read Room types and rooms out of service.
• Which room types count as rooms is set on the PMS tab.