Agentic commerce is shopping where an AI agent does some of the work for the customer: it searches, compares, builds a cart and, in some cases, completes checkout with the shopper's approval. The agent might be ChatGPT, Google's AI Mode or Gemini, or a retailer's own assistant. For merchants, it means your products must be readable and purchasable by software, not only by people on your website. As of November 2026, discovery inside AI assistants is well established, while agent-completed checkout is limited: Google's in-AI checkout is in phased early access, and ChatGPT sends shoppers to merchants' own checkout.
Agentic commerce in plain English
Traditional ecommerce has one path: a person visits your site, browses, adds to cart and pays. Agentic commerce adds a middle layer. The shopper tells an assistant what they want ("a waterproof hiking jacket under $200, delivered by Friday"), and the assistant does the legwork across many stores. Depending on the platform, it either sends the shopper to your site to buy, or completes the purchase through a standard protocol while you remain the seller.
Three things make this possible:
- Structured product data the agent can trust: feeds, catalog APIs and on-page structured data.
- Protocols that define how agents talk to stores, such as Google's Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP), whose lead maintainers are OpenAI, Stripe and Meta.
- Payment methods built for delegation, such as tokenized cards that let an agent pay without ever seeing the card number.
Who does what
This table shows the five parties in an agent-led purchase and what each one is responsible for.
| Party | Role | Examples (as of Nov 2026) | What it needs from the store |
|---|---|---|---|
| Shopper | States the need, approves the purchase, receives the goods | A consumer or a business buyer | Clear prices, delivery dates, returns policy and trust signals |
| Agent (AI surface) | Interprets the request, finds and compares products, assembles the cart, asks for approval | ChatGPT; AI Mode in Google Search; Gemini; retailers' own assistants | Accurate, current product data; access to pages or feeds; stock and price on request |
| Protocol | Standard language for discovery, cart, checkout, identity and order updates | UCP (Google and partners); ACP (OpenAI, Stripe and Meta); MCP as a common transport for tools | Endpoints that implement the protocol, or a platform that does it for you |
| Store (merchant) | Validates the order, calculates tax and shipping, accepts or declines, fulfills, handles returns | Your Adobe Commerce or Magento store, and its ERP and OMS | Remains the merchant of record under both UCP and ACP |
| Payment provider | Issues and processes tokenized credentials, screens fraud, settles funds | Google Pay with Google Wallet; Stripe Shared Payment Tokens; other PSPs | A PSP integration that supports the agent's payment method |
What is actually live (November 2026)
This area changes month to month. Here is what the companies' own pages say as of November 2026:
- Google: Google introduced the Universal Commerce Protocol in January 2026, developed with Shopify, Etsy, Wayfair, Target and Walmart. Google's Merchant Center help describes UCP-powered checkout as a buy button on eligible listings in AI Mode in Search and Gemini, paid with Google Pay. It applies to products in the US, Canada and Australia, and access is through a phased early access program.
- OpenAI: On March 24, 2026, OpenAI said the first version of Instant Checkout had not offered the flexibility it wanted, so it is letting merchants use their own checkout while it focuses on product discovery. Merchants share product feeds through the Agentic Commerce Protocol, directly or through providers such as Salesforce and Stripe, and Shopify merchants are covered through Shopify Catalog. Retailers that want a deeper native experience can build a ChatGPT app; Walmart launched one with account linking and loyalty.
- Stripe: Stripe documents ACP and Shared Payment Tokens for agent purchases, and separately the Machine Payments Protocol (MPP), co-authored with Tempo, for agents paying for APIs and services.
- Adobe: Adobe has stated that it is committed to supporting ACP and UCP for Adobe Commerce. Its Experience League page for the Commerce MCP, last updated October 8, 2026, marks it as coming soon. What you can use will depend on your edition, licence and version.
For a side-by-side view of the protocols, read UCP vs ACP vs MPP explained.
Why it matters to merchants now
Even where agents do not complete checkout, they already shape which products a shopper sees. If an assistant cannot read your stock, price or returns policy, it will recommend a competitor whose data it can read. The groundwork for agent checkout (clean data, reliable APIs, clear policies) also improves search, marketplaces and your own site. That makes the preparation low-regret even while the protocols settle.
Agentic commerce readiness checklist
Product data
- Every live product has a unique ID, GTIN where one exists, brand, clear title, full description, price, currency and availability.
- Variants (size, color) are modeled consistently so an agent can pick the right one.
- Feeds refresh when price or stock changes, not once a week.
- Google Merchant Center is free of disapprovals and warnings.
- Product pages carry valid Product structured data. See our product schema guide.
Access
- robots.txt does not block the crawlers of assistants you want to appear in (for example OAI-SearchBot for ChatGPT search).
- Bot protection and rate limits let legitimate agent and crawler traffic through.
Commerce APIs
- Stock and price can be queried in real time.
- Cart and checkout can be created via API, including tax and shipping calculation. Headless-ready stores are ahead here.
- Order status, shipment and refund updates are available as events or webhooks.
Payments and risk
- Your payment provider supports the agent payment methods you plan to accept (for example Google Pay, or Stripe Shared Payment Tokens).
- Fraud rules account for orders placed through agents, which may look different from normal browser sessions.
Policies and identity
- Shipping, returns and warranty policies are written clearly and available in machine-readable form where the protocol asks for it.
- If you run loyalty or B2B pricing, plan for account linking (OAuth), which both UCP and ACP support.
Measurement
- Orders and referrals from AI surfaces can be identified in analytics and your order data.
Where MCP fits
The Model Context Protocol (MCP) is a general standard for connecting AI applications to tools and data. In commerce it often acts as the transport: UCP can be bound to MCP, and Adobe describes its upcoming Commerce MCP as a way to build agentic experiences from discovery to checkout using real-time commerce data and tools. Our MCP for ecommerce guide explains it in more detail.
Risks and open questions
- Protocol churn. Specs are versioned and still changing. Prefer platform-level support or a thin integration layer over deep custom work.
- Customer relationship. When the purchase happens inside an assistant, you may see less of the journey. Both main protocols keep the merchant as merchant of record, but data sharing varies.
- Returns and disputes. Agree how agent-placed orders are handled when something goes wrong.
- Regional availability. Many programs launch in the US first. Check eligibility for each market you sell in.
Agentic commerce is one part of a wider set of AI changes; our guide to AI in ecommerce ranks the other use cases.
FAQ
Do I need to implement a protocol myself?
Not necessarily. Platforms and payment providers are adding support, and some merchants will get basic participation through their platform or feed provider. Custom implementation makes sense when you need control over checkout logic, B2B pricing or loyalty.
Will agents replace my website?
No. As of November 2026, ChatGPT sends shoppers to merchants' own checkout, and Google's in-AI checkout is in phased early access. Agents are mainly a discovery and comparison channel for now.
Is agentic commerce available outside the US?
Partly. Google lists the US, Canada and Australia as eligible for UCP-powered checkout, with access phased. Check each program's current country list.
Getting ready
Start with the data and access sections of the checklist; they pay off whatever protocol wins. Mistri's agentic commerce services cover readiness audits, feeds and protocol integration for Adobe Commerce and Magento stores.
Sources
Google Developers Blog: Under the hood of the Universal Commerce Protocol (January 11, 2026); Google Merchant Center Help: About UCP-powered checkout; OpenAI: Powering product discovery in ChatGPT (March 24, 2026); Agentic Commerce Protocol on GitHub (maintainers and versions); Stripe Docs: Agentic Commerce Protocol; Adobe Developer Blog: The architectural foundations of an agentic commerce platform; Adobe Experience League: Commerce MCP overview. Checked November 2026.


