The storefront layer is no longer a single vendor decision. The reality of most clients is multiple storefronts hitting one SAP backend: a Magento B2B portal, a Shopify D2C front, a marketplace presence on Amazon, sometimes an Acumatica or Microsoft Dynamics layer in a subsidiary. Each one needs the same five things from SAP: product master, pricing, availability, order create, and order status.
The pattern we use
We expose those five SAP capabilities as Cloud Integration iFlows. Each storefront integrates against the same canonical contract: it is the iFlows that translate to the storefront's preferred shape. Adding a new storefront becomes a one-cartridge job, not a rebuild.
Where teams get it wrong
- Treating inventory as a synchronous lookup from the storefront to SAP. It is not - it is a published event that the storefront subscribes to.
- Trying to keep storefront pricing in sync with SAP via overnight batch. Customers see stale prices, support tickets follow.
- Forgetting the back-channel: the storefront has to know that an order failed downstream after acknowledgement, and reconcile.
What we deliver
- Canonical SAP-side contract for product, pricing, availability, order, status.
- Per-storefront cartridges in Integration Suite that translate to/from that contract.
- Idempotency and reconciliation layer so a retried order does not become two.