Learn / Protocols and standards
Do you need to adopt a commerce protocol at all?
Most merchants do not implement a commerce protocol directly, because the protocols are adopted by platforms and payment providers rather than by individual stores. What matters for a merchant is which protocols their platform supports and whether their own product data is good enough to be worth transacting on, since no protocol compensates for a price that is not published.
For most merchants the answer is no, and not because the protocols are unimportant. They are being implemented by platforms and payment providers, which means the decision for a typical store is which platform it is on rather than which specification it implements.
What the protocols are doing
They standardise how an agent, a merchant and a payment provider agree on what is being bought and how it will be paid for. Google published the Agent Payments Protocol on 16 September 2025, saying it was built with more than sixty collaborating organisations. OpenAI and Stripe published the first version of the Agentic Commerce Protocol on 29 September 2025 under Apache 2.0, according to the protocol’s own repository. Google announced the Universal Commerce Protocol at NRF on 11 January 2026, built with Shopify, Etsy, Wayfair, Target and Walmart, and said on its company blog that more than twenty further companies had endorsed it.
Those are platform and payment level agreements. A merchant on a hosted platform inherits whatever their platform supports.
What a protocol cannot do for you
This is the part worth being firm about. A protocol carries data. It does not create it.
- If your price only exists after scripts run, a protocol has no price to carry.
- If your availability is product level, a protocol transmits an answer to the wrong question.
- If your shipping cost is unpublished, your delivered total is still uncomputable.
- If your bot rules block agents, nothing reaches the protocol layer at all.
Every one of those is fixable without adopting anything. See the agentic readiness checklist.
When it does become your question
On a custom stack, or where you are the payment provider, or where you have volume large enough that being a first party participant changes your economics. Those are real cases and they are a minority.
Even then, sequence it after the fundamentals rather than before them, and let measurement rather than principle decide which one. See how to tell which protocol your platform supports.
Questions
Am I falling behind by not implementing one?
Almost certainly not. Ask instead which protocols your platform supports and what it requires from you, since that is the layer where the decision actually sits for a store of ordinary size.
What if I run a custom stack?
Then the question becomes real, and it still comes after the fundamentals. A custom store with unreadable prices gains nothing from protocol support, because the protocol carries data it does not have.
Which one would I adopt if I did?
That follows from where your traffic comes from, which follows from measuring it. Adopting on principle rather than on evidence is how a small team spends a quarter on something no customer used.