> 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/roompulse/metaradar.md).

# MetaRadar

Scan several metasearch channels and several markets at once to find where your direct rate is being undercut.

MetaRadar is the wide view of undercutting. Where [Parity](/revhero-docs/roompulse/parity.md) examines your own channels for a single point of sale in detail, MetaRadar sweeps several metasearch channels across several markets at once and shows you where the undercutting concentrates — by channel, and by country.

An undercut is measured the same way as in Parity: **Brand Price − Undercut Price**. A positive difference means someone is selling your property below your own direct rate for that date and market.

![A channel selling your hotel below you](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-e7ad25d0b69d909da15187df404c172a210196e7%2Fundercut-on-metasearch.svg?alt=media)

*One metasearch result, and the same comparison totalled across markets.*

## Reading the page

The top of the page tells you when the results were last updated and describes the run — the forward window reviewed and how many markets it covered. **Configure Metaradar**, at the top right, sets what the scan looks at.

Below that, four stacked sections take you from headline to detail.

### Summary

One sentence stating how much of the forward window is undercut — for example, *at least one provider undercuts your direct rate on 25% of dates across all locations*. If you read nothing else on the page, read this: it tells you whether you have a parity problem at all.

### Undercut per Channel

Undercutting broken down by channel.

| Column                      | What it shows                                                                                                                                |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Channel**                 | The metasearch or OTA channel                                                                                                                |
| **Percentage of Undercuts** | The share of checked date-and-market combinations where that channel prices below you, with the count behind it — for example `34% (59/302)` |
| **Avg Undercut**            | The average size of that channel's undercuts                                                                                                 |

Read the two columns together. A channel undercutting on 40% of dates by €2 is a rounding problem; one undercutting on 5% of dates by €40 is a commercial one.

### Undercuts per Region

A bar chart of undercut percentage by country, with a tab per channel. Switching tabs shows where that particular channel undercuts you most — which is usually not evenly spread, and usually the most actionable thing on the page.

### Undercut Analysis

The detail table, one row per undercut found. Prices appear in the currency of the market.

| Column             | What it shows                                    |
| ------------------ | ------------------------------------------------ |
| **Date**           | The stay date                                    |
| **Channel**        | The channel undercutting you                     |
| **Region**         | The market, which also sets the currency         |
| **Brand Price**    | Your direct rate for that date and market        |
| **Undercut Price** | Their cheaper price                              |
| **Diff**           | The undercut amount                              |
| **Diff %**         | The undercut as a percentage of your brand price |

## Configure Metaradar

**Configure Metaradar** opens a panel controlling the whole scan, with **Close**, **Reset** and **Save**.

| Setting       | What it does                                                 |
| ------------- | ------------------------------------------------------------ |
| **Countries** | The markets to scan — up to six at a time                    |
| **Channels**  | Which channels to include in the scan                        |
| **Nights**    | The length of stay checked, from 1 to 7 nights               |
| **Threshold** | Optional. Only undercuts of at least this amount are flagged |

Saving re-runs the scan and refreshes every section against your new selection.

{% hint style="info" %}
Set a **Threshold** before you first read the detail table. Without one, a few euros of currency rounding across hundreds of date-and-market combinations will bury the undercuts that actually cost you a booking.
{% endhint %}

## Choosing which markets to scan

Six markets is a small number against the whole world, so choose them deliberately:

* Your largest source markets, from your own [business mix](/revhero-docs/your-hotels-performance/dashboard/business-mix.md).
* The market you are physically in, which is where your direct traffic mostly sits.
* One market you have no business in but believe you should — it will tell you whether price is the reason.

## What to do with a finding

MetaRadar finds undercutting; closing it is a conversation. Use the detail table to take a channel a specific, evidenced case — the dates, the markets and the size of the gap — rather than a general complaint. Then work the affected dates in [Parity](/revhero-docs/roompulse/parity.md), where you can see each one against your own channels and link straight out to the live listing.

## Related

* [Parity](/revhero-docs/roompulse/parity.md) — the day-by-day view of your own channels
* [Alerts](/revhero-docs/roompulse/alerts.md) — the **Parity Price Comparison** alert, for undercuts above a size you choose

***

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