Price Coverage
The share of searchable hotel/date/occupancy or route/date contexts for which pricing is available. Drops can signal connectivity or inventory issues.
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?
Price Coverage commonly appears across pricing, measurement layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Provider Health Scoring Model
Build an explainable travel-provider health score using latency, success, freshness, price accuracy, coverage and handoff quality.
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 →Agentic Travel Reference Architecture
Design AI agent → search → offer → reprice → confirmation → payment → booking → servicing with travel-specific authorization, idempotency and audit boundaries.
Explore →NDC Offer/Order Lifecycle: Search to Servicing
Model NDC Offer/Order lifecycle across search, offer, revalidation, order creation, payment, ticketing, servicing and reconciliation states.
Explore →Stale Availability / Offer Expired Troubleshooting
Diagnose stale availability and expired offers across freshness, cache, token and revalidation layers between search and booking.
Explore →Travel Search → Offer → Reprice → Booking Reference Architecture
Design an end-to-end reference architecture for travel search, canonical offers, repricing, payment and booking across supplier integrations.
Explore →