Every travel agent who's spent real time on a GDS has hit the same handful of frustrations. This guide lists the most common ones honestly, plus what actually helps with each — including where a few of these problems disappear entirely once you stop working with raw GDS output by hand.
1. The Learning Curve Is Genuinely Steep
The cryptic command interface ("green screen") that underlies every major GDS is not designed to be intuitive — it was built for 1960s-70s computing constraints, not modern usability. New agents often need weeks of training before they're comfortable reading and entering commands confidently, and many host agencies don't offer GDS training at all, assuming agents will pick it up elsewhere.
What helps: Structured GDS-specific training (many host agencies and IATA-affiliated programs offer this), and starting with pattern recognition — once you understand the segment-line structure, most of the "language" becomes far more readable.
2. Reading and Interpreting Raw PNR Output
Even experienced agents find that manually decoding a dense, multi-segment PNR — translating airport codes, calculating real flight durations across time zones, identifying status codes — is slow and error-prone, especially under time pressure with a client waiting.
What helps: A converter tool that handles the decoding automatically. This is specifically the kind of repetitive, error-prone task that's straightforward to automate reliably — see our free PNR converter guide.
3. Interface Inconsistency Across GDS Platforms
If your agency works with more than one GDS — common when handling diverse, multi-region itineraries — you're effectively learning multiple "languages." Amadeus, Sabre, and Travelport each have their own command syntax, formatting quirks, and conventions, and switching between them regularly causes real friction.
What helps: Tools that auto-detect and normalize output across different GDS formats reduce how often you need to context-switch mentally between systems.
4. Time Zone and Duration Errors
A subtle but very common mistake: assuming a flight's "duration" is simply arrival time minus departure time. Since PNRs show local times at each airport, this raw subtraction is wrong for any international route — sometimes wildly wrong. A flight that looks like it takes 11 hours might actually be a 7-hour flight once you correct for the time zone difference.
Quoting an incorrect flight duration to a client — even by a couple of hours — erodes trust fast, especially for time-sensitive connections. Always verify duration calculations account for time zones, including daylight saving time shifts on routes touching the UK, EU, North America, or Australia during their respective DST seasons.
5. Manual Itinerary Formatting for Clients
Clients don't want to see raw GDS text — but manually reformatting every booking into a clean, readable itinerary (airport names, proper times, layover calculations) for every single client takes real time, especially for multi-segment trips.
What helps: This is exactly the gap tools like PNRGenius fill — paste the raw PNR, get a formatted itinerary instantly, no manual reformatting per booking.
6. Keeping Up With NDC and Distribution Changes
As covered in our NDC guide, the distribution landscape is shifting, and not every agent's tools or training have kept pace. This creates a newer category of frustration: content gaps where certain fares or ancillaries simply aren't visible through traditional GDS queries anymore.
The Pattern Across All of These
Most of these challenges share a common thread: they're rooted in systems built decades ago, retrofitted repeatedly rather than redesigned, and still requiring a human to bridge the gap between cryptic machine-formatted output and what an actual client needs to see. Automating that translation step — wherever it's genuinely possible — tends to be the highest-leverage fix.
Stop Decoding PNRs Manually
PNRGenius handles airport codes, time zones, layovers, and formatting automatically — free, no signup.
Try the Free Converter →