Glossary
What is the Universal Commerce Protocol (UCP)?
Definition
The Universal Commerce Protocol is a proposed open standard for how AI agents interact with merchant systems across the whole shopping journey, not only the checkout. The Agentic Commerce Protocol covers the transaction; UCP reaches further back, into discovery, cart and fulfillment. It is early, and most merchants have nothing to implement yet.
At a glance
- CategoriesCommerce
- Related fieldsCommerce, Technical
- DifficultyIntermediate
At a glance
- UCP is Google-backed, developed with commerce platform partners, and published openly.
- Its scope is deliberately wider than a checkout specification: catalog, cart, order and order status.
- Nothing about it requires merchant action today. Support will arrive through commerce platforms.
- Details are still moving, so check the current specification before you rely on anything written about it.
How wide UCP is trying to reach
Scope is the whole difference. A checkout specification starts where the shopper has already chosen. UCP aims at everything around that too: how an agent finds a catalog, asks about a product, assembles a cart, and follows an order once it ships.
The ambition is one interface a merchant exposes once, which any compliant agent can use for any stage of the journey rather than for the payment alone.
Whether that survives contact with real merchant systems is the open question. Broad standards are harder to agree than narrow ones, because the wider the scope, the more parties have to say yes to each piece.
No reason to bet on either yet
Standards fights are normal and slow. This one is not yours to resolve.
The cost of picking wrong sits almost entirely with your commerce platform, which is the party writing the implementation. Your exposure is the data underneath, and both specifications want the same data: accurate price, live stock, real shipping cost, a stated return policy, clean product identity.
So stay unconvinced and stay ready. A brand that spends this quarter arguing ACP versus UCP, then discovers half its catalog has no GTIN, has optimized the wrong thing.
Two standards coexisting is an ordinary outcome anyway. Payments has lived with several for decades.
What to do while the standards argue
- Implement nothing protocol-specific. Unless you run your own commerce stack and have engineers idle, there is no merchant-side work here that pays off yet.
- Fix what both specifications assume you already have. Product identity, price, availability, shipping cost, returns. Product feed optimization covers most of it and pays off in channels you already use.
- Put the question to your platform quarterly. Which protocols are supported, which are planned, and what would be asked of you. A one-line answer each quarter is enough.
- Write down the commercial terms you would accept before anyone asks you to sign. Fee ceiling, eligible categories, whether you require a customer email.
UCP and ACP side by side
| Agentic Commerce Protocol | Universal Commerce Protocol | |
|---|---|---|
| Scope | Checkout and payment | Discovery through fulfillment |
| Behind it | OpenAI with Stripe | Google with commerce platform partners |
| Maturity | Published, with a live implementation | Published, adoption still forming |
| What a merchant does now | Enable it through a platform | Wait |
| Your main risk | Fee terms you did not model | Building to a spec that keeps moving |
Frequently asked questions
-
Is UCP competing with ACP?
In practice yes, though neither is framed that way. They overlap on the transaction and differ on scope, and both are backed by companies with an interest in agents shopping on their surfaces. Whether the industry lands on one, two or a merged standard is genuinely unknown.
-
Do I have to choose between them?
No, and you probably will not be asked to. Commerce platforms will support whatever gets adoption, the way they already support several payment methods. Choosing is a platform decision unless you built your own checkout from scratch.
-
When will UCP actually matter to my business?
When your commerce platform says it is available and an assistant your customers use is sending volume through it. Both conditions, not one. Until then the name is worth knowing and nothing more, which is unsatisfying but honest.
-
Is there anything useful I can do today?
Yes, and none of it is protocol work. Make product data accurate and complete, get facts out of images and into text, keep price and stock consistent across feed, page and markup. That pays off in agentic commerce whichever specification wins, and in paid shopping meanwhile.