Skip to content
Free score
Platform guides

WooCommerce agent-readiness: the complete checklist

What WooCommerce supports for AI shopping agents as of October 2026 (MCP, Store API, UCP, ACP) and a prioritised checklist to get your store ready.

By the ConversionVector teamUpdated 13 min read

Contents

Direct answer: As of October 2026, WooCommerce's agentic commerce page lists its Model Context Protocol (MCP) integration as beta and the WordPress Abilities API as live. Google's Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP) route through Stripe are both "coming soon". WooCommerce says MCP helps AI assistants manage a store, not check out shoppers. So for most WooCommerce stores, agent readiness today means the basics: let shopping agents in, fill the gaps in WooCommerce's built-in product data (brand, shipping and returns), keep guest checkout on and free of captchas for verified agents, and keep Google Merchant Center accurate. Add protocol checkout when official support reaches your market.

This guide is for WooCommerce store owners, ecommerce leads and the agencies and developers who run their stores. It covers what WooCommerce officially supports, what its core code puts in your pages, a checklist in priority order, and how to judge the third-party plugins that promise UCP or ACP today.

Last verified: 27 October 2026 against WooCommerce's agentic commerce page and developer documentation, the WooCommerce 11.2.1 source code, the WordPress.org plugin directory, and documentation from Stripe, Google and OpenAI.

Where WooCommerce stands (October 2026)

CapabilityStatus per WooCommerceWhat it means for you
MCPBeta. "AI assistants can read your store's products and orders. Requires WooCommerce 10.9 or later. Built on the Abilities API in WordPress 6.9."A way for your team's AI tools to work with products and orders. Not a shopper checkout
WordPress Abilities APILive. "Built into WordPress core."The framework MCP runs on. Plugins can register their own abilities
UCP (Google)Coming soonNo official WooCommerce UCP checkout yet. Google's own UCP checkout runs through Merchant Center
ACP (Stripe Agentic Commerce Suite)Coming soon. "Agentic checkout is coming to Stripe for WooCommerce"Only through the Stripe extension. WooCommerce says stores on WooPayments "can't use it yet"
Store APIPublic, unauthenticated, "for the development of customer-facing cart, checkout, and product functionality"A documented, machine-friendly route to products, basket and checkout already exists on your store
Google Merchant CenterThrough the Google for WooCommerce extensionSyncs your products to Merchant Center, the product data source for Google's shopping surfaces

WooCommerce's August 2026 selling through AI post is more upbeat about ACP, saying it is "rolling out to US businesses now". Stripe's documentation describes the Agentic Commerce Suite as a private preview "available in the US, Canada, and select European countries", with a waitlist. Treat the status page as the baseline and confirm with Stripe before planning around it.

On the Google side, Merchant Center Help says UCP-powered checkout in AI Mode and Gemini applies to products eligible in the United States, Canada and Australia, and is "available for select merchants at this time", through an interest form. Google Universal Cart for retailers covers what that means for stores in other markets.

Our Agent Commerce Index Q4 2026 identified none of the retailers it measured as running WooCommerce, so we have no Index figures for the platform. Everything below comes from WooCommerce's documentation and source code, and from the checks in our Agent Conversion Score specification (v0.6).

What WooCommerce MCP is, and is not

Some agency posts describe WooCommerce MCP as a way for ChatGPT to buy from your store. It is not. From the developer documentation, as of 27 October 2026:

  • It is a developer preview. "Implementation details, APIs, and integration patterns may change in future releases."
  • There is no WooCommerce setting to turn on. It runs on the WordPress Abilities API and needs the separate MCP Adapter plugin, which "WooCommerce does not bundle".
  • It authenticates as a store user. Remote connections use a WordPress username and an Application Password. The docs say: "Do not use your account password or a WooCommerce REST API key."
  • It works on products and orders. The built-in abilities query, create, update and delete products, and query orders, update order status and add order notes. The docs carry a data privacy notice, because order data includes customers' personal details.
  • The endpoint has moved. Clients connect to the MCP Adapter's default server. The docs say the older /wp-json/woocommerce/mcp endpoint is removed in WooCommerce 11.3 (11.2.1 was the latest release when we checked), so update any older set-up instructions.

What this means: MCP can be useful for your team, for example bulk-editing products or looking up orders from an AI assistant. It does not make you visible to shopping agents. Because it acts with a real user's permissions, follow the docs' advice to use a dedicated user with the minimum capabilities the task needs, and revoke the Application Password when you are done.

What WooCommerce core puts in your product pages

Before the checklist, it helps to know what a stock WooCommerce store already gives agents. We read the structured data class in the WooCommerce 11.2.1 source. On a product page it outputs Product JSON-LD with:

  • Name, description, image, URL and SKU. If a product has no SKU, the product ID is used instead, which is not a real product identifier.
  • GTIN, only when the "GTIN, UPC, EAN or ISBN" field holds a valid 8- or 12- to 14-digit number. WooCommerce added that field in version 9.2, on products and variations.
  • An Offer with price, currency, availability, a price-valid-until date and the seller's name. Variable products whose variations have different prices get an AggregateOffer with the lowest price, highest price and number of offers. A URL that selects one variation gets a single Offer for it.
  • Ratings and reviews, where they exist.

It does not output a brand, shipping details or a return policy. The development code on GitHub, marked for 11.3, adds a link-only return policy that points to your refund page, but that is not in a release yet. Those gaps are where most of the work below sits, and SEO plugins often replace WooCommerce's output altogether, so check what your store actually serves.

The checklist

Items are in priority order within each section. Each maps to a check in our Agent Conversion Score specification v0.6, so you can see how it is scored.

1. Access: let agents reach your pages

CheckHow to do it on WooCommerceSpec
robots.txt does not block shopping agentsWordPress serves a virtual robots.txt unless there is a physical file, and SEO plugins and hosts often edit it. Open /robots.txt and look for Disallow: / under OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-User or *ACC-01 to ACC-09
Product pages return 200 to agentsSecurity plugins (firewalls, "bad bot" lists), managed-host firewalls and CDNs can return 403 or 429. Check their logs for AI user agentsACC-10 (score capped at 40 if it fails)
No JavaScript challenge or captcha served to agentsTurn off "under attack" or browser-check modes for product, basket and checkout URLs, or exempt verified botsACC-12
Product pages respond in under 3 secondsCache product pages, so agents are not kept waiting on uncached PHPACC-13
No consent or age gate hiding product contentCookie banners are fine if the content is in the HTML underneathACC-14

Separate training crawlers from shopping agents. Blocking GPTBot or Google-Extended is a training decision. Blocking OAI-SearchBot or ChatGPT-User takes you out of ChatGPT's shopping answers. Are you blocking AI shopping agents? has the full decision table and CDN settings.

2. Legibility: make product data readable

CheckWhat to verify on WooCommerceSpec
Product JSON-LD on every product pageView source, not the inspector. Core prints its JSON-LD in the page footer, so scroll to the bottomLEG-01
Offer with a numeric priceCore outputs one. Check that an SEO or page-builder plugin has not replaced it with something weakerLEG-02 (score capped at 50 if it fails)
priceCurrency and availabilityCore includes both on every OfferLEG-03, LEG-04
Real identifiersFill the GTIN field and set real SKUs. Without a SKU, core falls back to the product IDLEG-05
BrandNot in core's structured data. Add it with your SEO plugin or a small filter on woocommerce_structured_data_productLEG-06
Organization JSON-LD with sameAsCore does not output it. Most SEO plugins can, from their site settingsLEG-07
Name and price in the server-rendered HTMLSome page builders and quick-view themes load price with JavaScript. Fetch the page with curl and checkLEG-08

Two common problems on WooCommerce are duplicate Product blocks (core and an SEO plugin both emitting, sometimes with different prices) and variable products that show only a price range. Product structured data for AI agents has examples, and Google's Rich Results Test validates product markup.

3. Offer: make terms machine-readable

CheckHowSpec
Structured price matches the visible priceWatch for tax display settings (inclusive or exclusive), currency switchers and page caching producing a mismatchOFF-01
Price visible without login or region gateWholesale and "log in to see prices" plugins hide price from agentsOFF-02
Shipping cost and delivery timeCore does not add shippingDetails. Add it through your SEO or feed plugin, and state delivery time on the product pageOFF-04, OFF-05
Returns terms in structured dataCore does not add a return policy (as of 11.2.1). Add hasMerchantReturnPolicy to the Offer or your OrganizationOFF-06
Currency explicit on the pageShow the currency code or symbol next to the priceOFF-07

If you sell in more than one currency, give each currency its own fetchable URL and make sure the structured price matches what that URL shows. A page-fetching agent does not carry your currency cookie, so it sees whatever your default is.

4. Transact: let an agent buy

CheckHow on WooCommerceSpec
Guest checkout onWooCommerce > Settings > Accounts & Privacy > "Enable guest checkout". The docs note that customers still need an account to buy subscriptionsTRX-01 (score capped at 60 if it fails)
Basket reachable by agentsMake sure /cart/, /checkout/ and the Store API (/wp-json/wc/store/v1/) are not blocked by your firewall or security pluginTRX-02
No captcha on basket or checkoutAnti-fraud plugins often add reCAPTCHA or Turnstile to checkout. Limit them to payment submission or risk-based triggers, and exempt verified agentsTRX-03
An agent can put a product in the basket and reach checkoutKeep the Store API's cart/add-item endpoint working for anonymous sessions, and keep the standard add-to-basket form in the page HTML. Our basket test uses the Store API on WooCommerce storesTRX-10
Product feedGoogle for WooCommerce syncs your catalogue to Merchant Center. The Store API's product endpoints also count as a machine-readable catalogueTRX-07
Payment methods declaredList accepted methods on the page and in structured dataTRX-08
Variations as their own offersCore outputs an AggregateOffer for variable products, not a ProductGroup. Agents choosing a size or colour need each variation's price and stock, so add ProductGroup with hasVariant if your SEO plugin supports itTRX-09
UCP / ACP / MCP discoveryWait for official support (see the status table), or test a plugin on stagingTRX-04, TRX-05, TRX-06

The WooCommerce Store API is a real advantage. It is unauthenticated, cart sessions use cookies, and write requests need a nonce, which a well-behaved agent can obtain the same way your theme does. Many other platforms have no public equivalent. Page-fetching vs browsing agents explains why server-rendered basket actions matter for agents that do not run JavaScript.

5. Trust: make your policies easy to find

Publish clear returns, delivery and contact pages, link them in the footer, and keep them consistent with your structured data. Agents compare stores on these terms, and a returns window in your markup that differs from your returns page undermines both.

Third-party UCP and ACP plugins

Because official UCP and ACP support has not shipped, several plugins on WordPress.org offer pieces of it. We checked them through the WordPress.org plugin directory on 27 October 2026:

Plugin (as listed)VersionWhat it describesOur notes
UCP/ACP Agent for WooCommerce0.1.0UCP and ACP endpoints, with UCP conformance claimed against protocol version 2026-04-08First version, listed September 2026
SDX AI Readiness Toolkit for WooCommerce0.4.0A UCP profile, an MCP server, ACP checkout and a Merchant Center feedPre-1.0
WPMR Agentic Checkout for WooCommerce1.3.1Checkout inside ChatGPT ("Buy it in ChatGPT")Built around Instant Checkout, which OpenAI scaled back in March 2026 to focus on product discovery
SM Agent Kit2.1llms.txt, agent manifests, content signals and a read-only product feedNo checkout or payment

The first three reported fewer than 10 active installations. SM Agent Kit reported about 60. None had any reviews. That does not make them bad, but nobody has proved them in production yet. Before installing one:

  1. Read exactly which endpoints it exposes and which protocol version it targets. Protocols are still changing month to month.
  2. Check how it handles payment. A plugin that advertises checkout but cannot take payment can leave you with abandoned orders.
  3. Test on staging, including stock, tax and shipping calculation.
  4. Plan to remove it when WooCommerce's official support ships.

On the OpenAI change: in March 2026 OpenAI said "the initial version of Instant Checkout did not offer the level of flexibility" merchants needed, and that it would let merchants "use their own checkout experiences" while it focuses on product discovery (OpenAI). That makes a clean, agent-friendly checkout on your own store more important, not less.

What to fix first

This week (no developer needed):

  1. Open /robots.txt and your security plugin and CDN settings. Make sure shopping agents are allowed.
  2. Turn on guest checkout.
  3. Take the captcha off basket and checkout, or limit it to risky sessions.
  4. Run the free Agent Conversion Score to get a baseline.

This month:

  1. Fill the structured data gaps: one Product block per page, real SKUs and GTINs, brand, shipping details and returns policy.
  2. Check that price and the add-to-basket form are in the server-rendered HTML, especially on variable products, and that the Store API is not blocked.
  3. Install Google for WooCommerce and fix any Merchant Center issues.

This quarter:

  1. If you take payments through the Stripe extension, join Stripe's waitlist and watch WooCommerce's agentic commerce page for ACP. If you use WooPayments, that route is not open yet.
  2. If you sell in the US, Canada or Australia, look at Google's UCP interest form and requirements.
  3. Use MCP internally only if it helps your team, with a least-privilege user.

Common mistakes

  • Treating MCP as a sales channel. WooCommerce describes it as a tool for managing the store.
  • Using a REST API key for MCP. The docs say to use an Application Password.
  • Security plugins blocking every bot. "Block AI bots" toggles can include the shopping agents you want.
  • Assuming core structured data is complete. As of 11.2.1 it has no brand, shipping or returns.
  • Two schema sources. Core and an SEO plugin both emitting Product, with different prices.
  • Installing an early protocol plugin on a live store without testing.

Sources

Questions

Does WooCommerce support AI shopping agents?
Partly, as of October 2026. WooCommerce's agentic commerce page lists its MCP integration as beta and the WordPress Abilities API as live, while Google's UCP and Stripe's ACP route are both listed as coming soon. WooCommerce says MCP helps AI assistants manage a store, not check out shoppers. Agents can still read and buy from a well-built WooCommerce store through its pages and its public Store API.
How do I turn on WooCommerce MCP?
There is no WooCommerce setting for it. The developer documentation says MCP is a developer preview, needs WooCommerce 10.9 or later on WordPress 6.9, and needs the separate MCP Adapter plugin, which WooCommerce does not bundle. Remote clients authenticate with a WordPress Application Password for a dedicated, least-privilege user, not with your account password or a WooCommerce REST API key.
Can AI assistants check out on my WooCommerce store?
Not through an official WooCommerce protocol yet. WooCommerce says agentic checkout is coming to the Stripe for WooCommerce extension through Stripe's Agentic Commerce Suite, which Stripe describes as a private preview in the US, Canada and select European countries. Stores on WooPayments can't use it yet. Browsing agents can already use your normal basket and checkout if your security settings let them.
Should I install a third-party UCP or ACP plugin?
Treat them as experiments. The four agent-commerce plugins we checked on WordPress.org on 27 October 2026 were early versions with no reviews, three of them reporting fewer than 10 active installations. One was built around ChatGPT Instant Checkout, which OpenAI scaled back in March 2026. Test on staging and read exactly what each implements.
What should a WooCommerce store fix first?
Make sure shopping agents are not blocked by robots.txt, a security plugin or your CDN, turn on guest checkout, take the captcha off basket and checkout for verified agents, and fill the gaps in WooCommerce's built-in structured data: brand, shipping and returns. These work today on any WooCommerce store, whatever happens with protocols.

Published . Last updated . More in Platform guides and the guide library.

Related guides