The Origins and Scale of the Big Three Networks
The modern Global Distribution System is one of humanity's most resilient computing achievements. In the late 1950s, American Airlines partnered with IBM to develop SABRE (Semi-Automated Business Research Environment) running on vacuum-tube mainframes. In Europe, Air France, Iberia, Lufthansa, and SAS joined forces in 1987 to build Amadeus, while another airline alliance developed Galileo (now part of Travelport along with Worldspan and Apollo).
Today, these three entities—Amadeus (headquartered in Madrid/Nice), Sabre (Southlake, Texas), and Travelport (Langley, UK)—process trillions of dollars in gross booking volume annually, maintaining uptime guarantees exceeding 99.99% across global multi-datacenter clusters.
PNR Lifecycle: Creation, Commit, and Teletype Synchronization
When an agent or an OTA booking engine reserves a flight, the GDS builds an in-memory transactional structure known as a Passenger Name Record (PNR). To transition from a temporary workspace to a committed reservation, the PNR must conform to strict IATA Resolution 722 standards.
Once the mandatory fields are populated, the agent enters the commit command (in Sabre: 'E' for End Transaction; in Amadeus: 'ET'). At this millisecond, the GDS assigns a 6-character Record Locator and dispatches a Type A EDIFACT segment sell message directly to the operating airline's Passenger Service System (PSS).
If the operating carrier acknowledges seat allocation, it returns a second Record Locator (the Carrier PNR). The travel agent's GDS record now contains both locators, establishing a distributed state across two physically independent mainframes.
| Action Description | Sabre Cryptic Command | Amadeus Cryptic Command | Modern REST/JSON API Endpoint |
|---|---|---|---|
| Flight Availability Search | 124OCTJFKLHR | AN24OCTJFKLHR | POST /v2/shopping/flight-offers |
| Display Seat Map | B*7 | SM7 | GET /v1/shopping/seatmaps?flightOfferId=... |
| Add Passenger Name | -SMITH/JOHN MR | NM1SMITH/JOHN MR | Included in POST /v1/booking/flight-orders body |
| Commit PNR Reservation | E or ER | ET or ETK | POST /v1/booking/flight-orders (Atomic execution) |
| Issue Electronic Ticket | WÂ¥TKT | TTP | POST /v1/booking/flight-orders/{id}/issuance |
Fare Construction and the ATPCO Pricing Engine
GDS search engines do not merely match flight numbers; they execute multi-variable combinatorial math. To determine if an itinerary can be ticketed, the GDS evaluates tariffs filed by airlines with ATPCO (Airline Tariff Publishing Company).
ATPCO defines Category rules (such as CAT-01 Eligibility, CAT-08 Stopover limits, CAT-10 Combinability, and CAT-16 Penalties & Refunds). A single round-trip query can trigger tens of thousands of permutation checks within fractions of a second to discover the lowest combinable fare basis code.
