Google promises hotels they keep the guest. Read who "you" is in that sentence.

Google's lodging page guarantees that the merchant of record keeps the customer relationship, and on an independent's AI Mode booking the merchant of record is the OTA

by Markus Busch

The promise, in Google's words. Its UCP for Lodging page says you remain the Merchant of Record and keep all of your customer data and relationships. Asked outright whether integrating means losing control of your customer data, the page answers no, and spells it out: full ownership of customer relationships, data and the post-booking experience. "You own the transaction."

That is a written guarantee about the one thing hotels have spent fifteen years losing.

Now look at who it is written to. UCP is a protocol, and a protocol is something you integrate. The only thing that page lets you do is join a waitlist, and it offers the button twice. Detailed onboarding and specs are coming soon, and have been for about four months. No partner is named anywhere on it. The picture of the product carries a caption saying it is a conceptual mock.

Meanwhile the bookings are already happening. Since September 1, a traveler in the United States can finish a hotel reservation inside AI Mode and pay with Google Pay, across ten launch partners. None of them arrived through UCP, because there is nothing yet to build against. The guarantee is live, and it is live for whoever was already wired in.

So read the pronoun. Your room reaches that conversation through the OTA you already sell through. On that reservation the merchant of record is the OTA. Google's promise is not being broken — it is being kept, precisely, to the company holding the transaction. "You" is whoever the guest reaches when she wants to move her dates by a night, and on that booking it is not your front desk.

Two chains read the same sentence and answered differently. Choice took the checkout: a traveler finds a property in AI Mode, taps through, pays with Google Pay, and Choice stays merchant of record. Hilton put its inventory and its points into AI Mode and then declined the checkout, routing the traveler back to Hilton.com to finish.

Opposite answers. What matters for you is that both companies were asked. That is what a direct connection buys — not a better outcome, a choice.

The catch, and it cuts both ways. With no spec published, nobody outside Google can say what integrating would require, what it would cost, or whether a single property could do it at all rather than a chain or a platform. Google has not said whether independents are in scope. And holding the transaction is not the same as holding a guest record you can use: it settles who takes the money and carries the liability, and nothing more. Do not read the guarantee as bigger than it is, in either direction.

Monday. Two things, both cheap. Join the waitlist, because it costs nothing and it is currently the only way to be counted at all. Then ask your OTA account manager who is named as merchant of record on reservations that originate in Google's AI Mode, and whether those arrive on your side marked any differently from an ordinary booking. The answer, or the absence of one, tells you more than the promise does.

Google has written the sentence hotels wanted to read, and the sentence is true. It was addressed to whoever holds the transaction, and the page where you would ask to be included is still a form.

Read also: Google isn't after your booking. It's after your guest. · An independent has three ways into the AI booking channel. Two of them are somebody else's.

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 →