IATA ONE Order explained: what replaces the PNR and the e-ticket

ONE Order is IATA’s programme to replace the passenger name record (PNR), the electronic ticket and the electronic miscellaneous document (EMD) with a single order record that describes everything a customer bought and how each item is being delivered. If NDC changes how airline products are sold, ONE Order changes how they are recorded, fulfilled and accounted for.

The problem with three records

Today a single trip can be spread across several records. The PNR holds the itinerary and passenger data. The e-ticket represents the right to travel and the money paid for it. EMDs represent ancillaries such as bags or seats. These records are linked, but they live in different places and follow standards designed decades ago.

That fragmentation creates real cost: reconciliation between systems, complex rules for revalidation and reissue, and difficulty selling anything that does not fit the ticket concept, such as a bundle combining a flight with a hotel night or a rail segment.

What a ONE Order record contains

Conceptually, an order is simple:

• Order items — what was bought: flight services, seats, bags, lounge access, or non-air products.
• Passengers and contacts — who the items are for.
• Payments — what was paid, how, and against which items.
• Fulfilment state — whether each service has been delivered, used, changed or refunded.

The airline owns the order and is the source of truth. Sellers and partners interact with it through standard messages instead of each holding their own copy of a PNR.

Why airlines want it

Airlines want to behave more like retailers: offer products dynamically, bundle them, and change them without the constraints of ticket and coupon logic. A single order makes it simpler to:

• sell and service non-traditional products,
• reduce reconciliation between reservation, ticketing and accounting,
• give every channel the same, current view of what the customer owns.

A transition measured in years

Moving the industry off tickets is a long process. Airport systems, interline and codeshare partners, revenue accounting, settlement and agency back offices all depend on ticket numbers. Airlines adopting order-based processing will run hybrid models for a long time, issuing “order-based” records internally while still producing tickets where partners require them.

For a travel platform, that means two worlds coexist, and your system must not assume either one is universal.

How to prepare your platform

The most practical preparation is in the data model, not in new connectors:

1. Model bookings as orders. An internal order with items, passengers, payments and states maps naturally onto both PNR-based and order-based suppliers.
2. Keep supplier documents as attributes. Ticket numbers, EMD numbers and airline order IDs are references attached to order items, not the primary key of your booking.
3. Track fulfilment per item. A bag can be refunded while the flight is used. Item-level state avoids “the whole booking is cancelled or not” logic.
4. Separate money from inventory. Payments, refunds and adjustments should be their own ledger linked to items, which also simplifies back-office automation.
5. Version supplier capabilities. Record what each airline supports for change, cancel and refund so the UI can route customers correctly.

What it means beyond airlines

The order concept is not unique to air. Hotel, rail and tour suppliers already work with order-like confirmations. A platform built on a channel-neutral order model can combine products from different suppliers into one customer trip, which is where much of the commercial opportunity in modern travel retailing sits.

The takeaway

ONE Order is less about a new API and more about a new definition of “the booking”. Platforms that stop treating the PNR and the ticket as their core objects, and adopt an order with items and states, will find the industry’s transition far less disruptive.