Google is moving toward a more standardized way of handling hotel reservations through its AI-powered search experience.
The company plans to adopt the Universal Commerce Protocol (UCP) Lodging Booking draft specification for hotel booking in Google AI Mode over the coming months.
The development could make it easier for hotels, booking platforms and travel businesses to connect their reservation systems with Google’s AI experiences while allowing businesses to remain the Merchant of Record and retain control of their customer relationships and booking data.
The announcement follows the publication of the first UCP draft specification for lodging bookings on September 25. The specification establishes a common technical framework for handling hotel availability, pricing, guest information, booking sessions, payment arrangements and reservation completion.
For hotels and travel marketers, the development is significant because AI search is increasingly moving beyond providing information toward helping users complete transactions.
What Is The Universal Commerce Protocol?
The Universal Commerce Protocol (UCP) is an open standard designed to provide a common framework for AI agents, businesses and consumer platforms to interact during commerce transactions.
Google introduced UCP as part of its broader push toward agentic commerce. The protocol is designed to support commerce experiences across Google’s AI surfaces and can work with other industry protocols and standards.
With the expansion into lodging, UCP now defines how platforms can interact with hotel and lodging businesses to manage reservation workflows.
Instead of creating a completely separate integration for every AI platform, an open protocol can provide a standardized structure for exchanging booking information and completing reservations.
UCP for Lodging is designed to enable direct bookings across supported Google surfaces, including AI Mode in Search.
Google Plans To Use UCP For AI Mode Hotel Booking
Google’s developer documentation states that the company plans to adopt the UCP lodging standard to power its hotel booking feature in AI Mode over the coming months.
This is important because Google had already introduced hotel booking capabilities in AI Mode for U.S. English users before the lodging specification was published.
Google began rolling out hotel booking in AI Mode on August 27, working with hotel chains and online travel platforms. The UCP lodging draft was published afterward, giving businesses a first look at the standard Google plans to adopt for the experience.
The distinction is important: Google has not said that every existing AI Mode hotel booking is already operating through UCP. Instead, the company says it plans to adopt the standard for its hotel-booking feature over the coming months.
A future UCP-enabled booking journey could broadly look like:
Hotel discovery → Availability check → Room and rate selection → Guest details → Payment → Booking confirmation
The goal is to reduce friction between travel research and reservation completion.
What Does The UCP Lodging Specification Cover?
The draft specification focuses on the booking lifecycle between a platform and a lodging business.
It includes functionality for:
- Checking real-time room availability
- Retrieving current pricing
- Selecting accommodation and rate plans
- Providing check-in and check-out dates
- Managing guest information
- Managing occupancy details
- Handling payment arrangements
- Supporting cancellation and other booking policies
- Creating and updating booking sessions
- Completing reservations
- Cancelling booking sessions
The draft defines a progressive booking session in which information can be added or updated before the reservation is completed.
For example, a traveler could express an initial booking request, after which the platform could establish a booking session containing the property, stay dates and selected rate. Guest information, occupancy, booker information and payment details can then be added or updated during the session.
The specification currently defines operations including Create Booking Session, Get Booking Session, Update Booking Session, Complete Booking Session and Cancel Booking Session.
Real-Time Pricing And Availability Are Central To UCP
One of the important aspects of UCP for lodging is its focus on authoritative booking information.
Before presenting the final booking action, Google’s current documentation says it performs a real-time price and availability check against the partner’s API.
The UCP specification similarly requires the lodging business to evaluate the requested property, accommodation and rate against real-time availability and inventory constraints.
The business is responsible for returning authoritative pricing, booking information and applicable policy terms.
This is particularly important in hotel distribution because prices and availability can change quickly.
An AI system displaying outdated room inventory or pricing could create problems at the point of booking. Connecting the transaction to the business’s booking infrastructure is intended to help ensure that the information used to complete the reservation reflects the business’s current systems.
Hotels Remain The Merchant Of Record
One of the most important details for hotels is that adopting UCP does not transfer the Merchant of Record role to Google.
The business remains the Merchant of Record, retaining control of its customer relationships, booking data and post-stay experience.
This could be particularly relevant for hotel brands that prioritize direct bookings, loyalty programs and ownership of the guest relationship.
The UCP model connects the AI platform with the hotel’s booking infrastructure while allowing the lodging business to remain responsible for the actual reservation and its associated commercial terms.
The hotel’s own Terms and Conditions apply to a UCP reservation and must be accepted during the booking process.
Will UCP Affect Hotel Search Rankings?
According to Google’s FAQ, participating in the UCP booking integration does not affect how a property’s listings or rates are ranked.
However, offers that are integrated with UCP can receive the direct booking option within the supported experience.
This distinction is important for hotel marketers.
UCP integration should therefore be understood as a way to support bookings through Google’s AI surfaces rather than as a direct ranking signal.
In simple terms:
UCP integration does not equal a ranking boost.
Instead, it provides an opportunity to participate in the direct-booking experience.
What Happens To Customer Data?
The UCP model also addresses the relationship between AI platforms and businesses after a booking takes place.
The lodging business remains the Merchant of Record and retains ownership of its customer relationships, booking data and post-stay experience.
Standard privacy and consent requirements continue to apply.
This means UCP is designed to enable AI-assisted reservations without completely separating the hotel from the customer relationship.
For hotel businesses, this could make AI-generated bookings easier to incorporate into existing reservation, customer-management and post-booking processes.
UCP Supports Existing Technology Standards
Another notable aspect of UCP is its interoperability with other protocols.
UCP for Lodging is designed to work with technologies and standards including:
- Agent2Agent (A2A)
- Agent Payments Protocol (AP2)
- Model Context Protocol (MCP)
The lodging specification also supports technical bindings including REST and MCP.
These technologies have different roles.
UCP provides the broader commerce and reservation framework, while AP2 can operate as a specialized payment layer within UCP, particularly for future agent-led payment scenarios.
What About Payments?
Payments are an important part of the hotel booking workflow, and the UCP lodging specification includes payment-related functionality.
The specification supports payment arrangements such as deposits and deferred balances, allowing different portions of a hotel reservation to be charged at different points in the booking lifecycle.
Google also says businesses do not need to support checkout through the Google Pay API on their own website or app. However, their Payment Service Provider must be capable of processing Google’s payment tokens.
The draft specification states that the lodging business does not need to become PCI DSS compliant merely to accept card payments through this UCP capability.
However, applicable payment-security and compliance requirements can still apply to the payment infrastructure and entities handling sensitive payment credentials.
AP2 can also be used as a specialized payment layer within UCP for agent-led transactions. This is particularly relevant to future scenarios involving autonomous AI agents.
AI Does Not Necessarily Book The Hotel Completely Autonomously
There is an important distinction here.
The UCP lodging draft does not mean that an AI agent can automatically purchase every hotel reservation without the user’s involvement.
Under the current draft, unless the AP2 Mandates extension is supported, the booking must be finalized by the user through a trusted interface.
The specification also describes a handoff to a trusted and deterministic user interface for reviewing and completing the booking.
This means the immediate UCP model is better understood as:
AI-assisted discovery and booking → Structured booking session → User review and confirmation → Reservation
rather than automatically allowing an AI agent to make every hotel purchase independently.
AP2 provides a framework for more agent-led payment scenarios, but those represent a more advanced stage of agentic commerce.
The Specification Is Still In Draft
Businesses should not treat the current UCP lodging specification as a completely finalized standard.
The official specification is explicitly marked as a draft and work in progress.
It warns that data models, protocol bindings and operational flows are still being developed and may undergo breaking changes as the specification evolves.
This is important for hotels, booking engines, PMS providers, CRS providers and other technology companies considering implementation.
The overall direction is becoming clearer, but businesses should expect technical details to evolve before the specification reaches a more stable version.
What This Means For Hotel Businesses
Google’s planned adoption of UCP could provide hotels and lodging businesses with another way to reach travelers during the AI-assisted discovery and booking journey.
Instead of requiring users to leave an AI conversation, find a booking page and complete several steps themselves, UCP is designed to allow more of the reservation process to take place through the AI experience.
For hotel businesses and technology providers, this puts greater emphasis on:
- Real-time inventory and pricing accuracy
- Structured accommodation and rate data
- Booking API compatibility
- Payment infrastructure
- Cancellation and rate policies
- Guest and booker information
- Customer-data management
- Direct booking infrastructure
- AI-enabled booking experiences
However, businesses should distinguish between being technically capable of supporting UCP and actually being onboarded to Google’s AI Mode hotel-booking program.
Google’s current lodging documentation directs interested businesses toward its onboarding process and waitlist, while detailed implementation guidance continues to develop.
What Happens Next?
Google has not announced a specific date for switching its AI Mode hotel-booking experience to the UCP standard.
Its current documentation says that Google plans to adopt UCP for AI Mode hotel booking over the coming months.
The first milestone focuses on booking. Google’s FAQ describes the initial milestone as supporting booking for one room, while multiple-room booking is identified as a potential future extension.
The underlying draft data model, however, is already structured around one or more stay units, showing that the specification has been designed with more complex reservations in mind.
The specification is also open to public feedback through the UCP project. As implementation progresses, the industry can expect additional guidance and potentially new capabilities.
For now, businesses should view UCP for Lodging as an emerging integration standard rather than a finalized replacement for existing hotel distribution, reservation or booking-engine infrastructure.
Why This Matters For The Hotel Industry
The significance of UCP goes beyond another API integration.
Historically, hotel distribution has largely been built around websites, booking engines, OTAs, metasearch platforms and traditional APIs.
AI introduces another interface between the traveler and the hotel.
A traveler may no longer need to search for a hotel, open multiple websites, compare rates and manually enter information across different systems. Instead, an AI interface could increasingly help with discovery, comparison and reservation within a single interaction.
UCP provides a standardized technical framework for connecting that AI experience with the hotel’s booking infrastructure.
That could potentially reduce fragmentation as more AI platforms begin supporting travel transactions.
However, the ultimate impact will depend on how widely the protocol is adopted, how the specification evolves and how hotels, booking platforms, payment providers and technology vendors implement it.
Final Thoughts
Google’s planned adoption of the UCP Lodging Booking specification marks another step toward connecting AI search with actual hotel transactions.
The draft provides a standardized framework for handling important parts of the reservation lifecycle, including availability, pricing, accommodation and rate information, guest details, payment arrangements and booking completion.
At the same time, Google’s documentation makes several points clear: the hotel or lodging business remains the Merchant of Record, UCP participation does not affect property or rate rankings, and businesses retain control of their customer relationships and booking data.
The technology is still evolving. The lodging specification remains a draft, and Google has not yet announced a specific date for moving its AI Mode hotel-booking experience to the standard.
For now, the development is best understood as an early step toward a more standardized infrastructure for AI-assisted hotel booking.
As Google and the wider travel industry continue developing agentic commerce, protocols such as UCP could become an increasingly important technical layer between travelers, AI platforms and hotel reservation systems.
