Readiness
SAP knows more about your supply than anything else. It will not tell you when stock moves.
Your S/4HANA holds the supplier records, the purchasing info, the customer-specific net prices and the lead times that a buying agent needs and almost never gets. On data alone, no other system we read comes close.
The problem is not the data. It is that nothing in S/4HANA tells you when a stock number changed, so whatever reads it is polling and guessing how stale the answer is.
Is SAP S/4HANA ready for agentic commerce and supply chain automation?
On data, yes, and by a distance. Availability comes back as a confirmed quantity and date per schedule line, real time, non-destructive, with no extra license, and the same call returns the true customer-specific net price. No other ERP we looked at answers availability that cleanly.
On access and freshness, the hardest of any system we looked at. Getting connected is a committee decision measured in weeks or months with no self-serve path, and there is no stock-level change event to subscribe to, so a connector polls.
Simulate a sales order to get real availability
The instinct is to read stock on hand and treat it as availability. Do not. In S/4HANA that number ignores allocations, planned movements and the promising rules the business actually runs on, so an agent quoting from it will over-promise.
Simulating a sales order is the right call instead. It is non-destructive, it runs in real time, it returns a confirmed quantity and date for each schedule line, and it needs no additional license. An agent gets a commitment it can quote rather than a number it has to interpret.
There is no stock-level change event
The blunt version of this claim, that SAP has no events, is wrong, and an SAP person will spot it immediately. S/4HANA does have an eventing framework and business objects do emit through it. What does not exist is an event for a stock level changing, and consumption against availability emits nothing at all. The messaging layer that carries events is separately licensed on top.
The consequence for anything agent-facing is that freshness comes from polling on your own schedule, and the poll interval becomes the accuracy of every promise you make.
The only reliable net price comes from the same simulation
SAP prices through a condition technique flexible enough that reading a customer's real net price out of configuration is impractical for an outsider. The simulation answers it directly instead, including the condition-level breakdown that explains how the number was reached.
The tradeoff is shape rather than accuracy: this is a request per quote, not a bulk feed you can index. A connector has to decide what it caches and for how long, and be honest with the agent about which it is serving.
Getting connected takes a security review and weeks
Nothing about connecting an outside system to S/4HANA is self-serve. It runs through a security review and typically several people, and realistically that is weeks at best. The one thing that goes the other way is that once credentials exist they do not expire on their own, so the cost is entirely up front.
That is why this connector is built alongside a first customer rather than shipped and advertised. If you run S/4HANA and this reads like your situation, that is the conversation worth having.
Frequently asked questions
- 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.
- Is Conduit Connector live yet?
- Coming soon. Hub shows the shape of mapping today, and you can tell us which system you run. Request a demo if you want a walkthrough.