PRACTICAL AIRLINE-DISTRIBUTION GUIDE
GDS and NDC: Choosing the right foundation for a flight booking platform
GDS and NDC both connect travel sellers to airline content, but their access, offer structures, servicing and implementation requirements differ.
This guide explains each model, when hybrid distribution may fit and what to evaluate before building.
COMMON AIRLINE MODELShop → Reprice → Book → Fulfil → Service
Flight ShoppingPricingBranded FaresAncillariesBookingTicketingServicing
THE QUICK ANSWER
GDS and NDC solve related—but not identical—distribution problems
A GDS commonly provides broad multi-airline access and established agency workflows. NDC supports airline-controlled offers and richer retailing through structured API connections.
Airlines and routesMarkets and channelsFares and ancillariesCommercial accessTicketing modelServicing requirementsAccreditationInternal capability
Choose against the complete booking and servicing workflow—not only the source that returns a search response.
01 / GDS
Established multi-airline distribution for travel-selling workflows
A Global Distribution System connects eligible travel sellers with participating airline schedules, fares, availability and reservation functionality.
- One-way, return and multi-city shopping
- Multi-airline availability
- Public, negotiated or private fares
- Fare rules, cabin and baggage
- PNR creation and retrieval
- Special-service requests
- Ticketing where authority exists
- Voids, exchanges, refunds and queues where supported
Available functionality depends on the agreement, market, credentials, accreditation and ticketing authority.
02 / NDC
Airline-controlled offers through modern distribution APIs
New Distribution Capability is an airline-distribution standard supporting flexible offers and modern retailing workflows through airlines or approved providers.
- Airline-controlled flight offers
- Branded fares and fare families
- Baggage and seat offers
- Meals, priority and other ancillaries
- Offer repricing
- Order creation and retrieval
- Cancellation and servicing where exposed
- Airline-specific retail presentation
Do not assume every NDC connection supports identical search, payment, ticketing, change or refund workflows.
03 / PRACTICAL COMPARISON
GDS vs NDC
This comparison is directional. Confirm actual functionality against current documentation and commercial access.
AreaGDSNDC
Primary modelBroad multi-airline distribution and established agency workflowsAirline-controlled offers and modern retailing workflows
CoverageOften broad across participating airlinesVaries by airline, provider and agreement
Fare presentationTraditional fare, class and rule structuresCan support branded fares and richer details
AncillariesDepends on airline and GDS capabilityCan expose airline-specific offers
Booking recordCommonly PNR-basedCommonly offer- and order-based
TicketingEstablished workflows where authority existsDepends on airline, provider and fulfilment model
ServicingOften supports mature agency workflowsVaries significantly by provider and airline
Typical fitBroad coverage and established operationsSelected content and richer retail experiences
04 / SOURCE STRATEGY
Which model fits your platform?
Begin with business, fulfilment and operational requirements.
GDS-Led
Prioritize broad coverage and established servicing.
- Multi-airline breadth
- Agent or corporate channels
- Existing ticketing workflows
- Negotiated fare access
NDC-Led
Prioritize selected airline offers and retail content.
- Branded fares
- Ancillary merchandising
- Airline-controlled offers
- Supported order servicing
Hybrid
Use several sources where one cannot satisfy the model.
- GDS plus selected NDC
- Market-specific sources
- Commercial routing
- Common offer model
Hybrid complexity: plan normalization, duplicate offers, source identity, booking routing and source-specific servicing from the beginning.
05 / COMPLETE AIR-BOOKING JOURNEY
From search request to serviced booking
Search
Collect route, dates, travellers, cabin and filters.
Normalize
Map journeys, segments, fares, baggage and references.
Commercialize
Apply currency, fees, pricing and source preferences.
Compare
Explain schedule, fare, inclusions, policy and total price.
Reprice
Confirm availability, amount, validity and ancillaries.
Collect
Validate passenger, contact, document and service data.
Pay
Authorize, capture or record the approved payment state.
Book
Create the PNR, NDC order or provider reservation.
Fulfil
Track ticketing, documents and customer confirmation.
Service
Handle retrieval, changes, cancellation and refund.
06 / INTEGRATION ARCHITECTURE
Keep source-specific logic behind a controlled distribution layer
Customer, Agent or Corporate Interface
Flight Booking Platform API
Search, Pricing and Booking Orchestration
Common Airline Data Model
GDS / NDC / Airline Adapters
Distribution Providers and Airlines
Provider Adapters
Contain authentication, shopping, parsing, repricing, booking, ticketing, servicing and source errors.
Common Airline Model
Represent airports, journeys, segments, fares, baggage, offers, orders, PNRs and tickets consistently.
Booking Orchestration
Control selection, repricing, passenger data, payment, booking, fulfilment and notification.
Operational Layer
Expose references, payment, booking and ticketing states, schedule changes, queues and audit history.
07 / PROVIDER CAPABILITY
Do not compare distribution sources on search coverage alone
Shopping+
- One-way, return and multi-city
- Passenger and cabin combinations
- Flexible dates and carrier filters
- Private or negotiated content
Fare and Retail Content+
- Fare families and branded fares
- Baggage and seats
- Meals and additional services
- Change and cancellation conditions
Repricing+
- Offer validity
- Final fare revalidation
- Price-change response
- Separate ancillary validation
Booking+
- Passenger and contact requirements
- PNR or order creation
- Duplicate protection
- Booking retrieval
Ticketing and Fulfilment+
- Authority and time limits
- Ticket-number retrieval
- Pending-ticketing handling
- Document responsibility
Post-Booking+
- Cancellation and void
- Exchange and rebooking
- Refund and corrections
- Schedule-change handling
08 / RELIABILITY
Design for real air-distribution behaviour
Offer Expiry
Stop an expired offer from moving silently into payment or booking.
Price Change
Display the revised amount and require acceptance before continuing.
Provider Timeout
Use controlled timeouts without leaving the customer in an uncertain state.
Duplicate Submission
Protect booking and payment with idempotency and state controls.
Paid but Not Booked
Record the mismatch, alert operations and trigger the approved recovery path.
Booked but Not Paid
Identify the provider record and begin payment recovery or cancellation.
Ticketing Pending
Show the real status instead of an inaccurate completed message.
Schedule Change
Connect provider messages to the correct booking and service queue.
09 / TESTING
Verify shopping, booking, fulfilment and servicing
One-way, return and required multi-city searchAdult, child and infant combinationsDirect and connecting journeysFare families, baggage and ancillariesOffer repricing and price-change handlingOffer expiry and passenger validationPayment success and failureBooking success and failureDuplicate-request protectionTicketing and pending-ticketing workflowsBooking retrieval and cancellationRefund and schedule-change handlingTimeouts, limits and provider errorsOperational alerts and audit loggingMobile and desktop booking journeys
Use provider-approved sandbox, certification or test environments wherever available.
10 / PROVIDER EVALUATION
Confirm commercial, technical and operational fit
Commercial questions+
- Airlines and markets covered
- Required agreement and applicable access
- Private or negotiated fares
- Accreditation, ticketing and fulfilment
- Support and certification requirements
Technical questions+
- Documentation and realistic test environment
- Shopping and retail-content coverage
- Repricing and booking retrieval
- Servicing, webhooks and messages
- Rate limits and error documentation
Operational questions+
- Offer-expiry behaviour
- Pending-ticketing handling
- Schedule-change delivery
- Manual-intervention boundaries
- Incident escalation and refund handling
11 / COMMON MISTAKES
Avoid incorrect assumptions before integration begins
Choosing on search alone
Assess booking, fulfilment and servicing—not only shopping results.
Designing the interface first
Provider constraints must influence fares, ancillaries, payment and servicing.
Treating sources as identical
GDS and NDC structures require mapping into a common model.
Assuming all NDC is rich
Content varies by airline, route, market, provider and agreement.
Assuming full automation
Some changes, refunds and disruption cases remain agent-assisted.
Combining transaction states
Track payment, booking and ticketing independently.
Unsafe booking retries
Unprotected retries can create duplicate reservations or charges.
Ignoring operational users
Teams need references, queues, alerts and recovery tools.
Technical implementation experience and official provider partnership status are different. Public wording must reflect the documented relationship.
COMMON QUESTIONS
Clarity before complexity.
Is NDC replacing the GDS?+
NDC is changing airline distribution but does not replace every GDS workflow. Many businesses use GDS, NDC or a combination based on coverage, servicing and commercial requirements.
Is NDC always cheaper?+
No. Commercial outcomes depend on the airline, provider, fare, market, agreement, workflow and servicing costs. The architecture should not assume a guaranteed price advantage.
Can one platform combine GDS and NDC offers?+
Yes. A hybrid platform can normalize offers and route booking through the correct source while preserving its references, fulfilment and servicing rules.
Do we need accreditation?+
Requirements vary by provider, country, agreement, ticketing model, agency status and fulfilment partner. Confirm them before implementation.
Can NDC support ticketing?+
Some workflows support order creation and fulfilment, but the model varies. Ticketing authority, commercial access and production permissions must be confirmed.
Can GDS and NDC support changes and refunds?+
Potentially. Coverage varies by provider, airline, fare and workflow. Unsupported cases need a structured agent-assisted process.
How long does a GDS or NDC integration take?+
Timing depends on access, certification, shopping scope, retail content, payment, booking, ticketing, servicing and the existing architecture. Discovery produces a phased plan.
Can GDS or NDC be added to an existing platform?+
Yes, after reviewing the current booking engine, internal model, payment flow and operations. Targeted refactoring may be required first.
FROM AIRLINE CONTENT TO A COMPLETE BOOKING JOURNEY
Planning a GDS, NDC or hybrid flight platform?
Bring your selected provider, target airlines, markets, customer channel or existing integration. We will help map shopping, pricing, payment, booking, ticketing and servicing before development begins.
50+Travel-Tech Projects Delivered
12+ YearsTravel-Technology Experience
Shopping to ServicingConnected Air-Booking Workflows
GDS, NDC and HybridArchitecture for Real Distribution