The Universal Commerce Protocol, Explained for B2B Suppliers
A protocol, a cart and an agent arrived under one headline. Only one of them already matters to a supplier selling into Europe, and it is not the checkout.
Three different things are travelling under one headline. The universal commerce protocol (UCP) is a specification: a common language that lets software ask a business what it sells and how to buy it. Universal Cart is a Google product for shoppers, built on that specification and launched in the United States on 15 October 2026. An agent is software that acts for a person, and it may use either of them or neither. Most of the coverage since mid October treats the three as one, and for a supplier that sells to other companies the difference decides whether there is anything to do this quarter.
The short answer, for a B2B exporter selling into Europe: the protocol is worth an hour of reading, the cart is not aimed at you, and the agent is the part that already affects you, though not through checkout.
What the universal commerce protocol specifies
UCP is an open standard announced by Google on 11 January 2026 and co-developed with Shopify, Etsy, Wayfair, Target and Walmart. The specification is public at ucp.dev and on GitHub under the Apache 2.0 licence. It defines a conversation between two roles.
- The platform is whoever consumes capabilities. The specification's own examples are an app, an AI agent, a procurement system or another business.
- The business is whoever exposes them: a retailer, a supplier, a service provider.
The mechanism is discovery followed by negotiation. A business publishes a JSON file at a fixed address, /.well-known/ucp, listing the services it supports, the capabilities inside them and the payment handlers it accepts. Capabilities carry reverse domain names such as dev.ucp.shopping.checkout, dev.ucp.shopping.cart and dev.ucp.shopping.order. A platform sends its own profile with every request. The business intersects the two lists and picks the highest version both sides understand. The same service can be exposed over a REST API, over MCP for AI agents, or over A2A for traffic between agents. For payments an agent authorises on someone's behalf, UCP leans on a separate standard, the Agent Payments Protocol (AP2).
Two details matter to a supplier. First, the business stays merchant of record. It keeps the transaction, the liability and the customer relationship, and payment runs through its own payment provider. Second, the specification states that its roles apply equally to B2C, B2B and agent to agent commerce. On paper, the purchasing system at one of your customers could be a UCP platform and your web shop a UCP business.
On paper is the operative phrase. The capabilities published today sit under a shopping namespace: cart, checkout, order, discounts, fulfilment. As of 20 October 2026, the core concepts page of the specification has no capability for requesting a quote, which is where a great many B2B orders begin.
Universal Cart is a product, and an American one
Universal Cart is what Google built for consumers on top of the protocol. The launch post of 15 October 2026 describes a single cart that collects products from several retailers across Google Search, including AI Mode, and the Gemini app. It watches price and stock changes, surfaces promo codes and card perks from Google Wallet, and lets the shopper either pay with Google Pay inside the cart or move the items to the retailer's own cart. The checkout is powered by UCP. The retailers named are consumer brands such as Nike, Sephora, Target and Walmart, and the rollout is in the U.S.
The wider timeline points the same way. In January, Google said UCP checkout would start with eligible U.S. retailers and expand globally in the coming months, without naming a single country. On 16 September it said the new merchant capabilities were rolling out in the U.S., with Australia and Canada to follow early next year. No European market appears in any of these announcements.
For a manufacturer in Lyon or Stuttgart selling valves to maintenance departments, the cart therefore changes nothing today. Its buyers are not putting a gearbox next to a pair of trainers.
Where the agent sits, and why Google keeps it apart
The launch post draws the line itself. Google describes two tracks: agentic capabilities that act on the user's behalf, and practical tools such as the cart. The cart holds products a person has chosen. An agent is the thing that would do the choosing.
That separation puts the protocol in its place. UCP governs what happens after a decision: which capabilities a seller exposes, how a payment credential travels, who owns the order. It says nothing about how an agent arrived at that seller. Fetching a manifest from /.well-known/ucp presupposes that the agent already has your domain.
Before that moment, the agent did what assistants do. It read sources, compared suppliers and produced a shortlist. A buyer who asks an assistant for stainless steel ball valve manufacturers with ATEX certification gets names, not a cart. The supplier that is not named never receives the request, whatever its manifest declares. The purchasing side of this is covered in the supplier search that happens behind the login, and the Google surfaces involved are not a single product either, as Gemini is not Google AI Mode explains.
What changes for a European B2B exporter, and what does not
What does not change, today, is how your European customers order. Framework agreements, customer specific price lists, payment on invoice at 30 or 60 days, an order confirmation sent as a PDF. None of this runs through a Google Pay checkout, and the protocol does not yet model it. There is no deadline here, and no reason to rebuild an order process around a consumer launch on another continent.
What may change is cheap to prepare for.
- Read the specification. The core concepts page at ucp.dev takes under an hour and settles more than a stack of commentary. If you sell spare parts or consumables at list price through a web shop, those are the products closest to what UCP already describes.
- Ask your shop platform. Shopify co-developed the protocol, and other platforms may add support. Whether yours will is a question for its vendor, not for your developers.
- Keep product data in plain HTML. Any agent, with or without UCP, reads prices, availability and specifications more reliably from a page than from a PDF or from a configurator that needs JavaScript to render.
- Watch the country list. Google has named the U.S., then Australia and Canada. The day a European market appears, the question becomes concrete.
What has already changed is the step before any protocol. Assistants answer supplier questions in every language your customers use, and they name some companies and leave out others. That is measurable now: PSentry runs the same questions twice a month on ChatGPT, Claude, Gemini and Perplexity, language by language, and records which suppliers each answer names and which sources it cites. It does not change those answers and it does not touch checkout. It tells you whether you are on the shortlist an agent would start from.
A protocol only carries an order to a supplier that has already been chosen. For a B2B exporter in Europe, the interesting question in October 2026 is not whether to publish /.well-known/ucp. It is whether the assistants your buyers use would hand an agent your name in the first place.
What suppliers ask before touching UCP
Do I need to publish a /.well-known/ucp file now?
Not if you sell in Europe today: no European market has been named for UCP checkout, and the specification has no capability for quotes yet. Reading the core concepts page at ucp.dev and asking your shop platform vendor about support is enough for now.
Can the universal commerce protocol handle quote requests?
As of 20 October 2026, no. The published capabilities sit under a shopping namespace (cart, checkout, order, discounts, fulfilment), and the core concepts page has no capability for requesting a quote.
Who owns the order when an AI agent buys through UCP?
The business does. It stays merchant of record, keeps the transaction, the liability and the customer relationship, and takes payment through its own payment provider.
How does an AI agent find a supplier in the first place?
Not through UCP. The agent reads sources, compares suppliers and builds a shortlist before any protocol is involved, and fetching /.well-known/ucp presupposes it already has your domain.