New Distribution Capability (NDC): Operator Guide 2026

New Distribution Capability is an IATA XML data standard that lets airlines distribute rich, personalized offers such as dynamic fares, bundles, and ancillaries directly to agencies and platforms, instead of pushing flat fares through the legacy [GDS](/glossary/gds). The point of NDC is offer control: an airline that distributes through NDC decides what to merchandise, how to bundle it, and who owns the customer record, where the old EDIFACT GDS pipes reduced its product to a price in a comparison list. For travel agency operators, OTAs, and platforms, NDC changes how flight content arrives, what an [IATA number](/glossary/iata-number) and accreditation now require, and which technology partner can actually surface NDC offers. This guide explains NDC versus the GDS, what operators and agencies need to adopt it, and the partner and affiliate distribution angle for any brand reselling air content.

NDC Defined: The IATA XML Standard for Airline Offers

New Distribution Capability is an IATA-led XML messaging standard that lets airlines build and distribute their own offers directly to selling channels rather than filing fares into the GDS. IATA created NDC to solve a 30-year-old constraint: the EDIFACT messaging the GDS runs on can carry a price and a schedule but cannot carry a rich, personalized offer, so airlines could not merchandise the way any modern retailer does. With [NDC](/glossary/new-distribution-capability), the airline assembles a tailored offer (a fare plus bag, seat, lounge, and bundle options) and sends it as a single rich response, keeping control of what is shown and to whom. IATA frames NDC as the foundation of airline retailing, and Phocuswright research tracks its share of bookings rising year over year.

NDC is a standard, not a product, which is the detail operators most often miss. IATA publishes the schema and certifies airlines, aggregators, and sellers at capability levels, but each airline implements its own NDC offers and each technology provider builds its own connection. That means adopting NDC is not flipping a switch; it is integrating against airline APIs or routing through an NDC-enabled aggregator that normalizes many carriers into one feed. The fragmentation is the single biggest adoption friction, and Phocuswire coverage of NDC rollouts repeatedly cites inconsistent implementations as the reason agencies move cautiously.

NDC vs GDS: 3 Decades of Distribution, Rebuilt

The core difference between NDC and the GDS is who controls the offer presented to the buyer. The [GDS](/glossary/gds) (Amadeus, Sabre, Travelport) aggregates airline fares into a neutral marketplace where agents compare price and schedule, which made flights a commodity sorted by cost. NDC inverts that by letting the airline present a merchandised offer with ancillaries and personalization intact, so the same seat can be sold as part of a richer, differentiated product. The GDS is not disappearing; most carriers run NDC and GDS content in parallel, and many GDS providers now carry NDC offers themselves. The strategic shift is that control of the offer moves back to the supplier.

The parallel to hotel distribution is exact and worth naming. Hotels watched OTAs commoditize rooms into a price-sorted list while keeping the guest relationship, and they responded by investing in direct and affiliate channels they control. Airlines watched the GDS do the same to fares and responded by building NDC. Both moves answer the same question: how does a supplier distribute widely without surrendering the offer, the [ancillary revenue](/glossary/ancillary-revenue), and the customer data. The [hotel distribution strategy guide](hotel-distribution-strategy-channel-mix-operator-guide-2026) covers the lodging version of this exact rebalancing toward owned channels.

What Agencies and Platforms Need to Adopt NDC

Adopting NDC requires 4 things from an agency or platform: an NDC connection, IATA accreditation, an aggregation strategy, and an offer-and-order management layer. The connection is either a direct API integration with each airline or, more commonly, a link through an NDC-enabled aggregator that normalizes many carriers. An [IATA number](/glossary/iata-number) and the right accreditation remain the gate for ticketing authority and settlement through systems like BSP, so NDC does not remove the accreditation requirement; it changes what the connection behind it looks like. The third need is a deliberate aggregation choice, because integrating dozens of airline APIs directly is rarely viable for a mid-size seller.

The fourth need is the one operators underestimate: order management. NDC replaces the old PNR-and-ticket model with an order-based model, so servicing a change, refund, or exchange runs through NDC order management rather than legacy ticketing flows. US DOT consumer-protection rules on refunds and disclosures still apply to whatever the seller offers, which means an agency cannot adopt NDC offers without a servicing path that meets those obligations. A clean [central reservation system](/glossary/central-reservation-system) or order platform behind the connection is what keeps NDC bookings serviceable rather than stranded.

The Partner and Affiliate Distribution Angle

An owned affiliate channel is the distribution path that preserves NDC's offer control all the way to the sale. An airline or air-content reseller that builds NDC offers wants those offers in front of high-intent buyers without handing the relationship to an intermediary, and an owned [travel affiliate program](/glossary/travel-affiliate-program) does exactly that. Partners and creators route demand to the brand's own booking flow through tracked deep links, the NDC offer renders with its ancillaries intact, and the brand pays a performance commission on a confirmed booking instead of a flat intermediary fee. The offer control NDC delivers survives all the way to the sale.

Affiliate and partner channels also solve the data problem NDC is meant to fix. Because an affiliate booking lands in the brand's own order system, the brand keeps the customer record, the ancillary attach data, and the attribution back to the partner who drove it. Partners earn a [CPA](/glossary/cpa) per confirmed booking, a [RevShare](/glossary/revshare) of fare-plus-ancillary value, or a hybrid, with the attribution window and the completed-trip trigger set so a cancellation triggers a clawback rather than a paid-out fare the traveler never flew. That control is impossible when the same demand flows through an [OTA](/glossary/ota) or a neutral [metasearch](/glossary/metasearch) listing that hands the airline a thin booking and keeps the rest, and it is why the brand can down-weight brand-bidding or coupon partners that intercept demand it already owned. Track360 tracks partner-driven bookings and pays on results, which is why air-content resellers building NDC-rich offers increasingly add an owned affiliate channel, a structure detailed in the [flight and airline affiliate guide](flight-airline-affiliate-programs-operator-guide-2026) and the pillar [travel affiliate marketing guide](travel-affiliate-partner-marketing-for-brands-otas-channel-strategy-2026).

NDC Adoption Risks and Open Questions

Three risks define NDC adoption and operators should price them in before committing: implementation fragmentation, servicing complexity, and content parity gaps. Fragmentation means each airline's NDC implementation differs, so a seller integrating directly faces dozens of slightly different APIs, which is why most route through an aggregator and accept that layer's coverage limits. Servicing complexity comes from the order-based model: changes and refunds that were routine in the GDS world require NDC order management that not every back office supports yet. Skift and Phocuswire coverage both flag these as the friction points slowing adoption despite IATA's targets.

Content parity is the open question that matters most commercially. Airlines increasingly reserve their richest fares and ancillaries for NDC channels, so a seller stuck on GDS-only content may show incomplete or less competitive offers over time. The defensive move is to ensure the distribution channels a brand controls (direct, affiliate, and partner) can surface NDC-rich offers, so the brand is not forced to choose between reach and a complete offer. Operators who own their distribution channel keep that choice; those who rent it through intermediaries inherit whatever content the intermediary chooses to carry.

5 Steps to Build an NDC-Ready Distribution Plan

Operators get NDC-ready in 5 steps that connect the standard to the channels where offers actually sell.

1. Audit your current air content and connection. Document which airlines you sell, whether content arrives via GDS or NDC, and where your IATA accreditation and ticketing authority sit. You cannot plan a migration without knowing the starting point. (Timeline: 2 to 3 weeks)
2. Choose direct API versus aggregator. Decide whether to integrate airline NDC APIs directly or route through an NDC-enabled aggregator that normalizes carriers; for most mid-size sellers the aggregator is the only viable path to scale. (Timeline: 3 to 6 weeks)
3. Stand up order and servicing management. Build or buy the order-management layer that handles NDC changes, refunds, and exchanges in line with US DOT consumer-protection rules, so bookings stay serviceable. (Timeline: 6 to 10 weeks)
4. Wire NDC offers into owned channels. Surface NDC-rich offers in your own booking flow and partner deep links so ancillaries and personalization survive to the sale, and the brand keeps the customer data. (Timeline: ongoing)
5. Add a performance partner and affiliate layer. Recruit content publishers, creators, and loyalty partners, track their bookings against the NDC offers, and pay on confirmed results so distribution cost stays variable and attributable. (Timeline: 6 to 10 weeks)

The sequence puts servicing before scale, because an NDC offer you cannot service is a liability, not an asset. Once the connection and order management are solid, the owned partner and affiliate layer is what turns NDC's offer control into measurable, attributable distribution. Track360 tracks partner-driven bookings against those offers and pays on confirmed results, so the air-content seller keeps the customer data and the attribution that NDC and the GDS alone cannot return.

Frequently Asked Questions