In plain words
To pause, turn your rules off: the prices they set stay where they are. To undo what a rule did, delete it. To hold a price on some nights, type it. To put the whole property back into simulation, email us; only we can switch it. Turning rules off, typing a price or going back to simulation never puts back a rate MAYA has replaced. Deleting a rule is the one route that does: its changes come off and the new prices are sent.
Five ways to stop, and what each keeps
| You want to | Do this | Prices already in your system |
|---|---|---|
| Stop every rule acting from now on | Turn each rule Off on the Rules tab | Stay as they are |
| Undo everything one rule did | Delete the rule | Go back to what they would be without it, and are sent |
| Stop one rule on certain nights | Answer Stop for this night on the amber banner | Stay as they are, unless the rule's undo box is ticked and cancellations mean the rule is no longer true |
| Hold a price on a night or a stretch | Type the price on the Calendar tab, with through… for a range | Become the price you typed (a 0 is saved but not sent) |
| Stop sending altogether, keep everything else | Email us to go back to simulation | Stay as they are |
On Mews, MAYA sends nothing, so each of these changes MAYA's prices only.
Turn rules off
Every rule on the Rules tab has an On / Off switch. Click it and the rule is off from the next . There is no confirmation for switching off.
Off freezes. The rule stops acting, and every change it has already made stays on the price, unchecked for cancellations; nothing is sent to undo it. Turning it On again opens the window with the days it will change, where you apply or skip the price adjustments. Read The On/Off switch.
To pause everything, turn every rule off. Nothing else happens: MAYA keeps reading your bookings and your rates, and sends a price only when one changes. With every rule off, a price changes when you type or clear one, or when a floor or ceiling you change moves it. And each morning one new night enters the window. It goes out at your own rate, kept between your floor and ceiling. Pause everything for a while is the short version.
Delete a rule
The red Delete button opens a dialog with Delete Rule and Undo Its Changes, Turn It Off and Keep Its Changes and Cancel. Deleting removes the rule and every effect it had: the next prices every night as if it had never run, and the prices that changed are sent (on Mews they change in MAYA only). The change log keeps its older price entries; your answers to the rule's keeps-adjusting banner go with it. Read Delete.
Stop a rule on certain nights
Once three of a or pickup rule's changes are on the same night, the amber Rules that keep adjusting banner asks you what to do. Stop for this night stops that rule on that night. What it already changed there stays, unless its undo box is ticked and cancellations mean the rule is no longer true. Your other rules keep working there. The rule then shows a "Stopped on 1 night" chip (one more for each night you stop) on the Rules tab, and Let it run again puts it back. Rules that keep adjusting explains the banner. There is no way to stop a rule on one night before the banner asks, other than turning the rule off everywhere. A typed price takes off what the rule already did on that night, but the rule can act on it again.
Hold a price on a night or a stretch
Click a night on the Calendar tab, type a price for a room type, click through… to pick the last night if you want a range, and click Save. On a live property, nights inside the 396-night window go to your system as typed, now. Nights further ahead are sent as they enter the window. In simulation nothing is sent. A price of 0 is saved but never sent, and no rule raises it: set the night to 0 in your system yourself. Rules that had already moved those nights pause for that room type. Rules that fire later still apply on top of any other price, so a typed price is a starting point, not a lock. A range can run from tonight up to 399 days ahead (366 nights at most in one save).
Clear takes your price off the night, and your rules set its price again. Setting a price yourself has every detail, and Hold a price for a wedding or event weekend is the short version.
Back to simulation
There is no switch in MAYA to put a property back into simulation. Going live is one-way in the app. To go back, email us from your MAYA sign-in address with your property name. We switch it for you.
What happens once we do:
- Sending stops on the next cycle. Everything else carries on: bookings are read, rules run, the change log fills, the calendar shows what MAYA would send. The amber simulation strip is back at the top of every screen, new runs in the change log are tagged Simulation and say what would have happened, and the runs from your live stretch keep saying whether each price was sent.
- The prices already in your system stay. MAYA never sends a rate to undo an earlier one. If you want different rates, set them in your system, or wait until you are live again and type them in MAYA.
- On a night MAYA never sent to, a rate you change in your system becomes the base. For example, a night that entered the window after we switched you back. MAYA reads your rate again within the hour (Cloudbeds and ThinkReservations) and uses it as the night's starting price. It is not kept as a .
- On a night MAYA sent to while you were live, a rate you change in your system waits. While you simulate, your rules keep working from the base that night already had. When you go live again, MAYA reads your rate as that night's base (next point).
- When you go live again, with Go live on the amber strip that is back at the top of the dashboard, MAYA reads your rates once more before its first send, and your rules work on top of them. A night whose rate you changed while simulating starts from that rate. A rate you changed in your system on a night MAYA had sent to, and that MAYA had already kept as a manual price ("Changed in Cloudbeds"), stays a manual price. Because MAYA has sent to the window before, the confirm offers only its Go live, which sends MAYA's prices: starting from your current rates is offered only to a property MAYA has never sent to (When the dialog offers only Go live).
- A rule still waiting after you went live from your current rates keeps waiting through the switch back, until MAYA measures it not true on that night (How a rule waits).
- Your rules, limits, history, manual prices and team are untouched.
Simulation mode describes the state you go back to.
Cancelling, and disconnecting
Cancelling your subscription is a different thing from pausing. It is done in the billing portal or by email, takes effect at the end of the paid period, and MAYA keeps working until then. After that, reading, pricing and sending stop, and the rates in your system stay as they are. Your rules and history stay too, and Restart your subscription brings MAYA back. Cancelling, restarting and leaving has the steps.
There is no disconnect button in MAYA. On Cloudbeds, uninstalling MAYA from your Cloudbeds account disconnects it: Cloudbeds tells MAYA, and reading, pricing and sending stop. On ThinkReservations or Mews, email us and we handle it with you. Disconnecting reverts nothing and does not cancel billing. To stop completely, cancel first, then disconnect. Reconnecting and disconnecting has the steps for each system.
A closed season
MAYA does not read future closures from your system, and there is no screen to enter one. Nights you are closed are priced and sent like any others while they are inside the 396-night window. Three ways to handle a closed stretch, from simplest:
- Close the nights in your system. Set the rate to 0 there (or close the night the way your system does, if that reports as a rate of 0). On a night MAYA has already sent to, MAYA reads the 0 on its next hourly read, your rules stop running on that night, and any there is cleared. On a night MAYA has never sent to, a rate of 0 means the night is not priced at all. Either way nothing more is sent for it. With MAYA's price wins on, clear the prices you typed in MAYA on those nights first, or MAYA sends them again over the 0. When you reopen and load a rate, MAYA reads it as the night's base and your rules work on top of it. This works for Cloudbeds and ThinkReservations. Nothing is sent to Mews in any case.
- Turn your rules off for the closed stretch and back on afterwards. Simple to do, but it pauses every night, open or closed.
- Type a price for the closed nights as a range. A typed price is sent as typed, so this only helps if a placeholder rate is what you want in your system. A 0 typed in MAYA is not sent, so for 0 use step 1.
A closure in the past is a separate matter: it should not skew comparisons. MAYA finds long stretches in your history with nothing booked (a stray booking or two allowed) and asks on the review, "Were you closed ...?" for a one-off stretch, or "Is your property normally closed ...?" for one that repeats each year. Confirming keeps those nights out of comparisons. Checking what MAYA found explains that card.
Example: January at the Harbour Inn
The Harbour Inn closes every January. In late November, Sam sets every night of the coming January to 0 in Cloudbeds. They are all inside the 396-night window, so MAYA has already sent to them. On its next hourly read MAYA finds the 0, the rules stop running on those nights, and the manual price Sam had typed for New Year's Day is cleared. Sam sets the January after that to 0 as well. Those nights are more than 395 nights ahead, so MAYA has never sent to them: each is read as 0 when it enters the window, and never priced. Nothing more goes to Cloudbeds for either January.
In mid-January Sam decides to open a week early and loads $150 for Standard on the last week of January, nights he had set to 0. MAYA reads $150 as the base for those nights and "Busy nights" raises the ones over 80% full to $165 as usual. (A rate changed in Cloudbeds on a night that was never closed, and that MAYA had sent to, is kept as a "Changed in Cloudbeds" price instead.)