An airline booking system is the commerce stack (search, pricing, seat hold, and ticket issuance) a carrier and its distribution partners use to sell flights, connecting the storefront to the airline reservation system for PNR creation and ticketing.
Where the ARS is the airline’s system of record, the booking system is the flow that gets a passenger from a fare display to a paid ticket. It includes shopping (schedule and availability), pricing (fare rules, taxes, ancillaries), reservation (PNR creation), and issuance (ticket plus payment). Retail and B2B channels (airline.com, mobile app, OTA connections via GDS or NDC) all sit on top. When a support agent handles a duplicate booking or a fare mismatch, they trace the failure back through this chain.
Support desks see the booking system indirectly, through failed bookings, price mismatches, and payment declines. A travel-native help desk links each ticket to the booking record via reference lookup, so an agent responding to a “my card was charged twice” ticket can see the actual booking attempt (not a re-typed summary) and process the refund correctly.
Common questions
What is the difference between an airline booking system and an ARS?
The booking system is the sales flow (search, price, book, pay); the ARS is the system of record that holds the PNR and inventory. In practice the two are tightly coupled and often sold together.
Do OTAs use the airline’s booking system directly?
OTAs usually connect via a GDS or via NDC APIs. Either way, the final PNR sits in the airline’s ARS, so the OTA’s confirmation and the airline’s record must reconcile.