> 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/setting-your-rates/offers/yielding-board-integration.md).

# Offers on the Yielding Board

How active offer groups are simulated beside your rates on the Yielding Board, and how to read what you keep while you yield.

Offers earns its keep in the moment you are yielding — and in that moment you are on the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md). This page covers how active offer groups appear there, what each figure means, and how to use the simulation while making a rate decision.

Each active group is a **worst-case offer stacking simulation** of one commercial agreement. Beside your send rate you read what the guest pays at each level of that group's stack, and what you keep once commission is taken — or once a partner has marked your rate up before it reaches the channel.

The relationship runs one way. Offers feeds the board with its simulation; the board never writes back into your group definitions.

![Each active offer group simulated beside the send rate](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-df749e65c283a1a0f2c486b42ddca408dd4d75b5%2Fnet-columns-beside-the-send-rate.svg?alt=media)

*One read-only column per active group sits beside the send rate, and every figure moves when you edit that rate.*

## The Active toggle is the join

Revhero renders one column per offer group whose **Active** toggle is on, next to the send rate, in the order the groups appear in the Offers table. Inactive groups do not appear at all.

| Offers                    | The board                                                                |
| ------------------------- | ------------------------------------------------------------------------ |
| No active groups          | No offer columns. The board behaves as though the module were not there. |
| One active group          | One column next to the send rate, headed with the group name             |
| Two to five active groups | One column each, in the order the groups are listed                      |

The column header is the group name, so name your groups the way your team refers to the channels.

## What each cell shows

For a given date, room, board and occupancy, the group's column shows what that cell's send rate is worth through that agreement, after its stacking method, its discounts and its commission. Open the cell to see the breakdown — the send rate, the effect of each discount, the commission, and the figure you keep at the end. That is your audit trail for any number on the screen.

The send rate is the input; every offer figure is worked out from it. Edit the send rate and every active group updates in place — no saving, no reloading. Typing a candidate rate and watching the result land is the whole point of the integration.

## Both views

| View              | How the simulation appears                                                                                                                       |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Table View**    | One column per active group, to the right of the send rate. Pinning the send rate next to one or two key groups makes side-by-side reading easy. |
| **Calendar View** | The day tile shows the send rate; click a tile and the day drawer breaks it down per group. Calendar is for scanning, Table is for editing.      |

## Comparing agreements on one date

This is the comparison the integration exists to give you. On a €180 send rate, with plausible worst-case stacks:

| Active group                                                     | What you keep at €180 |
| ---------------------------------------------------------------- | --------------------- |
| Direct, no commission                                            | €180.00               |
| An online channel with two 10% discounts and 15% commission      | €123.93               |
| An online channel with one 10% discount and 18% commission       | €132.84               |
| A wholesale contract, 10% markup and 25% discount, no commission | €148.50               |

Read that way, the decision changes shape. It is no longer "is €180 the right rate?" but "is €180 worth doing through the channel that will actually fill this date?"

It also shows why a cut hurts unevenly. Dropping €200 to €175 costs €25 direct. Through a channel carrying a full discount stack the absolute loss is smaller, but it lands on a much smaller base — so the same cut can take a marginal date below your cost per room on one agreement while staying comfortable on another.

## A yielding routine that uses it

1. **Check which groups are active** before you open the board, and pick the ones that matter today.
2. **Read the performance context** in the [KPI drawer](/revhero-docs/setting-your-rates/yielding-board/kpi-drawer.md), then the recommended rate.
3. **Tentatively edit the send rate** to the recommendation, or to your own override.
4. **Read each active group's figure.** Does what you keep stay above your cost per room on the agreements that fill this date?
5. **Send if it does.** If it does not, raise the rate or reconsider the channel mix.

After a bulk update — copying recommended rates across a window, for example — scan the offer columns across the whole window before sending. That is where an over-discounted cell shows itself.

## What is not simulated

The simulation is deliberately narrow, and knowing its edges keeps you out of trouble:

* **Tax, VAT, city tax and environmental tax** are handled by your published [Pricing](/revhero-docs/setting-your-rates/pricing.md) structure. The stack runs on the send rate as the board shows it.
* **Restrictions** — minimum stays and close-outs — do not change the rate, so they do not change what a group returns.
* **Availability and volume.** The simulation tells you what 1 booking is worth at this rate, not how many bookings you will get.
* **What a channel actually sells at.** Revhero simulates what your agreement says the rate should return, not what the channel does with it.

**Min Rate** and **Max Rate** are a separate check, and they work differently. They mark a rate that falls outside the range you set in [Pricing](/revhero-docs/setting-your-rates/pricing.md). They do not change the rate and they do not block the send. The offer columns and the Min Rate and Max Rate marks answer two different questions, so read both before you send.

{% hint style="info" %}
Sending pushes your send rate, never a simulated figure. The offer columns are a reading of what that rate becomes after an agreement's own stack. The channel produces the actual amount on each booking.
{% endhint %}

## When something does not appear

| What you see                          | Usually because                                                                | What to do                                                                                                           |
| ------------------------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| No offer columns at all               | No group is active, or no published structure, so there is no rate to simulate | Activate a group; publish the Pricing structure                                                                      |
| An offer column with blank cells      | The send rate on those cells is blank or zero                                  | Fill the send rate — the simulation needs a rate                                                                     |
| The figures do not move after an edit | The edit has not been committed                                                | Click off the cell, then reload if it persists                                                                       |
| Columns in an unexpected order        | Column order follows the group order in Offers                                 | Reorder the groups                                                                                                   |
| A newly activated group is missing    | The board loads its groups when it opens                                       | Reload the board after changing a toggle elsewhere                                                                   |
| Nothing simulated on past dates       | The board does not edit past dates                                             | Expected — past performance lives in [Daily Performance](/revhero-docs/your-hotels-performance/daily-performance.md) |

The offer columns are read-only annotations on each row. To order the board, sort by send rate, recommended rate or one of the standard data columns.

## Related

* [Offers](/revhero-docs/setting-your-rates/offers.md)
* [Offer groups](/revhero-docs/setting-your-rates/offers/offer-groups.md)
* [How offers stack](/revhero-docs/setting-your-rates/offers/stacking-methods.md)
* [Table View](/revhero-docs/setting-your-rates/yielding-board/table-view.md)
* [Calendar View](/revhero-docs/setting-your-rates/yielding-board/calendar-view.md)

***

**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%20offers%2Fyielding-board-integration.md) and quote this page: `offers/yielding-board-integration.md`. Say what you expected to find — that is the part we can fix.
