Skip to main content
Talk to an expert
SAP Commerce Cloud logo

SAP Commerce Cloud integration for ecommerce

Your storefront and operational estate work as one system SAP Commerce Cloud is the commerce platform layer. iWeb defines the flows to ERP, PIM, payments, fulfilment, search, marketplaces and CRM so products, stock, pricing, orders and customers stay in step. Integrates with the ERP, PIM, OMS and operational systems commerce teams already run.

Also searched as: commerce platform, storefront, online store, shop platform, commerce engine.

Your systemsiWeb integration layerSAP Commerce Cloud
Talk to an expertSee the estate map ↓
Works with - SAP ERP (S/4HANA, ECC) · SAP C/4HANA · PIM systems · OMS and WMS · Payment gateways
On this pageGet a brief reviewed
01 · What you get

What a SAP Commerce Cloud integration gives you.

Product data published cleanly

Product teams know that SAP Commerce Cloud displays governed attributes, images, descriptions and pricing from the PIM and ERP without manual intervention or channel-specific gaps.

Orders flow reliably to the ERP

Every web order becomes a source document in the ERP or OMS with customer, line-item and shipping data intact. Exceptions are surfaced and owned; no orders are lost or duplicated in flight.

Stock stays in sync across channels

Stock-keeping teams see real-time or periodic stock state flowing from the ERP or WMS into SAP Commerce Cloud. Oversell risk is controlled via allocation rules and refresh frequency; shopper visibility respects buffer policies.

Checkout runs without fallback surprises

Payments, tax calculation, shipping options and customer-account validation integrate into checkout without hidden failures. Errors are logged and routed to operations; no orders silently fail mid-transaction.

Customer accounts reconcile across systems

Customer profiles, addresses, account status and credit limits stay in step between SAP Commerce Cloud and the ERP. Account changes trigger customer master updates; credit or contract changes reflect in the storefront within a defined window.

02 · When it's worth it

Where a SAP Commerce Cloud integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publish product catalogue and pricing from SAP ERP and PIM into the storefront
Route and fulfil orders from SAP Commerce Cloud into ERP and OMS
Synchronise stock availability and inventory across commerce, ERP and warehouse
Integrate payments, tax and shipping into checkout without breakage
Feed customer data, consent and behavioural events to SAP Marketing Cloud
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Product data governance across channels

SAP Commerce Cloud does not manage multi-channel product attributes, completeness rules or channel-readiness workflows. These governance decisions sit with PIM or the operational estate; the commerce platform consumes the result.

Stock buffering and allocation logic

The platform lacks native multi-location stock reservation and order routing. These rules live in ERP, OMS or WMS; commerce must sync stock state frequently and respect allocation decisions from upstream systems.

Order acknowledgement and exception handling

SAP Commerce Cloud captures orders but does not implement ERP-acknowledgement rules, return-to-stock logic or exception queues. These workflows must be defined in the integration layer and the downstream OMS or ERP.

Pricing and promotion sourcing

The platform can display pricing and promotions but does not calculate or arbitrate them. Price books, customer-specific pricing and promotion rules must come from ERP, PIM or a pricing engine; the platform is a display sink.

Customer account and credit governance

SAP Commerce Cloud supports customer sessions but does not hold ERP account master data or credit limits as a system of record. Account and contract changes must sync with the ERP; fallback rules must be predefined.

04 · The real work

Commerce platforms and ERP systems speak different languages. The integration layer must translate ownership, timing and failure handling so that neither system owns the other; both respect defined boundaries.

05 · Where it sits

Where this integration sits in your estate.

SAP Commerce Cloud is the commerce platform - the customer-facing experience, catalogue, checkout and account area. The iWeb integration layer wires it into the ERP, PIM, OMS, WMS and payments systems it depends on. The estate map helps agree ownership before anything is built.

Commerce is only half the job. SAP Commerce Cloud needs a governed link to ERP, PIM and warehouse to trade properly.

Customer-facing commerce
Commerce platform
SAP Commerce Cloud
Ecommerce platform and customer-facing order capture
  • Storefront browse and search experience
  • Shopping cart and checkout flows
  • Customer sessions and login
  • Order submission and transient order state
  • Payment and shipping selection UI
iWeb integration layer
Systems behind the platform
Systems it depends on
SAP ERP (S/4HANA, ECC)SAP C/4HANAPIM systemsOMS and WMSPayment gatewaysMarketplaces (Amazon, eBay)Search and merchandisingCRM and marketing platforms
  • Product display from PIM/ERP feeds
  • Pricing and promotion rendering
  • Stock visibility and availability rules
  • Customer account validation at checkout
  • Order-to-ERP transmission
Connected neighbours
Integration layer
ERP (S/4HANA, ECC)
Holds product master, pricing, stock, customer accounts, GL and order records; SAP Commerce Cloud feeds from and reports to the ERP
Integration layer
PIM
Governs product attributes, media, descriptions and enrichment; feeds product catalogues into SAP Commerce Cloud
Integration layer
OMS/WMS
Manages order routing, fulfilment, dispatch and warehouse stock; receives orders from SAP Commerce Cloud and sends back tracking/status
Integration layer
Payments
Processes authorisation, capture and refunds; integrates into checkout; reconciles with ERP
Integration layer
Search/merchandising
Indexes product catalogue and handles facets, synonyms, ranking; feeds from PIM/ERP or SAP Commerce Cloud product data
Integration layer
Marketplaces
Receive product feeds and stock from SAP Commerce Cloud; send orders back for fulfilment in the same OMS/ERP
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb wires SAP Commerce Cloud into whatever ERP, PIM, OMS, WMS, payments and operational systems your estate already runs.

Systems behind the platform (examples)
  • SAP ERP (S/4HANA, ECC)
  • SAP C/4HANA
  • PIM systems
  • OMS and WMS
  • Payment gateways
  • Marketplaces (Amazon, eBay)
  • Search and merchandising
  • CRM and marketing platforms
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE
←From COMMERCE & OTHER SYSTEMS
↔BOTH WAYS
Product catalogue and pricing: Product attributes, descriptions, images, categories and base pricing flow from PIM or ERP into SAP Commerce Cloud
The storefront displays governed product data and refreshes pricing rules as contracts and promotions change.
Stock and availability: Real-time and batch stock updates from ERP, OMS or WMS feed SAP Commerce Cloud stock levels
The storefront uses stock state to control visibility, checkout availability and allocation rules.
Web orders and checkout events: Customer orders, basket state, shipping selections and payment intents flow out of SAP Commerce Cloud into ERP and OMS
Order-capture events trigger fulfilment, invoicing and customer service workflows downstream.
Customer and account data: Customer profiles, addresses, account status and credit limits flow both ways between SAP Commerce Cloud and ERP or SAP C/4HANA systems
Account changes in commerce trigger customer master updates in the ERP; credit or contract changes flow back to the storefront.
Payments, tax and shipping: Payment authorisation, tax calculation and carrier / shipping rates integrate into SAP Commerce Cloud checkout
Response events and settlement reconciliation flow back to commerce, ERP and reporting systems.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design the data flow architecture

    iWeb maps which data moves between SAP Commerce Cloud, ERP, PIM, OMS, payments and reporting systems. We define timing (realtime sync vs batch), direction (one-way or bidirectional), error handling and fallback behaviour for each flow.

  2. 02
    Build order capture and acknowledgement

    We implement order-to-ERP flows that preserve customer, line-item, payment and shipping data. We define acknowledgement rules, timeout handling and exception queues so operations can resolve stuck orders without losing data.

  3. 03
    Implement stock and pricing sync

    iWeb builds the feeds that move base pricing, promotional pricing and stock levels from ERP or PIM into SAP Commerce Cloud. We define refresh cadence, buffer logic and staleness alerts so the storefront stays accurate.

  4. 04
    Govern customer and account data

    We design bidirectional customer synchronisation between SAP Commerce Cloud and the ERP or C/4HANA system. We map account status, credit limits, pricing attributes and trade account rules so commerce sees the correct customer state.

  5. 05
    Integrate payments, tax and shipping

    iWeb connects payment providers, tax engines and shipping carriers into SAP Commerce Cloud checkout. We handle authorisation, capture, tax calculation, rate lookups and reconciliation so transactions complete reliably.

  6. 06
    Monitor and support in production

    iWeb sets up observability for data flows, order queues, stock sync and customer record changes. We own exception handling, data reconciliation and incident response so the integration stays reliable after launch.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataProduct catalogue, attributes, images and descriptions
Source / ownerPIM or ERP product master
Maintained byProduct and merchandising teams
NotesSAP Commerce Cloud displays this data; it is a sink, not a source. Updates flow from PIM/ERP into the storefront via governed feeds.
DataBase pricing, customer-specific pricing and promotions
Source / ownerERP price books or pricing engine
Maintained byFinance and commercial teams
NotesSAP Commerce Cloud renders pricing rules; it does not calculate or arbitrate them. Price feeds and promotion schedules come from the ERP or pricing system.
DataStock levels and availability
Source / ownerERP or WMS inventory
Maintained byWarehouse and supply-chain teams
NotesSAP Commerce Cloud displays stock state; it does not own or allocate inventory. Real-time or batch stock feeds come from ERP/OMS/WMS into the storefront.
DataOrders, checkout data and customer transactions
Source / ownerSAP Commerce Cloud (transient), then ERP or OMS after order capture
Maintained byCommerce operations and order management
NotesSAP Commerce Cloud captures the order; the integration layer hands it to ERP/OMS for fulfilment, invoicing and returns. The storefront is not a ledger of record for completed orders.
DataCustomer profiles, addresses and account status
Source / ownerERP or SAP C/4HANA customer master
Maintained byCustomer service and account management
NotesSAP Commerce Cloud maintains customer sessions; the ERP holds the account master. Changes sync bidirectionally; SAP Commerce Cloud is not the system of record for customer account data.
DataPayment authorisations, captures and reconciliation
Source / ownerPayment gateway and ERP accounts
Maintained byFinance and payment operations
NotesSAP Commerce Cloud initiates payment; the payment gateway and ERP record the transaction. Reconciliation logic sits in the integration layer and ERP, not the storefront.
10 · Experienced integrator

Built this before

iWeb has implemented SAP Commerce Cloud integrations across multiple SAP estates (S/4HANA, ECC, C/4HANA). We understand how the commerce platform sits at the centre of the ecommerce experience and how to connect it reliably to ERP, PIM, OMS, payments and reporting systems without creating hidden dependencies.

We design order-capture and acknowledgement flows so every web order reaches the ERP as a source document with complete and accurate data; no orders are lost or duplicated.
We map stock and pricing feeds from ERP and PIM into the storefront so product data, availability and pricing stay governed and in sync without manual intervention.
We implement customer and account synchronisation between SAP Commerce Cloud and the ERP so credit limits, trade-account pricing and customer master changes are visible in real time.
We integrate payments, tax engines and shipping carriers into checkout so transactions complete reliably and settle correctly against the ERP.
We set up observability and exception handling so order queues, stock drift, payment failures and customer record changes are monitored and resolved before they disrupt the business.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Product feed parity: Verify attributes, images and pricing from PIM reach SAP Commerce Cloud within the agreed cadence and match the source system.
Order transmission: Confirm every test order from the storefront creates a matching order in the ERP with correct customer, line and shipping data; no orders are lost or duplicated.
Stock accuracy: Validate stock levels in SAP Commerce Cloud match ERP/WMS at scheduled refresh points; oversell risk is controlled via buffer policies.
Customer account sync: Confirm a new customer registration in the storefront creates a matching customer record in the ERP; credit and pricing changes sync back within the defined window.
Payment and tax: Test payment authorisation, capture and tax calculation; confirm payment status and tax detail flow to the ERP for invoicing.
Exception handling: Trigger failures (ERP down, payment timeout, stock unavailable) and verify exceptions are logged, queued and alerted without silent loss or customer impact.
Failover and rollback: Confirm the integration can switch to fallback behaviour if the ERP is unavailable; verify rollback procedures restore order state without duplication.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Orders lost or duplicated in flight

Without clear order-capture flows and acknowledgement logic, web orders can be lost between SAP Commerce Cloud and ERP, duplicated if retries are not idempotent, or dropped if the integration layer fails silently. This bites when order volume spikes or the integration is re-deployed.

Stock oversell across channels

If stock sync is infrequent, buffered poorly or not respected by allocation rules, the storefront can oversell to shoppers when stock has already been allocated to other channels. This happens under high concurrency or when WMS and ecommerce stocks drift.

Pricing mismatches and customer confusion

If price-feed timing, customer-specific pricing rules or promotion effective dates are not synchronised, shoppers see stale or incorrect prices at checkout. Disputes and order cancellations follow.

Checkout fails silently due to account or payment errors

If customer-account validation, credit-limit checks or payment integration fails without clear error messaging and exception logging, shoppers abandon checkout and orders never reach the ERP. Operations do not know orders were attempted.

Customer account changes not propagating

If customer master data, account status, credit limits or trade-account pricing are not synchronised bidirectionally, SAP Commerce Cloud shows stale or incorrect customer state. This causes checkout rejections or pricing errors that confuse the customer.

Integration drift after ERP or platform upgrades

If field mappings, API contracts or payload structures are not managed and version-controlled separately from the commerce platform and ERP, upgrades to either system can break the integration without warning. This is especially risky if custom code is embedded in commerce configuration.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about SAP Commerce Cloud integrations.

How do product updates from the PIM reach SAP Commerce Cloud?

Product feeds (attributes, images, descriptions, categories) flow from the PIM via scheduled batch or API-driven sync into SAP Commerce Cloud. The commerce platform displays these feeds; it does not edit product master data. Update cadence and field mapping are agreed during integration design.

How are orders captured from the storefront and sent to the ERP?

When a customer places an order, SAP Commerce Cloud captures the basket, payment and shipping selections. The integration layer validates the order and transmits it to the ERP or OMS as a source document. The ERP acknowledges receipt; the integration logs the confirmation or exception.

What happens if an order fails to reach the ERP?

If transmission fails, the integration logs the event and the order sits in an exception queue. Operations are alerted; the order can be manually resubmitted or the root cause investigated. The integration is designed so no orders are silently lost or duplicated.

How does stock synchronisation work between SAP Commerce Cloud and the warehouse?

Stock levels flow from the ERP or WMS into SAP Commerce Cloud via batch feeds or API calls at a defined frequency (e.g. hourly or daily). The storefront uses this state to control visibility and checkout availability. High-velocity environments may use real-time sync or inventory reservations.

Can the storefront oversell if stock syncs are infrequent?

Yes, if sync cadence is too slow or allocation rules are not respected, the storefront can show available stock that has already been allocated elsewhere. Allocation and buffer policies are designed during integration planning to manage this risk.

How are customer-specific prices published to the storefront?

Customer-specific pricing rules (trade accounts, volume discounts, contract prices) flow from the ERP into SAP Commerce Cloud via price feeds or catalogue sync. The platform applies these rules at checkout based on the logged-in customer's account or segment.

What if a customer's credit limit changes in the ERP?

Credit-limit changes can sync from the ERP to SAP Commerce Cloud periodically or in near-real time. The integration can enforce credit checks at checkout; if a customer exceeds their limit, the order is rejected or flagged for approval. The grace period is defined in the integration design.

How do payments integrate with SAP Commerce Cloud checkout?

Payment providers integrate into checkout via SAP Commerce Cloud payment adapters or direct API calls. Authorisation happens at order submission; capture and reconciliation happen after order confirmation. Payment status flows back to the ERP for invoicing and reporting.

What if the payment gateway times out during checkout?

Timeout and failure handling are designed into the checkout flow. If payment authorisation fails, the shopper sees an error message and can retry. The integration logs the failed attempt; the order is not created in the ERP until payment succeeds.

How do tax calculations integrate into SAP Commerce Cloud?

Tax rates and calculations can come from the ERP tax module, a third-party tax engine or SAP Commerce Cloud native rules. The chosen source is configured during integration design. Tax is calculated at checkout and included in the order sent to the ERP.

Can SAP Commerce Cloud integrate with multiple marketplaces or channels?

Yes. SAP Commerce Cloud can feed product data, pricing and stock to marketplaces (Amazon, Marketplace, etc.) via separate connectors. Orders from each channel flow back into the same ERP or OMS. Channel-specific inventory allocation and pricing are managed in the integration layer.

What happens during an ERP or SAP Commerce Cloud outage?

If the ERP is unavailable, orders cannot be transmitted downstream; they queue in the integration layer and are retried once the ERP recovers. If SAP Commerce Cloud is down, shoppers cannot browse or checkout; failover and communication plans are agreed during design.

How is customer data synchronised between SAP Commerce Cloud and the ERP?

Customer profiles, addresses, account status and contact details flow bidirectionally between SAP Commerce Cloud and the ERP or SAP C/4HANA. New customer registrations in commerce flow to the ERP; customer master changes in the ERP flow back to commerce. Sync frequency and conflict resolution are defined.

How are returns and refunds handled?

Returns are initiated in SAP Commerce Cloud or a customer-service portal. The return request flows to the OMS or ERP; stock is returned to inventory; refunds are processed via the payment gateway and reconciled in the ERP. The integration tracks each step so operations can monitor refund status.

What visibility do operations have into integration health?

iWeb sets up monitoring and alerting on data flows, order queues, stock sync latency, customer record changes and payment status. Dashboards show real-time and historical metrics. Exception queues are monitored daily; unresolved exceptions trigger escalation.

How often are integrations tested or validated after launch?

iWeb performs ongoing health checks on data parity, order transmission, customer synchronisation and stock accuracy. Testing is performed before peak periods (sales events, new collections) and after platform or ERP upgrades. Issues are caught and resolved before they impact shoppers.

14b · Same category

Other commerce platforms integrations.

Adjacent integrations in the same category. Same shape of work, different vendor.

Commerce platforms
Next step

Have a SAP Commerce Cloud integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →