Google Universal Commerce Protocol: What It Changes for Your E-Commerce and How Busony Can Help

Google has just opened a new chapter for online commerce with the Universal Commerce Protocol (UCP) and a dedicated onboarding guide in Merchant Center. This is no longer just a technical announcement: merchants now have a clear path to connect their e-commerce systems to Google's AI agents (Search, Gemini, shopping surfaces). UCP is set to become the "HTTP of commerce" — a standard language that lets agents discover products, fill carts, process payments, and track orders directly within AI interfaces.

This article explains, in operational terms, what UCP changes for retailers, how Google's new onboarding works, and how Busony can help you take advantage of it.

1. UCP in two minutes: the AI agents' language for buying from you

The Universal Commerce Protocol is an open standard that describes how an agent (for example an AI agent in Google Search, Gemini, or other surfaces) can interact with your e-commerce system to:

• browse your catalog,
• check prices, stock, promotions, and shipping costs,
• create and update a cart,
• initiate and finalize a payment,
• access order tracking.

Instead of building a specific integration for each new interface, you expose standardized endpoints once. Agents that understand UCP can then connect to them and orchestrate the entire purchase journey. [1][2][3]

Google emphasizes two important points in its documentation:

• you remain the merchant of record: it is always your store that carries the transaction, stock rules, pricing, taxes, and returns; [3][1]
• UCP does not impose a single checkout: it provides mechanisms to handle guest checkout or account-based journeys, building on your existing systems. [4][1]

2. Why Google is publishing a UCP onboarding guide now

Until now, UCP was mostly discussed among developers and platforms. Google now provides a merchant onboarding journey in Merchant Center, moving from a technical concept to a program with clear steps, forms, and a sandbox. [5][6]

The onboarding guide covers:

• creating and configuring a UCP profile in Merchant Center; [5]
• setting up identity linking — how an AI agent links a Google user to a customer account on your side (guest mode, linked account, OAuth); [1][5]
• integrating UCP checkout APIs: creating, updating, and finalizing payment sessions; [7][5]
• using a sandbox to test the integration with simulated orders before going live. [4][5]

In parallel, Google announces the extension of UCP with new modules such as Cart and Catalog, and a gradual opening of onboarding to more merchants. [6][8][9]

3. What this enables on the buying experience side

Once UCP is integrated, AI agents operating on Google surfaces can, in theory:

• understand concrete requests like "buy a white linen shirt, delivered by Friday",
• browse your products, check prices, availability, and delivery times in real time,
• fill a UCP cart,
• offer the user the option to pay directly in the interface with Google Pay or another supported method,
• create and track the order in your systems, without the user re-entering their information. [9][10][1]

For merchants, this potentially means:

• less friction for highly intentional queries; [10][1]
• better leverage of AI search modes (AI Mode, conversational search), which become conversion surfaces; [9][10]
• a new transactional channel running largely in a Google interface, but with your business rules. [3][1]

4. What Google requires from merchants for onboarding

UCP onboarding requires a certain level of data and technical maturity.

4.1. E-commerce prerequisites

• a clean Merchant Center: complete product feeds, errors corrected, return policies filled in; [4][5]
• correct structured data on your pages (schema.org, price, availability); [10]
• a controlled checkout on the back-end: ability to create orders via API, manage inventory, taxes, payment methods, etc. [7][1]

4.2. UCP technical steps

The core technical requirements: [1][7][4]

• publish a UCP profile describing your store (currencies, delivery zones, policies, etc.);
• implement REST checkout endpoints:
• session creation (price, cart, fees, delivery options),
• update (adding/removing products, address changes),
• finalization (payment success, order confirmation);
• choose an identity linking strategy: guest checkout or OAuth 2.0 recognition; [1][4]
• connect these APIs to your systems: ERP, OMS, CRM, logistics tools.

4.3. Merchant Center process

The onboarding guide also covers: [6][5]

• submitting a UCP program participation request;
• a sandbox testing phase with simulated orders;
• compliance validations;
• the switch to production with UCP session quality monitoring.

5. Strategic impact: SEO, acquisition, and customer relationships

5.1. SEO and visibility in an AI world

Recent updates show that Google wants to turn AI search modes into full transactional surfaces. With UCP, these modes will be able to not only recommend products but also purchase them directly. [9][10]

For retailers, this implies thinking not just in terms of "classic SEO ranking" but also in terms of being actionable by AI agents — working on both traditional signals and UCP eligibility signals. [10][9]

5.2. Acquisition and attribution

If conversions come through AI agents in Google interfaces:

• the product page is no longer the mandatory touchpoint;
• attribution must be rethought (identifying conversions from UCP sessions);
• marketing campaigns must be aligned with UCP logic. [9][10][1]

5.3. Customer relationship and CRM

When transactions partially take place in a Google interface, how do you ensure customers are properly integrated into your CRM journeys? UCP provides mechanisms to surface the necessary data, but these must be connected to your CRM and data stacks. [3][1]

6. How Busony can help you with UCP

At Busony, we already work on AI agent architectures, voicebots, and e-commerce integrations. UCP fits directly into these topics: connecting your systems to an ecosystem of agents that will speak commerce on your behalf.

6.1. Strategic framing

• Decoding UCP applied to your context (industry, size, sales models).
• Identifying priority use cases: products, segments, countries, and journeys where UCP delivers immediate value.
• Choosing between AI experiences "on Google" and experiences on your own interfaces.

6.2. Architecture and technical integration

• Audit of your Merchant Center, product feeds, and structured data.
• UCP architecture design: APIs to expose, security, identity linking, system roles.
• Implementation of UCP endpoints and integration with your existing IT systems. [7][4][1]

6.3. AI agents and Voice / Chat Commerce

UCP naturally complements voice agents and chatbots: the same building blocks that allow a Google AI agent to orchestrate a purchase can also be used by your own agents.

Busony can help you design conversational agents capable of interacting with your customers and your UCP endpoints, and monitor all these flows in a coherent framework.

7. Where to start?

A pragmatic action plan:

1. Fix the fundamentals: Merchant Center, product feeds, structured data, stock and price quality. 2. Map your purchase journeys and identify where a UCP journey adds the most value. 3. Launch a UCP pilot on a limited scope to learn without risk. 4. Prepare your CRM/data stacks to integrate UCP conversions. 5. Scale gradually, aligning UCP with your other AI projects (voicebots, chatbots, co-pilots).

Busony can support you on all or part of this journey — from strategy to implementation. [6][9]

Sources

[1] Under the Hood: Universal Commerce Protocol – Google Developers [2] ucp.dev [3] Universal Commerce Protocol Explained – Coveo [4] UCP Guides – Google Developers [5] UCP Onboarding – Google Merchant Center [6] Google UCP Merchant Onboarding – The Keyword [7] UCP – Google Developers [8] Google Expands UCP with Cart & Catalog – Search Engine Journal [9] Google Expands Universal Commerce Protocol – Search Engine Land [10] Google UCP: The End of E-Commerce as We Know It – Lengow