Readiness
Salesforce answers in a standard shape. What the answer means is up to the merchant.
Salesforce B2C Commerce hands an AI buying agent a response shaped exactly the way the documentation says it will be. That is rarer than it sounds, and it is why an agent can integrate against it fast.
What the agent cannot tell is whether the numbers inside mean what they look like, because Salesforce lets a merchant rewrite a response on its way out, and that is a supported feature rather than a workaround.
Is Salesforce ready for agentic commerce and supply chain automation?
B2C Commerce: ready for commerce, not for supply. Catalog data is excellent, there is an availability API built for exactly this kind of high-frequency question, and an agent can take a basket through to an order. Supplier and lead-time data is confirmed absent.
CRM and CPQ: the inverse. No stock at all, and the best business-to-business quoting primitives of anything we looked at: real approvable quotes, contracted pricing, contracts and terms. Two products, two opposite profiles, which is why this page covers both.
Modify-response hooks are a supported extension point
Salesforce documents hooks that let a merchant enrich or alter the response document before it is returned, across the read and write methods, and the same hooks fire for both the current and the older API. This is not a loophole. It is a documented, encouraged way to customize behavior.
For a buying agent it means the envelope is trustworthy and the semantics are not. A field can be present, correctly typed, and populated with something a merchant computed for reasons the caller cannot see.
What the B2C track gives an agent
The availability API is purpose-built for callers that ask often, which is the right shape for agents. It comes with limits worth designing around: a cap on how many items one call can cover, a sentinel value standing in for effectively unlimited stock, and merchant-configurable thresholds that decide when a number is reported at all.
Ordering works cleanly up to the payment step. An order lands unpaid, and completing payment depends on which payment integration the merchant installed, so the last step is merchant-specific rather than platform-standard.
The CRM track has the opposite profile
If the question is business-to-business quoting rather than storefront checkout, nothing else we looked at comes close. Quotes that go through a real approval, contracted pricing, contracts and terms all exist as first-class objects an agent can read and create.
Change data capture is also excellent here, with per-field changes and durable replay over a multi-hour window, so a connector can rebuild state after an outage instead of resyncing everything. The constraint that decides the design is the API call ceiling, which is tight enough that polling strategies have to be planned rather than assumed.
What that costs a merchant who plays it straight
Because a response can be edited, nothing reading your store can take availability at face value. It has to weigh what actually happens when an order is placed, which is how Conduit ranks merchants: on completed checkouts rather than on what a catalog claims.
That is bad news for a store inflating its numbers and good news for yours. If your availability is honest, being measured on outcomes is the thing that separates you from the store that is not.
Frequently asked questions
- How can merchants get discovered by AI agents?
- Merchants install Conduit Connector for their stack (Shopify, WooCommerce, Salesforce, SAP, Oracle, NetSuite, Microsoft Dynamics, Odoo, or a custom API/MCP) with no replatforming. Their live stock, prices, rails, lead times, and carriers then become readable and buyable by autonomous buyers, and they earn rank by delivering, never by paying.
- Do I have to change my ERP?
- No. Connector reads the stack you already run. You do not migrate.
- 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.