Skip to content
Blog

GDS systems for travel agents: what the contract decides

Tekravel Editorial
Written with the help of AI

The agency sells flights the way many small agencies do. Fares come from a consolidator's portal, quotes go out on WhatsApp, and the consolidator issues the ticket once the customer has paid. It works. Then a supplier rep visits, or a former colleague who now runs a bigger office says it over coffee: a real agency has its own GDS. The owner goes home, searches "which GDS is best for travel agents", and spends an evening comparing screenshots of fare displays.

That comparison is the wrong place to start. GDS systems for travel agents differ in their screens, but what decides whether one pays for your office is written in the contract and in your own operation: who issues the ticket, what you are committing to, who will sit at the terminal, and where the booking goes after it is made. Two agencies can sign with the same GDS on the same day and have opposite outcomes.

What a GDS gives an agency, and what it does not

A GDS is a booking channel. Through it, trained staff search airline inventory, hold seats in a PNR, price the itinerary against the fare rules, and see schedules and availability the way the trade has seen them for decades. For an agency that does complex itineraries, group bookings or a lot of changes, that working screen is genuinely useful. A good agent on a terminal is fast.

What the subscription does not give you is the list that surprises people:

  • Ticketing authority. Making a booking and issuing a ticket are separate permissions. Issuing in your own name means accreditation and the settlement obligations that come with it. Without that, a consolidator or host agency still issues, and you are back to the arrangement you had, with one more contract on top.
  • Credit with airlines. The GDS does not lend you money or extend you a limit. Whoever issues carries the settlement, and sets its terms with you.
  • A website. A terminal is for your staff. Your customers do not see it, and nothing on it turns into a page they can book from.
  • Markups, customers and reports. The booking lives in the GDS. Getting it into your invoices, your customer records and your monthly numbers is a mid-office or back-office job, usually done by other software or by hand.

If the reason for wanting a GDS is "we want to look like a real agency", this list is worth reading twice. Most of what makes an agency look real to a customer sits outside the terminal.

Questions that decide the cost, before anyone shows you a screen

Every GDS can search, book and price. A demo will prove that and nothing else. Take these questions to the provider's rep instead, and get the answers in writing:

  1. Who issues the ticket? Your own accreditation, or a consolidator you already work with? If it is the consolidator, will they accept bookings made in your GDS office, and on what terms?
  2. What volume are you committing to? Many agency contracts are tied to booking volume. Ask what the commitment is, how it is measured, and exactly what happens in a quiet month.
  3. Who will work the terminal? Name the person. Ask how they are trained, how long before they are productive, and what happens to your bookings when that person is on leave or resigns.
  4. Where do bookings go next? How does a PNR become an invoice, a customer record and a line in your monthly report? If the answer is "your staff re-type it", count that time.
  5. Is your content there? If your customers mostly fly carriers that sell outside the traditional channel, or book hotels and packages more than flights, check that the GDS shows what they actually buy.
  6. What does leaving cost? Notice period, early termination, what happens to your PNR history. You are more likely to switch later than you think today.

Notice that "which GDS is best" does not appear. Once these six are answered for two providers, the comparison usually makes itself, and the screens become a minor point.

The NDC question belongs in the fifth item, and it has its own article: what NDC changed and what it did not covers it for the people integrating it. If you have never held your own ticketing authority, how a non-IATA agency gets a ticket issued explains the arrangement you are already in, and why it may not need replacing.

Four ways to sell flights, side by side

A GDS contract is one answer to "how should we sell flights". It is not the only one, and for some offices it is not the best. Here are the four shapes small agencies actually run.

GDS with own ticketingGDS, consolidator issuesConsolidator's B2B portalBranded booking site on supplier content
Who issues the ticketYouThe consolidatorThe consolidatorDepends on the supplier arrangement behind the site
What you signGDS contract plus accreditation and its obligationsGDS contract plus the consolidator's termsThe consolidator's termsThe platform's terms; supplier access as agreed
Who must be trainedTerminal staff and ticketing staffTerminal staffAnyone who can use a websiteYour staff on an admin panel; customers book themselves
What your customer seesNothing; you quote by messageNothing; you quote by messageNothing; you quote by messageA booking site under your brand
Markups, customers, reportsSeparate software or spreadsheetsSeparate software or spreadsheetsWhatever the portal offersIn the site's own admin
Cost of changing courseHighest: two sets of obligationsThe GDS contract's exit termsLowLow to moderate

Some readers will disagree with the last row, and they should check it against their own contracts. The point of the table is that the four columns answer different problems. A GDS answers "my staff need a faster, deeper booking screen". A branded site answers "my customers should be able to book without messaging me". An agency that has the second problem and buys the first solution will be disappointed by a perfectly good GDS.

On this platform, flight and hotel content reaches an agency through supplier groups, each service is switched on per agency, and every agency gets its own admin panel with bookings, customers, markups and reports. A branded storefront can be started from the signup wizard without a card. If you want your own systems or a partner's to book through it instead, the platform's flight and hotel APIs are opened by a conversation, not a self-serve key; see what the travel APIs cover before deciding where your bookings should start.

What choosing on screens costs

The failures are not dramatic. They are slow.

An agency signs for a volume it reaches in its best months and misses in the others, and the shortfall becomes a line on an invoice that nobody budgeted for. One employee learns the terminal; when they leave, the bookings they made are hard for anyone else to service, and the next hire needs training before they are useful. PNRs pile up in the GDS while the accounts are still built from WhatsApp screenshots, so the month's numbers never match. And after all of it, the agency still has no website, because the GDS was never going to provide one.

None of this means a GDS is a mistake. For an office with accredited ticketing, steady volume and staff who live on the terminal, it is the right tool. It means the decision is made by the six questions above, not by which fare display looks clearest in a demo.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.