> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/learn-revhero/top-tips/setting-your-rates.md).

# Setting your rates

When to move a rate, how far one edit travels, and what to check in the preview before you send.

Nine decisions you will make most often, with the signal that should trigger each one.

## High occupancy and bookings still arriving?

**Find it:** Dashboard → [Occupancy](/revhero-docs/your-hotels-performance/dashboard/occupancy.md), then [Pickup](/revhero-docs/your-hotels-performance/dashboard/pickup.md)

**Look for:** high occupancy **and** pickup that has not slowed.

High occupancy on its own is not a reason to raise the rate. It may simply mean the date is nearly done. Occupancy plus live pickup is a different signal.

**If** occupancy is already around 84% and bookings are still arriving, the remaining rooms are worth more than the ones you have sold.

**Consider** raising the rate now, rather than waiting until 4 rooms are left.

| Example              |               |
| -------------------- | ------------- |
| Occupancy            | 84%           |
| Current rate         | €150          |
| Pickup               | Still strong  |
| **Consider testing** | **€160–€165** |

**Don't** raise the rate on high occupancy alone. If pickup has stopped, a higher rate sells nothing.

## Sitting on your Min Rate? The range is the problem, not the rate

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → Table View → sort **Send Rate** against **Min Rate**

**Look for:** a long run of dates sitting exactly at **Min Rate**.

The board will not send below your floor. A recommendation is held there too: where the suggestion would be lower, you get your **Min Rate** instead, with **Minimum Rate** given as the reason.

**If** 30 or 40 dates all sit exactly on the floor with the same reason, that is not agreement. It is a floor with nowhere to go.

**Consider** reviewing the **Min Rate** for that period in [Pricing](/revhero-docs/setting-your-rates/pricing.md) before you touch a single date.

| Example                       |                                                       |
| ----------------------------- | ----------------------------------------------------- |
| Dates at **Min Rate**         | 38 of 90                                              |
| **Min Rate**                  | €120                                                  |
| Recommendations, if unbounded | €95–€115                                              |
| **Consider**                  | **Whether €120 is really your floor for this season** |

## Check the yield mode before a bulk update

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → the **Yield Mode** buttons

**Look for:** which of the four is selected, before you press anything.

| Mode       | What one edit moves                                                 |
| ---------- | ------------------------------------------------------------------- |
| **Base**   | The base room, board and occupancy. Everything else derives from it |
| **Room**   | The same, inside one room type                                      |
| **Custom** | Exactly the cells you edit. Nothing derives                         |
| **Unit**   | One per-unit room, priced on its own                                |

**If** a bulk update seems to have missed rooms, the mode is the usual cause, not a fault.

**Consider** switching to **Custom** and clearing your filters, then running it again.

A per-unit room — a villa or an apartment — sits outside the pricing hierarchy. Move the base rate and it does not move. **Unit** is the only mode that shows those rows, so give them their own slot in your weekly routine.

## Accept a stable stretch in 4 clicks

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → **Bulk Update** → **Copy From** → **Recommended Rates**

**Look for:** a run of ordinary dates where the recommendation sits within a few euro of your current rate.

**If** you are still changing rates one cell at a time, this is the hour you get back each week.

**Consider** sweeping the ordinary dates in one pass, then opening only the few that need a decision.

Bulk Update, Copy From, Apply, Send — a 90-day sweep in four clicks. **Apply** only creates pending edits, so nothing leaves until you read the preview and confirm. **Initially Loaded Rates** is the reverse, and puts the period back to your published structure.

## Read the preview: the row count is the check

**Find it:** the preview that opens when you click **Send**

**Look for:** the row count first, then the new rate against the current one.

**If** you edited 1 base cell and the preview lists 14 rows, that is correct. Derived rates are calculated at the moment you send, so the preview is the first place you see them.

**If** one row has moved far more than you intended, that is usually a wrong supplement rather than a wrong decision.

**Consider** opening **Details** on one derived row before you confirm. It breaks the figure down.

There is no undo on a send. The **Last Send** column holds the value you replaced, so keep it visible — that is your way back.

## Blank Init, Min and Max? The date has no range to yield in

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → **Init Rate**, **Min Rate**, **Max Rate**

**Look for:** dates where all three are empty.

**If** they are blank, no published pricing structure covers that day. It is inside your **Operational Period** but has no period attached, or the structure was never published.

**Consider** opening the Periods tab in [Pricing](/revhero-docs/setting-your-rates/pricing.md) and filtering to next year to find the gaps. Overlaps are impossible — revhero greys out days already taken — but gaps are not.

**Don't** treat one period for the whole year as tidy. The range belongs to the period, so one period gives you one range for all 12 months.

## Publishing is not sending

**Find it:** [Pricing](/revhero-docs/setting-your-rates/pricing.md) → **Publish**

**Look for:** what changes and what does not.

Publishing pushes **Init Rate**, **Min Rate** and **Max Rate** onto the board for every day in every linked period. That is your range. **Nothing reaches your channel manager.**

**If** someone re-publishes a structure, the live rates do not move. The range underneath them does.

**Consider** opening the board on one date in that period afterwards, and checking **Init Rate**, **Min Rate** and **Max Rate** landed where you expected.

## Close the date, or price it — not both

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → **Edit Restrictions** → **Close Out**, and the **Close Out Date** column

**Look for:** close-outs still running from a reason that has passed. **Close Out Date** shows when each one was set.

A close-out is not a very high price. It is no price. Raise the rate and the guest who would have paid it can still book. Close the date and they go elsewhere, and you never learn what they were worth.

**If** the reason is "the rate feels too cheap", the rate is the lever, not the close-out.

**Consider** keeping close-outs for reasons that hold at any price: no inventory, maintenance, or rooms held for another channel.

**Don't** assume restrictions expire. A close-out set in February is still running in July, and nobody notices a booking that did not happen.

## Aim a minimum stay at one date, not a week

**Find it:** [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md) → **Edit Restrictions** → **LOS**

**Look for:** a strong single date with soft nights either side.

Minimum stay changes who can book, rather than what they pay. Aimed at one peak date, it pushes a 1-night booker into the quiet nights beside it. Spread across a week, it only turns business away.

**If** demand is weak, a minimum stay will not fix it. It earns its place when you have demand and a bad stay pattern.

**Consider** setting it on the peak night only, and reading pickup on the shoulder nights a few days later.

| Example      |                                                                    |
| ------------ | ------------------------------------------------------------------ |
| Saturday     | Sold out                                                           |
| Friday       | 40% sold, mid-week rate                                            |
| **Consider** | **2-night minimum on Saturday, and price Friday in its own right** |

## Next

* [Your market](/revhero-docs/learn-revhero/top-tips/your-market.md) — where your rate sits, and what that is worth.
* [Lesson 7 · How to send a rate](/revhero-docs/learn-revhero/learn/07-sending-a-rate-safely.md) — the send, step by step.

***

**Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20top-tips%2Fsetting-your-rates.md) and quote this page: `top-tips/setting-your-rates.md`. Say what you expected to find — that is the part we can fix.