A WooCommerce store cannot complete a sale through a shopping agent today on WooCommerce's own code alone: the agentic features shipped in core are for store management, while the two shopper-facing checkout rails WooCommerce points at, Google's UCP and OpenAI's ACP, are still marked coming soon and are reached through partner extensions or third-party plugins.
Key takeaways
- WooCommerce's live agentic features (MCP and the Abilities API) let a merchant's own AI assistant read the store. No shopping agent buys through them.
- WooCommerce lists Google's UCP and Stripe's ACP as coming soon, and routes them through the Google for WooCommerce and Stripe for WooCommerce extensions.
- Core releases 11.0 and 11.1 shipped no agentic features, and the public request for native UCP support has sat open since January with no update.
- The work that helps regardless of rail comes first: accurate real-time stock, shipping and returns on the product page, and a clean Merchant Center feed.
What WooCommerce says ships today
WooCommerce publishes its own protocol status, and it is the honest starting point because it separates what is live from what is not.
| Status | Protocol | WooCommerce's wording |
|---|---|---|
| Live | Model Context Protocol (MCP) | AI assistants can read your store's products, orders, and settings. Shipped in WordPress 6.9 and WooCommerce 10.3 with 9 built-in abilities. |
| Live | Abilities API | Your store declares what it can do in a format any AI agent understands. Built into WordPress core. |
| Coming soon | Universal Commerce Protocol (UCP), Google | Google's protocol for AI-powered shopping, built on Merchant Center and structured data. |
| Coming soon | Agentic Commerce Protocol (ACP), Stripe | Connects your catalog to multiple AI agents through the Stripe Agentic Commerce Suite. |
WooCommerce's agentic-commerce page marks MCP as live, describing it as letting "AI assistants can read your store's products, orders, and settings," and stating it "Shipped in WordPress 6.9 and WooCommerce 10.3 with 9 built-in abilities"Spec-factWooCommerce, Agentic Commerce. The same page marks the Abilities API as live, describing it as the way a store "declares what it can do in a format any AI agent understands," built into WordPress coreSpec-factWooCommerce, Agentic Commerce. The version numbers in that MCP line are WooCommerce's own wording, quoted here rather than restated as a shipping date.
The two shopper-facing rails are a different column. The page lists Google's Universal Commerce Protocol and OpenAI and Stripe's Agentic Commerce Protocol as "coming soon," and names two sync extensions, Google for WooCommerce and Stripe for WooCommerce, as the path to themSpec-factWooCommerce, Agentic Commerce. WooCommerce's own setup steps for those extensions are its documentation to write and keep current, so this page links to them rather than reproducing them.
Store management is not a shopper-facing rail
The single most common misreading of this table is that live MCP means a WooCommerce store is now buyable inside ChatGPT or Gemini. It is not, and the distinction matters.
WooCommerce's developer roadmap states that "As of WooCommerce 10.3, an early version of the WooCommerce MCP integration is in beta and ready for broader testing"Spec-factWooCommerce developer roadmap. What that integration exposes is a store's own data to a merchant's own AI assistant: reading products, orders and settings. We read this as store management rather than a selection rail. It lets you point an assistant at your own store, but no shopping agent completes a purchase for a shopper through it, so installing MCP does not place a store inside a shopping agent's resultsHypothesis (our analysis). If the goal is to be selected and bought by a shopper's agent, MCP is not the mechanism, and treating it as one wastes the quarter.
What WooCommerce tells merchants to do
WooCommerce's own merchant guide is the useful part of its output here, because most of it holds no matter which rail arrives first.
WooCommerce's merchant prep guide tells stores to keep real-time stock from a single source, put shipping and return details on the product page, use the Stripe for WooCommerce extension as the ACP on-ramp, feed Google Merchant Center through the Google for WooCommerce extension, and re-test quarterly in ChatGPT, Gemini and PerplexitySpec-factWooCommerce, From found to bought. One constraint in that guide is specific and easy to miss. The guide states that stores using WooPayments cannot use the Stripe ACP path yetSpec-factWooCommerce, From found to bought. If you are on WooPayments and were counting on the Stripe extension for the OpenAI rail, that is a plan you cannot execute today.
For the substance behind those steps, make your product feed AI-readable covers the feed, and UCP vs ACP covers what each rail actually standardizes.
Where the gap is
WooCommerce's agentic push is real, but it lives outside core releases, and the honest reading of the release history matters to anyone planning a roadmap.
WooCommerce 11.0 covered foundations cleanup, guest checkout and analytics, and shipped no agentic, AI, MCP, UCP, ACP or feed featuresSpec-factWooCommerce 11.0 release notes. WooCommerce 11.1 covered variation image galleries, EU order-withdrawal rights, a 30-42% speedup to the Store API and REST API, and an experimental product-gallery video, and likewise shipped no agentic, AI, MCP, UCP, ACP or feed featuresSpec-factWooCommerce 11.1 release notes. The agentic capability that exists came from the 10.3 MCP integration and from partner extensions, not from a recent core release.
The clearest signal of where native support stands is a request WooCommerce has left open. The public feature request for native UCP support was submitted on 2026-01-13, carries 34 votes and 9 comments, and its status is still open with a last update of 2026-01-13, as read on 2026-09-18Spec-factWooCommerce feature request: native UCP support. So the agentic-commerce page says UCP is coming soon while the public request for it sits open and unanswered eight months on.
We read this as native agentic support that is signalled but not scheduled. A merchant who needs an agent checkout rail this quarter should plan for the extension path or a third-party plugin, not wait on a core releaseHypothesis (our analysis). That is a statement about timing, not a criticism of the approach: WooCommerce's open architecture is a genuine argument for adopting protocols on your own schedule, and the Stripe and Google extensions it points at are real, shipping code.
The WordPress layer underneath
WooCommerce's agentic features build on primitives that live in WordPress core, and that layer is moving on its own track.
WordPress 7.0 adds a provider-agnostic PHP AI Client, giving plugins a single interface to call model providersSpec-factWordPress core, AI Client in WordPress 7.0. WordPress 7.0 also adds a client-side JavaScript Abilities API and a Connectors API, building on the Abilities API introduced in WordPress 6.9Spec-factWordPress core, client-side Abilities API in WordPress 7.0. For a store, the practical point is that the machine-readable declaration WooCommerce leans on is a WordPress-level capability, so it will keep growing under any commerce plugin, not only under WooCommerce.
The third-party plugin path
Until WooCommerce ships native UCP and ACP, community plugins are how a store gets on the Google and OpenAI rails, and at least one is worth looking at as a concrete example of what that involves.
An independent GPL-2.0 plugin, ucp-for-woocommerce, implements both UCP (spec v2026-04-08) and OpenAI's ACP (spec v2026-04-17) for WooCommerce, with HTTP Message Signatures, JSON-validated product feeds and Stripe Shared Payment TokensReporteducp-for-woocommerce (ooasis), GitHub (2026-09-18). Its maintainer states that it "Passes the official UCP conformance suite: 75/75 (2 expected skips)"Reporteducp-for-woocommerce (ooasis), GitHub (2026-09-18). That figure is the maintainer's own claim and is not independently verified here. Other community plugins target the same gap; this page examined only the one linked above and does not endorse any of themHypothesis (our analysis).
Treat any of these the way you would treat any code that touches checkout. A plugin that handles a live checkout flow and holds signing keys deserves a security review before it goes near a production store. That is not a knock on any project; it is the baseline for code that can move money.
What to do today
The ordering below puts the work that pays off regardless of which rail arrives first, then the rail-specific work that depends on someone else shipping.
- Fix the product-page fundamentals first. Keep real-time stock accurate from a single source, and state shipping and return terms on the product page. WooCommerce names accurate single-source stock and shipping and return details on the product page as prerequisites for selling through AISpec-factWooCommerce, From found to bought. This is available now and helps every agent that reads your store.
- Publish a clean Merchant Center feed through the Google for WooCommerce extension. Available now, and it is the same feed work UCP will build on. See make your product feed AI-readable for what "clean" means field by field.
- Add the ACP on-ramp when you need it, through the Stripe for WooCommerce extension, remembering that WooPayments stores cannot use that path yet. This depends on the extension, not on WooCommerce core.
- If you need an agent checkout rail before native support lands, evaluate a third-party UCP or ACP plugin, and put it through a security review first. This is the option that does not wait on anyone else.
- Re-test quarterly. Agent behavior and protocol status both move, so a working setup is a thing to re-check, not a thing to finish. Serving agent traffic without breaking your origin and information density for agents cover the infrastructure and content sides of keeping those surfaces cheap and legible.
The split we would keep in mind: steps one and two are available today and depend only on you, while steps three and four depend on a partner extension or a plugin author, and native support depends on WooCommerce shipping itHypothesis (our analysis).