AI Agents Are Coming for E-Commerce — What Autonomous Shopping Means for Your Store
- Four competing protocols now govern how an AI agent pays a merchant: OpenAI/Stripe’s Agentic Commerce Protocol (ACP), Google’s Agent Payments Protocol (AP2), Visa’s Trusted Agent Protocol, and Mastercard Agent Pay. None of them replace the need for clean product data — they sit underneath it, at the payment and identity layer.
- OpenAI retired ChatGPT’s in-chat Instant Checkout on 24 March 2026, under six months after its 29 September 2025 launch, after fewer than 30 of Shopify’s millions of merchants went live with it. Agents still find products in chat; the purchase now happens back on the merchant’s own site.
- That retreat raises the stakes for WooCommerce stores rather than lowering them: if the agent hands off instead of completing the sale itself, your product pages and checkout carry the transaction, not just the discovery.
- Stores with structured, machine-readable product data — accurate specs, schema markup, unambiguous policies — are what every one of the four protocols needs to find before any payment mandate can execute.
The working assumption behind most “get ready for AI shopping agents” advice, including the first version of this post, is that agents complete the purchase themselves, inside the chat window, and a store’s job is to feed them clean data and stay out of the way. That assumption was already out of date the day it was written: OpenAI had quietly retired ChatGPT’s native in-chat checkout weeks earlier, and four competing protocols for how an agent identifies itself and pays a merchant had been live for months without making it into the advice. None of it changes what a store does first — clean, structured, unambiguous product data — but it changes why that work pays off, and what “agent-ready” now has to mean underneath the marketing language.
What AI Agents Actually Look for When They Visit Your Store
Agents are not reading your marketing copy (“crafted with passion”). They are extracting structured data: dimensions, weight, materials, compatibility, certifications. If your product page does not have these as distinct, parseable fields rather than buried in a paragraph, the agent either guesses or moves to a competitor that lists them explicitly.
Google’s Product and Offer schema tell AI systems the price, availability, SKU, and review rating in a machine-readable format. Stores without schema markup force the agent to infer this from rendered HTML, which introduces errors the agent has no way to catch before checkout — the same machine-readable-first shift is reshaping how businesses get cited in AI answers generally, not just in shopping agents specifically.
Agents complete purchases on behalf of users who stated preferences upfront (“free returns only”, “deliver within 3 days”). Your return and shipping policies need to be findable, machine-readable, and unambiguous. “We try to process returns quickly” is not parseable. “Free returns within 30 days, processed within 2 business days” is.
The Protocol War Nobody’s Product Page Mentions
“Add schema markup” is table stakes advice that predates agentic commerce by a decade. What’s new in 2026 is a second, separate layer underneath product data: how an agent proves its identity to a merchant and authorizes a payment without ever holding the buyer’s card number. Four organizations shipped competing answers within seven months of each other, and none of them talk to one another yet — a separate, narrower piece covers exactly what ships today versus what’s only announced for WooCommerce specifically; this section stays at the protocol level.
Agentic Commerce Protocol (ACP), co-developed by Stripe, OpenAI, and Meta and announced 29 September 2025, defines the checkout session itself: cart and product feed, payment-token delegation via OAuth 2.0, and order/webhook lifecycle events. It is the protocol behind ChatGPT’s shopping flow, and the one a WooCommerce store integrates against if it wants an AI agent to complete a purchase using tokens the store never sees in raw form.
Agent Payments Protocol (AP2), announced by Google on 17 September 2025 with more than 60 launch partners including Mastercard, PayPal, and Coinbase, works one layer up from ACP. It chains three cryptographically signed Verifiable Credentials — an Intent Mandate (what the user authorized), a Cart Mandate (the exact items and price the user approved), and a Payment Mandate (the credential the payment network actually processes) — into a non-repudiable audit trail of who authorized what, and within what limits.
Visa’s Trusted Agent Protocol, unveiled 14 October 2025 with Cloudflare, takes a different approach: it adds a cryptographically signed header to the ordinary HTTPS request, verified against a Visa-operated directory, so a merchant’s server can tell a known, accountable agent from an anonymous bot before the request ever reaches checkout logic. Mastercard Agent Pay, announced 29 April 2025, solves the same identity problem from the card-network side with Agentic Tokens — an extension of Mastercard’s existing tokenization service that binds a card credential to one agent, one merchant, and one consent policy.
| Protocol | Creator | Announced | What it actually governs |
|---|---|---|---|
| ACP | Stripe + OpenAI + Meta | 29 Sep 2025 | Checkout session, cart, payment-token delegation |
| AP2 | Google + 60 partners | 17 Sep 2025 | Signed mandate chain: intent → cart → payment |
| Trusted Agent Protocol | Visa + Cloudflare | 14 Oct 2025 | Cryptographic agent identity on the HTTP request |
| Agent Pay | Mastercard | 29 Apr 2025 | Tokenized card credential scoped to one agent |
None of these four protocols substitute for the others, and a WooCommerce store does not choose one and ignore the rest — the payment processor and card networks a store already uses determine which of these it can reach without writing new integration code. What all four have in common is the same precondition this post opened with: they authenticate a payment and a checkout session, not a product. Structured data is what makes the product findable and correctly priced before any of these four mandates gets created.
Why OpenAI’s Retreat From In-Chat Checkout Raises Your Stakes, Not Lowers Them
OpenAI’s Instant Checkout launched with Etsy on 29 September 2025 as the first live implementation of ACP. It shut down on 24 March 2026. Onboarding merchants proved harder than the launch announcement implied, and fewer than 30 of Shopify’s millions of merchants ever went live with it before OpenAI pulled the feature and pivoted to what it calls “agentic commerce”: ChatGPT still surfaces products in conversation, but the buyer now completes the purchase on the merchant’s own storefront, inside an in-app browser or a separate tab.
Every earlier version of this post’s advice treated that in-chat handoff as the finish line — get your data clean enough for the agent to complete the sale itself, and the store’s own checkout page barely matters. That premise no longer holds for ChatGPT specifically, and ChatGPT is the platform most of this advice was written for. If the agent’s job stops at discovery and the human finishes the transaction on your site, your product page, your checkout flow, and your page-load performance are back in the critical path, not routed around. The structured-data work in this post is unchanged; the reason it matters just got more direct.
The stores that thrive in the age of AI shopping agents are not the ones with the most persuasive copy — they are the ones with the most accurate, complete, and structured product data. The agent does not care about your brand story. It cares whether your Product schema says the item ships in 2 days and costs $49.99, and whether your own checkout page loads fast enough to keep the human who just arrived from an agent conversation.
How to Prepare Your Store
This is one piece of a broader shift covered across the AI for commerce teams guide series. Agent-readiness and human-readiness are mostly the same work. Cleaner product data, explicit specifications, accurate pricing, and clear policies convert better for humans too — the difference is priority. Traditional conversion work spends budget on button-color tests; agent-readiness spends it on the product feed and the policy text an agent actually parses.
- Add Product and Offer schema (JSON-LD) to every product page — price, availability, SKU, and rating as distinct fields, not prose.
- Move dimensions, weight, materials, and compatibility out of the description paragraph and into structured attribute fields WooCommerce exposes to the feed.
- Rewrite the returns and shipping policy as unambiguous, quantified statements: a time window and a process, not “we try to.”
- Confirm your payment processor’s roadmap for ACP, AP2, Visa TAP, or Mastercard Agent Pay before building custom integration work against any one of them.
- Check your bot-handling rules (robots.txt, WAF, rate limits) do not block the user agents ACP- and AP2-compliant agents identify themselves with.
- Load-test and profile your own checkout page — with Instant Checkout retired, ChatGPT hands the buyer back to it directly.
- Re-audit product data quarterly. Every protocol in this post shipped or changed within the last twelve months, and the pace is not slowing — see what changes next in e-commerce integrations through 2027.
Get the working checklists
The runbooks and decision checklists from these guides, as printable PDFs — free in the SoftXone guide library.
A structured-data and integration audit surfaces exactly which fields on your store an agent can’t parse today. See how SoftXone scopes that work →
References
- Schema.org Product MarkupSchema.org — structured data vocabulary AI shopping agents parse.
- Google Product Structured DataGoogle Search Central — Product schema implementation guide.
- Agentic Commerce ProtocolStripe — ACP specification: checkout, cart, payment and authentication delegation.
- Stripe and OpenAI launch Instant Checkout and ACPStripe Newsroom — the original 29 September 2025 announcement.
- OpenAI revamps shopping in ChatGPT after Instant CheckoutCNBC — the March 2026 retirement and merchant-adoption numbers.
- Announcing Agent Payments Protocol (AP2)Google Cloud Blog — the mandate chain and launch partner list.
- Trusted Agent Protocol OverviewVisa Developer Center — agent identity verification on the HTTP layer.
- Mastercard Debuts Agent PayPYMNTS — the April 2025 Agent Pay and Agentic Tokens announcement.
- Perplexity Shopping: How to Optimize Your StoreShopify — merchant-facing guidance on Perplexity’s shopping features.
Frequently asked questions
Which agentic commerce protocol should a WooCommerce store support?
None exclusively. ACP, AP2, Visa’s Trusted Agent Protocol, and Mastercard Agent Pay solve different layers — checkout session, payment mandate, and agent identity — and the payment processor a store already uses determines which of these it can reach without new integration work.
Did ChatGPT’s in-chat checkout go away?
Yes. OpenAI retired Instant Checkout on 24 March 2026 after fewer than 30 Shopify merchants went live with it. ChatGPT still surfaces products in conversation, but the purchase now completes on the merchant’s own site.
Does the protocol war change what a WooCommerce store should do first?
No. The first priority is unchanged: structured, machine-readable product data. What changed is the payoff — since agents now hand off instead of completing the sale, your own product and checkout pages carry the transaction, not just the discovery.
Is Perplexity’s shopping feature the same thing as ACP or AP2?
No. Perplexity’s Buy with Pro and Instant Buy are Perplexity’s own checkout features, the latter built on PayPal. ACP and AP2 are open protocols other platforms and payment networks use so independent agents can transact with any participating merchant.
Leave a Reply