When an airline sells a seat, it is not selling a product in the way a retailer sells a book. It is making a promise — a promise about a specific seat, on a specific aircraft, departing at a specific time, with specific services attached — that must be fulfilled across dozens of systems, multiple service providers, and an often unpredictable operational environment. Managing that promise is what order management is actually about.
What a PNR Was Never Designed to Do
The Passenger Name Record has been the core data structure of airline reservations for decades. It was designed to hold enough information to check a passenger in and seat them on a flight. What it was not designed to do is represent a complete, structured commercial transaction that can be modified, queried, and fulfilled in the way a modern order can.
A PNR holds a snapshot. A modern order is a living document. When an airline sells a seat and a meal and a bag and a lounge pass as a single bundled product, the PNR struggles to represent the relationships between those services, the conditions under which they can be changed or cancelled, and the downstream obligations each creates. The result is a series of workarounds: separate segments for ancillaries, remarks fields used as free-text data stores, and back-office systems that have to reverse-engineer what was actually sold by parsing PNR data through proprietary rules.
The Downstream Cascade Problem
Airline operations do not pause for retailing complexity. When a flight delays, cancels, or changes equipment, every ancillary attached to the affected passengers needs to be re-evaluated. A passenger who bought an exit row seat on a 737 might now be on an A320 with different exit row configurations. The meal they selected might not be catered on the replacement flight. The lounge access they purchased might be through a third-party provider who needs to be notified.
In a PNR-based system, managing this cascade requires manual intervention at each step. An agent has to identify what the passenger bought, determine what can be transferred and what needs to be refunded, communicate with each relevant service provider, and update the record. The passenger, meanwhile, is waiting at the airport wondering what has happened to their carefully assembled journey.
The Data Ownership Gap
A significant portion of airline tickets are sold through intermediaries — travel agents, OTAs, corporate booking tools — who hold the booking record in their own systems. The airline knows a reservation was made, but the detailed order data — what was bought, under what conditions, by whom — lives in the GDS or the agency's own system. When the passenger contacts the airline directly to modify their booking, the airline's systems may not have complete visibility into what they actually sold.
This data ownership gap makes personalized servicing nearly impossible. The airline cannot see the customer's full purchase history, cannot honor preferences that were set through the booking channel, and cannot proactively service the customer the way a true retailer would.
The Path Forward
Solving airline order management is not primarily a technology problem — it is a data model problem. Airlines need a single, authoritative record of what was sold, under what conditions, and what has been fulfilled or changed. That record needs to be accessible to every system that touches the passenger journey, from the booking engine to the airport to the call center.
The IATA ONE Order standard exists precisely to define that record. But like NDC, the standard is only as useful as the industry's collective willingness to adopt it and the technology to implement it properly.