Setting a price yourself

Where it is

Open the Calendar tab and click a day. Under the grid, one card per room type appears. At the bottom of each card sits the price editor: a box marked with your property's currency sign ($, € or £, or the currency's code, such as CAD), pre-filled with the night's current price (or the price already typed for it), a through… link, Save, and a ? that opens a short explanation titled "Setting a price yourself". Clear appears only while a typed price is open on that night, and never on a night that has passed.

Setting or clearing a price needs Revenue Manager access or higher. Everyone on the property can see the prices that have been set.

Type the price

1. 1
   Click the night on the calendar, then find the room type's card.
2. 2
   Type the price in the box. Whole numbers or cents are both fine.
3. 3
   For a run of nights, click through… and pick the last night the price applies to. The × beside it goes back to a single night.
4. 4
   Press Enter or click Save. A line under the box confirms what happened (see below).

Save stays greyed out while the box is empty, not a number, below 0, or while the last night is before the first.

The calendar updates on its own, and the box keeps up with the night's price until you click into it. Once you type, your number stays in the box until you save it, even if a booking moves the night's price meanwhile, and Save sends exactly what you typed. If you click into the box and leave without typing, it catches up with the night's price as you leave. After a save or a clear, the box follows the night again.

A comma or a point? Type a point for cents, as in 180.50, and no thousands separator, as in 1250. The box is your browser's own number box, so whether it also takes a comma (180,50) depends on your browser and its language. If it cannot read what you typed, it counts as empty and Save stays greyed out, so nothing wrong is saved. The amount and threshold boxes in the rule builder work the same way.

What your price does to the night

Your number becomes the starting point for that night and room type, ahead of the rate in your property system and everything else MAYA might have started from. Three things follow.

• Changes already on the night are taken off. A standard rule (no booking speed or pickup count condition) that was holding a change on that night keeps its place but stops moving the price. A booking speed or pickup rule's change on that night is taken off. Before you save, once you click into the box, type, change the last night or point at Save, MAYA checks, and a moment later a grey line under the box names them: "Saving pauses "Warm-date bump" on this night for this room.", "on these 5 nights" for a run, and with more than three rules "Saving pauses 5 rules on this night for this room: ..." with the first three names and how many more. It checks again each time you click back into the box or point at Save, and after a Clear the line goes until you start on a price again. Once it has checked, no line means no rule's change is on those nights. If it could not check, the line reads "Couldn't check which rules this pauses." and saving still pauses whatever is there. After the save, the confirmation line counts them: "Paused 2 rules on this night for this room".
• Rules that fire later stack on top. Your price is not a lock. A rule whose condition starts holding after you typed, or a booking speed or pickup rule that fires after its wait, changes the price from your number. The change log then reads "Priya set the base rate to $180.00." followed by that rule's sentence.
• Your price is published as typed. It has to sit between the floor and ceiling when you save it (a price of 0 is the one exception, see Limits below). If you change the floor or ceiling later, a price you already typed stays as typed. Rules stacked on it are still held within the limits, widened no further than your price, so no rule takes the price further out than you put it.

If you want a night left at your number for good, there is no lock. Type the price, then type it again when a rule moves it, or turn off the rules that would move it. Turning a rule off stops it on every night, not only this one. To stop one rule on this night alone, answer Stop for this night when the amber banner asks, which is only after that rule has adjusted the night three times. This works for booking speed and pickup rules only. A standard rule (a rule with no booking speed or pickup count condition) can only be switched off everywhere.

Every confirmation line and what it means

The system's name in these lines (Cloudbeds, Think Reservations, Mews) comes from your connection, which MAYA reads when the dashboard opens. With no connection on file, or for a moment while the dashboard opens, the lines and the ? panel say "your PMS".

When your price is sent

In simulation the price is saved and shown, and nothing is sent. If you go live later, it goes out with the first live send like every other price.

What the line says afterwards

On a live Cloudbeds or ThinkReservations property, the line under the box does not stop at the save. MAYA reads what became of the night about 20 seconds, 1 minute and 3 minutes after a save, and once more when you open a day that already has a typed price. When the save said the price goes on the next cycle, or that Cloudbeds isn't answering, it also reads about 6 and 11 minutes after. It stops early once the answer cannot change by itself (sent, or stopped), and does not keep asking after the last read. While the answer says no more than the save did, the save's line stays. Once it says more, the line changes to one of these:

• "Sent to Cloudbeds." Cloudbeds took the price. On ThinkReservations, MAYA's hourly read of your rates found it there.
• "Accepted by Think Reservations, checking." ThinkReservations took the price, and the hourly read has not found it there yet. It reads "Sent to Think Reservations." once it does, which can be after the line stops being read: open the day again to see. A price ThinkReservations still has the old rate for 3 hours later is sent again (ThinkReservations).
• "Sending to Cloudbeds now." The send is under way.
• "Saved. It couldn't be sent yet. MAYA will retry 3 more times." Cloudbeds did not take it for a cause that usually clears on its own: slowing down, not responding, never confirmed. MAYA sends it again every cycle, up to 10 tries at this price, and the number is the count left, read from MAYA's own record of the sends. When Cloudbeds could not find the rate MAYA sends to, MAYA reads your rate plans again and sends once more, so the line says "MAYA will retry 1 more time."
• "This price couldn't be sent to Cloudbeds." MAYA has stopped retrying on its own: the tries at this price are used, or the cause needs you, such as a rate rule or a permission in Cloudbeds. Two buttons follow. Try again sends the price once more now, and the line follows that try: "MAYA will retry 1 more time." while it is on its way, then "Sent to Cloudbeds." or the same line again. Pressing it twice sends once. See the error log opens the Change Log at the "Prices not reaching Cloudbeds" item for that night, which names the cause and what to do. A cause that usually clears on its own reaches the change log only once it has lasted about two hours, and a night that had already begun may never reach it. Until there is an item, there is no See the error log, and the cause is written under the line instead, with what to do when there is something.
• "This price couldn't be sent to Cloudbeds." with no Try again, even for a Revenue Manager: the room type has no rate in Cloudbeds for MAYA to send to, such as no base rate of its own, or only rates that follow another plan. The cause is written under the line, or See the error log opens its item. Once you add a base rate in Cloudbeds, the night usually goes out on the next cycle.

Try again needs Revenue Manager access or higher, like typing a price. Everyone on the property sees the line, the cause and See the error log.

Behind the ?, once the night's status has been read, a line says how retries work: a price your system doesn't take is sent again, up to 10 times at that price, then once a day. So a night is never given up on for good. A change you make in your system is picked up within a day, and Try again picks it up now. When your property system does not accept a price explains every cause.

A price typed while you simulate, on Mews, on a Disconnected connection, past the window, or while MAYA's work is paused has no line of its own after the save: nothing is sent, and the save's line says so. A night MAYA's own checks held back keeps the save's line too.

Limits

A price outside the floor or ceiling is refused, not rounded to the limit. Type a number inside the limits, or change the limits first. Floors and ceilings explains where they are set.

Prices in these messages, the price box and the Manual badge show your property's currency sign.

A price of 0: a comp night

Type 0 and the night becomes a comp night for that room type. It is allowed under the floor. No rule raises it, and no rule can cut it, because it is already at the lowest a price can go.

MAYA does not send a price of 0 to any property system. The confirmation says so, and while the night stays at 0 the change log carries an item headed "Prices not reaching Cloudbeds" that reads "MAYA doesn't send a price of 0 to Cloudbeds, so Standard rates set to 0 in MAYA weren't changed there", with the action "If the night is meant to be free, set it to 0 in Cloudbeds yourself." Once your system has the night at 0, the item closes on its own. Make a night free has the short version.

Your rules after your price

A booking speed or pickup rule waits again from your price. A rule that existed when you typed the price waits its wait, in whole days from the day you typed, then reads its whole window afresh, as if nothing had happened on the night before. A rule you add after typing the price doesn't wait for it. After a typed price explains the wait.

A standard rule pauses. A standard rule that was already true when you typed stays quiet on that night. When it stops being true and becomes true again, or when you clear the price, it moves the price again. A current rate rule reads the price you typed: if the price you typed makes it true, it stays quiet the same way, and if it makes it not true, its change comes off. Read Current rate. A booked so far vs usual rule is judged on the first check that prices the night after you type: true then, it stays quiet the same way; true only later, it acts on top of your price.

The three-times question closes. If the Rules that keep adjusting banner was asking about that night and rule, your price takes its changes off and the question closes for that night. It asks again if the rule adjusts your price three times.

Clear: handing the night back

Clear removes your price for that room type on that night. For a run of nights, open through…, pick the last night, and click Clear: "Cleared 5 nights. Your rules price them again."

Clear reaches tonight onwards only, because your rules never price a night that has passed. A past night has no Clear button, and its typed price stays on it as the record of what it sold at. A run of nights that starts before tonight is cleared from tonight.

After a clear, your rules run on the night again straight away. The starting point is the rate MAYA read from Cloudbeds or ThinkReservations for that night. A night your system has no rate for is left unpriced after the clear, and the day card says so, until your system has a rate for it. If MAYA had already sent your typed price there, that price stays in Cloudbeds or ThinkReservations and the day card keeps showing it, and MAYA doesn't price or send the night again until you change or load a rate there yourself. Mews properties have no rate read, so a cleared Mews night stays unpriced until you type a price again.

A standard rule that was holding quietly moves the price again. A booking speed or pickup change that your price took off stays off. The rule can fire again later, on its own terms.

Your typed price is kept as a record of who set what and when. It is not shown once cleared.

What you see afterwards

On the room type's card, an amber badge reads "Manual · $180.00". Hover it for "Set" and the date and time you saved it, in your browser's clock. The change log carries an entry whose bold line reads "Nov 13 · Standard · Price set by hand, Warm-date bump +10% came off" and whose sentences name you and the rule your price paused: "Priya set the base rate to $180.00.", then ""Warm-date bump" stopped applying an earlier 10% raise here: this night's price was set by hand.", then the move from the price the night had, "That took this night from $165.00 to $180.00.". On a night no rule had changed, the bold line is only "Nov 13 · Standard · Price set by hand", with no sentence for a rule. If your profile has no name, it reads "A manager". While your property simulates, the bold line reads "Simulation: Nov 13 · Standard · Price set by hand", the line under it "Nothing was sent to Cloudbeds.", and the sentence "Priya typed a price of $180.00." The change log has the shapes.

A rate you change in your property system, on a night MAYA had sent to, is kept the same way and shows as "Changed in Cloudbeds · $180.00", unless your setting is MAYA's price wins. Rates you change in your property system explains that. With MAYA's price wins on, a price you type here is the one way to set a price by hand, and nothing in your system changes or clears it: MAYA sends it again over any change there. With Keep the change as your price, a later change in your system on that night replaces it, as any change there does.