Servicing
The post-booking lifecycle covering changes, cancellations, reissues, refunds and support. Strong search/booking APIs do not compensate for weak servicing capabilities.
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?
Servicing 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
Travel Servicing Architecture
Model post-booking change, cancellation, refund, exchange, ancillary and schedule-change workflows with a canonical servicing architecture.
Explore →Agentic Travel Servicing, Consent and Auditability
Design agent-driven cancellation, refund and servicing with explicit consent, traceability, versioned evidence and post-booking authorization 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 →Amadeus Enterprise APIs and NDC Integration Guide
Design Amadeus Enterprise API Portal and Travel Platform/NDC integrations around access, entitlement, offer/order lifecycle, servicing, quota boundaries and observability.
Explore →Amadeus NDC Integration Guide
Implement Amadeus Travel Platform NDC content around source normalization, entitlement, booking/servicing and Offer/Order lifecycle.
Explore →Flight Reprice, Schedule Change, Ticketing and Order State
Separate reprice, schedule change, order, PNR, payment and ticket/document states across the flight-booking lifecycle.
Explore →