Common Challenges Travel Agents Face With GDS Systems

Every travel agent who has spent real time on a GDS has hit the same handful of frustrations. This guide lists them honestly, with what actually helps for each. Some are about the systems themselves. Others come from the gap between what a GDS stores and what a client needs to see. A few disappear almost entirely once you stop handling raw GDS output by hand.

1. The Learning Curve Is Genuinely Steep

The cryptic command interface ("green screen") under every major GDS was designed for the computing constraints of the 1960s and 70s, not for ease of use. New agents often need weeks before they enter commands confidently, and many host agencies assume agents will pick up GDS skills elsewhere.

What helps: Structured training, if your agency or host offers it, and a deliberate order of learning. Start with reading a PNR before you build one. Once you can see the segment-line pattern (airline, flight, class, date, route, status, times), most of the "language" is readable. Then learn six entries: availability, sell, name, retrieve, end and cancel. Our command cheat sheet lays them out for Amadeus, Sabre and Galileo, and the Sabre Red 360 guide covers how graphical screens and commands fit together.

2. Reading and Interpreting Raw PNR Output

Even experienced agents find that decoding a dense, multi-segment PNR (translating airport codes, spotting overnight arrivals, reading status codes) is slow and error-prone when a client is waiting. The mistakes are rarely dramatic. A HL read as "probably fine". A date rollover missed because the arrival shows only a time. A segment left on the wrong passenger.

What helps: A checklist for every PNR you read before you reply: names spelled as on the passport, every segment status confirmed, dates and days of the week plausible, contact and ticketing fields present. The status code reference covers the codes, and a converter can do the mechanical decoding so your attention goes to checking. See our free PNR converter guide.

3. Interface Inconsistency Across GDS Platforms

If your agency uses more than one GDS (common with multi-region itineraries, or after a host agency change), you are effectively working in several languages. Amadeus uses NM1 for a name, Sabre uses a hyphen, Galileo uses N.. Ending a transaction is ET in one system and E in another. The risk is not that you can't do it. It's that muscle memory from one system quietly produces an error message, or worse, a different action, in another.

What helps: Keep one system as your home base and learn the others by mapping them to it, rather than trying to hold all three equally. Tools that auto-detect and normalise output across formats also reduce how often you switch mentally between systems.

4. Time Zone and Duration Errors

A subtle and very common mistake: assuming a flight's duration is simply arrival time minus departure time. A PNR shows local times at each airport, so that subtraction is wrong for any route that crosses time zones.

For illustration, take a flight departing London at 1000 and arriving New York at 1305 on the same day. Subtracting gives 3 hours 5 minutes. New York is normally five hours behind London, so 1305 in New York is 1805 in London, and the actual flight time is 8 hours 5 minutes.

What helps: Never hand-calculate durations on international itineraries. Use a tool that applies the correct offset for the actual date, and be especially careful with overnight arrivals (the +1 day marker) and tight connections where an hour matters.

5. Manual Itinerary Formatting for Clients

Clients do not want raw GDS text. But reformatting every booking into a readable itinerary, with airport names, proper times, layover calculations and baggage notes, takes real time, particularly on multi-segment trips, and it is where transcription errors creep in. A date mistyped while reformatting is a client problem that did not exist in the PNR.

What helps: Paste the raw PNR into a converter and review the output against the PNR, rather than retyping it. Our guide on PNR vs itinerary explains what belongs in the client version and what should stay out.

6. Ticketing Time Limits That Quietly Expire

An unticketed booking is a promise with a deadline. Airlines set a ticketing time limit, and if the booking isn't ticketed in time they can cancel the segments, sometimes with no warning to the agent beyond the deadline itself. Missing one means a client who thinks they're booked and an agent re-selling a flight that may now cost more, or may be gone.

It can cost the agency too. One airline's published agency debit memo tariff, for example, lists "ticketing time limit violation" and "unticketed no-shows" among its charge categories. Policies differ airline by airline, so read the ones for the carriers you sell most.

What helps: Treat the ticketing deadline as a diary entry the moment you create the booking, not something you'll "get to". Check the earliest deadline across all segments, since different airlines on one PNR can have different limits. Clear the booking from your working queue only when it is ticketed or cancelled.

7. Schedule Changes Nobody Tells You About

Airlines retime, re-route and cancel flights constantly, and how you find out is less standardised than most agents expect. ARC has noted that airlines are not required to use a standard GDS notification and that schedule-change notices often arrive as remarks in the booking, as an email, on a website bulletin or by phone. With no automation linked to your own booking records, finding the affected clients can mean searching by hand.

The same source separates a planned schedule change from an irregular operation: an involuntary change within 72 hours of departure is treated as an IROP, anything earlier as a planned schedule change. Once a passenger has checked in, you may no longer be able to manage the booking at all.

What helps: A routine. Work your schedule-change queue (your office's GDS queue setup will define which) at fixed times. For bookings departing within a week, re-check the itinerary yourself. If you save bookings with PNRGenius, schedule-change alerts on saved bookings can flag a retime so you aren't relying on a message arriving.

8. Agency Debit Memos and Booking Hygiene

Airlines can bill agencies through an agency debit memo (ADM) when they believe a booking or ticket broke their rules. The published reasons vary by carrier. One airline's tariff lists incorrect fares, taxes or fare basis, class abuse, name corrections, churning, hidden-city ticketing and throw-away ticketing among others, and notes that its list isn't exhaustive. The same airline's policy keeps ADM rights on NDC bookings for cases such as fare misapplication and failure to follow fare rules.

What helps: Read the ADM policy for each airline you sell regularly, since each publishes one. Book the class you intend to sell, don't hold speculative or duplicate bookings, and correct names through the airline's proper process rather than cancelling and rebooking. This is general guidance, not advice on any specific dispute. If you receive an ADM, check it against the airline's policy and your agency agreement, and ask your host agency or accreditation body how to dispute it.

9. Keeping Up With NDC and Distribution Changes

As covered in our NDC guide, distribution is shifting, and not every agent's tools or training have kept pace. This creates a newer kind of frustration: content that is simply missing from a traditional GDS search, or bookings that can be made but are harder to change.

The industry has also shown that the transition isn't smooth. American Airlines pulled fares from traditional GDS distribution in 2023, then reversed course in early June 2024 after agents and trade associations complained about difficulties with comparison shopping, changes and rebooking. Air France-KLM removed some short- and medium-haul "Light" fares from traditional GDS channels, leaving them NDC-only, according to trade press in 2024.

What helps: Ask your host agency or GDS which NDC airlines you can actually book and service, and test the servicing path (changes, cancellations, refunds) on a low-value booking before a client depends on it.

When a GDS Problem Lands on Your Desk

1. Redisplay the booking and read the raw PNR, not a summary.
2. Check statuses and dates on every segment, and the ticketing deadline.
3. Read the exact error text. It usually names the field that failed.
4. Rule out your office's rules (mandatory fields, queue settings) before blaming the GDS.
5. Escalate with the record locator to your GDS help desk or host agency, having noted what you typed and when.

The Pattern Across All of These

Most of these challenges share a root: systems built decades ago, retrofitted repeatedly rather than redesigned, still needing a human to bridge cryptic machine output and what a client needs. The agents who cope best aren't the ones who memorise the most commands. They have routines for deadlines, schedule changes and checking, and they automate the mechanical translation wherever they safely can.