Skip to content
U UpNorthHub

Preparing E-Commerce for the Agentic Commerce Era

Preparing e-commerce for the agentic commerce era — what ACP, AP2, and UCP actually mean for merchants, and how to get checkout-ready for AI agents.

Talal Emran

Talal Emran

Web Developer & Designer

Published

10 min read

preparing-ecommerce-for-the-agentic-commerce-era

Bain projects the US agentic commerce market will reach $300–500 billion by 2030 — 15 to 25% of total US e-commerce sales — while McKinsey puts the global figure at $3–5 trillion over a similar horizon. Those aren’t distant, speculative numbers anymore. Over 1 million Shopify merchants, along with Etsy, Glossier, SKIMS, Spanx, and Vuori, are already live on ChatGPT Shopping, and 45% of consumers report already using AI somewhere in their buying journey.

This guide breaks down what agentic commerce actually means for a merchant preparing for it in 2026: the protocol landscape that’s formed around it, what’s genuinely live versus still emerging, and the practical steps that matter regardless of which specific protocol ultimately wins out.

How We Evaluated This Guide

Every protocol name, launch date, and backer here is cross-referenced across multiple independent 2026 sources, since this is a genuinely new and fast-moving space where getting a date or a backer wrong is easy. We prioritized distinguishing what’s actually live and transacting today from what’s announced but still limited, since that distinction matters enormously for deciding what to actually build right now versus what to simply monitor.

What Agentic Commerce Actually Means

Agentic commerce is the model in which autonomous AI agents act as proxies for buyers — discovering products, comparing options against stated constraints, qualifying merchants, and in many cases completing checkout, without a human directly browsing a website. Instead of a person clicking through search results, an agent inside ChatGPT, Google AI Mode, Gemini, or Perplexity queries machine-readable catalogs and policies, shortlists merchants it can verify, and transacts through a checkout protocol.

One myth worth correcting directly: in most current implementations, AI agents recommend, and the shopper still buys on the retailer’s own site — full autonomous, unsupervised purchasing is less common right now than agent-assisted discovery that hands off to a human-confirmed checkout. Understanding that distinction matters for prioritizing what to build first.

The Protocol Landscape: Six Standards, Not One

shopping cart artwork

This is the part of agentic commerce that trips up most merchants trying to prepare for it — there isn’t a single standard to adopt. Six protocols currently define the working stack, each solving a different layer of the problem.

ProtocolBackersWhat It HandlesStatus as of 2026
ACP (Agentic Commerce Protocol)OpenAI + StripeCheckout conversation between agent and merchantLive — powers ChatGPT Instant Checkout, 1M+ Shopify merchants
UCP (Universal/Unified Commerce Protocol)Google + ShopifyProduct discovery and checkout across AI surfacesLive — launched January 11, 2026
AP2 (Agent Payments Protocol)Google + 60+ payment partnersPayment authorization and cryptographic proof of consentLive — donated to FIDO Alliance April 29, 2026
MCP (Model Context Protocol)AnthropicHow agents read context and connect to store dataLive — donated to Linux Foundation’s Agentic AI Foundation, Dec 2025
A2A (Agent-to-Agent Protocol)GoogleCommunication between multiple cooperating agentsEmerging, used in complex multi-agent negotiation scenarios
Visa TAP (Trusted Agent Protocol)VisaCard-network-level agent transaction trust signalsLaunched commercially in 2026 after piloting with 100+ partners

A full agentic transaction typically chains several of these together: a shopping agent running MCP for discovery still needs ACP or UCP for the actual checkout call, AP2 or Visa TAP for the authorization signature, and a settlement rail — a card network, Stripe, or a stablecoin rail like x402 — for the actual money movement. No single protocol covers the whole transaction end to end.

“Most large retailers have responded by integrating into ACP, UCP, and AP2 in parallel rather than picking one, on the same logic that drove early multi-channel strategies in mobile commerce.” — Eco, 2026 agentic commerce guide

Best for most merchants deciding where to start: don’t try to pick a single winning protocol — the pattern among large retailers already live is parallel integration across ACP, UCP, and AP2, treating this the same way multi-channel mobile strategy was treated a decade ago rather than betting on one standard.

How AI Agents Actually Decide Which Merchant to Recommend

Agents score merchants on three specific dimensions, and understanding them directly shapes what a merchant should prioritize fixing first:

  • Structural completeness — stable GTINs, fully populated product attributes, and fresh, accurate inventory data.
  • Semantic density — long-form, genuinely detailed product descriptions an agent can actually parse and reason about, not just a short marketing tagline.
  • Trust signals — external reviews on platforms like Trustpilot and Google Reviews, clear return policy language, and documented shipping speed.

This scoring model is the real reason structured catalog quality at the protocol layer is what agents actually evaluate — a visually polished storefront built for human browsing can still score poorly with an agent if the underlying structured data behind it is thin or inconsistent.

Best for merchants unsure where to invest first: audit against these three dimensions specifically before building any new protocol integration — a technically perfect ACP endpoint connected to an incomplete, poorly reviewed catalog still won’t get recommended.

The 2025–2026 Timeline, Condensed

A few dates are worth anchoring to directly, since this timeline moves the conversation from theoretical to concrete:

  • September 29, 2025 — OpenAI, Stripe, and Meta jointly announce the Agentic Commerce Protocol under an open Apache 2.0 license; ChatGPT Instant Checkout goes live first on Etsy in the US.
  • November 2024 — Anthropic’s Model Context Protocol launches, later becoming the standard way agents read context from a store’s own data, including via Shopify’s Storefront MCP endpoint.
  • January 11, 2026 — Google’s Unified Commerce Protocol launches, co-developed with Shopify, defining how products become buyable directly inside Gemini and Google Search.
  • April 29, 2026 — Google donates AP2 to the FIDO Alliance, the industry body behind passkeys, alongside version 0.2 and a “human not present” mandate for specific transaction types.
  • June 16, 2026 — Adyen launches Adyen Agentic, the first stack explicitly bridging ACP, UCP, and AP2 together, though currently in limited availability for US enterprise merchants only.
  • March 2026 — Checkout functionality inside ChatGPT partially rolled back toward discovery-only in some contexts, a reminder that even live implementations are still being actively adjusted.

That last point matters for setting realistic expectations: this space is still genuinely in motion, not a settled standard merchants can implement once and ignore.

A Practical Readiness Checklist

  1. Start with data, not protocols. Complete, accurate, structured product information — pricing, availability, shipping, returns — is the prerequisite every protocol depends on; fixing thin or inconsistent catalog data delivers value regardless of which specific protocol ultimately dominates.
  2. Implement Schema.org markup on every product page. Product, Offer, AggregateRating, and Review JSON-LD with complete required fields (name, image, offers with price and currency) is foundational groundwork shared across every protocol in the stack.
  3. Evaluate your commerce platform’s native support. Shopify merchants can enable Agentic Storefronts to become discoverable across AI surfaces with comparatively little custom engineering; confirm what your specific platform already supports before building custom integrations from scratch.
  4. Keep pricing and policy information consistent across every channel an agent might read. An agent encountering conflicting prices or return policies between your website and your product feed is a direct trust signal failure.
  5. Make sure order, refund, and return APIs actually work reliably. Agents surface broken flows immediately and consistently — a checkout or return process that merely tolerates human patience with an occasional glitch will get flagged and deprioritized by an agent far faster.
  6. Decide and document which agents you actually allow to transact on your behalf. This is a real, deliberate business policy decision, not a technical afterthought — merchants need an explicit position on which agentic checkout flows they’re comfortable authorizing.
  7. Track AI-referred traffic as its own distinct segment. Separating this channel in analytics from the start makes it possible to measure its actual growth and conversion behavior rather than discovering it buried inside generic referral traffic later.

Where Merchants Should Be Cautious, Not Just Eager

A few things are worth real skepticism rather than blanket enthusiasm. Marketplaces and courts are still actively deciding which agents may transact and under what conditions — the legal and platform-policy framework around agentic commerce is not fully settled, and a merchant integrating today is building on infrastructure that’s still being actively negotiated at the policy level, not just the technical one.

The AP2 “human not present” mandate specifically signals that the industry itself recognizes fully autonomous, unsupervised agent purchasing as a distinct, higher-risk category requiring its own explicit authorization framework — not something to treat casually even once the technical integration is complete.

Where This Guide Falls Short

A few honest limitations belong here, since agentic commerce is advancing faster than almost any other topic covered on this site.

  • This is the newest, least settled space in e-commerce right now. Protocol names, backers, and even specific feature rollbacks (like ChatGPT’s March 2026 checkout adjustment) are changing within the same year covered by this guide — verify current protocol status directly before committing significant engineering resources.
  • Full protocol coverage requires real, non-trivial engineering investment. Smaller merchants without dedicated technical resources will likely rely on their commerce platform’s native support (Shopify’s Agentic Storefronts, for instance) rather than building custom ACP or UCP integrations from scratch, which is a reasonable and common approach, not a compromise.
  • Legal and platform-policy frameworks are still forming. Which agents are permitted to transact, under what authorization standards, and with what liability framework remain active, unresolved questions — not fully settled infrastructure.
  • Market size projections vary significantly by source. Bain’s $300–500 billion US estimate and McKinsey’s $3–5 trillion global estimate reflect different scope and methodology — treat both as directional signals of a genuinely large shift, not precise forecasts to plan a specific budget around.

The Bottom Line

Agentic commerce isn’t a future hypothetical merchants can defer indefinitely — over a million Shopify merchants and several major consumer brands are already transacting through it, and nearly half of consumers report already using AI somewhere in their buying journey. But it’s also not a single standard a merchant can implement once and consider finished — six protocols currently share the stack, the legal framework is still being negotiated, and even live implementations like ChatGPT’s checkout flow are still being actively adjusted. The practical path forward is the same one large retailers are already taking: fix the underlying product data and structured markup first, since that work pays off regardless of which protocol wins, then integrate across ACP, UCP, and AP2 in parallel rather than betting the whole strategy on one standard.

FAQ

Do I need to pick one agentic commerce protocol, or should I support several?

Support several — the pattern among large retailers already live is parallel integration across ACP, UCP, and AP2, the same multi-channel approach that defined early mobile commerce strategy, rather than committing to a single standard.

What’s the single most important thing to fix before integrating any specific protocol?

Product data quality and structured markup — complete GTINs, accurate inventory, detailed descriptions, and Schema.org Product and Review markup are prerequisites every protocol depends on, and fixing them delivers value regardless of which protocol ultimately dominates.

Is agentic commerce actually live and transacting today, or is it still mostly theoretical?

It’s genuinely live — over 1 million Shopify merchants plus brands like Etsy, Glossier, SKIMS, and Vuori are already transacting through ChatGPT Shopping via ACP, though full autonomous checkout without human confirmation remains less common than agent-assisted discovery that hands off to a human-confirmed purchase.

What does AP2’s “human not present” mandate mean for merchants?

It signals that fully autonomous, unsupervised AI agent purchasing is treated as a distinct, higher-risk transaction category requiring its own explicit authorization framework, separate from the more common pattern of an agent recommending a product that a human then confirms and purchases.

Can a small merchant without a dedicated engineering team prepare for agentic commerce?

Yes, largely through their existing commerce platform rather than custom protocol integration — Shopify merchants, for example, can enable Agentic Storefronts with comparatively little custom engineering, making platform-native support the realistic path for most smaller businesses.

Keep reading