Agentic Commerce

Definition

Agentic commerce is retail in which autonomous AI agents take actions on both sides of the transaction. It covers two distinct shifts that are frequently conflated:

• Agents you run — software that operates inside your business, handling customer support and WISMO, inventory reorder decisions, margin exceptions, return-abuse investigation, and B2B quoting. These agents call your systems.
• Agents that buy from you — assistants inside ChatGPT, Google AI Mode, Gemini and elsewhere that discover products, compare them, and complete a purchase on a person’s behalf. These agents call you.

They share a data foundation and almost nothing else. The first is an operations and authorization problem. The second is a catalog legibility and protocol problem.

The two protocols

Two open standards now govern the inbound half.

The Agentic Commerce Protocol (ACP) was released by OpenAI and Stripe on September 29, 2025 under Apache 2.0 and powers Instant Checkout in ChatGPT. It defines machine-readable product feeds, a conversational checkout flow with stateful negotiation, and payment handling via delegate tokens.

The Universal Commerce Protocol (UCP) is Google-led and covers the full journey — discovery, purchase, and post-purchase support — on Google AI surfaces including AI Mode and Gemini, with merchant integration through Merchant Center and Google Pay.

Which one matters to a given merchant depends on channel mix. The merchant-side work behind both is largely the same: structured product attributes, reliable identifiers, and a callable surface over commerce data.

Why the catalog is the real work

Agents compare on attributes, not adjectives. A product whose weight, dimensions, or material composition lives in a prose description rather than a structured field is, to a shopping agent, a product with no weight — and it does not get shortlisted.

This is the part no platform does for you. Protocol plumbing will increasingly arrive as a feature of Shopify, commercetools, or Adobe Commerce. Attribute completeness, variant structure, specification data trapped in marketing copy, and the join keys between product, inventory and pricing are merchant-side work that pays off regardless of which standard wins.

What it is not

It is not agent-to-agent payment. Amazon Bedrock AgentCore Payments (GA August 18, 2026) covers microtransactions against a session budget — an agent paying for an API call, an MCP server, or another agent. That is a different layer from a shopping agent buying a product for a person.

It is not a chatbot on your storefront. A retrieval chatbot answering product questions is not agentic; an agent is defined by having tools and the latitude to decide which to call. See AI agent.

It is not settled. Two competing standards, thin public volume data, and immature attribution mean any confident revenue projection right now is a guess. The catalog work is the low-regret move.

Related terms

AI agent · Agentic Commerce Protocol · Universal Commerce Protocol · Model Context Protocol · Generative engine optimization · Amazon Bedrock AgentCore