Occupancy Pricing
A pricing model where amounts vary by adult/child counts, child ages or room occupancy.
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?
Occupancy Pricing commonly appears across pricing layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Hotel Rate Plans and Pricing Models Explained
Learn how rate plans, occupancy pricing, length-of-stay pricing, restrictions and derived rates interact inside hotel distribution and metasearch systems.
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 →ARI vs Live Search vs Reprice: Hotel Pricing and Availability Lifecycle
Compare ARI, live search and reprice/check flows across freshness, granularity, latency, booking confidence and source-of-truth.
Explore →Bedbank vs B2B Marketplace for Wholesale Travel Supply
Compare bedbanks and B2B travel marketplaces across inventory contracts, pricing, credit, booking lifecycle and supplier ownership.
Explore →Cache Invalidation Patterns for Travel Pricing
Design TTL, event invalidation, stale-while-revalidate and live-reprice boundaries for hotel and flight pricing.
Explore →Google Hotels Integration: Developer Guide
Implement Google Hotels from a developer perspective with Hotel Lists, property mapping, Pull/Changed Pricing/ARI, Transaction XML, landing pages, OAuth2, request/response models, error handling and monitoring.
Explore →