In plain words
Open the first night on the Calendar tab, type the price on each room type card, click through… to pick the last night of the weekend, and Save. That price goes to Cloudbeds or ThinkReservations as typed (on Mews, set it in Mews itself), and rules that had already moved those nights are paused. Rules that fire later still stack on top, so to keep your number, go to the Rules tab and switch off the rules that would move those nights. Rooms held in your system without bookings are invisible to MAYA: enter them as .
Type the price for the weekend
- 1
Open the first night
Go to the Calendar tab and click the Friday. The room type cards appear under the grid.
- 2
Type the price on a room type card
In the box on the Standard card, type the price you want for the weekend, say 250.
- 3
Cover the whole weekend
Click through… and pick the Saturday as the last night. The × beside the date goes back to a single night.
- 4
Save, then repeat for each room type
Click Save. The line under the box confirms it: "Saved. Sending to Cloudbeds now." on a live property, or "Saved (simulation: not sent to Cloudbeds)." while you are simulating. Each room type has its own card, so do the same on Deluxe and Suite.
Setting a price needs Revenue Manager access or higher. Prices apply from tonight up to 399 days ahead, and one save covers at most 366 nights. A price under the room type's floor or over its ceiling is refused with the limit named, for example "Above this room type's ceiling of $300.00."
On Mews, MAYA does not send prices yet, so set the weekend's rate in Mews itself. Typing it in MAYA only changes what MAYA shows, and the line under the box says so: "Saved. MAYA doesn't send prices to Mews yet." on a live property. Switching rules off changes nothing in Mews either. Read Nothing is sent to Mews.
What holds and what does not
Your typed price becomes the starting point for those nights and room types. Rules that had already raised or cut them are paused for that room type, and the confirmation counts them: "Paused 2 rules on this night for this room".
It is not a lock. A rule that fires afterwards stacks on top of your number. A rule waits its wait, in whole days from the day you typed, then reads its whole window again, bookings from before your price included. A (a rule with no booking speed or condition) that becomes true later applies on top too.
Switch off the rules that would move those nights
The reliable way to keep your number today is to type the price and then switch off the rules that would move those nights. On the Rules tab, click a rule's switch so it reads Off. Click it back to On once the weekend has passed, and apply or skip the price adjustments in the window that opens.
Off stops the rule on every night, not only the weekend, and what it already did stays. For a weekend held as a block, the rules to switch off are usually the ones that cut, because a block adds no bookings (see below). Read Off, delete or change.
If you would rather keep a rule on, type the price again whenever it moves one of those nights. Each save takes the rule's change off that night again.
Stop for this night on the amber banner, answered after you type, cannot keep your number. The banner asks only once a or rule (the two kinds that fire, then wait before firing again) has three of its changes on a night, and your typed price takes its changes off, so that count starts again from zero. So by the time it asks, the rule has already moved the night three times from your price. Answering Stop for this night then prevents a fourth adjustment, and does not undo the three. If the banner is already asking about a weekend night before you type, answering Stop for this night first keeps that rule off the night, and the price you then type holds against it.
A block held in your system
MAYA reads bookings from Cloudbeds, ThinkReservations and Mews. It does not read blocks, allotments or rooms held without a booking. A wedding pencilled in as a block adds nothing to occupancy and nothing to , so the night can read as slow and a cut rule can fire. Once guests book from the block, each room counts for occupancy, and on Cloudbeds and ThinkReservations the block's (or group's) bookings count as one booking for booking speed (or up to the number under Count a group as up to in Settings), once MAYA has read your history with the group links.
Two fixes. First, type the price as above and switch off the cut rules that would act on those nights. Your price alone does not stop them: the block keeps the night reading slow, so a booking speed cut can still fire on top of your price once its wait has passed.
Second, on the PMS tab, under the room type, click + Rooms out of service and enter the held rooms not yet booked for those dates, so reads against what you can still sell. As guests book from the block, lower that number (clear the entry and add it again with fewer rooms). Otherwise occupancy and rooms left won't read right once guests book from the block. This changes sellable occupancy and the rooms left count, so either can make a raise rule true, and that rule then stacks on your typed price: switch those raise rules off for the weekend as well. Booking speed counts bookings, and a block has none. Read Tell MAYA rooms are out of service.