The corporate booking tool found your hotel. An AI decided which version to show.

Your biggest corporate account books you most weeks. Someone inside their travel program opens a tool, types your city, and your property comes up with a price beside it.

You have never seen that screen.

You know the rate you loaded. You know the room type you mapped it to, the access code that unlocks it, the override you pay the agency every month. What happens between the rate leaving your system and the traveler clicking a button is somebody else's software, and it has been getting busier.

The shelf your rate lands on

Amadeus publishes the numbers itself. Its hotel platform for travel sellers carries "more than 120,000 hotels worldwide" of what the company calls reliable, commissionable content. That is the GDS inventory — yours among it, if you are connected. The same platform carries "over 2 million properties."

The difference comes from Amadeus Value Hotels, "over 750,000 properties available at competitive net rates," direct agreements with hotel partners, and what Amadeus describes as content from its global and regional aggregator partners. Eleven or more aggregators for business travel alone. All of it, in the company's own phrase, in one booking flow.

Do the arithmetic on your own position in that. The channel you loaded your corporate rate into accounts for roughly six percent of what the seller can put on screen.

SAP's numbers land in the same place from the other direction. The old Concur Travel showed around 650,000 hotels through the GDS. The new one shows up to six million accommodation options.

Neither company is hiding any of this. Both sell it as choice, and for the corporation buying travel, it is choice.

Your account picked a pipe, and nobody told you

Read SAP's own documentation for how that choice gets made and one sentence stops you.

"Only one single source of hotel content per country configuration will be supported in the new hotel booking experience."

One source per country. Not per hotel — per country. The corporation running the tool picks a pipe, and everything its travelers see in that market comes down it.

The pipe might be the GDS. It might be what SAP calls Hotel Connector, live as of its July 2025 documentation with HRS, Amex SMP, BCD TripSource, Omnibees and HCorpo, with more added since. And SAP notes in the same document that those suppliers "source their content from multiple providers, including GDS and a variety of hotel aggregators."

So your rate can still reach the traveler when the configuration goes the other way. It reaches them as an ingredient in another company's product, blended with rates from suppliers you have never contracted with. The same hotel group can be seen through one pipe in France and a different one in Germany, in the same week, by the same account.

Nobody sends the hotel that configuration.

Two of your rooms, one listing

Navan published the clearest description of what happens next, in its own announcement in March 2026.

The platform carries 2.6 million properties. They come from Sabre and Amadeus on the GDS side, from Expedia, Booking.com and MakeMyTrip on the agency side, and from direct connections with brands including Wyndham, Travelodge UK and Premier Inn. Booking.com, named as a supplier, sitting inside the corporate booking tool alongside the GDS feed.

The problem this created, in Navan's words, was conflicting hotel room data. Travelers could not tell whether two listings were the same room. Some of them arrived at a property to find a room that looked "nothing like the photos or description."

The fix was a unified room catalog and what the company calls a room intelligence mapper — "an AI-powered tool that acts as a universal translator to turn multiple messy descriptions into one clear, verified listing." Room rate options went up 70 percent.

Read that from behind the front desk.

Your king deluxe enters the tool twice. Once as you described it to the GDS, in the fields that system gives you. Once as an OTA describes it, with its own photography and its own room names. A model reads both, decides they are the same room, and writes the single listing your corporate guest actually reads. Whichever description it found clearest becomes the room somebody arrives expecting.

You did not write that listing. You cannot see it.

What decides, and what doesn't

The order of the results is a setting. In Concur, an administrator at the corporation picks the default sort from a short list — preference rank, lowest price, star rating, distance, company policy — and underneath those sits what the documentation calls a provider-controlled property sort.

Navan states the trade plainly on its own blog. Suppliers, it says, are "usually more willing to put negotiated rates — and rates that offer loyalty rewards — into the GDS." OTA rates do not earn the traveler points, but they "can help save companies money."

That is your negotiated rate and a public rate for your own room, set against each other on one screen, with the choice already framed: loyalty on one side, savings on the other.

What none of this establishes is what any single traveler sees. Content configuration is set per customer, so the screen in front of your corporate account is theirs, not an industry standard. The Concur sort documentation read for this piece covers the legacy version of the tool. Those are the limits of what is public.

Here is what is not limited.

Ask your largest corporate account to send you a screenshot of your property as it appears in their booking tool. Not the rate they believe they have — the screen. Put it beside what you loaded: the room name, the description, the photograph, the price, and whatever sits above and below you in the list.

Most general managers have never seen one. It takes an email.

The GDS still answers to you. Your terms travel as you wrote them, and that remains the argument for the channel. It answers on a screen where it is one line in twenty, next to a version of your room that somebody else described.