Universal Commerce Protocol Expands to Lodging and Food — UCP for Hotels/Food Specs and Vertical Co-Developers Explained

Google Marketing Live 2026 takes UCP out of retail

How we're helping retailers thrive with new Universal Commerce Protocol features and AI tools on Google

New UCP-powered features and AI tools will create a more intuitive, agentic shopping experience for consumers and retailers.

blog.google

Google Marketing Live 2026, held on May 20, 2026, extended the Universal Cart and Universal Commerce Protocol (UCP) announced at I/O the day before, pushing them into two non-retail verticals: hotel booking and local food delivery. VP/GM of ads and commerce Vidhya Srinivasan stated in the official Google blog that UCP is expanding "to even more verticals, starting soon with hotel booking and local food delivery" (Google).

If I/O was the consumer-experience reveal, Marketing Live was where Google repositioned UCP as a cross-industry protocol. The protocol's official portal ucp.dev now adds Lodging and Food tabs alongside Shopping, each with a dedicated specification in preparation. This piece looks at what these two extensions mean at the protocol level and how they affect lodging and food businesses.

UCP for Lodging: what the hotel booking protocol actually contains

The most-watched extension is UCP for Lodging, published at developers.google.com/hotels/ucp. ucp.dev summarizes its purpose as follows.

"

Enables high-quality booking flows within AI surfaces — complete with real-time pricing and availability checks, smooth handling of complex rate plans, easy guest registration, and secure checkout.

Source: ucp.dev / UCP for Lodging

The sentence is short, but it captures Google's design intent for "protocolizing hotel booking." Where e-commerce inventory is largely binary (in-stock / out-of-stock), hotel inventory is a multi-dimensional rate construct — date, room type, occupancy, cancellation policy, breakfast inclusion, loyalty status, and more. UCP for Lodging is the extension module that absorbs that difference.

Amadeus, Booking.com, Hilton, Marriott at the same co-development table

The co-developers listed on the Lodging tab of ucp.dev are:

• Amadeus (one of the largest GDS / PMS / CRS vendors globally)
• Booking.com (Booking Holdings, world's largest OTA)
• Expedia Group (Expedia, Hotels.com, Vrbo)
• Hilton (global chain pushing direct booking)
• Marriott (world's largest hotel chain)
• Trip.com (leading APAC OTA)
• Google

Having GDS, the largest OTAs, and chains pursuing direct distribution sit at the same protocol specification table is historically unusual for hotel distribution. Booking and Expedia have long contested chain direct channels for inventory share. UCP creates a shared problem — how to fairly receive traffic mediated by AI agents — that pulls them onto the same page.

Skift reported that Google had "publicly committed to extending its agentic commerce infrastructure to travel," and made clear that travel packages (flight + hotel) remain ineligible for UCP checkout. The initial AI surface is Google's Gemini Spark AI.

"The property remains Merchant of Record"

A critical technical point on Google's lodging developer page is the explicit "transparent accountability trail". The roles of merchants, credential providers and payment services are clarified, and the property ultimately remains Merchant of Record.

This addresses a known problem: if AI surfaces sold hotel rooms directly, responsibility for any service issues becomes ambiguous. As with OTA-mediated bookings, the property keeps responsibility for delivering the stay, collecting funds, and managing cancellations. The AI agent and Google remain matchmakers, not retailers. That positioning is the precondition the hotel industry needs to feel safe adopting the standard.

AI Mode in Search becomes a booking funnel

Once UCP for Lodging is live, a user can tell AI Mode in Google Search: "I need a hotel near Haneda for next Wednesday's business trip, breakfast included, under ¥30,000, eligible for Marriott Bonvoy benefits." Rather than receive a list of results, the user gets booking and payment completed inside the conversation.

The technical substrate is UCP's Catalog Search, Cart Building, Identity Linking (OAuth 2.0), Checkout, and Order Management — overlaid with Lodging-specific rate-plan extensions. Payments run through AP2 (Agent Payments Protocol). Loyalty IDs and membership tier are linked via the OAuth 2.0 standard, with the agent acquiring scoped authorization on behalf of the user.

UCP for Food: protocolizing conversational meal ordering

The other extension, UCP for Food, lives at developers.google.com/actions-center/verticals/ordering/ucp. ucp.dev describes it as follows.

"

Powers conversational food ordering journeys that seamlessly handle nuanced meal customization, real-time availability and deals, tipping, and delivery instructions through a scalable checkout experience on AI surfaces.

Source: ucp.dev / UCP for Food

If hotels are about multi-dimensional rates, food is about combinatorial customization and real-time availability. Pizza toppings, spice levels, side items, delivery address and time, tipping, and store-specific promotions all need to be handled inside a conversation.

Uber Eats, DoorDash, Toast, Square at the same table

Food's co-developers are equally striking.

• DoorDash (US market leader in delivery)
• Uber Eats (global delivery)
• Toast (restaurant POS / online ordering)
• Square (Block, POS for small operators)
• Google

What stands out is that POS players Toast and Square are co-developers. This signals that UCP's scope is not only "delivery platform → agent" but also "store POS → agent." Member-only deals and limited-time discounts run by individual stores could potentially reach AI Mode and Google Maps conversations.

Google Maps becomes an ordering funnel

The experience side: while looking at Google Maps, a user asks "spicy noodles from here, peanut-allergy safe," and the in-map chat seamlessly switches to an ordering flow. Delivery address, scheduled time and tipping are completed inside Maps; payment lands on AP2-backed Google Pay or the store's own checkout.

Three things lodging and food operators need to act on now

From the operator's point of view, three issues stand out.

First, publishing machine-readable data from PMS / CRS / POS becomes a competitive precondition. Without an API that exposes inventory, rates, deals, cancellation policies, and customization options in a structured way, you receive zero agent-driven traffic. That Amadeus and Booking.com are co-developers suggests UCP onboarding could accelerate legacy PMS/CRS replacement cycles.

Second, rebalancing investment away from OTA and delivery-app dependence. With AI agents in between, users skip opening the Booking.com or Uber Eats app. Operators built on assumed OTA/platform commissions need to start tracking direct agentic intake as a KPI early.

Third, making loyalty IDs available over OAuth 2.0. UCP standardizes Identity Linking on OAuth 2.0. Whether your loyalty program — Marriott Bonvoy, Hilton Honors, your own QSR program — can be safely invoked by AI agents will become a key differentiator between direct brand bookings and OTA-mediated bookings.

Ask Advisor on the operator side rides the same protocol world

The seller-side operator agent Ask Advisor was announced the same day. Embedded in Merchant Center, it spans Google Ads and Google Analytics to surface insights and execute tasks. Combined with AI Performance Insights (visualizing your share of voice on AI surfaces vs. similar brands) and Conversational Attributes (product attributes tuned for conversational queries), it raises the operator side by another agent-level notch (Search Engine Land).

For lodging and food operators, that means analyzing and optimizing UCP-received bookings and orders through Ask Advisor naturally fits the same workflow. The structural takeaway from Marketing Live as a whole is that the protocol (UCP) and operator agent (Ask Advisor) now integrate from the same Merchant Center base.

Summary

UCP extending to Lodging and Food marks a turning point — agentic commerce moving from "buying products" to "booking services." Amadeus, Booking.com, Hilton and Marriott on the hotel side; DoorDash, Uber Eats, Toast and Square on the food side. Both industries, long built on vertical-specific protocols, are now hosting a cross-industry one.

What to watch next: when the Detailed Specifications for Lodging and Food drop, which chain produces the first AI Mode-driven hotel booking or food order case study, and when PMS / CRS / POS vendors put UCP integration on their roadmaps. A world where one protocol unifies industries is already approaching travel and dining storefronts.