What Is NDC? A Practical Guide to Modern Airline Distribution

What Is NDC? A Practical Guide to Modern Airline Distribution

The way travellers search for and purchase flights continues to evolve. Customers increasingly expect clear product information, relevant choices and the ability to add services such as baggage and seats during the booking journey.

Airlines also want greater flexibility in how they create, present and distribute their products across direct and indirect sales channels.

New Distribution Capability, commonly known as NDC, was introduced to support this evolution in airline retailing. However, NDC is often described using technical terminology that can make its practical role difficult to understand.

This guide explains what NDC is, why it was introduced, how an NDC transaction works and what travel sellers should evaluate before adopting it.

What is NDC?

NDC stands for New Distribution Capability.

It is a travel industry-supported programme launched by the International Air Transport Association, or IATA, for the development and adoption of an XML-based data-transmission standard.

In practical terms, NDC provides a standardised method for airlines and travel sellers to exchange shopping, pricing, booking and servicing information through APIs.

The standard supports interactions across different stages of the airline retailing lifecycle, including:

• Searching for flights and available products
• Receiving airline-generated offers
• Confirming and pricing selected offers
• Creating an order
• Processing supported payments
• Adding seats, baggage and other services
• Retrieving and servicing an existing order
• Changing or cancelling an order
• Processing eligible refunds

NDC is not a consumer-facing booking website or a complete reservation system. It is a communication standard that participating airlines, travel sellers, aggregators and technology providers can implement within their respective systems.

The standard is open to airlines, intermediaries, technology providers and other industry participants. Its use is not limited to IATA members.

Why was NDC introduced?

Traditional airline distribution has commonly represented flight products using schedules, availability, booking classes, fares and fare rules.

These processes have supported global travel distribution for many years. However, a fare, booking class and flight schedule may not always communicate the complete value of an airline product.

Two offers for the same route may differ in several ways, including:

• Checked and cabin baggage allowances
• Seat-selection options
• Change and cancellation conditions
• Meals or onboard services
• Lounge access
• Priority services
• Fare flexibility
• Bundled ancillary products

When these attributes are not clearly available during shopping, customers may find it difficult to understand why one offer differs from another.

NDC was developed to support a more retail-oriented exchange of information. Depending on the airline and its implementation, travel sellers may receive more detailed product descriptions, ancillary options, branded fares and airline-created offers.

The objective is not merely to introduce another API. It is to improve how airline products can be created, distributed, compared, purchased and serviced.

How does an NDC transaction work?

Although technical workflows and supported capabilities vary by airline, an NDC booking journey generally includes several connected stages.

Shopping

The travel seller sends a shopping request containing information such as:

• Origin and destination
• Departure and return dates
• Passenger types
• Number of travellers
• Cabin preference
• Preferred airline, where applicable
• Direct-flight preference or other search criteria

The airline or its authorised technology provider processes the request and returns the available offers.

An offer may include the itinerary, price, fare conditions, baggage allowance, included services and available ancillary products. The level of information returned depends on the airline’s implementation.

Offer confirmation and pricing

After the customer selects an option, the offer may need to be confirmed or priced again before booking.

This step allows the airline to verify that the selected itinerary remains available and that the price and conditions are still valid.

NDC offers may have expiry periods. Travel sellers must therefore manage offer identifiers and time limits carefully. A previously returned offer should not be assumed to remain available indefinitely.

If the price or availability changes, the application should communicate the change clearly and allow the customer to review it before continuing.

Order creation

Once an offer has been selected and the required passenger information has been collected, the travel seller sends an order-creation request.

If the request is successful, the airline creates an order containing the confirmed flight products and services.

The airline response normally includes identifiers that must be retained for later transactions. These references may be required when retrieving, paying for, fulfilling, changing or cancelling the order.

Applications should store the complete response securely rather than relying only on the information displayed to the customer.

Payment and fulfilment

Payment and fulfilment processes vary between airlines, markets and commercial arrangements.

Payment information may be supplied during order creation or through a separate transaction. The supported forms of payment can also depend on the travel seller’s agreement with the airline or technology provider.

A successful order response should be checked carefully. The creation of an order does not always mean that every payment or fulfilment process has been completed.

Travel sellers should distinguish between confirmed, pending, partially completed and failed states. If the result of a transaction is uncertain, the application should retrieve the order status before attempting the request again.

This helps reduce the risk of duplicate orders or payments.

Order servicing

After a booking has been created, supported NDC workflows may allow the travel seller to:

• Retrieve the order
• Add baggage or seats
• Add other ancillary services
• Change an itinerary
• Cancel an order
• Request an eligible refund

Servicing capabilities vary considerably between airlines. An airline may support shopping and order creation while offering only limited post-booking servicing through its NDC connection.

Travel sellers should therefore evaluate the entire lifecycle rather than considering booking functionality alone.

What can NDC change for travel sellers?

NDC can give travel sellers access to offers created by participating airlines.

Depending on the airline connection, these offers may contain:

• Branded fares and fare families
• Detailed baggage information
• Seat-selection options
• Paid ancillary services
• Airline-specific bundles
• Promotional offers
• Product descriptions
• Fare attributes and restrictions
• Images or other rich content
• Airline-defined servicing options

This information can help travel businesses present flight options using schedule, price and product characteristics.

It may also help customers understand what is included before completing a purchase, reducing ambiguity during the booking process.

However, access to additional information does not automatically produce a better customer experience. The travel seller remains responsible for organising and presenting the information clearly within its website, application or booking platform.

What NDC does not guarantee

NDC should not be interpreted as a guarantee that every participating airline provides the same content, fares or functions.

NDC does not automatically guarantee:

• The lowest available fare
• Every product offered by an airline
• Personalised offers for every customer
• Identical workflows across airlines
• Complete post-booking servicing
• Every form of payment
• The same API version across all connections
• Replacement of every existing distribution channel

Each airline determines its commercial arrangements, supported markets, available content, technical implementation and servicing capabilities.

Airlines may also implement different versions of the standard or interpret certain workflows according to their own operational requirements.

For this reason, connecting to an NDC API requires more than sending and receiving standard messages. Applications must handle airline-specific behaviour, offer expirations, warnings, errors, timeouts and uncertain transaction states.

Direct airline connections and NDC aggregation

Travel sellers can access NDC content through direct airline integrations or an aggregation provider.

Direct connections

A direct connection establishes an integration between the travel seller and an individual airline.

This approach may provide close alignment with that airline’s technical and commercial requirements. However, every connection generally needs to be developed, tested, certified, monitored and maintained separately.

The operational effort can increase as more airlines are added.

NDC aggregation

An NDC aggregator connects with multiple participating airlines and provides access through a more consistent integration layer.

The aggregator may help standardise common shopping, pricing, order-creation and servicing processes while retaining airline-specific information where necessary.

Aggregation does not make every airline connection identical. Airlines continue to control their offers, business rules, supported features and servicing capabilities.

The value of aggregation lies in reducing unnecessary integration differences and providing a more manageable way to connect with and maintain multiple airline relationships.

The appropriate model depends on the travel seller’s airline priorities, expected transaction volumes, internal technical capacity, servicing needs and commercial arrangements.

What should travel sellers evaluate?

Before selecting an NDC connection or technology provider, travel businesses should look beyond the number of airlines displayed in a connectivity list.

Important questions include:

• Which airlines and markets are currently available?
• Is each connection live, certified or still under development?
• Which shopping and pricing functions are supported?
• Can bookings be created and fulfilled?
• Are seats, baggage and other services available?
• Which forms of payment are supported?
• Can existing orders be retrieved and serviced?
• Are changes, cancellations and refunds supported?
• How are offer expiry and price changes handled?
• How are warnings and partial successes communicated?
• What testing and certification support is provided?
• How are production incidents monitored and resolved?
• How are airline-specific differences documented?

The answers should be evaluated against the travel seller’s actual business model and customer journey.

Preparing an application for NDC

A successful implementation also requires careful application design.

Travel sellers should consider how their systems will:

• Store offer and order identifiers
• Retain complete API responses
• Protect passenger and payment information
• Manage offer-expiry periods
• Handle price or availability changes
• Prevent duplicate booking requests
• Recover from timeouts
• Confirm uncertain transaction results
• Display airline warnings and restrictions
• Support post-booking operations

Logging and monitoring are particularly important. Technical teams should be able to trace a transaction from the original shopping request through order creation, payment and servicing.

Testing should include unsuccessful scenarios as well as successful bookings. Examples include expired offers, unavailable seats, payment failures, duplicate requests and partially completed transactions.

How Pratra supports airline connectivity

Pratra provides airline connectivity technology that helps travel agencies, online travel businesses and travel technology platforms access supported airline content through a unified integration.

Instead of developing and maintaining a separate customer-facing connection for every participating airline, travel sellers can use Pratra’s connectivity layer to support common shopping, pricing, booking, fulfilment and servicing workflows.

Travel businesses retain control of their website, application and customer experience, while Pratra manages the underlying connectivity with supported airline systems.

The content and functionality available through each connection remain subject to the airline, market, commercial agreement and implementation status. Travel sellers should therefore evaluate individual airline capabilities across the complete booking and servicing lifecycle.

Frequently asked questions

Is NDC an API?

NDC is a data-exchange standard commonly implemented through APIs. An individual airline’s NDC API uses the standard alongside that airline’s technical and commercial requirements.

Is NDC the same as an aggregator?

No. NDC is a standard for exchanging airline retailing information. An aggregator is a technology provider that connects with multiple airlines and makes supported content available through an integration layer.

Does NDC replace the GDS?

Not automatically. NDC can operate alongside existing distribution channels. The channels used by a travel business depend on its airline requirements, commercial arrangements and operating model.

Does every airline support the same NDC features?

No. Available functions vary by airline, connection, market and agreement. Shopping and booking may be supported even when particular payment, ancillary or servicing functions are unavailable.

Is NDC relevant only to large travel agencies?

No. NDC may be relevant to online travel agencies, travel management companies, corporate booking platforms, tour operators, consolidators and other travel technology businesses.

Each organisation should evaluate the business case based on its airline content requirements, customer experience and technical capabilities.

Moving from connectivity to effective airline retailing

NDC provides a modern framework for exchanging airline offers and orders. Its practical value depends on the quality of each airline implementation, the functionality available and the way the resulting information is presented and serviced by the travel seller.

A successful NDC strategy should therefore consider the complete customer journey—from the initial flight search through booking, payment and post-booking support.

For travel businesses evaluating NDC, the most useful question is not simply whether a connection is available. It is whether that connection provides the airline content, operational reliability and servicing capabilities required by the business and its customers.