New Distribution Capability (NDC) Explained for OTAs

New Distribution Capability (NDC) is the IATA-led standard reshaping how airlines distribute their content to OTAs, B2B platforms, and travel agents. NDC moves the offer-and-order flow from the legacy GDS model (discrete fare classes filed in advance) to a modern model where airlines construct offers in real time with full ancillary catalogues, continuous pricing, and personalised bundles. The standard has been in development for over a decade and reached meaningful adoption across major full-service carriers globally. This page covers what NDC actually is, how it differs from traditional GDS distribution, why it matters for OTAs and B2B platforms, the major airlines that have adopted it, the integration economics and operational challenges, and where NDC is heading. The companion guides for the broader airline distribution context are airline system management as the cluster anchor for the airline-side framing, airline API integration for the OTA-side integration patterns, airline booking system architecture for the OTA platform view, and OTA commission on airline tickets for the channel economics. Cross-cluster reach into travel API integration covers the supplier-integration patterns that NDC depends on.

What NDC Actually Is And Why It Exists

NDC emerged from a structural problem in airline distribution that the legacy GDS model could not solve. The traditional model dates to the 1960s and 1970s when GDS systems (Sabre, Apollo, later Amadeus and others) were built to distribute the simple inventory airlines offered then - flight number, date, fare class, seat count. Decades later airlines wanted to distribute much richer content - bundled offers, ancillaries with specific terms, dynamic prices, personalised pricing, branded fare families - but the GDS plumbing could not carry it. The result was that airlines spent billions on revenue management and offer construction internally, then watched the GDS strip the richness out for distribution. NDC is the IATA standard developed to solve this gap. The standard, formally Resolution 787, defines XML schemas (and increasingly JSON variants) for airline-to-partner communication covering the offer-and-order flow, ancillary distribution, servicing, and settlement. The standard is governed by IATA's NDC Programme with industry working groups setting the direction. The offer-and-order model at NDC's heart works differently from GDS PNRs. The airline constructs an offer in response to a partner request - a specific itinerary with a specific price including specific ancillaries valid for a specific time. The partner accepts the offer to create an order; the airline binds the order through ticketing or order servicing. The model is more flexible than GDS PNRs because the airline controls the offer construction in real time. The richer content NDC carries includes branded fare families (Lufthansa's Light/Standard/Plus/Flex tiers, Singapore Airlines' Lite/Standard/Flexi, similar from many carriers), bundled ancillaries (seat selection, baggage, meals priced together at a discount), personalised pricing (where regulation permits), and continuous pricing (specific prices per request rather than discrete fare classes). The commercial drivers for airlines investing in NDC are real. Airlines pay GDS segment fees of 6 to 12 USD per ticketed segment for short-haul and higher for long-haul; bypassing GDS for distribution saves these fees. Airlines also want to distribute their full ancillary catalogue rather than a stripped-down GDS subset. The combination of cost savings on distribution and revenue lift on ancillary attach makes NDC strategically important to airline economics. The OTA implications are equally real. OTAs that integrate NDC directly with airlines see better commission rates because the airline saves the GDS segment fee. The OTA's cart can surface the airline's full ancillary catalogue rather than the GDS-stripped version. Travellers get richer offers and more options. The ten-year journey from NDC standard launch to material adoption reflects the difficulty of changing distribution at industry scale. The major carriers invested years in NDC implementation; aggregators and OTAs invested more years in integration. The industry is now at a tipping point where NDC distribution is meaningful, growing, and reshaping commercial dynamics. The cluster guide on airline system management covers the airline-side context, and the cross-cluster integration view is in airline API integration.

The cluster guides below cover the airline distribution context, broader API integration patterns, and supplier integration that interact with NDC.

NDC Versus GDS And The Channel Mix Decision

OTAs and B2B platforms run hybrid distribution today, with both NDC and GDS in their channel mix. The decision of which to integrate when shapes the platform's economics for years. GDS distribution through Amadeus, Sabre, and Travelport remains important for the long tail of airlines and routes. GDS coverage spans thousands of airlines globally; NDC adoption is concentrated in major full-service carriers in mature markets. An OTA that goes NDC-only loses access to the long-tail airlines that have not adopted NDC. NDC distribution on participating airlines delivers better economics, richer content, and ancillary depth that GDS cannot match. An OTA on GDS-only on participating airlines misses the upside that NDC integration would capture. The hybrid integration runs both channels with routing logic that picks the right channel per request. The same airline might be available through GDS and NDC; the platform's adapter routes to NDC where economics are better and falls back to GDS where NDC is unavailable, slow, or returning errors. The integration sequence matters strategically. Most OTAs start with GDS for breadth (one or two GDS providers cover the long tail), add NDC for the highest-volume airlines first (where the commission spread justifies the engineering), and grow NDC coverage over time as the integration matures. Direct NDC integration with each airline takes 3 to 6 months and 30,000 to 150,000 USD per airline; the sequence has to follow commercial value rather than completionism. Aggregator-mediated NDC wraps multiple airline NDC connections into a single API the OTA can call. Travelport's NDC offering, Sabre's NDC orchestration, Amadeus's NDC, and third-party providers (Duffel, Verteil, others) deliver multi-airline NDC through a unified interface. Aggregators reduce per-airline integration cost at the price of aggregator fees on top of the airline's commission. Smaller OTAs typically start with aggregator-mediated NDC; larger OTAs integrate directly with high-volume airlines and use aggregators for the long tail. The channel routing logic in the platform's adapter layer applies real-time decisions per request. For each airline, the adapter knows whether NDC is available, whether the OTA has commercial agreements with the airline for NDC distribution, and what the economic spread is between NDC and GDS. The routing picks the channel with better economics where both are available; it falls back gracefully when one channel is unavailable. The operational complexity of running both channels is real. Servicing flows differ - cancellation through GDS uses one set of API patterns; cancellation through NDC uses another. Reconciliation differs - GDS settles through BSP; NDC settlement varies by airline. Reporting must aggregate across channels to give finance and commercial teams a single source of truth. The cluster guide on Sabre software covers one major GDS-and-NDC vendor, and the cross-cluster channel-economics view is in OTA commission on airline tickets.

Major Airlines And NDC Maturity

NDC adoption varies meaningfully across airlines. Some carriers have invested heavily and route a substantial share of their distribution through NDC; others remain GDS-heavy with NDC as supplementary. The maturity matters for OTA integration strategy. Lufthansa Group (Lufthansa, Swiss, Austrian, Brussels Airlines, Eurowings) has been one of the most aggressive NDC adopters globally. The group introduced a Distribution Cost Charge on GDS bookings years ago to incentivise partner migration to NDC; the move drew significant industry pushback but signalled the strategic importance the group placed on NDC. Lufthansa Group's NDC implementation is mature; OTAs integrating NDC see meaningful economic upside. British Airways and IAG (British Airways, Iberia, Aer Lingus, Vueling, LEVEL) have invested in NDC alongside continued GDS distribution. The IAG NDC implementation supports rich offers and ancillaries; OTAs integrate at varying depth. American Airlines took a strong NDC stance, removing certain content from GDS and offering it only through NDC channels. The move reshaped North American distribution; OTAs without American Airlines NDC access lost competitive position on AA routes. Air France-KLM has invested in NDC with similar strategic emphasis to Lufthansa. The Franco-Dutch group's NDC implementation is mature and growing. Singapore Airlines operates NDC as part of its KrisConnect distribution platform with strong ancillary support. Emirates distributes through NDC with growing partner adoption. Qantas has invested in NDC distribution to OTAs and corporate partners. Cathay Pacific operates NDC alongside its broader distribution. ANA and JAL distribute through NDC with growing partner integration. The mid-tier and regional airlines are at varying stages. Some have launched NDC; some are in development; some have no NDC plans. The long tail of small carriers and regional airlines remains GDS-only or direct-API-only. The low-cost carriers have a different relationship with NDC. Many LCCs operated outside GDS historically through their own direct distribution; NDC offers them a structured way to reach OTAs without joining GDS. Some LCCs have adopted NDC; others continue with proprietary direct APIs that may or may not align with NDC standards. OTA strategy integrates NDC airline-by-airline, prioritising by volume on the OTA's traffic and commercial spread. An OTA with heavy traffic on Lufthansa Group routes might integrate Lufthansa NDC first; an OTA with US-heavy traffic might prioritise American Airlines, United (which has NDC), and Delta. The integration sequence follows the OTA's commercial reality rather than a generic checklist. The certification and onboarding per airline NDC integration is real. Airlines have specific certification programmes for NDC partners that include technical validation, commercial agreement negotiation, and onboarding support from the airline's distribution team. Most major airlines run formal NDC partner programmes with defined eligibility criteria and certification paths. The aggregator alternative for accessing multiple NDC airlines through a single integration matters most for OTAs lacking the engineering capacity to integrate each airline directly. Travelport's NDC, Sabre's NDC orchestration, and third-party providers like Duffel and Verteil deliver multi-airline NDC access. The trade-off is the aggregator's fees on top of the airline's commission and the dependency on the aggregator's roadmap. The cluster guide on airline API provider covers the API-provider landscape, and the cross-cluster cluster integration view is in travel API development services.

Operational Reality And The Future Of Distribution

NDC integration in production reveals operational realities that the marketing material does not always emphasise. The platforms that succeed with NDC do so by treating it as long-term infrastructure investment rather than a feature ship. Per-airline implementation variations are real and material. Each airline's NDC implementation has quirks - which optional fields are populated, how error responses differ from the standard, how the airline handles edge cases like multi-leg interline tickets or codeshare pricing. The OTA's adapter layer must handle each airline's quirks while maintaining a consistent internal model. The variations mean integration is per-airline engineering work; the standard helps but does not eliminate the work. Servicing flows on NDC differ from GDS. Cancellation, modification, name changes, refund processing, schedule-change handling - each operation calls different NDC endpoints with different patterns than equivalent GDS flows. The OTA's servicing layer must implement parallel paths for NDC and GDS bookings. Travellers should not see the difference; the platform's internal complexity is real. Reconciliation against airline settlement for NDC bookings varies by airline. Some airlines settle NDC orders through traditional BSP-like frameworks; others use direct billing relationships with NDC partners. The OTA's reconciliation layer must handle different settlement formats per airline rather than the standardised BSP report. The reconciliation complexity is one of the more underestimated aspects of NDC operations. Webhook handling for airline-initiated events on NDC bookings (schedule changes, fare adjustments, cancellation notifications) follows airline-specific patterns rather than a uniform standard. The OTA's webhook receiver must handle each airline's event format and process it appropriately into the booking record. Continuous pricing complications arise because the same flight at the same time may price differently for different requests. The OTA's caching strategy must avoid caching prices (already a best practice but particularly important for NDC). Reconciliation needs to capture the price actually offered and ticketed rather than expecting fare-class consistency. The ONE Order initiative is the next industry effort layered on NDC. ONE Order replaces the multi-document booking record (PNR plus EMD plus various other artefacts) with a single order representing the customer's complete trip. ONE Order is in early adoption; most airlines and OTAs continue to operate the legacy order representation alongside ONE Order pilots. The future direction for distribution combines several trends. NDC adoption continues to grow as more airlines implement the standard and existing implementations mature. Direct distribution beyond NDC (airlines selling direct through their own platforms with deeper personalisation) competes with both NDC and GDS for share. Aggregator-platform competition with traditional GDSs reshapes the long tail of distribution. AI-assisted offer construction lets airlines produce more sophisticated dynamic offers, with NDC carrying the richer offers to partners. Sustainability features in offers (carbon impact per route, lower-emission options surfaced first, offset bundling) emerge as standard NDC content. For OTAs and B2B platforms, the NDC future is hybrid for years to come. GDS remains important for breadth; NDC is essential for depth on participating airlines; aggregators bridge the gap for operators without engineering capacity to integrate everything directly. The platforms that win invest continuously in NDC integration as it matures rather than treating it as a one-time project. The honest framing is that NDC is not a destination; it is the current direction of airline distribution. The standards will evolve; airlines' implementations will mature; the OTA's commercial logic will continue to adjust as distribution dynamics shift. The platforms that get NDC right do so through long-term commitment to the technology and the partner relationships, not through quarterly feature pushes. The cluster anchor on airline API integration covers the broader integration patterns, and the cross-cluster commercial-economics view is in OTA commission on airline tickets. NDC done right delivers richer content, better economics, and competitive positioning that GDS-only platforms cannot match. NDC done badly produces fragile integrations that break under load and consume operations time. The difference comes down to engineering investment and operational discipline.

FAQs

Q1. What is New Distribution Capability (NDC)?

NDC is the IATA-led standard for direct airline distribution that lets airlines expose richer offers, ancillaries, and dynamic pricing through modern XML or JSON APIs. It bypasses the traditional GDS distribution layer for the offer-and-order flow, letting airlines distribute the full content their internal systems produce rather than the discrete fare classes GDS forces.

Q2. Why does NDC matter to OTAs and B2B platforms?

Airlines that have invested in NDC distribute richer offers (full ancillary catalogues, continuous pricing, personalised bundles) and pay higher commission to platforms that integrate directly because they save the GDS segment fee. OTAs and B2B platforms that integrate NDC unlock better economics on participating airlines and access content that GDS distribution cannot easily deliver.

Q3. How does NDC differ from traditional GDS distribution?

GDS distribution uses discrete fare classes filed in advance by the airline; NDC uses an offer-and-order model where the airline constructs offers in real time tailored to each request. GDS speaks legacy SOAP/XML protocols; NDC speaks modern XML or JSON over HTTP. GDS distributes through aggregator pipes shared across many airlines; NDC connects directly between the airline and the partner.

Q4. Which airlines have adopted NDC?

Major full-service carriers globally have invested in NDC at varying maturity levels. British Airways, Lufthansa Group, American Airlines, Air France-KLM, Singapore Airlines, Emirates, Qantas, Cathay Pacific, ANA, JAL, and many others operate NDC distribution alongside GDS. The maturity varies - some airlines route a majority of their distribution through NDC for partners.

Q5. What does NDC integration cost?

Each NDC integration with a major airline takes 3 to 6 months of engineering work and costs 30,000 to 150,000 USD per airline depending on the complexity of the airline's NDC implementation. Ongoing maintenance per airline runs 5 to 15 percent of original integration cost annually because airlines update their NDC schemas frequently.

Q6. Should an OTA integrate NDC directly or through an aggregator?

Direct integration delivers better economics at scale and full feature access; aggregators simplify integration at the cost of extra fees and dependency on the aggregator's roadmap. Smaller OTAs typically use aggregators (Travelport's NDC, Sabre's NDC orchestration, Amadeus's NDC, third-party providers like Duffel, Verteil). Larger OTAs integrate directly with their highest-volume airlines.

Q7. What ancillaries does NDC support that GDS does not?

NDC carries the full ancillary catalogue an airline offers - seat selection with specific seat maps, baggage by piece and weight, in-flight meals with dietary options, lounge access, fast track at security, priority boarding, on-board duty-free, and travel insurance. GDS supports a subset and varies in depth per airline.

Q8. How does NDC handle continuous pricing and dynamic offers?

NDC offers can be priced dynamically per request rather than against discrete fare classes. The airline's revenue management produces a price specific to the search context - origin, destination, dates, traveller profile where shared, and supply-demand at the moment. Platforms consuming NDC need to handle continuous prices alongside the legacy discrete fare class structure.

Q9. What are the operational challenges of NDC integration?

Each airline implements NDC with its own quirks - schema variations, optional fields used differently, error handling that diverges from the standard. Servicing flows (cancellation, modification, refund) on NDC bookings differ from GDS bookings and require parallel implementation. Reconciliation against airline settlement varies because NDC settlement frameworks are still evolving.

Q10. What is the future of NDC and travel distribution?

NDC adoption continues to grow, with airlines pushing more distribution through NDC to capture better economics and offer richer content. ONE Order is the next standard layered on NDC for unified order management across the booking lifecycle. The legacy GDS distribution remains important for the long tail of airlines and routes that have not adopted NDC. Modern OTAs run hybrid integrations with both channels.