What is UCP, and why Google is bringing it to hotels

From recommending to selling

For a while now, AI assistants have been good at recommending a hotel. The harder, more valuable step is selling one: taking a traveller from "that looks nice" to a confirmed reservation without ever leaving the conversation. That is the shift the industry calls agentic commerce, where the AI does not just suggest, it acts.

Google's answer to it is UCP, and in 2026 it named hotels as one of the first places it will live.

So what is UCP?

UCP stands for Universal Commerce Protocol. It is an open standard from Google that gives AI agents, platforms, merchants and payment providers a shared language for completing a transaction. For a hotel, it is what turns a conversation inside Google's AI Mode or Gemini into a real, direct booking, with the price validated and the payment taken, all in the same window.

It is built to work alongside the other emerging standards rather than against them. It stays interoperable with MCP, the data layer an assistant uses to read your live systems, and with AP2, the payment layer that lets an agent pay on a traveller's behalf. In short: MCP lets the assistant understand and reach you; UCP lets it close the sale.

What happens in the conversation

When a traveller asks to book, a UCP-enabled flow runs the whole thing in place:

• It checks your live availability for the dates.
• It validates the real price and conditions before anything is charged.
• It collects the guest's details and room preferences.
• It takes payment through your existing payment provider, by tokenisation, without forcing a particular wallet.

The traveller never clicks through to a website. And the part that matters most for a hotel: you remain the Merchant of Record. The guest data, the relationship, the post-stay and the remarketing rights stay with you, not with an intermediary.

How it fits with MCP

It is easy to confuse the two, so it helps to keep them in their lanes. An MCP is the connection that lets an assistant read your live rates, availability and content. UCP is the commerce standard that lets it complete a purchase against them, with AP2 handling the payment itself. One moves the data, the other closes the deal. A hotel that wants to be bookable by AI ends up needing both.

Why this is a distribution moment, again

Google did not launch UCP for hotels quietly. It arrived with the largest names in travel already on board, the major OTAs and chains among the first partners. That should sound a familiar alarm. The properties that are ready will be bookable directly inside AI Mode. The ones that are not will be reachable only through the aggregators that are, paying for the privilege a second time, exactly as they learned to with search.

Merchant of Record is the line between those two futures. It is the difference between owning the guest and renting them back from whoever sold the room.

What a hotel actually needs to do

The good news is that most hotels will not implement UCP themselves. The work sits with your booking engine and CRS vendors. So the job is to make sure you are not left behind by them:

• Ask your vendors whether they are building toward UCP, and on what timeline.
• Keep your property data structured and API-accessible, so it can flow into these standards cleanly.
• Protect your Merchant-of-Record terms, so the direct relationship stays yours.
• Get found first. None of this helps if the assistant never surfaces you; visibility comes before the booking.

At Listo, we help hotels get ready for exactly this moment: visible to the assistants, connected to their systems, and in a position to be booked directly when the conversation gets to checkout. The sale is moving inside the chat. The question is whether, when it does, your hotel is one it can actually complete.