Middleware is not the most exciting subject in aviation. Nobody puts it on a conference keynote slide. Yet it is the piece that decides whether an airline can actually retail the way it says it wants to, or whether it stays waiting on a vendor's roadmap for every new idea.
Understanding why starts with understanding what middleware actually does.
What middleware actually is
An airline's technology stack breaks into three parts. The front end is everything the customer touches: the website, the mobile app, and increasingly the agentic layer, where AI agents shop and book on the traveller's behalf. The back end holds the core services, often bought from providers: flight shopping and inventory, pricing, payment, order management. In between sits the middleware.
Middleware is the layer that connects the two. It takes the raw services coming from the back end and orchestrates them into something coherent. A single booking might block inventory through one provider, take payment through another, trigger fulfilment somewhere else, then send the confirmation email from a fourth system, which is the most complex of these flows to get right. Check-in is another: the middleware updates the departure control system, issues the boarding pass, sends the email and generates the passes for Apple Wallet and Google Wallet. The customer sees one smooth transaction. The middleware is what makes those separate services behave as one.
That orchestration role is significant. Without it, an airline is either exposing raw vendor services directly to its channels, which is hard to change and slides into vendor lock-in, or buying the front end and middleware as a single package from one vendor, which sharply limits the experience it can deliver.
Why the topic is surfacing now
Two forces are pushing middleware up the agenda.
The first is the move to Offer and Order. As airlines plan the shift away from the passenger service system toward an order-based world, the middleware plays two roles at once. It surfaces the new capabilities, the ancillaries, dynamic products and richer content that an order-native platform can deliver, to the channels customers actually use. And it acts as the bridge during transition, letting an airline run its current PNR-based setup and its new order-based capabilities side by side, a coexistence architecture rather than a single risky cutover. Only 27% of airlines have begun Offer and Order transformation programmes despite 72% recognising their importance, and the middleware question is one of the first things that separates the airlines doing it from the airlines talking about it.
The second force is control. Airlines want to own the experience they present to customers, across web, mobile and conversational channels, because that experience is how they differentiate. You can buy a retail front end or a mobile app off the shelf, but if every airline runs the same boxed product, none of them stands out. The moment an airline decides it wants to build something distinctive, it needs a place to build it, and that place is the middleware.
Control also shows up in timelines. With an out-of-the-box solution, adding a new ancillary or surfacing a new capability means requesting a new development from the vendor, with the cost and timeline that come with it, and only if the vendor agrees to build it at all. When the middleware belongs to the airline, the airline controls the timeline. That single shift, from waiting on a roadmap to owning one, is the practical meaning of independence.
What good middleware architecture looks like
The published work with Virgin Australia is the clearest public example of the principles that make a middleware layer worth building.
The first is separation of concerns. In a well-layered design, a change to an external API should only affect the lowest layer of the stack, leaving the core business logic untouched. When a vendor delivers a new service, or an airline switches providers, only a few services inside the middleware need adjusting, without affecting the whole ecosystem. That is what turns a vendor change from a multi-month project into a contained one.
The second is building for extensibility. New channels, new capabilities and new back-end systems should slot in without disrupting what already runs. As standards and technology keep moving, the airline integrates the new pieces with minimal rework rather than facing a rebuild each time.
The third is abstracting backend complexity. A mobile app should be able to request a seat map and receive it in a consistent format, regardless of whether the data comes from a legacy PSS, a modern NDC or order-based provider, or several sources at once. The channel does not need to know or care where the data came from. That abstraction is what keeps the customer experience consistent while everything behind it changes.
Put together, these principles describe a layer that is PSS agnostic, ready for the order-based world, and built to absorb change rather than resist it. It holds a shifting set of airline system integrations behind a front end that stays stable. As Virgin Australia put it, the aim was "a foundation that should allow us to adapt quickly as industry standards evolve."
What this means for airlines planning their next move
Building an independent middleware layer does not mean rebuilding everything at once. The path to an order-based future runs through a series of deliberate steps.
If middleware is treated as an afterthought, it can cause recurring problems down the line. When a vendor timeline blocks a launch, or when a promised new product needs six months of integration work across four disconnected systems. The airlines that treat it as the foundation give themselves room to move at their own pace.
Middleware will never be the exciting part of the story. It is the part that lets the exciting parts happen.
To explore how Branchspace helps airlines design the architecture behind modern retailing, visit our consulting services, or read how we designed Virgin Australia's middleware.
Related reading: Airline Offer Management: The Engine Behind Personalised Retailing
