How SAP Commerce Cloud (B2B) connects to SAP S/4HANA
SAP Integration Suite (first-party integration)
SAP Integration Suite carries the messages between Commerce Cloud and S/4HANA. Master data replication goes from the ERP toward the storefront, and order creation goes the other way. SAP documents this in its learning journey on the Commerce Cloud and S/4HANA Cloud integration; for an on-premise S/4HANA you also need a secure connection into your network, commonly through SAP Cloud Connector.
Real-time ERP calls for price and stock
B2B stores often need contract prices and availability from the ERP rather than a copy. Plan which values are replicated and which are fetched on demand, because that choice drives storefront speed and ERP load.
What data moves
| From | To | Data | When |
|---|---|---|---|
| S/4HANA business partner | Commerce Cloud | B2B customers, units, contacts and sold-to / ship-to relations | Initial load, then change replication |
| S/4HANA material master | Commerce Cloud | Products, descriptions, units of measure, classification | Initial load, then change replication |
| S/4HANA pricing | Commerce Cloud | List and customer-specific prices | Replication or on-demand call at browse and checkout |
| Commerce Cloud | S/4HANA sales order | Order header, items, ship-to, requested date | Customer places the order |
| S/4HANA | Commerce Cloud | Order status, delivery and invoice status | Status change in ERP |
Setting it up
- 1Decide the data ownership modelChoose what the ERP owns (customers, materials, prices, stock) and what lives only in the storefront (content, images, marketing text).
- 2Provision Integration SuiteSet up SAP Integration Suite and the integration content for Commerce Cloud and S/4HANA, with connectivity to the ERP.
- 3Connect on-premise S/4HANAEstablish the secure tunnel, typically SAP Cloud Connector, and expose only the required services.
- 4Load business partners and materialsRun the initial replication, then verify B2B units, account hierarchies and product catalogs.
- 5Configure pricing and availabilityDecide between replicated prices and live ERP pricing, and set caching rules for each.
- 6Map order creationDefine sales organization, distribution channel, division, order type and partner functions used for web orders.
- 7Test the full order cyclePlace orders with different customers, units of measure and partial stock, and follow them to delivery and invoice.
- 8Plan error handlingSet alerts for failed replications and orders that did not reach the ERP, with an owner for each.
What usually breaks
- !Customer hierarchies in SAP not matching the B2B unit structure, so users see the wrong accounts.
- !Unit of measure conversions differing between the webshop and the material master.
- !Replicated prices going stale when condition records change, leaving quotes that disagree with invoices.
- !Web orders failing on a blocked customer, missing incompleteness fields or credit block, with no one notified.
- !Stock shown from a single plant when fulfillment draws from several.
- !Cloud-to-on-premise connectivity breaking after network or certificate changes.
A private AI layer across both systems
Failed order triage
A private assistant reading the integration monitor and S/4HANA sales documents can explain why a web order stopped (credit block, missing partner, incompleteness) and suggest the fix for a person to apply.
Price mismatch investigation
Compare the price shown on the storefront with the condition records used in the ERP and point at the record that differs.
Customer self-service answers
Let customer service ask in plain language where an order is, reading order, delivery and invoice status from S/4HANA without opening several screens.
Try it here, free
Ecommerce B2B Portal ROI Calculator
Model the labor and rework savings from moving manual order entry to a self-service B2B portal, and see the payback period against build and run cost.
When something else fits better
- A non-SAP B2B storefront on a headless commerce platform, if your catalog and content needs are unusual.
- Customer portals using SAP Fiori apps directly for a small, known customer base.
- EDI for large repeat customers, which skips the webshop and keeps order entry machine to machine.
Frequently asked questions
Does Commerce Cloud B2B work with on-premise S/4HANA?
SAP documents the integration for S/4HANA Cloud and S/4HANA through SAP Integration Suite. For an on-premise system you need a secure path from the cloud into your network, commonly SAP Cloud Connector. Confirm supported releases in SAP documentation.
Which system owns prices?
Normally the ERP does. You decide whether to replicate prices to the storefront or fetch them live from S/4HANA, trading speed against accuracy. Customer-specific pricing usually pushes teams toward live or frequently refreshed values.
Can orders be edited after submission?
Once an order exists in S/4HANA, changes are made in the ERP, and the storefront reflects status. How much editing customers can do online is a design decision for the project.
Pairing documented at learning.sap.com/learning-journeys/discover-the-foundations-of-sap-commerce-clou . SAP Commerce Cloud (B2B) is a product of SAP; Netray is independent and not affiliated with either vendor.