What a global distribution system (GDS) is

This definition is written by the team behind GTOS, the Global Travel Operating System from Voraal, and is built on operating experience across 100,000+ trips. A buyer-oriented comparison is in NDC vs GDS and the guide NDC vs GDS for corporate travel. We do not claim certification on any GDS, and we do not publish a list of live connections.

What a GDS is for

For decades, a GDS has been the default way many desks reach airline inventory, with a shared workflow for pricing, booking and after-sales messages. Programme managers still meet it because a large share of corporate itineraries still travel on that path, and because many advisers are trained on it. That familiarity is a genuine operating fact. It is not an argument that every fare a company needs will always be there, or that a GDS is the only honest path.

A booking created on a GDS still has to land somewhere the organisation can govern. Policy, approval, duty of care and spend do not live “in the GDS” as a corporate record. They live in the travel operating system or TMC platform that holds the trip. If the fare never reaches that record, the programme will treat the GDS as a side channel, and unofficial or unapproved travel will be hard to see.

GDS and mid-office are not the same

Mid-office quality, change and queue work sits on the file a content path produced. A GDS can be that path. So can an NDC connection, a hotel source, or a desk booking recorded by hand. The mid-office question is whether an operations person can complete or amend the trip without starting a second file. The GDS question is whether that particular content path is available for the itinerary in front of the adviser. Mixing the two questions leads to the wrong software brief: teams buy a content access story when they needed a record, or they buy a record and assume content will appear without a scoped conversation.

GTOS is not a GDS. The GDS integration and GDS mid-office pages describe the intended relationship: a fare or segment that arrives along a GDS path should still sit on the GTOS trip record, in Control Tower and in the client view. Whether a given connection is in place, and how messages flow, is discussed in a demo. It is not asserted here as a badge.

How programmes actually mix paths

Most mature programmes already mix content. Some fares are still most reliably reached through a GDS. Some airline offers are reached through NDC. Hotel and car inventory may arrive on yet another path. The operating standard does not change with the path: the selected offer has to become a trip the organisation can approve, change and report. A demo that only shows a GDS screen has shown a content path. A demo that shows the same booking under policy, in an approval chain, and later as spend, has shown the record.

Buyers should also resist a false choice. “We are a GDS house” or “we are an NDC house” is a supply posture. It is not a programme design. The design is managed travel on one file, with content sourced in the ways the itinerary actually requires.

Language to use in a buying conversation

Say “GDS” when you mean the distribution path. Say “mid-office” when you mean operations on the file. Say “trip record” when you mean the system of record for the company or the TMC. If a vendor uses the three interchangeably, ask them to walk one itinerary from search to a changed invoice and name, at each step, which system is doing the work. That walkthrough is more useful than any slogan about networks.