TL;DR
- On 25 September 2026 the UCP project merged the first draft of its Lodging Booking capability (dev.ucp.lodging.booking) and opened it for public feedback on GitHub.
- The draft was shaped by a Lodging Tech Council of seven named members: Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com.
- Google's FAQ says it will adopt the standard for AI Mode hotel booking over the coming months, with no date, and that opting in does not affect property or rate ranking.
- Hotels stay merchant of record and keep customer data; their PSP must process Google tokens, and the first milestone covers one-room bookings.
- AI Mode hotel booking has rolled out for US English users since 27 August 2026; no source gives a date for Thailand.
Google will move hotel booking in AI Mode onto the Universal Commerce Protocol (UCP), an open standard whose first draft lodging booking specification was merged on 25 September 2026. Google's developer FAQ for UCP for Lodging says: "Over the coming months, Google will adopt this standard to power its hotel booking feature on AI Mode." The same FAQ states that opting in does not change how Google ranks a property or its rates, that the hotel stays the merchant of record, and that onboarding is currently handled through a waitlist. No switch-over date has been published.
What was released on 25 September 2026
On 25 September 2026, a maintainer of the Universal Commerce Protocol project announced in GitHub Discussion #864 that the initial draft of the Lodging Booking capability had been merged into the UCP repository and was open for public feedback and contributions. The capability is named dev.ucp.lodging.booking. The announcement describes it as the formal expansion of UCP into the lodging domain, following an earlier "multi-vertical architecture milestone".
The announcement credits a Lodging Tech Council for shaping the draft and names seven members: Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com, plus open source contributors. Search Engine Journal reported that the council was set up on 11 August 2026 and that UCP's 25 August release introduced the structure needed to expand beyond retail.
The GitHub announcement lists four capability highlights for the draft:
- Real-time pricing and availability checks for rooms inside AI surfaces.
- Guest registration covering guest details, occupancy counts, check-in and check-out dates, and custom accommodation requirements.
- Checkout with complex payment schedules: deposits, deferred balances, split payments, and cancellation and refund policies tied to the booking lifecycle.
- Interoperability with core UCP primitives such as identity linking and payment handlers.
The data table: what Google and the draft spec say
The table below collects the commitments that matter commercially to a hotel or booking site, each taken from Google's UCP for Lodging FAQ or from the draft specification itself.
| Question | What the source says |
|---|---|
| When does AI Mode switch to UCP? | "Over the coming months" (Google FAQ); no date given |
| Does opting in affect ranking? | No; it "does not influence how we rank your properties or rates" (Google FAQ) |
| Who is merchant of record? | The hotel or booking business, which keeps customer and booking data (Google FAQ) |
| Rooms per booking in this milestone | One room; multiple rooms "potentially as a future extension" (Google FAQ) |
| Is the spec stable? | No; draft status, breaking changes possible (UCP spec banner) |
How the booking flow works in the draft specification
The UCP draft specification for dev.ucp.lodging.booking describes a booking as a session that moves through defined states. A platform, such as an AI assistant, starts a session with property, stay, rate plan and date details taken from earlier search results. It then adds guest profiles, booker information and payment details over one or more updates. The session becomes a confirmed, immutable reservation only when the platform calls Complete Booking Session.
The states named in the draft are incomplete, requires_escalation, ready_for_complete, complete_in_progress, completed and canceled. When a hotel needs information its API cannot collect, or when policy requires the traveller to review something, the session moves to requires_escalation and the business must supply a continue_url that hands the traveller over to the hotel's own interface.
The draft also separates the booker, the legal contracting party responsible for payment, from the guests who will physically stay. That split is meant to support corporate, proxy and multi-stay bookings. Guest identifiers are generated by the platform, scoped to a single booking session, and must not carry personal data or be used to track people across merchants.
Search Engine Journal reported that the spec describes booking sessions handled via REST or MCP. The draft lists both a REST binding and a Model Context Protocol binding.
Payments, taxes and price transparency
The draft states that the business "remains the Merchant of Record (MoR) and does not need to become PCI DSS compliant to accept card payments through this capability". It also says that unless the AP2 Mandates extension is supported, the booking must be finalised manually by the user through a trusted UI. In plain terms, an AI agent can help choose dates, rooms and guests, but in the default flow a person confirms the booking on a deterministic screen.
Pricing rules are strict. The draft requires one authoritative all-in total per booking session and says platforms and businesses must show the guest the complete stay liability before confirmation, citing consumer rules such as FTC and EU price transparency directives. Payment timing is modelled separately from the price breakdown, with schedule types for immediate payment, deferred payment (for example a balance due at check-in) and payment collected at the property (for example local tourist taxes or resort fees). If totals change during a session, the business must flag it with a "totals_changed" warning, and the platform must not hide that disclosure.
Search Engine Journal added that the draft ties into payment extensions for deposits, deferred balances and split payments from UCP's 25 August release, along with a new extension for cancellation policies.
What Google's FAQ commits to for hotels
Google's UCP for Lodging FAQ, last updated on 24 September 2026, answers several questions hotel marketers will ask first.
Ranking. Google says opting for the booking integration "does not influence how we rank your properties or rates in listings". The listing experience stays the same, but offers integrated with UCP will show a direct booking option.
Customer ownership. The business is the merchant of record and keeps ownership of customer relationships, booking data and the post-stay experience. The hotel's own terms and conditions cover the booking, and the traveller must accept them during the flow. Google says it is planning a feature that lets travellers opt in to marketing communications during booking in a future update.
Payments. A hotel does not need Google Pay checkout on its own website or app, but its payment service provider must be able to process Google's tokens. Existing Google Pay settings such as card restrictions do not carry over; UCP needs its own configuration.
Accuracy. Before the final "Book" button is enabled, Google runs a real-time price and availability check against the hotel's API. Google also expects the hotel's system to update rates, taxes and fees dynamically as guest details change.
Reporting. Booking, reservation and transaction lifecycle events are exchanged through the API contracts in the specification, which Google says lets a hotel tell traffic and payments from AI surfaces apart from its own website or app.
How this connects to the AI Mode hotel booking launch in August
Google began rolling out hotel booking in AI Mode for US English users on 27 August 2026. Search Engine Journal reported that Google worked with 10 hotel chains and online travel platforms for that launch, and that Google connected hotel booking to UCP at Google Marketing Live in May. The August launch post did not say whether every integrated partner uses the protocol. Google's FAQ and lodging page do not give a date for the AI Mode switch or say which existing booking partners will move to the standard, according to Search Engine Journal.
So the sequence is: a live but limited AI Mode booking feature since late August, a published open draft since 25 September, and a stated plan to move the feature onto that draft "over the coming months".
What the sources did not say
Several points remain open, and it is worth being exact about them. Google has not given a date for moving AI Mode booking to UCP. Neither the FAQ nor the GitHub announcement names markets or languages beyond the existing US English AI Mode launch. There is no public onboarding path yet beyond the waitlist on Google's UCP for Lodging page, as Search Engine Journal noted. Multi-room booking is described only as a possible future extension. And because the specification is a draft, field names, bindings and flows may still change before a stable release.
What this means for Thai marketers
Hotel booking in AI Mode is currently a US English feature, and neither Google nor the UCP project has said when, or whether, it will reach Thailand or Thai-language searches. Thai properties should treat this as something to prepare for, not something to launch this quarter.
The points below are analysis, not anything Google has promised for Thailand.
- Technology partners. Thai hotels that sell through online travel agencies, booking engines or channel managers depend on those partners for any new connection. Two OTAs named on the council, Booking.com and Expedia, plus Amadeus on the distribution side, help shape the standard. Hotels can ask their booking-engine and payment providers whether they plan to support UCP and whether their PSP can process Google payment tokens.
- Rate and inventory accuracy. The draft and the FAQ both lean on real-time price and availability checks and all-in pricing. Properties whose direct rates, taxes and fees are inconsistent across channels will find that harder under this model.
- Measurement. Because the protocol carries lifecycle events that separate AI-surface bookings from direct bookings, hotels that do adopt it will need reporting that keeps those channels apart.
For content and search teams, the story connects to how AI answer engines pick and present options. The work of making a property understandable to AI systems sits in AI SEO, and the broader question of being cited and chosen inside AI answers is covered under generative engine optimization (GEO).
FAQ
Is AI Mode hotel booking with UCP live in Thailand?
Not stated; the sources give no Thailand date. Google's AI Mode hotel booking began rolling out for US English users on 27 August 2026, and Google's FAQ only says it will adopt UCP for that feature over the coming months.
Will joining UCP improve my hotel's ranking in AI Mode?
No, according to Google. Its FAQ says opting in "does not influence how we rank your properties or rates in listings", although UCP-integrated offers will show a direct booking option.
Do hotels lose their customer data if bookings happen inside AI Mode?
No, Google says the hotel stays the merchant of record. It keeps the customer relationship, booking data and post-stay experience, and its own terms and conditions apply to the booking.
Does a hotel need Google Pay on its website to use UCP?
No, but its payment service provider must be able to process Google's tokens. Card restrictions and similar settings must be configured separately for the UCP channel.
Can an AI agent complete a hotel booking on its own under the draft?
Not by default. The draft says the booking must be finalised by the user through a trusted UI unless the AP2 Mandates extension is supported.
What to watch next
The draft is open for feedback on GitHub. The next signals are a stable lodging release, Google opening onboarding beyond the waitlist, and additions such as the multi-room extension that Google's FAQ describes as a possibility. The source document for this article is Google's UCP for Lodging FAQ on Google for Developers. If you want to check how ready your property or booking site is for AI-driven search and booking, Relevant Audience can review your setup with you.
