What Is a GDS? Complete Guide for New Travel Agents

If you're brand new to the travel industry, "GDS" is one of the first acronyms you'll run into — and one that's rarely explained clearly. This guide breaks down what a GDS actually is, why it exists, and why it still matters even as the industry shifts toward newer standards like NDC.

What Does GDS Stand For?

GDS stands for Global Distribution System. It's a computer network that acts as a middleman between travel agents and travel suppliers — airlines, hotels, car rental companies — collecting their inventory, schedules, and fares, and making them searchable and bookable through one interface.

Why Does a GDS Exist?

Before GDS platforms existed, booking a flight meant calling an airline directly or checking printed schedules. Each airline had its own reservation system, and there was no easy way for a travel agent to compare options across multiple carriers. The first computerized system — Sabre — was built by American Airlines and IBM in the 1960s specifically to solve this. Over time, more systems emerged, eventually consolidating into the major GDS platforms used today.

The Three Major GDS Platforms

For a deeper comparison of these three, see our Amadeus vs Sabre vs Galileo guide.

What a GDS Actually Lets You Do

• Search real-time flight availability across many airlines at once
• Compare fares and booking classes side by side
• Create and manage a PNR for a passenger's full itinerary
• Issue tickets and handle changes, cancellations, and refunds
• Access hotel and car rental inventory in addition to flights

"Green Screen" vs GUI — Two Ways to Use a GDS

Every GDS has two interface options:

• The "green screen" (cryptic command interface) — the original text-based interface where agents type commands and read raw PNR output. This is what produces the cryptic text covered throughout our other guides.
• The GUI (graphical interface) — modern point-and-click versions like Sabre Red 360 or Amadeus Selling Platform Connect, designed to be more approachable for newer agents.

Do You Always Need a GDS?

Not necessarily. If you're a leisure travel agent booking primarily through supplier portals or package deals, you may never need direct GDS access. GDS access becomes more important for:

• Corporate travel management, where complex multi-airline itineraries are common
• Agencies needing broad, real-time airline inventory across many carriers
• Agents who need fare comparison across the full market rather than a handful of preferred suppliers

GDS vs CRS — A Common Point of Confusion

A Central Reservation System (CRS) is an individual airline's own internal booking system — it's been around even longer than GDS platforms, dating back to systems built by individual carriers in the 1940s-50s. A GDS sits on top of, and aggregates, many different CRS systems so agents don't need a separate login for every airline.

Beyond Flights: Hotels and Cars Inside the Same PNR

Flight segments get most of the attention, but a GDS PNR can hold hotel and car rental segments too, sitting alongside the air segments in the same record. A hotel segment typically carries the property, room type, rate, and check-in/check-out dates; a car segment carries the rental location, vehicle class, and pickup/drop-off dates. Bundling these into one PNR means an agent can build and manage a passenger's entire trip — flights, a hotel stay, and a rental car — from a single record rather than juggling separate confirmation numbers across different systems, and it's one of the practical reasons agencies handling complex, multi-component trips still lean on a GDS rather than piecing bookings together from separate supplier websites.

How GDS Relates to NDC

NDC (New Distribution Capability) is a newer IATA standard that's gradually changing how airlines distribute content — sometimes routing around GDS platforms entirely. This doesn't make GDS obsolete; most major GDS providers have added NDC support rather than being replaced by it. For the full picture, read our guide to NDC.

How a Booking Actually Moves Through a GDS

It helps to see the mechanics behind the scenes. When an agent builds a booking in the cryptic interface, they're really assembling a PNR one element at a time, in a fairly consistent sequence across platforms. A simplified Amadeus-style build might look like this:

AN15JULLHRJFK // availability display: LHR-JFK on 15 Jul
SS1 BA284 H15JULLHRJFK1 // sell 1 seat, flight BA284, class H
NM1SMITH/JOHN MR // add passenger name element
AP LON 020 7946 0123 // add contact/phone element
TK TL15JUL/1800 // set ticketing time limit
ER // end and retrieve — save the PNR

Every one of those lines corresponds to a required "element" the GDS demands before it will let you save a PNR — at minimum a name, a segment, a contact, and a ticketing arrangement. Sabre and Galileo/Travelport use different entry syntax for the same steps (Sabre typically starts a similar sell with a numbered availability line and a 0-prefixed sell entry, for instance), but the underlying sequence — search, sell, name, contact, ticket, save — is essentially universal across GDS platforms because it mirrors how a PNR itself is structured.

Who Pays for GDS Access, and How

A GDS isn't free to use — it just isn't usually the traveller who pays directly. GDS platforms typically charge participating airlines a fee for every segment booked through their system, which is a major reason airlines have pushed NDC as an alternative distribution channel with different economics. On the agency side, access to a GDS terminal is usually arranged through a host agency or a direct commercial agreement, often bundled with training, support, and sometimes segment-based incentives for booking volume.

This fee structure is part of why GDS platforms invest heavily in keeping airlines' content current and comprehensive — the airline relationship is a core part of the business model, not an afterthought.

When Things Go Wrong: Common GDS Troubleshooting Scenarios

New agents run into a handful of recurring GDS headaches. Knowing the likely cause before panicking saves time:

• A segment shows UN or UC after appearing to book successfully. This usually means the airline could not honor the request after all — often because availability closed between the search and the sell. The fix is almost always to re-search and rebook, not to assume the original entry will eventually clear on its own.
• A duplicate PNR gets created for the same passenger. This typically happens when a booking is restarted from scratch instead of retrieved and edited, or when two agents work the same request independently. Most GDS platforms run duplicate-checking logic, but it isn't foolproof across every scenario, so it's worth searching for an existing PNR by name before building a new one.
• An expected queue message never shows up. Before assuming an airline simply didn't respond, check that the PNR wasn't accidentally queued to the wrong office, or that queue routing wasn't affected by an agency configuration change.
• Fare pricing returns unexpectedly different numbers. Repricing entries like FXP in Amadeus, WPNCB in Sabre, or FXP in Galileo can return a different fare than expected if availability shifted, a fare basis expired, or a passenger type code was entered incorrectly — always re-verify segment status and passenger details before assuming the pricing engine is wrong.

Learning a GDS: What Training Actually Involves

Most formal travel agent training programs — whether through a host agency, a community college travel program, or vendor-run certification courses — dedicate a meaningful chunk of curriculum specifically to cryptic command entry, because it remains the fastest and most reliable way to handle non-standard bookings, even for agents who use a GUI day to day. Typical training progression covers availability and sell entries first, then PNR elements (name, contact, ticketing), then fare pricing and ticketing entries, and finally queue management and basic troubleshooting.

Because the three major GDS families use different command syntax for equivalent actions, agencies that work across multiple platforms often budget extra onboarding time for agents who are certified on one system and need to cross-train on another — the concepts transfer quickly, but the exact keystrokes don't.