PlatformDTC

Agentic commerce

What is agentic commerce?

Updated

Agentic commerce is commerce in which an AI agent completes steps a human shopper used to complete by hand: it reads a goal in natural language, queries merchant catalogs for real-time price and availability, compares options against stated constraints, and — where the merchant supports it — builds a cart and authorizes payment within limits the shopper set. For a merchant it is less a new sales channel than a new class of customer: one that never renders a page, never sees a promotion, and buys strictly on machine-readable data.

The definition that matters is the merchant-side one

Most definitions of agentic commerce are written for shoppers, and they all say roughly the same thing: you tell an assistant what you want and it goes and gets it. That framing is accurate and almost useless if you are the one selling, because it describes the half of the transaction you do not control.

The merchant-side definition is sharper. Agentic commerce is what happens when a meaningful share of your demand arrives from a client that does not render your page. It does not see your hero image, your urgency banner, your bundle upsell, or your carefully sequenced PDP. It reads whatever structured data you expose, and it decides on that. Everything you spent a decade optimising for human attention is invisible to it.

That is not a marketing problem. It is an architecture problem, and it lands on whoever owns the storefront, the catalog, and the checkout.

The three things an agent has to do to buy from you

Strip away the protocol arguments and every agentic purchase decomposes into the same three steps. A brand is "agent-ready" exactly to the degree that all three work without a human in the loop.

  • Discovery — the agent has to find your product and trust the data. This means a machine-readable catalog with real-time price and inventory, not a rendered page it has to guess at.
  • Cart and checkout — the agent has to be able to construct an order and get a price it can rely on, including shipping and tax, without simulating clicks in a browser.
  • Payment authorization — the agent has to prove that a specific human authorized this specific purchase, within limits, in a way you can verify and later defend against a dispute.

The demand is real and it converts better than human traffic

The reasonable objection to all of this is that it is a forecast dressed as a trend. That objection was correct a year ago and is not correct now, because the traffic is measurable and the conversion data has inverted.

Adobe measures sessions arriving from identifiable AI assistants — ChatGPT, Claude, Copilot, Perplexity, Google AI Mode — using referrer headers and user-agent classification. In Q1 2026, that traffic to US retail sites grew 393% year over year. Over the Nov–Dec 2025 holiday it was up 693% year over year.

The quality reversal is the more interesting number. In March 2025, AI-sourced traffic converted 38% worse than non-AI sources. By March 2026 it converted 42% better — and revenue per visit from AI referrals sat 37% above non-AI traffic, having been 128% below it a year earlier. Shoppers arriving via an assistant spend 48% more time on page and view 13% more pages per visit.

On the size of the prize, McKinsey projects agentic commerce could mediate $900 billion to $1 trillion in annual US retail revenue by 2030 — roughly 30% of projected B2C revenue — and $3 trillion to $5 trillion globally.

Most stores are not ready, and that is measurable too

The same Adobe research that found the traffic surge also found the bottleneck. Individual product pages score just 66% on machine readability — the lowest of any major page type on retail sites. A third of what is on the page an agent cannot reliably parse.

This is the single most actionable finding in the category. It says the constraint is not consumer adoption or protocol maturity; it is that the merchant surface was built for eyes. The brands that fix their machine-readable layer first are competing for agent-sourced demand against a field that mostly has not.

What this means for how you pick a platform

If agent-sourced demand is going to be a real channel, the questions you ask a commerce platform change. "Can I build a beautiful storefront" is table stakes. The questions that separate platforms now are whether the catalog is exposed as structured data by default, whether checkout can be driven by an API rather than a browser, whether agent actions are scoped and audited, and whether the platform is committing to the emerging protocols rather than waiting to see which one wins.

PlatformDTC was built from the agent side first: the same operations a merchant performs in the dashboard are exposed through the Agent Gateway as scoped, idempotent, audited API calls, and storefronts ship machine-readable product data without a plugin. Agent actions that move money pass a human approval gate before they execute.

Frequently asked questions

Is agentic commerce the same as AI-powered ecommerce?
No. AI-powered ecommerce usually means AI helping a human — recommendations, search ranking, generated copy, a support chatbot. Agentic commerce means an AI agent performing the transaction steps itself: querying the catalog, building the cart, authorizing payment. The distinguishing test is whether a human is in the loop for each step or only for the initial goal and the spending limit.
Do I need to support a specific protocol to sell to AI agents?
Not to be discovered. Assistants can already surface products from structured data on a normal indexed page, which is why machine readability is the highest-return first move. Protocol support — UCP, ACP, AP2 — matters for the cart and payment steps, where an agent needs a reliable programmatic path rather than a simulated browser session.
Does agentic traffic cannibalise my paid and organic channels?
The measured behaviour so far suggests it is additive and higher-intent rather than a straight substitution. Adobe found AI-referred visitors converting 42% better than non-AI traffic as of March 2026 with 37% higher revenue per visit, alongside longer sessions and more pages viewed — a profile that looks like considered purchases arriving further down the funnel.
How do I know if AI agents can already read my store?
Fetch one of your product pages with JavaScript disabled and check whether price, availability, variant and identifier survive in the raw HTML and in schema.org Product markup. If price and stock only appear after client-side rendering, an agent parsing your page is guessing. That single test predicts most of the machine-readability gap Adobe measured.

Sources

Related