Google Commits to UCP Lodging Spec for AI Mode Hotel Booking
Google's FAQ, updated Sept. 24, says it will adopt the UCP Lodging Booking draft standard for AI Mode hotel booking "over the coming months." The draft landed on GitHub Sept. 25.
Updated
The brief
- Google stated on Sept. 24 it will adopt the UCP Lodging Booking draft standard to power hotel booking in AI Mode "over the coming months."
- The draft spec, published Sept. 25, was developed by a Lodging Technical Council of Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, and Trip.com.
- Google's FAQ confirms UCP integration does not affect property ranking, and the business remains merchant of record with its own customer data and terms.
Google will adopt the Universal Commerce Protocol's new Lodging Booking draft specification to power hotel booking in AI Mode, the company stated in an FAQ updated Sept. 24. The commitment came one day after the UCP project published the draft in its GitHub repository on Sept. 25, giving hotels and booking sites their first public look at the standard.
"Over the coming months, Google will adopt this standard to power its hotel booking feature on AI Mode," the FAQ says. Google began rolling out hotel booking in AI Mode for U.S. English users on August 27, working with 10 hotel chains and online travel platforms. The company did not specify whether all integrated partners currently use the protocol.
What the spec covers. The dev.ucp.lodging.booking specification describes how a platform manages booking sessions via REST or MCP, covering creation, updates, completion, and cancellation. The announcement lists real-time pricing, availability checks, guest details, occupancy, check-in/check-out dates, and special requirements among its features.
The draft ties into payment extensions introduced in UCP's August 25 release, including deposits, deferred balances, and split payments, plus a new extension for cancellation policies. It also draws on shared UCP components such as identity linking and payment handlers.
The spec says PCI DSS compliance is not necessary for card payments. Bookings must be finalized by a person through a trusted interface, except when using UCP's AP2 Mandates extension for agent-led payments. A banner on the draft warns that data models and bindings may evolve, with breaking changes possible.
The Lodging Technical Council — comprising Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, and Trip.com — developed the standard.
Commercial questions answered. Google's FAQ addresses several concerns hotel and travel marketers have raised since AI Mode booking launched. The first milestone covers one room per booking, with multiple rooms "potentially as a future extension," though the open spec's data model allows a reservation to include one or more stay units.
Choosing the booking integration "does not influence how we rank your properties or rates in listings," the FAQ states. However, only entries with UCP integration receive the direct booking option. The business acts as the merchant of record, retains its own customer information and booking details, and applies its own terms and conditions to the reservation.
Lifecycle events shared through the API let a business see which traffic and payments arrived via Google's AI surfaces rather than its own website or app. Before the final "Book" button appears, Google verifies real-time price and availability through the partner's API.
Businesses do not need the Google Pay API on their site, but their payment provider must support processing Google's tokens. The FAQ mentions that AP2 can act as a payment layer within UCP for future agent-led transactions, though it stops short of calling it required.
A fast turnaround. The Lodging Technical Council was formed on August 11. UCP's August 25 release introduced the structure needed to expand beyond retail. As recently as August 31, the lodging specifications remained in development with no release timeline. Google connected hotel booking to UCP publicly back in May at Google Marketing Live.
For now, businesses interested in joining can sign up on Google's UCP for Lodging waitlist. Detailed onboarding instructions and specifications are "coming soon." The draft remains open for feedback on GitHub, and neither Google's FAQ nor its lodging page gives a date for the AI Mode switch or names which existing booking partners will move to the standard.
The next signals to watch: a stable lodging release, Google opening onboarding beyond the waitlist, and additions to the booking spec — starting with the multi-room extension the FAQ flags as a possibility.
Based on github.com
Filed under google, ai-mode, ucp, hotel-booking, travel
More from Amara Osei
Show full bio
News editor covering industry trends and analytics at Marketing Herald.
56 articles