Platforms · WooCommerce
Can AI agents buy from a WooCommerce store?
WooCommerce publishes a catalogue an anonymous agent can read: the Store API at /wp-json/wc/store/v1/products is open by default and returns titles, prices, variations and stock without a key. That puts a WooCommerce store closer to Shopify than to the enterprise platforms on the data half. What varies far more is the theme and the plugins, because on WordPress both are unconstrained.
How Ottom reads a WooCommerce catalogue
Source: the WooCommerce Store API. Ottom reads /wp-json/wc/store/v1/products, which WooCommerce serves without authentication unless it has been disabled. When it is unavailable the scan falls back to the sitemap and reads product pages one at a time, and the report says which it used.
What works in your favour
- A readable catalogue endpoint exists by default, so an agent can see the range without crawling it.
- Variations carry their own prices and stock, so an agent can tell which combination is actually buyable.
- Policy pages are ordinary WordPress pages, which are text by default rather than images.
Where agents tend to stop
- Themes are unconstrained, so a variation picker built as a custom widget can be invisible to anything without a pointer.
- Plugins add popups, age gates and cookie walls that a person dismisses and an agent treats as the page.
- A cart that only updates over AJAX with no form fallback stops a reader that does not execute the site’s scripts.
Read about these first
- Choosing a variant needs JavaScript the agent cannot run
- Add to cart needs JavaScript the agent cannot run
- A popup blocks the path to the cart
How often this happens on WooCommerce: not stated here. Ottom publishes frequency by retail category rather than by platform, so there is no per-platform figure to quote. The benchmark pages carry the category view, and publish one only once enough of its stores have been measured at every stage.
Questions
Do I need to expose the Store API?
You almost certainly already do. It is on by default and it is what your own blocks and themes use. If a plugin has disabled it, a scan still works from your product pages, it just reads a sample rather than the catalogue, and anything missing from a page is missing from what the agent knows.
We use a page builder. Does that matter?
It matters for the buy path rather than the data. Builders often produce controls that respond to a pointer and expose no form field, which is the single most common reason an agent gets to a product it wants and cannot put it in a basket.
See this on your own WooCommerce store
We run the four stages above against your storefront and tell you which of these it actually hits. One free scan per store, per email address, every 30 days.