Order Management in SAP Commerce Cloud: How It Works and What It Handles

Order management isn’t glamorous — but it’s where commerce actually happens. The best product catalogue and the slickest storefront mean nothing if orders get lost, inventory is wrong, or returns take weeks. In SAP Commerce Cloud, order management covers the entire lifecycle: cart creation, checkout, payment capture, fulfilment routing, shipping, and returns.

This guide covers what Commerce Cloud’s OMS handles, how the order lifecycle works, and where the platform’s strengths and gaps are.

TL;DR: SAP Commerce Cloud’s order management covers the full lifecycle — cart, checkout, payment, fulfilment, shipping, and returns. Global e-commerce reached $6.334 trillion in 2024 (eMarketer, 2024). At that scale, order management determines whether customers come back. Commerce Cloud handles B2C and B2B orders, multi-warehouse sourcing, order splitting, and returns — but complex orchestration scenarios may need SAP Order Management Services or a third-party OMS.

What Does the Order Lifecycle Look Like?

Global retail e-commerce reached $6.334 trillion in 2024, crossing 20% of all retail sales (eMarketer, 2024). Every dollar flows through the order management process.

Commerce Cloud processes orders through a defined lifecycle. Each stage triggers business logic, status updates, and integration events.

What OMS Capabilities Are Built In?

Gartner has named SAP a Leader in Digital Commerce for 11 consecutive years (SAP News, 2025). The built-in order management is a key reason — it handles the most common scenarios without additional software.

Centralised order management. View, edit, and manage all orders from Backoffice. Track order status, modify shipping details, process cancellations, and handle refunds from a single interface.

Multi-warehouse sourcing. Define sourcing rules that route orders to the optimal fulfilment location based on proximity, stock availability, or cost. Commerce Cloud evaluates all available locations and selects the best match.

Order splitting. A single order can be split into multiple consignments fulfilled from different locations. One item ships from warehouse A, another from warehouse B. The customer sees one order; the system manages multiple shipments.

Returns and refunds. Built-in RMA (Return Merchandise Authorisation) workflows handle return requests, restocking, and refund processing. Integrates with payment gateways for automated refunds.

B2B-specific capabilities. Purchase orders, approval workflows, cost centre allocation, and budget checks. B2B orders often go through multi-level approval before fulfilment — Commerce Cloud supports these workflows natively.

Where Does Built-In OMS Fall Short?

E-commerce accounts for 34% of B2B revenue (McKinsey, 2024). As order volumes and fulfilment complexity grow, the built-in OMS can hit limits.

Complex distributed fulfilment. If you need ship-from-store, dropship, and marketplace fulfilment alongside warehouse shipping, Commerce Cloud’s built-in sourcing may not be granular enough. SAP Order Management Services or a dedicated OMS like Fluent Commerce adds the orchestration layer.

Real-time inventory across hundreds of locations. Built-in inventory works well for a handful of warehouses. At scale (hundreds of stores and warehouses), you may need a dedicated inventory management system feeding Commerce Cloud.

Advanced orchestration. Multi-step fulfilment workflows (partial shipments, backorder management, substitution logic) often require customisation or an external OMS.

Cross-channel order modifications. Changing an in-flight order (adding items, changing delivery address after fulfilment has started) is limited in the built-in OMS.

The built-in OMS covers 80% of standard commerce scenarios. The remaining 20% — complex distributed fulfilment, real-time inventory at massive scale, advanced orchestration — requires extensions or additional services.

To see how Spadoom helps organisations get the most out of SAP Commerce Cloud — from order management to storefront design — visit our SAP Commerce Cloud solution page.

How Does Commerce Cloud Connect to ERP for Fulfilment?

Thirty-nine per cent of B2B buyers are willing to spend $500K+ per online order (McKinsey, 2024). Orders of that size need ERP integration for credit checks, pricing, and fulfilment.

Commerce Cloud connects to SAP S/4HANA and other ERPs through several integration patterns:

SAP Integration Suite. The recommended integration layer for Commerce Cloud ↔ ERP communication. Handles order replication, inventory sync, pricing, and delivery status updates.

Direct API integration. OCC APIs can push orders to ERP systems via middleware. This works but requires custom development and monitoring.

IDoc/BAPI integration. Traditional SAP integration methods still used in many implementations. Orders flow from Commerce Cloud to S/4HANA via IDocs, with inventory updates flowing back.

The critical integration points: order replication (Commerce Cloud → ERP), inventory availability (ERP → Commerce Cloud), pricing and tax (ERP → Commerce Cloud), and delivery status (ERP → Commerce Cloud).

FAQ

Does Commerce Cloud handle real-time inventory?

It supports near-real-time inventory through ATP (Available-to-Promise) checks. Stock levels are synchronised from warehouses and ERP systems. The refresh frequency depends on your integration setup — some implementations sync every few minutes, others near-instantly via event-driven integration.

Can I use Commerce Cloud for marketplace order management?

Commerce Cloud handles orders placed on your own storefront. For marketplace aggregation (managing orders from Amazon, eBay, and your own store in one system), you’d typically use a dedicated marketplace management tool that integrates with Commerce Cloud.

How does order management differ between B2B and B2C?

B2B adds approval workflows, purchase order references, cost centre allocation, and budget checks. B2C orders go straight to fulfilment after payment. B2B orders may need multiple approvals before they can be processed.

What payment gateways work with Commerce Cloud for order management?

Commerce Cloud integrates with major gateways: Stripe, Adyen, PayPal, and SAP’s own payment services. Payment authorisation happens at checkout; capture typically happens at fulfilment. Refunds are triggered through the returns workflow.

Can Commerce Cloud handle subscriptions and recurring orders?

Commerce Cloud supports recurring orders and subscription-like patterns through its cart and order APIs. For full subscription management (billing cycles, plan changes, usage-based pricing), you’d typically integrate a dedicated subscription platform like Zuora or Chargebee.