· Airline Distribution · GenX eSolutions
New Distribution Capability has been discussed in the travel industry for over a decade, which has had the unfortunate effect of making it sound like something perpetually about to happen. It is happening now, and the practical consequences for agencies are more specific than the marketing suggests.
What NDC actually is
NDC is an XML messaging standard published by IATA that lets airlines distribute content directly to sellers, rather than exclusively through the traditional GDS fare-filing pipeline. The important word is content, not fares. The old pipeline was built to distribute a fare and a schedule. NDC distributes an offer — which can include seat selection, baggage, meals, lounge access and bundles, priced for a specific customer at a specific moment.
Why airlines pushed for it
Airlines spent years watching their product be reduced to a price and a departure time on a comparison screen. Ancillaries were where the margin moved, and the traditional pipeline could not express them well. NDC is the airlines' answer to that: a channel where they control the offer and can differentiate it.
For an agency, the honest summary is that NDC means more content, more complexity, and no reduction in the number of systems you need to talk to.
What it means for your booking engine
The awkward reality is that NDC does not replace anything. Agencies now need GDS content, LCC direct connections, consolidator fares and NDC offers — and a customer expects to see them in one result set, sorted sensibly.
That has three practical consequences:
- Offer caching becomes harder. An NDC offer is specific to a request and has an expiry. You cannot cache it the way a published fare could be cached, which puts real pressure on search performance.
- Servicing splits. A booking made through NDC is often serviced through NDC. If your mid-office assumes everything can be reissued through the GDS, that assumption will break.
- Comparison gets genuinely difficult. An NDC bundle with bags and a seat is not comparable with a bare published fare, and showing them side by side without normalisation actively misleads the customer.
What we would advise
Do not treat NDC as a migration. Treat it as an additional content source that your engine must normalise alongside the ones you already have. The agencies handling this well are the ones whose platform already treats content sources as pluggable — for them NDC is a new adapter. The ones struggling are those whose booking flow was written assuming GDS semantics throughout.