The GDS terminal is fifteen percent of the channel

Sabre booked 12 million hotel reservations last quarter, 8% more than a year earlier. Almost none of it happened on the screen hoteliers picture when they hear the word GDS.

by Markus Busch

Start with the picture. Ask a hotelier what the GDS is and you get a room with a terminal in it. An advisor typing something cryptic, client on the line, pulling up your property. You know the channel by its rituals: the fam trip you hosted in spring, the preferred listing, the standing amenity, the consortia contract you signed in March.

All of it real. All of it fifteen percent.

The correction. Amadeus's own data puts around 15% of GDS bookings on a terminal. The rest arrive through connections — and that does not mean nobody is there. The agent didn't leave. Her screen did. She books your hotel from the tool her agency installed, or the corporate platform her client's travel policy runs on, and every one of those sits on a GDS connection rather than a green screen. Travelport reports the same shift on its side of the market: most of what it handles now arrives through a connection rather than someone typing.

And the channel is not dying. This gets lost, because the word legacy has been stuck to the GDS for a decade. Sabre booked 12 million hotel reservations in the second quarter, up 8% on the same quarter last year. Sabre publishes that figure and Amadeus publishes none, so read it as one operator rather than the whole market. But an operator selling more hotel rooms every quarter is not a dying pipe.

What happened this year. All three of them started wiring the eighty-five into AI. In June Travelport opened a platform that lets agencies, startups and AI tools reach its flights and hotels. Sabre has spent the year recruiting outside developers to build on it. On September 3 Amadeus said it is putting its content and its connections inside Claude Code, so that software can be assembled against them in plain language.

Where they differ is the way in. Until July, anyone building travel software could reach Amadeus content without asking permission, hotels included. On July 17 Amadeus shut that route; what is left is granted on request. Seven weeks later it named the replacement, and the replacement is not a portal you visit. It sits inside Claude Code, which is where a great deal of software now gets written. The documentation, the sign-in and the connection arrive in the place the work is already happening.

That is Amadeus following the people who build. It opens with flights and destinations. Hotels are not in the first release.

Travelport said it in June. Sabre has said it all year. Amadeus said it this month. The channel the industry wrote off as legacy now calls itself infrastructure for AI, three times over, inside a single season.

What that leaves you with. Not a different set of rates. Your BAR and your negotiated rates travel the same pipes as everything else and reach the same people. The booker working inside a corporate tool sees what you loaded for that account exactly as someone at a terminal would, because what you loaded is a rate code, not a screen.

What changes is what has to be true before anyone sees it. At a terminal your rate is read the way you loaded it. Everywhere else software fetches it and builds the screen first, and software does not work around a room type nobody mapped or a rate loaded where it can't be booked. It returns what it finds, and where it finds nothing there is no weaker listing to fall back on.

Enjoying this analysis? Hospitality.today delivers daily insights on hotel distribution, AI trends, and travel commerce — straight to your inbox. Subscribe for free at Hospitality.today →