Conditional Rate
A rate available only to users meeting membership, mobile, geography, loyalty or campaign conditions.
Why it matters
Pricing concepts only make sense with occupancy, stay, cancellation, tax/fee and eligibility context. Normalizing one numeric amount is easy; deciding whether two products are truly comparable is harder. Pricing semantics should remain consistent across display, ranking and booking handoff to avoid false parity and accuracy conclusions.
What does it look like in practice?
A €200 breakfast-refundable offer and a €192 room-only non-refundable offer may look close numerically but are not the same product. Pricing concepts need occupancy, rate-plan and tax/fee context.
Implementation questions
- Is the amount nightly or stay-total?
- Are mandatory taxes and fees included?
- Which occupancy and rate plan does it represent?
- Does it require revalidation before booking?
Common mistakes
- Confusing base and total price
- Dropping eligibility rules
- Treating different room/rate semantics as equivalent
Where does it appear in the travel stack?
Conditional Rate commonly appears across pricing layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Offer Identity & Offer Fingerprint Design
Design deterministic travel-offer fingerprints across provider, room/rate, policy and search-context dimensions without coupling identity to price.
Explore →Search Result Ranking Architecture
Design explainable travel ranking that separates relevance, normalized price, offer quality, provider reliability and commercial constraints.
Explore →Tripadvisor Hotels: Content, Offer Identity and Booking Boundaries
Separate Tripadvisor hotel content, Terra access and rate distribution; diagnose property mapping, offer mismatches and booking-handoff failures.
Explore →Amadeus Self-Service API Integration and Migration Guide
Operate and migrate Amadeus Self-Service integrations after the 17 July 2026 decommissioning, with clear OAuth, offer-lifecycle, booking-recovery and coverage boundaries.
Explore →Hotel Price Accuracy: Keeping Metasearch Rates Consistent
Manage hotel-metasearch price accuracy with mismatch taxonomy, source-versus-landing validation, cache age, taxes/fees, offer comparability, KPIs and root-cause playbooks.
Explore →Room and Rate Normalization for Hotel Metasearch
Learn how to normalize room types, rate plans, occupancy, meal, cancellation and package metadata so hotel offers can be compared without hiding meaningful differences.
Explore →