Rate
Compare the rate the guest can actually see against the direct booking offer.
AI-powered Booking Engine capability
PriceMatch that does not just compare. It acts.
Use AI to detect the OTA context, select the configured direct-booking response, retain proof and connect the outcome to the booking.
Check · Adjust · Prove · Book · Attribute
Geo
Account for location-specific OTA pricing where the connected source supports it.
Device
Identify differences caused by mobile and device-specific OTA offers.
Fidelity
Recognise signed-in OTA member pricing, including supported loyalty levels.
AI decisioning
Evaluate the detected context and select the direct-booking response within the hotel’s configured rules.
Act
Apply the configured direct-booking response rather than leaving the finding in a dashboard.
Prove
Keep a snapshot of the comparison context to support evidence and review.
What actually breaks parity
On desktop it looks clean. You only catch it on a phone.
Parity is rarely broken by the headline rate. It is broken underneath it, by a funded programme or an offer that only a certain guest, on a certain device, in a certain country, is ever shown. Mobile is where it goes first.
- Genius
- Booking.com’s own loyalty tiers. A signed-in member sees a discount off the rate you agreed, at a level you cannot see while signed out.
- Bonus Savings
- Campaign discounts Booking.com funds and applies on top, shown to selected guests rather than to everyone.
- Booking.com Pays
- The discount is funded out of the commission rather than your rate. Your net can be unchanged while your public price is undercut.
- Mobile and app-only rates
- A price shown on a phone or in the app and nowhere else. The desktop check that most hotels run comes back clean.
- Partner and affiliate offers
- Your rate redistributed through a partner site at a price you never set.
- Geo pricing
- A different price by where the guest is, so a check from your own office is not the check that matters.
The difference that matters
A rate shopper tells you on Monday. We change the price while the guest is still deciding.
Detection is the easy half. PriceMatch applies the response you configured on the live site, and keeps a snapshot of what it saw.
The price match, on the rate the guest is looking at
Not a report the revenue manager reads on Monday. It sits on the rate, in the booking, at the moment the guest is deciding.
BookingWhizz booking engine
Where the comparison happens
The rate your guest sees, wherever they are looking
PriceMatch reads the price on the channels a guest actually compares against, then applies the response you have configured on your own booking engine.
Google Hotel Ads too, so the direct rate is visible where travellers start comparing. Run through WhizzAds.
Channel names and logos are the property of their respective owners and are shown to identify the booking channels compared. Coverage varies by market and connected source.