How to prepare a ONE Order implementation roadmap
Transition should be organised around use cases and order-lifecycle capabilities rather than an abstract date for replacing the PNR. A roadmap built around a deadline instead of a capability tends to slip the deadline anyway.
Written for: Airline ecommerce, distribution, digital product, revenue, technology and customer experience leaders.

Transition should be organised around use cases and order-lifecycle capabilities rather than an abstract date for replacing the PNR.
The business problem behind the topic
ONE Order affects sales, fulfilment, delivery, revenue accounting, airport, partners and customer care. A purely technical roadmap underestimates processes, data, coexistence and organisational readiness. In service businesses, the decision does not end when a customer clicks “buy”: the digital promise must connect with operations, service delivery, data and profitability. This is why the topic should be treated as a business decision rather than an isolated marketing or technology enhancement.
The dimensions that need to be resolved
A sound approach combines four dimensions. Reviewing them separately helps expose friction; managing them as a system allows the direct channel to grow without transferring complexity to customers or the organization.
1. Business case and scope
Define the problems to solve: servicing, reconciliation, partnerships, customer view or time to market. The standard creates no value without a concrete case. Validation should be segmented by market, route, device, travel mission and passenger type. Network averages can hide very specific offer or experience problems.
2. Target order model
Specify states, services, ownership, source of truth and relationships with Offers, payments, delivery and accounting. The decision should translate into offers, pricing, content, terms and a recognisable reason to book direct. Passengers need to perceive value before starting checkout.
3. Coexistence architecture
Design synchronisation with PSS, PNR, tickets, EMDs, GDS and partners during a potentially long hybrid period. Dependencies across the PSS, IBE, Offer and Order, payments, CRM, airport processes and servicing should be mapped. A local improvement can fail when it crosses the rest of the journey.
4. Operating model and readiness
Adapt support, airport, finance, disruption, reporting and operations. Human capability is as critical as APIs. Governance should connect ecommerce, revenue, distribution, product, technology and operations through shared economic metrics. Otherwise, each function pushes the problem to the next stage.
A practical roadmap
Sequence matters. Starting with a tool or a feature list usually creates an expensive project that is difficult to govern. The following roadmap forces the business decisions first and the implementation second.
1. Assess Offer and Order maturity. Review standards, systems, processes and partners.
2. Choose a bounded use case. Prioritise a flow with value and controllable complexity.
3. Design lifecycle and coexistence. Model states, events, exceptions and reconciliation.
4. Pilot end to end. Include sales, changes, delivery, accounting and support.
5. Scale by product and partner. Expand coverage with gates, observability and rollback.
How to measure whether it works
A useful dashboard does not accumulate indicators: it connects behaviour, economics and execution. Metrics should be reviewed by segment, device, market and journey stage so that averages do not hide the actual problem.
Lifecycle coverage: The proportion of states and services managed through the order.
Manual reconciliation: Cases requiring intervention across booking, payment and accounting.
Servicing cycle time: Time and steps for changes, refunds or irregular operations.
Order integrity: Consistency of state and value across systems and partners.
Operational readiness: Teams, procedures and support prepared for production.
Common mistakes that reduce impact
Starting with a mass migration without a verifiable use case.
Ignoring accounting, airport or customer care until the end.
Treating coexistence as an unmanaged temporary exception.
Measuring success by messages processed instead of processes improved.
The warning sign is simple: if the project can be described only by the name of a platform, a campaign or a redesign, it is probably not yet sufficiently connected to the business outcome.
Conclusion
ONE Order is a transformation of the order operating model. A sound roadmap starts with value and lifecycle, tests the complete system and scales through controlled coexistence.
Consumer Services Hub helps airlines connect commercial strategy, booking experience, distribution and technology to grow the direct channel.
Consumer Services Hub - Strategic ecommerce consultancy for B2C service companies

Written by
Rodrigo Maroto
Founder of Consumer Services Hub. Consultant and strategist with 15+ years of experience in ecommerce, digital product management, and consumer services.
View LinkedIn profileGrow airline direct revenue
We audit booking funnels, ancillaries and retailing capabilities end to end.
Talk to usWhether you're launching a new digital channel, optimizing an existing one, or unlocking the next stage of growth — we're ready to help.
Related articles

NDC, ONE Order and PNR: differences and how they relate
PNR is a legacy booking record, NDC standardises the exchange of Offers and Orders, and ONE Order modernises fulfilment around a single order. Confusing these three slows down every conversation about what the airline is actually trying to build.

How ONE Order will impact airline ecommerce
ONE Order will change how airlines manage bookings, payments and service. Understanding its impact on ecommerce is critical before migration starts.

Is your airline ready for the ONE Order revolution?
The ONE Order revolution is coming and airlines must prepare now. This readiness assessment helps you understand where your airline really stands.




