Airline systems explained: PSS, CRS, GDS, OMS and DCS
A first-principles guide to the airline systems behind booking and travel, and what each one actually does.
First: separate what a system does from who sells it
A passenger sees one booking. Behind the scenes, commercial and operational systems maintain different records and fulfil different responsibilities. A single supplier can provide several functions, and one airline can combine systems from many suppliers.
PSS — Passenger Service System
The broad system family often covering reservations, inventory and ticketing, with links to other passenger service functions. Its boundaries depend on the particular airline architecture.
See booking records →CRS — Computer Reservation System
Supports creating, reading and modifying bookings. “CRS” and “reservation host” may be used differently between teams, so always clarify the actual capability.
Understand PNRs →GDS — Global Distribution System
Connects travel agencies and other sellers with airline shopping, reservation and servicing processes. It is a distribution platform, not necessarily the airline's inventory system.
Map distribution →OMS — Order Management System
Manages the lifecycle of Orders in Order-centric retailing. An airline may use an OMS alongside legacy PSS records during a gradual transition.
Explore coexistence →DCS — Departure Control System
Supports passenger check-in, airport processing, boarding and departure-related operations. It integrates with commercial records but does not normally price the itinerary.
See the journey →Payments, accounting and settlement
Payment services process authorization and collection; accounting and settlement coordinate financial records and reconciliation. These are connected, not interchangeable.
Advanced payment guide →Example: the booking exists, but check-in fails
A traveller changes their flight. The booking channel shows the updated itinerary, but the airport check-in workflow cannot locate the expected entitlement. That does not automatically mean the booking is missing. The reservation, ticket or Order, downstream flight data and DCS may have different states.
A practical investigator traces the identifier and state at each boundary: What changed in the booking or Order? Was ticketing or fulfilment updated? What was sent to the departure-control interface? What did the receiving system acknowledge? The right next step depends on which system owns the missing information.
Three pairs that newcomers confuse
GDS versus PSS: the GDS provides seller-facing distribution capabilities; the PSS is an airline-side core system family. They exchange data but serve different purposes.
PSS versus DCS: reservations and ticketing are commercial functions; departure control is concerned with passenger and aircraft departure processing. Implementations can share technology but the responsibilities remain conceptually distinct.
OMS versus PNR: an OMS manages an Order-centric lifecycle. A PNR is a reservation record used in traditional systems. During coexistence, one commercial journey may reference both.
At a glance
| System | Primary question | Not the same as |
|---|---|---|
| PSS | How are passenger services managed? | Agency distribution alone |
| GDS | How do travel sellers access airline content? | Airline inventory ownership |
| OMS | What is the customer's current Order state? | Every airport operational system |
| DCS | How is check-in and boarding processed? | The fare pricing engine |
Knowledge check: does a GDS necessarily control the airline's seat inventory?
No. A GDS may access or display availability while airline inventory functions control the underlying saleability rules.
Original industry references
The definitions are grounded in original industry materials. System boundaries vary by carrier, supplier and architecture.