Rate
Compare the rate the guest can actually see against the direct booking offer.
AI-powered Booking Engine capability
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
Whizz AI · Rate
PriceMatch reads the price the guest is actually shown, on rate, geo, device and member fare, applies the response the hotel configured, and keeps a snapshot of both prices.
Detected: Live check on Booking.com: a lower price for the same Deluxe Room and dates at BW Lakeside Resort, on a mobile member fare.
Activated: The response Lakeside configured for a mobile, member-fare mismatch is applied on the rate the guest is looking at. A snapshot of both prices is kept.
Compare the rate the guest can actually see against the direct booking offer.
Account for location-specific OTA pricing where the connected source supports it.
Identify differences caused by mobile and device-specific OTA offers.
Recognise signed-in OTA member pricing, including supported loyalty levels.
How it works
Four steps on the live rate, while the guest is still deciding. Detection runs on all major OTAs.
Step 1
Read the price the guest is shown on each major OTA, on rate, geo, device and member fare.
Step 2
Apply the response the hotel configured, on the live rate the guest is looking at.
Direct
matched in real time
$358
Step 3
Keep a snapshot of both prices and the context they were seen in.
09:14 · Rate · OTA
$358 seen, $364 direct
Matched. Snapshot kept.
Step 4
The guest books direct. The booking carries the response that was applied.
Deluxe Room
Earn 3,580 points
Parity-safe
BW Riverside Hotel
12 - 14 Oct · 2 adults
Directmatched against all major OTAs in real time
Same public rate on both. Nothing undercut.
Signed in: Riverside Rewards member
Member value sits under the rate, not in it.
Deluxe Room
Member rate
$364
taxes and fees in
What actually breaks parity
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.
The difference that matters
Detection is the easy half. PriceMatch applies the response you configured on the live site, and keeps a snapshot of what it saw.
Proof
Both prices, the signal, the context and what was applied. Kept when it acts, and kept when it did not need to.
BW Riverside Hotel
PriceMatch · Snapshots · Today
5 checks · 4 responses
| Time | Signal | Context detected | Response applied |
|---|---|---|---|
| 09:14 | Rate | Booking.com public rate $358 against direct $364. Deluxe Room, 12 - 14 Oct. | Direct rate matched at $358. |
| 09:41 | Device | Mobile-only rate $349 on the same room. Desktop check came back clean. | Configured mobile response applied on the rate shown to that guest. |
| 10:07 | Fidelity | Signed-in Genius rate $339 on Booking.com. | Member rate mirrored at $339 for signed-in members. Public rate unchanged. |
| 10:52 | Geo | Price from Germany $352, from the UK $364. | Configured response applied for guests in that market. |
| 11:20 | Rate | Booking.com and direct both $364. | No response needed. Snapshot kept. |
Questions revenue managers ask
All major OTAs, including Booking.com, Expedia and Agoda.
Four signals: Rate, Geo, Device and Fidelity. The price the guest is actually shown, by market, by device, and signed in as a member.
No. PriceMatch is defence, not discount. The mechanism is parity and mirroring, not undercutting. The public rate is matched, and member value is carried in points and perks.
Yes. The Fidelity signal recognises signed-in OTA member pricing, including supported loyalty levels. The response is a member rate, never a percentage off.
You do. The AI detects on your own data and acts inside your rules. It never tunes a number on its own.
Every response is retained as a snapshot: both prices, the signal, the context and what was applied. It keeps the evidence, and writes back to the systems you already run.
Where the comparison happens
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.
Bring your OTA listings. We will show you where parity breaks on a phone and the response you would configure.