How to Debug Hotel Price Mismatches

A hotel price mismatch occurs when the offer shown in metasearch differs from the price visible after click on the provider or booking engine. The first objective is not to decide which system is wrong; it is to prove that the same search context is actually being compared.

Symptom

A traveler sees one price for a property, dates and occupancy, then lands on a higher price, a different currency, another room/rate or an unavailable offer.

Possible causes

• Context: dates, occupancy, child ages, residency, currency or locale changed.
• Rate identity: room/rate-plan mapping is inconsistent.
• Tax/fee: base versus total or inclusive/exclusive semantics differ.
• Freshness: cached or feed data is stale.
• Provider: the supplier repriced after click.
• Landing: the deep link did not preserve search context.

Diagnosis

1. Reproduce the request with one correlation ID.
2. Persist the canonical search input.
3. Retrieve the provider-response snapshot used for rendering.
4. Compare dates, occupancy and currency in the click URL.
5. Capture room/rate identity and total price on landing.
6. Classify the delta as context, component or freshness.

Evidence to collect

Keep at least hotel, stay dates, occupancy, currency, room ID, rate-plan ID, base price, taxes, fees, total price and observation timestamp in one incident record.

Diagnostic decision tree

If context differs, treat it as propagation rather than price accuracy.

If context matches but room/rate differs, investigate mapping or deep-link construction.

If room/rate matches but components differ, inspect tax/fee normalization.

If all fields match but the snapshot is old, test cache and refresh behavior.

If the snapshot is current but landing differs, validate provider-side repricing or landing logic.

False positives

Currency rounding, per-night versus stay totals, “from” prices, member/mobile rates and refundable versus non-refundable products can look like mismatches while actually describing different products.

Recovery

After the fix, compare search response → rendered price → landing price using the same context. Do not close the incident merely because the UI now looks correct.

Observability

Track search-to-landing price delta, mismatch rate, unavailable-after-click rate, stale-offer age and provider-level price accuracy.

Prevention

Log offer snapshots together with context hashes, room/rate identity and price components. Trigger mismatch alerts only after context equality is established.