What Is NDC?

What is NDC?

New Distribution Capability (NDC) is an XML-based data standard developed by IATA, the International Air Transport Association, to modernize how airlines distribute their content to travel agencies, OTAs and other sellers. It is best understood as a messaging standard — a shared set of XML schemas — rather than a piece of software you buy or a channel you plug into.

The goal is simple to state: let airlines sell flights the way modern online retailers sell products. Instead of distributing a stripped-down, commoditized fare, an airline using NDC can present a complete, branded offer — the seat, the bag, the meal, the Wi-Fi, the bundle — priced dynamically and tailored to the request. NDC gives the industry a common language for those richer offers.

Why NDC exists

For decades, airline content has flowed to agencies over EDIFACT, a legacy messaging standard built around filed fares. That model is excellent at one thing — distributing a fare to many sellers consistently — but it was never designed for merchandising. Ancillaries, branded fares, rich media and real-time personalization are awkward or impossible to express well in it, so flights ended up looking like an undifferentiated commodity in many sales channels.

Airlines wanted to close that gap and own more of the customer relationship. NDC is the standard that lets them do it: present differentiated, dynamically priced offers directly, show what makes one fare better than another, and merchandise extras at the point of sale — the things every other retail industry takes for granted.

How NDC works: offer and order

NDC reframes a booking around two ideas: the Offer and the Order. Rather than assembling a fare from filed data, the airline itself constructs and prices an offer in real time when a seller shops; once the traveller accepts, that offer becomes an order the airline manages end to end. (The companion IATA initiative ONE Order extends this by replacing the separate PNR, e-ticket and EMD records with a single order.)

In practice a seller moves through a short sequence of NDC messages, and the airline’s offer engine does the heavy lifting:

1. Shop. The seller sends an AirShopping request describing the trip.
2. Offer. The airline returns live, priced offers — fares plus ancillaries and branding — and can re-price a selected offer (OfferPrice) to confirm it.
3. Order. The seller places the order (OrderCreate); changes, servicing and fulfilment then happen against that order.

Sellers reach this content in one of three ways: connecting to an airline’s NDC API directly, through a GDS that has built NDC capability, or through a travel API aggregator that integrates many airlines’ NDC feeds at once.

NDC vs the GDS and EDIFACT

This is where most confusion lives, so it is worth being precise. NDC is a standard; the GDS is a channel; EDIFACT is the legacy messaging that channel has traditionally used. NDC does not replace the GDS — Amadeus, Sabre and Travelport have all built NDC capability and can carry NDC offers alongside classic EDIFACT fares. For a fuller channel comparison, see travel API vs GDS.

Benefits of NDC

NDC shifts value to both ends of the pipe — the airline that creates the offer and the seller that presents it.

For airlines

• Merchandising and control. Airlines build and brand their own offers, differentiate fares, and sell ancillaries instead of distributing a commodity.
• Dynamic pricing. Offers can be constructed and priced in real time, rather than relying solely on pre-filed fares.
• A direct customer relationship and, often, lower distribution costs than traditional channels.

For sellers and OTAs

• Richer content — branded fares, bundles, seats, bags and other ancillaries — to merchandise like a modern retailer.
• NDC-exclusive fares and offers that some airlines make available only through NDC channels.
• Better product clarity for travellers, which tends to lift conversion and reduce post-booking surprises.

The challenges of NDC

NDC is powerful, but adopting it directly is genuinely hard, and it is fair to be clear-eyed about why:

• Fragmentation. NDC is a standard, but each airline implements it slightly differently, so “NDC” in practice means many subtly different connections.
• Multiple schema versions. Several NDC schema versions are in active use at once, and keeping up with them is ongoing work.
• Servicing complexity. Changes, refunds and exchanges under the order model differ from the familiar PNR/EMD workflow and from one airline to the next.
• Uneven adoption. Coverage varies by carrier and market, so NDC rarely replaces your other content sources — it sits alongside them.

NDC gives you what the airline actually wants to sell. The GDS gives you broad, consistent reach. Most platforms want both — which is exactly the problem an aggregator solves. — Industry framing of modern airline distribution

How a travel API makes NDC usable

Because NDC is fragmented across airlines and schema versions, integrating it carrier by carrier is a large, ongoing engineering commitment. A travel API aggregator absorbs that work: Tripgic connects to airline NDC offers, blends them with traditional GDS fares and low-cost carriers, and returns everything through one normalized REST API. Your platform gets NDC’s rich, dynamic content — branded fares, ancillaries and live offers — without parsing multiple NDC versions or maintaining a separate connection per airline. Connect once and reach modern and legacy airline content side by side.

Frequently asked questions

Tripgic Team

Travel Technology & Distribution

The Tripgic editorial team writes about travel APIs, airline distribution and booking technology. Tripgic operates a single travel API that connects OTAs, corporate travel platforms and travel startups to flights, hotels, cars and activities.

LinkedIn More articles