Rate parity

Why most rate parity alerts are wrong (340 of 346 were false)

Jacobo Hernandez ·

Short answer: in August 2026 we replayed every rate parity alert our own system had raised. It had flagged 346 undercuts. 340 were false. Six were real, all on one online travel agency, between $11 and $76 under our rate.

The owner who caught it said it plainly: the "parity issues" were fake, and in several cases the other site was charging more than we were. He was right.

A false parity alarm is not harmless. It teaches you to cut your rate to match a price that does not exist. Here are the four causes, a checklist you can use on any parity report, and the case that fools almost everyone: the sold-out night.

What a parity alert is supposed to tell you

Rate parity means your room costs the same on your own website as it does on Expedia, Booking.com and everywhere else. A parity alert says "a site is selling your room cheaper than you are." If true, guests book there, you pay commission, and your direct share drops.

To say that honestly, a checker has to get four things right: the right hotel, the right price to compare against, the right currency, and a site that actually sells your rooms. Miss any one and you get noise.

Why a false alarm costs more than a missed one

A missed undercut costs you some bookings on one channel until you notice. A false alarm costs you on every channel at once, because the usual reaction is to lower your own rate to match. If the "cheaper" price was a different hotel, a different currency or a room that was already sold out, you just cut your rate for nothing, on the nights that were selling anyway.

It also costs attention. After enough false reds, owners stop reading the report. Then the real undercut, the one worth $75 a night, sits in the same pile as the noise.

Cause 1: It matched the wrong hotel

A checker searches the web for your hotel by name. If the name is short or shares words with your city, it can land on somebody else.

In our case, one small property's name included its city. The checker matched it to a chain hotel near the airport with the same city in its name. 60 of the 97 dates checked on that path were the chain hotel, not ours. The match was saved once and never checked again.

Owner test: open the alert and click through. Is it your hotel, your address, your photos?

Cause 2: One weak signal was allowed to convict

There are two ways to know your own price: the rate you actually posted in your PMS, or the "official site" price Google shows. The second is a guess about you, made by a third party.

Our checker let either one alone raise an alarm. 322 of the flags came from properties where there was no posted rate to compare at all, only the Google-shown price.

Owner test: ask what the alert compared against. If the answer is not "the rate in my PMS for that night," do not act on it.

Cause 3: It compared different currencies

One of the hotels we watch prices in Colombian pesos and another in Canadian dollars. The checker assumed every price was US dollars. A peso price read as dollars looks like the deal of the century.

Owner test: if you sell in more than one currency, or a foreign site lists you, check the currency symbol on both prices.

Cause 4: The "cheaper site" was one you never signed with

The whole top of our alert leaderboard was resellers and wholesale sites we had no contract with. There is no extranet to log into, nothing to fix, and in several cases they were more expensive than us anyway.

Owner test: is this a channel you connected in your channel manager? If not, it is a different problem (a wholesaler leaking your rates), and it needs a different fix than cutting your price.

After all four fixes: 6 flags, all real.

The sold-out night: red alarm, nothing wrong

On September 24, 2026 our parity screen showed a red alarm for Forest Springs on September 26: "the posted rate is $220, the channels show $230." It looked like a feed error.

It was not. The $220 came from two rate plans that had zero rooms left. The price anyone could actually buy was $230, and every channel showed $230. The alarm compared the channels to a price nobody could book.

Two more things the same audit found:

  • A real undercut was hidden. On October 2, our direct price was $328 while Booking.com and two other sites showed $253. That is a $75 gap, and it did not raise an alarm, because the checker compared against the posted rate instead of the price a guest sees on our own site.
  • Weekend checks asked the wrong question. Our weekends carry a 2-night minimum. The checker searched 1-night stays, so our own site showed nothing, and some OTAs were selling a 1-night stay on a 2-night-minimum weekend. That is a restriction problem in the channel settings, not a price problem.

Checklist: vet any rate parity alert in 5 minutes

Use this before you touch a rate.

  1. Is it your hotel? Click through. Name, address, photos.
  2. Is the room sellable? If that night or room type is sold out on your side, the comparison is meaningless.
  3. Same stay length? Check the night's minimum stay. A 1-night search on a 2-night-minimum night compares nothing.
  4. What is "your price"? It should be the price a guest sees on your own booking site for the same room, dates and guests. Not a posted base rate, not a guess from a search engine.
  5. Same currency, same taxes? Some sites show prices with tax, some without. Compare like with like.
  6. Is the site a contracted channel? If you never connected it, the fix is with a wholesaler, not your rate.
  7. Is it still true right now? Search the same night yourself. Prices move, and a snapshot from 3 AM can be stale by breakfast.

If an alert passes all seven, it is real. Fix the rate or restriction on that channel, not your direct price.

The bigger lesson

The bigger lesson is not about parity. Before you trust any alert, ask what it compared against. A label on a screen is a claim, and a claim needs its evidence.

Want this checked on your own hotel? See Price every night or book a 30-minute walkthrough. More from us: how to find unpaid folios in Cloudbeds, money owed to your hotel and YieldWizard for Cloudbeds hotels.

Every night it finds the money, acts, and proves it.

30 minutes on your own numbers. See what it would have caught.