1. Introduction and Historical Context of Airline Distribution
For over four decades, commercial aviation distribution relied almost exclusively on the EDIFACT (Electronic Data Interchange for Administration, Commerce and Transport) protocol. Developed under IATA and UN standards in the late 20th century, EDIFACT enabled global connectivity between airlines and Global Distribution Systems (Amadeus, Sabre, Travelport).
While EDIFACT provided unprecedented global reach, its static 160-character message structures restricted product presentation to standardized elements: 26 discrete Booking Reservation Designators (RBD letters A through Z), basic 2-letter fare rules, and disconnected external tariff filings through ATPCO (Airline Tariff Publishing Company) and schedule feeds via OAG or Cirium. The emergence of airline unbundling (ancillaries such as baggage, seat selection, and priority boarding) and dynamic continuous pricing rendered EDIFACT structurally insufficient for modern retailing.
To bridge this architectural divide, IATA launched the New Distribution Capability (NDC) standard (Resolution 787 and XML/JSON-based Open Air schema). NDC transforms airline distribution from a decentralized static cache query into an airline-controlled dynamic shopping environment.
2. Technical Comparison: EDIFACT vs NDC Architecture
Understanding the fundamental architectural shift is essential for travel consultants, revenue managers, and distribution specialists:
• Pricing & Content Control: Under EDIFACT, GDS engines independently calculate prices using static fares and rules filed by airlines at ATPCO, matching them against inventory seats broadcast by airline Departure Control and Inventory systems. Under NDC, the GDS or aggregator sends an XML request directly to the airline's Offer & Order Management System (OOMS). The airline builds, prices, and controls the offer in real-time.
• Message Protocol: EDIFACT utilizes rigid, compressed syntax strings (such as UN/EDIFACT PAREQ, PRICER, or RESREQ). NDC utilizes modern, extensible XML and REST/JSON APIs, facilitating rich content transmission including images, seat pitch dimensions, meal descriptions, and tailored bundle combinations.
• Product Personalization: EDIFACT queries are largely anonymous; every agency querying a route sees identical published public fare classes regardless of the corporate account or loyalty profile. NDC enables authenticated retailing: when a frequent flyer number or Corporate ID is transmitted in the shopping request, the airline dynamically constructs tailored offers (e.g., complimentary lounge access, bundled checked baggage, or corporate negotiated discount rates).
• Inventory Granularity: EDIFACT is constrained to 26 static alphabetical booking classes (RBDs). NDC allows continuous pricing, letting airlines vary price points in minute dollar increments without needing a dedicated letter code.
3. Order Management: From PNR/ETKT/EMD to ONE Order
Under legacy distribution, an agency booking consists of three independent documents created across separate databases:
• The PNR (Passenger Name Record): Contains itinerary, passenger names, and contact details stored in the GDS.
• The E-Ticket (Electronic Ticket / VCR): A 13-digit accounting document holding flight coupons managed by the ticketing airline or clearing house.
• The EMD (Electronic Miscellaneous Document): Standalone documents (EMD-A or EMD-S) issued separately to track ancillary purchases (baggage, meals, Wi-Fi).
NDC forms the foundational retail layer for IATA's broader ONE Order vision. ONE Order replaces the fragmented PNR, E-Ticket, and EMD triad with a single, unified Order Record, identified by a unique alphanumeric Order ID. Every flight segment, lounge pass, seat reservation, and ancillary item exists as an interrelated Order Item within the airline's single source of truth.
4. Servicing Workflows and Agency Operational Challenges
While NDC expands retailing capabilities, it transforms operational agency servicing workflows:
• Involuntary Changes and Schedule Disruptions: In EDIFACT, travel agents retain significant autonomy to reissue tickets, alter routing within airline category 16/31 rules, or revalidate coupons. In NDC, the agency must initiate an Order Change service call to the airline API. The airline's automated decision engine returns permissible rebooking alternatives, which the agent accepts to update the Order directly.
• Voluntary Changes and Refunds: In legacy workflows, agents process refunds through GDS GDS automated refund tools or manual cat-33 calculations. In NDC, agents transmit an `OrderQuote` request for cancellation; the airline engine computes the exact cancellation penalty according to dynamic contract rules and returns an `OrderCancel` response containing the residual refund value.
• Commercial Surcharges: Major airline groups (such as Lufthansa Group, Air France-KLM, British Airways, and American Airlines) enforce EDIFACT Distribution Cost Charges (DCC) or GDS surcharges per coupon, while reserving lowest promotional price points, seat amenities, and flexible corporate bundles exclusively for NDC and direct API connections.
5. Worked Comparison Matrix
| Operational Dimension | Legacy EDIFACT Protocol | Modern NDC (IATA Open Air Standard) |
| :--- | :--- | :--- |
| Pricing Engine Location | GDS / Third-party pricing engine based on ATPCO data | Airline's internal Offer & Order Management System |
| Booking Construct | PNR + 13-Digit E-Ticket + EMDs | Single unified Order ID (ONE Order concept) |
| Fare Filing & RBDs | 26 Alphabetical RBD Letters (A-Z) | Continuous Pricing / Dynamic real-time offer generation |
| Rich Content & Merchandising | Very limited; requires external tools or text notes | Native XML/JSON: images, detailed specs, ancillary bundles |
| Servicing Autonomy | Agent-driven via standard GDS mask entries | API-driven via structured airline Order servicing calls |
| Distribution Surcharges | Subject to airline EDIFACT GDS surcharges | Surcharge-free on most major carriers; lowest fares included |
6. Aviation Industry Professional Q&A Pack
• Question: Why are major network carriers investing heavily in NDC while imposing surcharges on EDIFACT?
Answer: EDIFACT costs airlines substantial GDS booking fees while limiting their ability to merchandise premium products, personalized bundles, and dynamic continuous pricing. NDC transfers offer creation back to the carrier, eliminates third-party caching constraints, lowers overall distribution expense, and increases ancillary revenue through direct retailing.
• Question: How does Continuous Pricing differ between EDIFACT and NDC?
Answer: In EDIFACT, fares must be filed at ATPCO and tied to one of 26 booking classes (RBDs). If class 'Q' is $300 and the next available class 'M' is $450, an EDIFACT customer must pay $450 once 'Q' sells out. In NDC, the airline engine can price the seat dynamically at any intermediate value (e.g., $342 or $378) based on real-time willingness to pay, without requiring a pre-filed ATPCO tariff letter.
• Question: What happens to agency back-office accounting systems when transitioning to NDC?
Answer: Legacy mid- and back-office systems rely on standard Daily Booking Files (AIR, IUR, or MIR files) parsed from PNR and E-ticket numbers. To handle NDC, agencies must either integrate GDS-agnostic aggregator APIs that generate normalized financial data streams, or update back-office accounting platforms to ingest XML/JSON Order Records directly for automated settlement and reporting.
Key takeaways
• EDIFACT relies on third-party pricing from ATPCO and static 26-letter RBDs, whereas NDC relies on real-time Offer and Order engines managed directly by airlines.
• NDC replaces the disconnected PNR, E-Ticket, and EMD structures with a single, unified Order Record under the IATA ONE Order framework.
• Continuous pricing in NDC allows airlines to quote real-time price points without the pricing jumps inherent in traditional booking classes.
• Travel agencies must adapt their servicing workflows, accounting integrations, and queue monitoring to support API-driven Order management.