Readiness
Odoo has the resupply data. Your subscription decides whether an agent sees it.
Odoo stores what almost nothing else in the mid-market stores: a supplier per product, purchase lead time, and inbound receipts, all of it queryable. An agent could answer "when does more arrive" straight from a live Odoo database.
Whether it can comes down to a line on your subscription rather than anything technical.
Is Odoo ready for agentic commerce and supply chain automation?
Ready for both, once you are past the gate. Stock is live and per warehouse, an agent can place a real order, and the supplier and lead-time data is the best of any mid-market system we assessed. On the data alone, Odoo is the strongest case for agentic supply automation outside of enterprise ERP.
The gate is your pricing plan. Odoo documents that external API access is available only on Custom plans, and not on One App Free or Standard. On Standard you cannot grant an agent access at all without upgrading, so it is worth checking your plan before anything else.
The plan gate, and why you cannot code around it
The restriction is published on the external API documentation itself, and merchants hit it often enough that the Odoo forum carries several separate threads asking whether it is real or whether a trial gets around it. It is real. The Custom plan runs roughly one and a half times Standard per user per month.
The obvious workaround does not exist either. A custom server module cannot be installed on Odoo Online, so you cannot ship code into the instance to expose what the external API will not. On Odoo.sh or self-hosted the picture changes completely, which is why the hosting question comes right after the plan question.
What is in there once you are through
Stock is the strong point: real quantities per warehouse and location, live rather than nightly. Resupply is the rarer one. Supplier records, purchase lead times and inbound receipts all read over the same API, which means an agent can say when a shortfall clears instead of only that it exists.
Some of it depends on which apps a merchant has installed. Purchase and Inventory carry most of the supply graph, and a store running Sales alone will look thinner than the schema suggests.
Reading a price takes a round trip
Price resolution lives behind methods that are not part of the public read surface, so getting the price a specific customer would actually pay means creating a draft order and reading what comes back, then discarding it. It works and it is accurate. It is also a write to get a read, which shapes how often you can ask.
Webhooks are an invalidation hint
Outbound calls are fire and forget with a short timeout and no signature, so they tell you something changed without telling you reliably what, or proving the message came from the instance you think it did. Use them to invalidate a cache and re-read, never as the source of truth for a quantity an agent is about to commit to.
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.
- Do I have to change my ERP?
- No. Connector reads the stack you already run. You do not migrate.