Readiness
WooCommerce answers what you have. It cannot answer when more arrives.
If you sell on WooCommerce, an AI buying agent can already read your catalog, your prices and your stock without you doing anything. Ask it when a sold-out product comes back and it has nowhere to look, because the answer was never stored in WordPress in the first place.
That gap you can at least plan around. The one that catches people out is a pair of stock fields that tells an agent you have unlimited inventory when you have twelve units.
Is WooCommerce ready for agentic commerce and supply chain automation?
Ready for commerce, with one trap. Catalog, price and stock read cleanly over the v3 REST API with no per-store work, authorization is a single screen, and an agent can place a real order. The trap is a variation field pair that will make a careless agent order stock you do not have, and it is covered below.
Not ready for supply chain automation. There is no supplier, cost, purchase order or lead time in the documented product schema, so there is nothing for a resupply job to read. That data has to be added by a plugin, pulled from the system that actually holds it, or created as you go.
What the v3 REST API gives an agent
Stock comes back as manage_stock, stock_quantity, stock_status and backorders. That is the whole inventory model, and for a single-location store it is enough: an agent can tell in one request whether you can ship today.
The rest of the catalog is better than that. The product API has been stable since 2017, global_unique_id carries a GTIN, _fields trims a response to what you asked for, and modified_after makes incremental syncs cheap. Authorization is one screen at /wc-auth/v1/authorize, and webhooks are self-provisioned.
Most of the catalog fields an agent needs map with no per-store work at all. For a platform with no vendor standing between you and your own data, that is a strong position, and it is why WooCommerce is first in line for a Conduit connector.
The variation trap, which costs real orders
On variations, manage_stock is documented as boolean or the string "parent". A variation with manage_stock: "parent" and stock_quantity: null is not unlimited stock. It draws from the parent pool.
Read that pair naively and an agent will happily order 500 of something backed by 12. Any connector worth trusting resolves the parent before it treats a null as infinity.
What is missing, and how many stores it affects
Core WooCommerce has no supplier, no purchase order, no lead time and no cost in the documented product schema. Nothing about resupply survives the trip to an API client because nothing about resupply was ever entered.
ATUM is the exception worth knowing. It adds an atum/v1 namespace with a supplier record, purchase orders, and lead time per supplier and product. It is a real answer for the stores that run it, and its install base is a small fraction of the millions of stores running WooCommerce. Plugins that add multiple inventories handle locations only, and accounting connectors keep supplier data in the accounting system, where it never lands back in Woo.
So for the large majority of WooCommerce merchants there is no machine-readable supplier, cost, purchase order or lead time anywhere in the WordPress install. It lives in the owner's inbox and one spreadsheet.
Where the resupply half has to come from
Resupply data on WooCommerce cannot be read. It has to be gated on ATUM, pulled from the accounting or ERP system that actually holds it, or originated: captured once when a merchant connects and kept current from the orders that follow.
That is the shape of Connector for WooCommerce. Catalog and stock come from the store, and the supply graph gets built next to it rather than extracted from it.
Frequently asked questions
- What is Conduit Connector?
- Conduit Connector reads vendors, lead times, on-hand stock, and inbound from the ERP you already run and puts that graph in Hub. You stay in your stack. Once it is in Hub, Pipes can track lines, suggest alternatives, and request quotes.
- How long does Connector take to set up?
- Minutes. You connect from the system you already use. There is no replatforming and no second storefront.
- Which systems does Conduit Connector support?
- WooCommerce and Odoo are in development. Shopify, Microsoft Dynamics 365, NetSuite, Salesforce Commerce Cloud, Oracle Fusion, SAP S/4HANA, and custom API or MCP are coming soon. Per-stack notes live in Hub.