Book cover: Airline Systems Explained by Mathieu Montmessin

Order on Amazon

Published 10 November 2026. 161 pages, 6 x 9 in. Kindle, paperback and hardcover.

Airline Systems Explained is a 161-page book about the systems an airline rents and rarely understands: the passenger service system, the booking engine and the e-commerce stack, departure control, revenue management and pricing, revenue accounting, loyalty and disruption, the integration layer between them, the change from tickets to orders, the vendor landscape, what it all costs over ten years, the migration, right-sizing, and how to buy. It is the third book in the Travel Industry Explained series, was published on 10 November 2026, and ends with a thirty-item Airline Systems Buyer's Audit.

Why is choosing an airline system so hard?

One fact shapes the whole subject. An airline changes its core systems perhaps once every ten to fifteen years, so the people taking the decision have almost never taken it before, while the vendor's team across the table has done it fifty times. The contract outlasts the chief executive who approved it, and for a mid-sized carrier it costs more over its life than an aircraft.

A second fact makes it harder than it was for the previous generation of managers. The industry is changing generation in its core systems, from records built around the ticket to a single order. Airlines choosing today are choosing a generation as well as a vendor, and most will run both for years. The book explains both and the move between them.

What is a PSS, really?

People in airlines talk about the PSS the way people in a house talk about the boiler: one thing, in the basement, that somebody else understands. It is not one thing. Chapter 1 draws the map as seven families of systems, each holding one kind of truth, and chapter 2 takes the core apart: reservations, inventory, ticketing, fares and the customer profile.

The core is the hardest system to change not because the software is difficult, though it is, but because its records are shared. Hundreds of interfaces on a mid-sized airline assume something about the shape of the record on the other side, and some of the parties reading it, governments, airports and partner carriers, are not on your project plan.

What does an airline system really cost?

Chapter 11 builds the ten-year cost stack line by line: the per-passenger fee and its minimum, implementation, migration, integration, customisation at a day rate, training, hosting, support, upgrades, the airline's own team, and the cost of what the system cannot do, which never appears on an invoice and is often the largest line. A worked example compares three options for one airline.

My own feeling is that per-passenger pricing quietly favours volume, which is why chapter 13 argues that the biggest vendor's full suite is right for the biggest airlines and expensive for almost everyone else.

What changes with offers and orders?

Chapter 9 is the hinge of the book. It explains the two records, the ticket and the order, what offer, order, settle and deliver actually mean, how airlines really move from one generation to the other, and what it changes for the airline rather than for the standards body.

It is written for readers of the first two books as much as for IT people: every channel and every payment ends in a record inside a system, and that system decides more about what the airline can do than most commercial teams realise.

What is the Airline Systems Buyer's Audit?

Thirty scored items on your own systems, grouped by the chapters they come from: knowing what you run, the shop window and the money, sizing the decision, buying, contracting, and migrating. Maximum 60. In my experience an airline that has not run the exercise scores between 15 and 30, and one that has just finished a well-run core selection scores above 45.

The fillable PDF is free on this site and needs nothing else.

What is in the book

  1. What an Airline Runs On

    • Seven families
    • The core is the decision
    • Two generations
    • Five records, five questions
    • A composite scenario: one view of the customer
    • How to read the rest of this book
  2. The Passenger Service System

    • Reservations and inventory
    • Ticketing, fares and the profile
    • Why it is the hardest system to change
    • Two lineages
    • Hosted, and what is in the box
    • A composite scenario: one simple rule
    • Reading a PSS like a practitioner
  3. The Booking Engine and the E-commerce Stack

    • What the booking engine actually does
    • The app and the pieces around the engine
    • The core behind the screen
    • Three ways to own it
    • Where the low-cost carriers lead
    • A composite scenario: the capped conversion
    • Reading an e-commerce stack like a practitioner
  4. Departure Control and the Airport

    • From check-in to pushback
    • The messages that leave the airport
    • The tangle, and why outages are remembered
    • The buying question
    • The pressures on the old design
    • A composite scenario: four hours at the hub
    • The practitioner’s view
  5. Revenue Management and Pricing

    • What the revenue management engine does
    • Pricing, from filed fares to computed prices
    • Legs, networks and the policing function
    • A data problem before an algorithm problem
    • A composite scenario: the system that arrived before its data
    • The practitioner’s view
  6. Revenue Accounting

    • The coupon and its life
    • Sales audit
    • Proration and interline billing
    • Reconciliation, taxes and breakage
    • Orders, vendors and the money
    • A composite scenario: two percent in the tables
    • Reading revenue accounting like a practitioner
  7. Loyalty, Customer Data and Disruption

    • The loyalty platform
    • Customer data
    • The contact centre and the servicing tools
    • Disruption
    • What orders promise here
    • A composite scenario: the storm week, from the systems’ side
    • The practitioner’s view
  8. The Integration Layer

    • Four languages, three of them old
    • The inventory, partner by partner
    • What sits in the middle
    • Where budgets die
    • A composite scenario: the forty interfaces
    • Counting the interfaces like a practitioner
  9. From Tickets to Orders

    • Two records, or one
    • Offer, order, settle, deliver
    • How airlines actually move
    • What changes for the airline
    • The future fronts
    • A composite scenario: the list
    • The practitioner’s view
  10. The Vendor Landscape

    • The hosts and the low-cost platforms
    • The mid-sized cores and the new generation
    • The specialists and the outsourcers
    • The vendor economics
    • A composite scenario: three products, one shortlist
    • Reading a vendor’s positioning like a practitioner
  11. What It Really Costs

    • The cost lines over ten years
    • How per-passenger pricing favours volume
    • The hidden lines
    • Three options for one airline
    • Where the money really goes
    • A composite scenario: the CFO’s third year
    • Building your own cost stack
  12. The Migration

    • What moves
    • The cutover and the weeks around it
    • The failure modes, in order of frequency
    • What good programmes do differently
    • Bridging in place or a clean move
    • A composite scenario: the cutover weekend
    • The practitioner’s view
  13. Right-Sizing

    • What the big suite is built for
    • What a smaller carrier actually uses
    • The alternative is not cheap
    • When the big host is right anyway
    • Ten questions
    • A composite scenario: two carriers, five years on
    • The practitioner’s view
  14. How to Buy an Airline System

    • Requirements written around flows
    • The RFP, the demonstration and the reference call
    • Scoring what matters
    • The contract
    • Leverage, and the steering committee
    • A composite scenario: three identical answers
    • The practitioner’s checklist
    • What will not change

Plus: Glossary · Tips for Newcomers to Airline Systems · Appendix: The Airline Systems Buyer’s Audit · About the Author

Questions people ask

Do I need an IT background to read it?

No. It is written for the commercial, finance and operations people who sit on a steering committee for a systems decision as much as for IT. Every acronym is explained the first time it appears, and again in the glossary.

Does it name vendors?

Only where a reader would otherwise be lost, once and neutrally. Products change every year and the questions do not, so it is not a buyer's guide to any particular product.

Is it only about the passenger service system?

No. The PSS gets its own chapter, but so do the booking engine, departure control, revenue management, revenue accounting, loyalty and disruption, the integration layer, and the move from tickets to orders.

Is the Kindle edition the same content as the paperback?

Yes, the same text and the same audit. The paperback is 161 pages.

What is the Buyer's Audit, and do I have to buy the book to use it?

Thirty scored items on your own systems, grouped by chapter, with result bands and a score card. The fillable PDF is free on this site and needs nothing else.

Related reading

Share LinkedIn ↗ X ↗ Reddit ↗ Facebook ↗