Offer
A sellable commercial proposal combining itinerary/property, price, availability, seller and conditions. Offer identity should retain its source reference through repricing and booking.
Why it matters
In the flight domain, itinerary, leg, segment, carrier and seller identity are distinct. Flattening them too aggressively mixes schedule, fare, agent and booking rules. The search UI can be simple, but the source model needs enough detail for repricing and handoff.
What does it look like in practice?
The same itinerary can be sold by multiple agents with different fare brands, baggage and booking conditions. Segment schedule and seller/offer identity are different concepts.
Implementation questions
- Which legs and segments form the itinerary?
- Are marketing and operating carriers separated?
- Is agent/provider identity retained?
- Is the source reference available for repricing?
Common mistakes
- Modeling an offer as flight number plus price
- Mixing marketing and operating carriers
- Embedding agent identity into itinerary identity
Where does it appear in the travel stack?
Offer commonly appears across flight, transaction layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
momondo: Flight Offers, Seller Ranking and Booking Operations
Explore momondo's flight comparison, provider ordering and commercial boundaries, with fare-mismatch diagnosis, handoff checks and operational metrics.
Explore →Search Result Ranking Architecture
Design explainable travel ranking that separates relevance, normalized price, offer quality, provider reliability and commercial constraints.
Explore →Agentic Travel Reference Architecture
Design AI agent → search → offer → reprice → confirmation → payment → booking → servicing with travel-specific authorization, idempotency and audit boundaries.
Explore →Canonical Offer, Order and Booking State Model
Design canonical Offer, Order and Booking lifecycle boundaries with an explicit booking state machine for travel integrations.
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 →SHR Windsurfer CRS: Hotel Central Reservations Profile
A technical ecosystem profile of SHR Windsurfer/allora CRS across central reservations, distribution, direct booking and hotel commercial systems.
Explore →