Travel fares · Hotel rate parity
Hotel rate parity monitoring: find where your own rates are undercut
Rate parity monitoring checks whether your own room rates appear consistently across your website, online travel agents and metasearch, market by market. The disparities that cost money usually show up only from certain countries, so each check runs from an IP in that market and keeps the evidence.
Pay per GB · No subscription · Prices in EUR, excl. VAT
- €2.00
- per GB on ARC Fast, excl. VAT
- −44%
- at 1 TB (€1.12 / GB)
- 185+
- countries, city targeting
- Never
- expires — no subscription
Written for
- Hotel distribution managers
- Channel manager and booking-engine vendors
- Hotel group e-commerce teams
- Parity-monitoring tool builders
The short answer
- Parity monitoring compares your own rate with what third parties display for it; it is the mirror image of rate shopping, which watches competitors.
- Most disparities have an operational cause you can fix: wholesale rates leaking to retail sites, mapping errors, channel-funded discounts or currency conversion.
- Disparities are frequently market-specific, so a check from your own office's country misses them.
- In Germany and under the EU Digital Markets Act, the legal footing of contractual parity has changed; monitoring today is mostly about protecting your direct channel, not enforcing a clause.
The problem
What goes wrong without the right IPs
The undercut only appears abroad
A wholesale rate meant for one source market resurfaces on a retail site visible elsewhere. Checked from your home market the rates look aligned; checked from the market where the leak is sold, they do not.
Metasearch shows sellers you never contracted
A metasearch result can list third-party sellers alongside the OTAs you work with. If you only check your contracted channels, the cheapest offer in front of the guest is the one you never see.
Like-for-like is harder than it looks
A non-refundable room-only rate on one channel and a flexible rate with breakfast on another are not a parity breach. A monitor that compares the lowest visible price on each channel raises false alarms all day.
Currency conversion fakes a gap
A channel converting at its own rate can show a few percent of difference that does not exist in the source currency. Compare in the rate's original currency, or at a fixed reference rate you store with the check.
No evidence, no conversation
A partner manager asks for proof of a disparity seen two days ago. Without the timestamp, market, rate conditions and a snapshot of the page, the disparity is your word against their logs.
What to collect
What you can collect
- Your reference rate
- The rate you loaded, taken from your own booking engine or channel manager, not scraped. This is the baseline everything is compared with.
- Channel and seller
- The OTA, metasearch result or brand site checked, and on metasearch the seller actually displayed.
- Point of sale
- Exit country and, for regional promotions, city. A disparity is meaningless without the market it was seen in.
- Stay date, LOS and occupancy
- The exact search, so the same check can be repeated for verification.
- Room and rate conditions
- Room type, refundability, board and payment terms, to keep the comparison like-for-like.
- Displayed price and currency
- Exactly as shown, plus the comparable total you computed and the exchange rate used.
- Delta to reference
- Absolute and percentage difference, signed: undercut, overcut or aligned within your tolerance.
- Evidence
- Timestamp, request URL and a stored snapshot of the rendered page, for the partner conversation.
How it runs
How a collection run works
- 01
Take your baseline from your own systems
Export the rates you loaded per room, rate plan and date from your booking engine or channel manager. Your own data is the reference; never infer it from what channels display.
- 02
Check each channel from each market
For a sample of stay dates, run the same search on every channel from exits in your top source markets. One sticky session per check keeps search and room list on one IP.
- 03
Match like-for-like before comparing
Map room types and rate conditions first; compare only matched pairs. Unmatched rates are a mapping task, not a disparity.
- 04
Store evidence with every breach
Save the rendered page, timestamp and request parameters for anything outside tolerance, and re-check from a fresh session within the hour to rule out a transient cache.
- 05
Route by cause
Leaks go to the contracting team, loading errors to revenue, mapping errors to the channel manager. A weekly report of repeat offenders by channel and market is worth more than a stream of alerts.
Setup
Recommended setup
Parity checks are fewer than rate shops but must be right in the market where the breach happens, so the targeting matters more than the volume.
| Plan | Role | Session | Targeting | Price |
|---|---|---|---|---|
ARC Fast Rotating residential | Default for channel checks Residential exits in each source market, held long enough to search, open the property and read the room list. | Sticky, 10 minutes per check | Country + city (e.g. London, Munich, Paris) | €2.00 / GB €1.12 at 1 TB (−44%) |
ARC Mobile Mobile 4G/5G | Mobile-only rates Some channels show mobile-only prices. Carrier IPs let you see what a guest on a phone network is offered; there is no city targeting on this plan. | Sticky, 5–60 minutes | Country only (DE, GB, US, JP) | €3.50 / GB €3.15 at 1 TB (−10%) |
ARC Basic Rotating ISP | Your own brand site from abroad Checking that your booking engine shows the right currency and rates to each market is light HTML work for the cheapest pool. | Rotating | Country | €0.75 / GB €0.59 at 1 TB (−21%) |
Prices are list prices in EUR, excl. VAT. Volume discounts apply automatically at checkout — full ladder on the pricing page.
Connect
One connection string per market
The country, city and sticky session are tokens in the username. Change the token, change the market; keep the session handle, keep the IP.
http://USERNAME_pool-arcfast_country-de_session-k3f9a1x2_sesstime-10:PASSWORD@proxy.arcproxies.io:8000Swap _country-de for any market you quote. The full grammar is on the residential proxies page.
Illustration
What daily parity checks for a hotel group costs
An illustration with round numbers — your pages, payloads and retry rate will differ. The arithmetic is the real price ladder.
Assumptions
- Properties
- 25
- Stay dates sampled
- 30
- Channels
- 5
- Source markets
- 4
- Cadence
- daily, 30 days
- Weight per check
- 300 KB
- Bandwidth per month
- ≈ 135 GB
On ARC Fast
€183.60per month, excl. VAT
135 GB bought in one purchase at €1.36 / GB (−32% volume rung, applied automatically).
The same 135 GB on ARC Basic: €91.80 at €0.68 / GB. Move down as soon as the cheaper pool holds up.
Snapshots are rendered and stored on your side and add no proxy traffic beyond the page itself. Sampling 30 dates rather than the full year is usually enough to catch a systematic leak.
Bandwidth never expires, so a bigger single purchase is only ever cheaper per GB. See the ladder.
In depth
Hotel rate parity, in depth
What causes hotel rate disparities
Most disparities are not a channel misbehaving; they are a rate going somewhere it was not meant to be visible, or being displayed differently. Knowing the cause tells you who fixes it.
| Disparity | Typical cause | Where you usually see it |
|---|---|---|
| Retail site cheaper than brand site | Wholesale or package-only rate resold as room-only | In the source market the wholesale rate was sold to |
| One OTA consistently a few percent lower | Channel-funded discount or loyalty programme | Logged-out price on that OTA, often market-specific |
| Unknown seller lowest on metasearch | Third-party reseller of a net rate | Metasearch result lists |
| Small gap that varies daily | Currency conversion at the channel's rate | Markets with a different display currency |
| Gap on some dates only | Rate loading or mapping error | All markets, specific dates or room types |
| Cheaper on phones | Mobile-only promotion | Mobile carrier connections |
Parity clauses in Europe: what changed
For years many online booking contracts required hotels to offer the platform rates at least as good as elsewhere. The legal treatment of these rate parity clauses has since shifted, especially in Germany and at EU level. The detail is in our guide to hotel parity clauses in Europe; the milestones a distribution team should know are below. This is a summary, not legal advice.
| Date | Body | What happened |
|---|---|---|
| 23 Dec 2015 | Bundeskartellamt | Prohibited Booking's narrow best-price clauses (hotel website may not undercut the platform) for German hotels, with removal required by 31 January 2016 |
| Apr 2017 | European Competition Network | Monitoring report: about 16,000 hotels surveyed; increased price differentiation between OTAs after wide clauses were dropped; almost half of hotels unaware of the changes |
| 18 May 2021 | Bundesgerichtshof (Federal Court of Justice) | Confirmed that Booking.com's narrow price parity clauses were illegal |
| 13 May 2024 | European Commission | Designated Booking as a gatekeeper under the Digital Markets Act for its Booking.com intermediation service |
| 19 Sep 2024 | Court of Justice of the EU | Case C-264/23: neither wide nor narrow parity clauses can, in principle, be classed as ancillary restraints under EU competition law |
The Digital Markets Act also prohibits gatekeepers from preventing business users from offering better conditions through other channels, which removes parity obligations from the designated platform's contracts. Other platforms and other countries may be treated differently; check the current position with counsel for your markets.
Why parity monitoring still matters without parity clauses
If a platform can no longer demand parity, why monitor it? Because the commercial incentive is unchanged. A guest who sees your room cheaper on a third-party site books there, and you pay commission on a booking you could have taken direct. A leaked wholesale rate also undercuts every partner you do have a relationship with.
Monitoring now serves the hotel rather than the contract, and it uses the same market-by-market collection as the rest of travel fare aggregation: it shows where your direct channel loses on price, which partners leak, and whether a channel-funded discount is moving demand away from you in a specific market.
Choosing tolerance and sampling
- Tolerance: most teams ignore gaps under one or two percent, which conversion and rounding explain, and alert above that.
- Dates: sample high-demand dates and the next 30 days densely, the rest sparsely. Leaks tend to be systematic and show up on any date.
- Markets: start with your top four source markets by room nights, then add one market at a time when a leak points there.
- Re-check: confirm every breach from a fresh sticky session before it reaches a partner; caches produce one-off ghosts.
Works with anything that takes a proxy URL
Playwright- Puppeteer
- Python requests / httpx
- changedetection.io
- Docker
FAQ
Questions
Something not covered? Write to contact@arcproxies.io.
What is hotel rate parity?
Rate parity means a hotel's room is offered at the same price for the same conditions across its own website and third-party channels such as online travel agents and metasearch. A disparity is any channel showing the same room and conditions cheaper or more expensive than the hotel's reference rate.
Are rate parity clauses still legal in Germany and the EU?
In Germany, the Bundeskartellamt prohibited Booking's narrow parity clauses in December 2015 and the Federal Court of Justice confirmed that in May 2021. The EU Court of Justice held in September 2024 that parity clauses cannot in principle be treated as ancillary restraints, and Booking was designated a gatekeeper under the Digital Markets Act in May 2024. The position differs by platform and country, so check with counsel for specifics.
Why do parity checks need IPs in different countries?
Because many disparities are market-specific. A wholesale rate leaked into one source market, a geo-targeted promotion or a currency conversion only shows up when the check is made from that market, so a check from your own country can report parity where none exists.
What is a wholesale rate leak?
A wholesale leak happens when a net rate a hotel sold to a wholesaler or tour operator, intended to be bundled into a package, is resold as a standalone room on a public site. It often undercuts the hotel's own website and appears only in certain markets.
Can I check mobile-only rates?
Yes, with ARC Mobile, which exits on 4G/5G carrier networks in Germany, the UK, the US and Japan. It has country targeting only and sticky sessions of 5 to 60 minutes.
What evidence should a parity monitor keep?
The timestamp, exit market, exact search parameters, room and rate conditions, displayed price and currency, and a snapshot of the rendered page. That is what a channel partner needs to investigate a disparity.
Sources & review
Last reviewed by the ARC Proxies team. Prices are read from the live catalog at build time.
- [1]Bundeskartellamt: Narrow "best price" clauses of Booking also anticompetitive (23 December 2015)
- [2]Bundeskartellamt: Federal Court of Justice confirms illegality of Booking.com's narrow price parity clauses (BGH press release 099/2021)
- [3]Court of Justice of the European Union: Press release No 145/24: Judgment in Case C-264/23, Booking.com
- [4]European Commission: Commission designates Booking as a gatekeeper and opens a market investigation into X
- [5]Noerr: Relevance of the DMA for online intermediation services
- [6]Autorité de la concurrence: 6 April 2017: Online hotel booking platforms (ECN monitoring report)
Travel fares
More on travel fares
Get started
Buy a gigabyte and try it on your own targets.
No subscription, no sales call. Code WELCOME15 takes 15% off your first purchase, and whatever you do not use is still there next quarter.