What the lodging draft adds
The Universal Commerce Protocol merged the initial draft of its Lodging Booking capability on 25 September 2026. The protocol’s own announcements page dates the merge to that day and names the author: the Lodging Technical Council, made up of Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com. The capability carries real-time pricing and availability checks, guest registration and payment schedules.
Google’s developer page for UCP in lodging was last updated 24 September 2026. It states the plan in one line: over the coming months, Google will adopt this standard to power its hotel booking feature on AI Mode.
That adoption follows a live feature. PhocusWire reported on 27 August 2026 that hotel booking in AI Mode had launched in the United States with ten inventory partners: Expedia, Booking.com, Hilton, Hotels.com, Choice Hotels International, IHG Hotels & Resorts, Priceline, Marriott International, Wyndham Hotels & Resorts and Trip.com. The same report names the booking partner as the merchant of record and Google Pay as the payment method.
What the draft carries
The draft binds a reservation through a compound stay unit. Each stay links an accommodation type, a commercial rate plan, a date interval, an occupancy requirement and guest assignments. The full entity list runs to twenty entries: property, booking confirmation, booker, capacity, context, date interval, guest, guest assignment, link, message error, message info, message warning, occupancy, payment, policy, rate plan, stay, accommodation type, signals and total.
A booking session moves through three stages. The platform opens it with property, stay and rate-plan identifiers taken from an earlier search. It then enriches the session with guest profiles, guest assignments, booker details and payment information. It finalizes the session to create a confirmed reservation.
The business sets a status on the session at each stage. The permitted values are incomplete, requires_escalation, ready_for_complete, complete_in_progress, completed and canceled. A session the API cannot finish hands off to the traveler through a continue_url. The draft states that unless the AP2 mandates extension is supported, the booking must be finalized manually by the user in a trusted interface.
Pricing follows all-in rules written to consumer protection regulation, including the FTC and EU price transparency directives. Resort fees and municipal occupancy taxes sit inside the authoritative totals array. The business remains the merchant of record, and the draft states that a business accepting card payments through the capability does not need PCI DSS compliance.
The gap: agencies, commissions, group terms
The draft holds no field for a travel agency, a commission, or a group contract. A direct read of the specification page on 13 October 2026 returned zero occurrences of agency, commission, group, attrition or room block. The nearest adjacent commercial field is a company string on the booker entity, and the draft describes it as used for corporate invoicing.
Google’s own FAQ limits the first milestone to availability checks, previewing and completing a booking for one reservation. Multiple rooms appear as a possible future extension. A room block, an attrition clause and a commission share have no representation.
Who wrote it, and how firm it is
The Lodging Technical Council formed on 11 August 2026 with those same seven members. Search Engine Journal reported on 31 August 2026 that the protocol’s fourth release laid the groundwork for lodging commerce, and that the announcements page carried no release timeline for the lodging specification at that date.
The draft page carries its own warning. Data models, protocol bindings and operational flows remain under active iteration and may change in ways that break implementations built against them.
What it changes for hotel commercial teams
Three commercial terms sit outside the protocol. A property cannot express an agency relationship, a commission or a group contract through the booking session. Hotel teams that sell through agencies, consortia or negotiated blocks keep those arrangements on their own systems while the direct flow runs inside the protocol.
The rate plan in the draft is described as a commercial rate policy contract. The platform must present it as a unit alongside the accommodation type, the occupancy and the totals. A rate a property wants an agent to sell has to arrive as a rate plan the property’s system can price and confirm in real time.
The model separates the booker from the guests. The booker is the legal contracting party and carries the payment obligation. The guests are the occupants. The two can be the same person, and the entities stay decoupled so the reservation records who pays and who stays.
No field for a day block
A day block has no representation in the draft. The stay interval holds a check-in date and a check-out date in ISO 8601 format, and nothing else. A day room sells on a clock. A ten-to-four block or a four-hour rest between flights sits on a time window the specification cannot carry.
The Lodging Technical Council counts Hilton and Marriott among its members. The draft’s stay interval holds dates and no times, so the protocol cannot carry a day-room clock.