> 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/your-hotels-setup/integrations/what-data-flows.md).

# What data flows into Revhero

What Revhero reads from your systems, what it sends back, and what it never takes at all.

Hotels ask 2 questions whenever they connect a new system. What does Revhero take? What can Revhero change? This page answers both.

![What goes into Revhero, and what comes out](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-d66a36c48af14445b9acd636b0336d2306271cf2%2Fwhat-connects-to-revhero.svg?alt=media)

*Revhero reads from webhotelier, your PMS and RoomPulse, reads demand on its own, and sends back rates and minimum stay.*

## What Revhero reads

### From webhotelier

| What                  | What it is used for                                                  |
| --------------------- | -------------------------------------------------------------------- |
| Room types            | Your room list in Revhero, and the structure behind every rate       |
| Rate plans and boards | What you sell, so recommendations and sends go to the right products |
| Availability          | What is open for sale on each date                                   |
| Current rates         | The rate you are selling today, shown next to every recommendation   |
| Your operating season | So closed periods are treated as closed, not as empty                |

### From your property management system

| What                                        | What it is used for                                                      |
| ------------------------------------------- | ------------------------------------------------------------------------ |
| Confirmed reservations, at room-night level | Occupancy, room nights, pace, pickup, lead time and business mix         |
| The revenue on each stay night              | Revenue, ADR and RevPAR                                                  |
| Booking and stay dates                      | Your booking curve, and every comparison against the same time last year |
| Cancellations                               | Keeping the picture accurate, and showing where demand is weakening      |

### From RoomPulse

| What                                    | What it is used for                                                                                                                                                                                                                            |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your competitors' published rates       | [Competitor Rate Analysis](/revhero-docs/your-hotels-performance/dashboard/competitor-rate-analysis.md), the market view on the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board/kpi-drawer.md), and your rate recommendations |
| Where your own rate sits against theirs | [Market Rates](/revhero-docs/roompulse/market-rates.md) and [parity](/revhero-docs/roompulse/parity.md)                                                                                                                                        |

### Demand, sourced for you

Demand arrives with your connection. Revhero sources it itself, so you connect nothing and maintain nothing for it.

| What                                                                                | What it is used for                                                                                                                                |
| ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Property demand** — interest in staying at your own hotel on a date               | [Demand for your property](/revhero-docs/automation/rate-recommendations/what-it-considers/property-stay-demand.md), and your rate recommendations |
| **Destination demand** — interest in your destination                               | The Online Demand widgets on the [Dashboard](/revhero-docs/your-hotels-performance/dashboard/online-demand-overall.md)                             |
| **Market demand** — how that interest compares with what the season normally brings | [Market demand](/revhero-docs/automation/rate-recommendations/what-it-considers/market-demand.md), and your rate recommendations                   |

This is the part of your data you never have to prepare. It is there on the day you go live, and it keeps arriving without anyone at the hotel doing anything.

## What Revhero sends back

**Rates, and the minimum stay you set with them.** When you confirm a send, the approved rates go to webhotelier. Any minimum stay you set on those dates goes with them. They reach your channels from there.

Revhero does not touch your reservations, and it does not create or edit room types, rate plans or any other setting in your systems.

A rate only leaves after you have seen it in the preview and confirmed it. See [Sending rates](/revhero-docs/setting-your-rates/yielding-board/send-rates.md).

{% hint style="info" %}
Revhero sends rates for your base room, board and occupancy. Every other combination is calculated from your [supplement structure](/revhero-docs/setting-your-rates/pricing/supplements.md). This means a wrong supplement carries a wrong rate into every combination. Check the structure before your first large send.
{% endhint %}

## What Revhero never takes

Revhero reads your reservations at **room-night level only**. It does not import guest names, email addresses, telephone numbers or guest records. Revhero drops them as your reservations arrive, from every system.

Revhero is a revenue tool. It needs to know that a room was sold for a night, at a price, through a channel. It does not need to know who slept in it.

## When something looks wrong

Every screen tells you when its data last arrived. Look at the **Last Upd.** stamp on the [Dashboard](/revhero-docs/your-hotels-performance/dashboard.md).

Check that stamp before you question a number. Most "this looks wrong" questions are caused by a feed that has not arrived, not by a figure that is calculated incorrectly.

If the data is current and the number still looks wrong, send support one example date. One date with your own figure next to ours settles the question much faster than a description.

## Related

* [Where your numbers come from](/revhero-docs/your-hotels-setup/integrations/supported-systems.md)
* [Getting connected](/revhero-docs/your-hotels-setup/integrations/getting-connected.md)
* [Glossary](/revhero-docs/support/glossary.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%20integrations%2Fwhat-data-flows.md) and quote this page: `integrations/what-data-flows.md`. Say what you expected to find — that is the part we can fix.