DEV Community

Giuseppe Socci
Giuseppe Socci

Posted on

Your WooCommerce store is invisible to AI shopping agents. Here's how to fix it.

#agents #ai #api #wordpress

AI shopping agents are already buying things on behalf of real users. ChatGPT Shopping has been live since September 2025. Google announced Universal Cart at I/O 2026 — a persistent cross-merchant cart spanning Search, Gemini, YouTube, and Gmail. The underlying standard is UCP (Universal Commerce Protocol).
None of this works with a standard WooCommerce store.

What AI agents actually do when they shop
When a user asks ChatGPT "find me a waterproof jacket under €150 in size M", the agent doesn't open a browser and scroll through your homepage. It queries structured data sources — product feeds, APIs, discovery endpoints. If your store doesn't have one, it doesn't exist.
The agent needs to answer machine questions:

What's the exact current price?
Is size M actually in stock right now, or is it backordered?
Does this product have variants? Which ones are available?
Is there a discount I can apply at checkout?
How do I initiate a purchase session?

A standard WooCommerce store can't answer any of these questions in a machine-readable way. The data is there — buried in the database — but there's no structured API surface for an agent to consume.
This is the gap. And it's about to matter a lot.

What's shipping right now
ChatGPT Shopping — live since September 2025, 900M weekly users. Queries structured product feeds. Non-Shopify merchants need an ACP-compliant product feed to appear.
Google AI Mode — replaces the classic search results page with a structured product panel. Reasons over the Shopping Graph to match intent, not just keywords. Feed completeness and live data are the ranking signals — not SEO.
Google Universal Cart — announced at I/O 2026. Cross-merchant persistent cart across Search, Gemini, YouTube, Gmail. Powered by UCP. Initial rollout to Shopify merchants and major US retailers.
WooCommerce MCP — shipped in WooCommerce 10.3 (Oct 2025), finalized in 10.7. Lets AI assistants interact with WooCommerce stores via Model Context Protocol. Current focus: store management (products, orders). Consumer shopping via MCP is the stated next step.
The pattern is clear: every major AI platform is building a commerce layer, and they're all pulling from structured data. The stores with complete, machine-readable catalogs get surfaced. The rest don't.

The WooCommerce problem
WooCommerce powers ~28% of global online stores. Almost none of it is natively readable by AI agents.
The WooCommerce REST API exists, but it's designed for store management — not for agent consumption. It requires authentication, returns data in a format agents don't expect, and has no discovery mechanism. An agent landing on a WooCommerce storefront has no standardized way to find the catalog, understand its structure, or initiate a purchase.
Shopify solved this with their managed agentic stack. WooCommerce, being open-source, is taking the composable path — which means the solution space is open for plugins.

What a machine-readable WooCommerce store looks like
I've been building KaliCart Bridge — a free WooCommerce plugin that exposes your live catalog as a normalized REST API for AI agents.
Here's what it adds to a standard WooCommerce store:
Discovery signals — A <link rel="kalicart-agent"> in the page <head>tells any agent where to start. /.well-known/kalicart-bridge and /.well-known/ucp provide standardized discovery files. robots.txt explicitly allows the catalog endpoints.
Structured catalog API —/wp-json/kalicart/v1/discovery is the entry point. From there, agents can search with real filters (category, gender, color, on_sale, in_stock, price range), get paginated product lists, fetch individual products with full variations, and navigate the category tree.
Normalized product data — every product exposes:

{
  "price": {
    "current": 89.00,
    "regular": 110.00,
    "on_sale": true,
    "discount_pct": 19.1,
    "encoding": "decimal_major_units",
    "display": "89,00 €",
    "vat_included": true
  },
  "stock": {
    "in_stock": true,
    "availability_status": "in_stock",
    "quantity": 14,
    "quantity_tracked": true,
    "backorder_allowed": false
  },
  "variants": [...],
  "barcodes": [{ "type": "EAN", "value": "1234567890123" }],
  "metadata": {
    "purchase_readiness": "direct_cart_possible",
    "stock_confidence": "numeric_stock_quantity"
  }
}
Enter fullscreen mode Exit fullscreen mode

UCP compatibility — /.well-known/ucp declares dev.ucp.shopping.catalog.search and dev.ucp.shopping.catalog.lookup capabilities. Stock uses UCP-standard availability_status values. Price encoding is explicit (decimal_major_units) with a conversion hint for UCP minor units.
Checkout sessions — optional. Agents can create multi-product sessions returning cart_url and checkout_url. The human pays on WooCommerce. The merchant stays Merchant of Record.
No LLM. No cloud. No API key. Everything runs on your server.

The discovery flow
An agent that encounters a KaliCart Bridge store follows this path:

  1. 1. GET page HTML → finds
  2. GET /wp-json/kalicart/v1/discovery → reads capabilities, filters, UCP profile, checkout policy
  3. GET /wp-json/kalicart/v1/catalog/search?q=waterproof+jacket&in_stock=true&max_price=150
  4. GET /wp-json/kalicart/v1/catalog/product/{id} → full variants for variable products
  5. POST /wp-json/kalicart/v1/checkout/session → returns cart_url + checkout_url Five requests from zero knowledge to checkout-ready. No scraping, no guessing, no hallucinated prices.

Catalog health
The plugin also adds a health dashboard in WP Admin. Products are scored 0–100 based on data completeness. Deductions: NO_TITLE (−25), NO_DESCRIPTION (−30), NO_CATEGORY (−30), ZERO_PRICE (−25), NO_IMAGE (−8), NO_SKU (−4).
Products with blocking issues are quarantined — they don't appear in agent responses until fixed. The dashboard shows exactly what's wrong and links directly to filtered product lists for remediation.
This turns out to be useful even outside the agent context — most WooCommerce stores have a tail of products with incomplete data that nobody ever audits.

Where things are headed
The checkout layer (UCP + AP2) is still early — autonomous checkout at scale is probably 12–18 months away for the average merchant. But the discovery layer is live now.
Google AI Mode is already routing product searches away from classic results. ChatGPT Shopping is already surfacing products from structured feeds. The stores that are machine-readable today will have indexed history, agent familiarity, and structured data quality by the time autonomous checkout becomes mainstream.
The window to get ahead is now, not when it's obvious.

Try it

Top comments (0)