Saudia's Retailing Position: A Consumption Problem, Not a Capability Gap

The conventional read on Saudia's retailing programme is that it is a mid-table Gulf carrier catching up with its neighbours. That read is wrong, and the evidence for why is sitting on Saudia's own website.

Saudia's NDC API runs schema version 21.3 as preferred, with 18.1 retained for compatibility. Its order servicing coverage is broad and real: reshop and pay, reshop and pay later, reprice unpaid orders, void, refund, split order, order lists, change notifications, and both exchange and refund after involuntary disruption. In July 2025 it became one of the first carriers in the world to convert its entire PNR and e-ticket estate into Order records. On raw capability, Saudia is not behind its Gulf peers.

The problem is that almost none of it is consumable.

What Saudia Actually Has

Saudia publishes a functionality matrix on its NDC support pages — effectively a self-declared equivalent of an IATA Airline Retailing Maturity submission. It is more candid than most carriers' equivalents, and it repays close reading.

On the credit side: instant and deferred payment, shop and price for services and seats, full post-booking servicing, GDPR-compliant order splitting, and a set of capabilities explicitly flagged as 21.3-only — order changes for travel documents, contacts and frequent flyer details; waiver codes in exchange; seller remuneration; waitlist. That is a carrier operating a current schema in production, not a carrier running a pilot.

On the debit side, the constraint is payment.

A carrier that cannot accept card payment through NDC has a hard ceiling on which sellers can transact with it, irrespective of how good the Order layer beneath is. Everything downstream — the 21.3 capability set, the servicing breadth, the deferred payment support — is gated by that single line. ARC's absence closes the United States separately.

And one entry settles a question the market has been guessing at. Saudia describes its air and ancillary dynamic pricing as rule-based. Rule-based pricing is not dynamic pricing in the sense the vendor announcements implied, and it is several steps short of continuous pricing. The Order record exists. The intelligence that should populate it does not yet.

The Servicing Policy Nobody Is Discussing

Buried in the same support pages is a sentence with more commercial consequence than anything else Saudia publishes about NDC: once an NDC order is taken over by the airline's sales support team, it is no longer accessible to the agent and is managed exclusively by Saudia from that point forward.

Set that alongside what must leave the channel entirely — ticket revalidation and reissue, schedule change handling, no-show handling, EMD exchanges, and any conversion between NDC and EDIFACT.

The agent's calculation is then straightforward. A meaningful class of servicing events, several of them entirely routine, permanently transfers the booking relationship to the airline. An agency evaluating whether to build against Saudia NDC is being asked to accept that some proportion of its bookings will be taken away from it mid-lifecycle.

The premise of ONE Order is that a single record travels with the customer and every party servicing it works on the same object. A hand-off that extinguishes seller access reintroduces exactly the fragmentation the standard was designed to remove.

It is also, of everything in this assessment, the cheapest thing to fix. It requires no platform work at all. It is a policy decision.

Several Rules Engines, Not One Offer Engine

Saudia's commercial architecture has quietly consolidated over the past year, and the direction is positive. The standalone NDC portal that ran on a third-party gateway from 2016 no longer resolves, and that vendor now appears nowhere on Saudia's partner-facing pages. Four NDC partners are named: Amadeus, Sabre, Travelport and NuFlights. Neither party announced a separation, so this should be read as inference — but a decade-long platform partner, present through two certifications, absent from every current page, is a strong signal.

Separately, Saudia's travel agency programme runs on a specialist SaaS platform covering agency management, a commissions hub, contract and incentive management, and a business rules engine for commission and promotion logic. That is a sensible choice; agency incentive administration is a specialist problem and few airlines should build it themselves.

But naming the layers together produces the finding. Saudia's commercial logic now sits across at least three rules-based systems: fare and offer construction upstream in the legacy stack, order handling in the new platform, and agency remuneration policy in the agency management system. Each is individually reasonable. Together they describe a carrier whose commercial intelligence lives in several rules engines rather than one offer engine.

That is precisely the condition that produces rule-based rather than dynamic pricing. It is an explanation, not merely an observation.

There is a specific adjacency worth watching. NDC 21.3 supports seller remuneration and commission disclosure inside the offer itself, and Saudia marks seller remuneration as covered. Whether in-offer remuneration and the separately managed incentive programme constitute one commercial policy or two systems requiring reconciliation is not visible from outside. For an agency partner, that distinction determines whether the commission shown in the offer is the commission eventually received.

Where Saudia Stands in the Gulf

The Gulf hosts the most concentrated modern retailing contest anywhere in the world: five full-service carriers with overlapping networks, comparable capital access and near-identical strategic mandates, all rebuilding commercial architecture simultaneously.

Three of them publish itemised, version-stamped, live-flagged capability sets on IATA's Airline Retailing Maturity index — the industry's only independent capability register. A prospective partner can verify them in ninety seconds.

Saudia is not listed. Asked directly in its own FAQ whether it appears on the ARM index, the airline states that it is working towards inclusion. That confirms both the absence and the intent.

The honest summary is that Saudia is a credible second or third in the region on capability, first on Order operationalisation, and last on the ability to prove any of it. Its preferred schema sits above Qatar's confirmed-live position and well above Etihad's, though Emirates is running newer. Against Etihad it is comfortably ahead on almost every dimension — a claim the market does not currently make, because Saudia has no register entry with which to make it.

The Codeshare That Renders the Position

In September 2026 the industry saw its first live codeshare between an Offer-and-Order carrier and a legacy PSS carrier. The parties were Riyadh Air and Saudia.

Riyadh Air includes Saudia-operated segments directly inside its NDC shopping offers. A translation layer converts Saudia's standard messages into the order and reflects order changes back into the systems Saudia has run for decades. Booking and ticketing stay synchronised; servicing works in both directions.

It is a genuine technical achievement and both carriers benefit. But the asymmetry runs one way. Riyadh Air can retail Saudia inventory inside a modern, dynamically priced order. Saudia cannot reciprocate. The translation layer sits on Riyadh Air's side of the boundary, and so does the commercial flexibility it unlocks.

Two carriers, one integration, and a competitive position rendered in miniature. The incumbent's inventory is being retailed inside the challenger's architecture.

The Practical Takeaway

Saudia's problem in the market is not that it can do less than Emirates. It is that a partner cannot find out what Saudia can do. That is a different problem with a different, cheaper set of remedies — and it should be sequenced ahead of anything architectural.

Four moves, in order of return per unit of effort:

• Complete card acceptance and 3DS v2. Both are already in progress. Completing them converts a large volume of already-built capability from theoretical to transactable, and unblocks the seller segments that cannot work on cash and BSP. Adding ARC reporting opens the United States. Neither is a transformation programme.
• Register on the ARM index. Already intended per Saudia's own FAQ. It converts a self-published table into independently validated capability, in the one place partners actually check.
• Publish the schema version and build the developer tooling. "The latest version of our NDC API" is not something an aggregator can scope against. Sandbox, negative test cases, documentation and onboarding are exactly what the ARM setup group measures, and where the listed carriers each hold eleven validated entries.
• Revise the order hand-off policy. No platform work required. It currently gives every prospective agency partner a reason not to build.

Beyond those, the offer engine is the real programme. Rule-based pricing caps what can be offered just as surely as cash-and-BSP caps who can transact. Dynamic pricing, continuous pricing, bundling, personalisation and machine-readable distribution to AI assistants all wait on it.

But an offer engine is table stakes. Any carrier can buy one. The differentiated question is what feeds it — and here Saudia holds an asset none of its competitors can purchase. A loyalty programme with dozens of partners across banking, hospitality, telecoms and retail, in a market where loyalty is being repositioned nationally as an economic instrument rather than a frequent-flyer mechanic, and now, since July 2025, a unified order record that finally makes member-level purchase history coherent across a journey.

What is missing is the wiring. IATA's capability framework tracks this explicitly — personalising offers based on passenger type, loyalty programmes or other agreements — and both Emirates and Qatar have it validated as live. Saudia has the deeper loyalty estate and is not yet using it that way.

That matters disproportionately given who Saudia now competes with. The digitally native challenger has the better platform. It does not have four decades of member data, dozens of earn partners, or an incumbent relationship with the Kingdom's diaspora and pilgrimage traffic. The asymmetry that favours the incumbent is recognition — knowing who this guest is, what they are worth, and what they will accept.

The window in which an Order head start reads as a lead rather than a stranded asset is measured in quarters, not years. It closes not because the technology is difficult, but because a competitor with none of the constraints is already retailing the incumbent's inventory inside its own orders. Payment, proof and policy are the near-term work. Loyalty into the offer layer is the work that would make Saudia genuinely hard to compete with.