SAP Commerce Cloud: Features, Architecture, and What It Actually Does

SAP Commerce Cloud is SAP’s enterprise commerce platform for B2B, B2C and B2B2C, and its main argument is the back end: prices, stock, credit limits and orders come from or go to SAP ERP instead of being rebuilt next to it. That makes it a strong platform for companies with complex catalogues and B2B processes, and an expensive one for companies that do not need either.

This guide covers what the platform does, how its architecture is built, how it is used in different industries, where it sits next to the ERP and the rest of SAP CX, and when a simpler platform is the better choice.

TL;DR: SAP Commerce Cloud (formerly SAP Hybris) handles catalogue, pricing, orders and B2B processes natively and connects them to SAP ERP. Its architecture has five layers (Platform, commerce modules, product content management, OCC APIs, Composable Storefront), and you customise it through extensions instead of changing SAP’s code. It fits companies that run SAP ERP, sell B2B or across several countries and have a complex catalogue; for a simple direct-to-consumer shop it is usually too much.

What is SAP Commerce Cloud?

SAP Commerce Cloud is the cloud edition of the platform many teams still know as SAP Hybris. SAP runs it as a managed service: infrastructure, scaling and platform patches are SAP’s job, while your team or your partner builds and maintains the custom code. It is part of the SAP CX portfolio alongside Sales Cloud, Service Cloud and SAP Engagement Cloud (formerly SAP Emarsys). SAP’s product documentation covers the full feature scope.

What sets it apart from generic shop systems:

• B2B in the data model. Organisation hierarchies, approval workflows, contract pricing, punchout catalogues and self-service portals are part of the core, not a plugin on top of a B2C shop.
• ERP as the source of truth. Prices, available-to-promise stock and credit checks can come directly from SAP S/4HANA or ECC, and orders flow back into order-to-cash.
• Product content management. Built-in PCM handles complex hierarchies, classifications, variants and multilingual content, so many customers do without a separate PIM system.
• Multi-site, multi-country. One installation serves several brands, countries, languages and currencies, with localised tax, shipping and payment.
• A headless storefront. The SAP Composable Storefront (formerly Spartacus) is an Angular front end that talks to the platform only through APIs.

SAP has been named a Leader in the Gartner Magic Quadrant for Digital Commerce for eleven consecutive years (SAP News, November 2025). Useful as a market signal; whether it fits your business depends on the points above. Where else SAP holds Leader positions, and how to weigh them in a selection, is covered in what SAP’s Gartner Magic Quadrant positions mean in practice.

What are the core features?

Product and catalogue management

Configurable products, bundles, multi-dimensional variants (size, colour, region) and classification systems. Product data is maintained in Backoffice, loaded with ImpEx scripts or taken from SAP ERP master data. Catalogue versioning lets you prepare a staged catalogue and publish it in one step.

Order management

The full order lifecycle: cart, checkout, payment, fulfilment, returns and refunds. For B2B this includes approval workflows, purchase-order checkout and, with SAP ERP connected, credit checks and available-to-promise inventory.

Personalisation and search

Rules-based personalisation adapts recommendations, content and promotions to segment and context. Search is Solr-based with faceted navigation, boosting rules and synonym management. It is solid for most catalogues; very large or search-driven B2C shops sometimes add a specialised search service.

Integration

Commerce Cloud connects to SAP systems through integration packs and SAP Integration Suite, and to everything else through REST APIs: payment providers, tax engines, shipping services and procurement systems. How much work the integration is depends on your scenario; the ERP mapping of prices and order types is usually the largest item.

How is the architecture built?

Every architecture decision in Commerce Cloud is a trade-off: customise too aggressively and you pile up upgrade debt, stay too close to the standard and you cannot differentiate. Knowing the layers makes that trade-off visible.

Layer	What it does
Platform	Type system (data model declared in XML), persistence, Spring framework, extension mechanism, caching and clustering
Commerce modules	Cart and checkout, pricing and promotions, order management, customer management including B2B organisations, Solr search
Product content management	Hierarchies, classifications, variants, media, catalogue versions
OCC APIs (Omni Commerce Connect)	REST endpoints that expose the commerce functions to storefronts, apps and third-party systems
Composable Storefront	Angular front end with server-side rendering, driven by CMS content from SmartEdit

The type system is the concept to learn first. You declare item types, attributes and relations in XML; extensions add new types without touching existing ones, and the platform takes care of the database tables. Spring runs through the whole stack: services are beans you can override or replace. The OCC APIs are the decoupling layer that makes headless commerce possible, whether the front end is the Composable Storefront, a mobile app or a custom React application.

How the extension mechanism works

All functionality ships as extensions, and your own code does too. You declare custom item types, override Spring beans to change standard behaviour and add or adapt OCC endpoints, while SAP’s delivered code stays untouched. When SAP releases an update, your customisations do not collide with it. Teams that modify core code instead create upgrade debt that has to be paid on every release; we have taken over installations like that, and cleaning them up is slow work.

A sensible order for customisation

1. Configuration first: standard settings and business rules.
2. Existing extensions second: SAP’s delivered extensions and certified add-ons.
3. Custom extensions third: your own code, following SAP’s patterns.
4. Core modification never.

Every custom extension has to be carried through upgrades, so this order directly shapes your total cost of ownership. SAP’s ongoing platform upgrades, such as the move to Java 21 and Spring 6, are much less painful when custom code stays in clean extensions.

How is it used in B2B, B2C and different industries?

A B2C fashion retailer and a B2B manufacturer use the same platform in very different ways. The data model, the checkout and the integrations differ.

	B2C	B2B
Customer model	Individual accounts	Organisations with units, roles and budgets
Pricing	List prices and promotions	Contract, tiered and customer-specific prices, often from ERP
Checkout	Immediate payment	Approvals, purchase order, credit check
Catalogue	Shared catalogue	Customer-specific catalogues
Ordering	Single items	Bulk order, quick order, reorder
Integration	Payment and shipping	ERP, punchout (cXML/OCI), EDI

Both run on one installation if needed: B2B2C is a standard configuration, with separate storefronts sharing product data, order management and the ERP connection.

Retail and fashion. Multi-dimensional variants, visual merchandising with SmartEdit, seasonal catalogue changes and built-in returns handling. Campaigns come from SAP Engagement Cloud, and purchase data flows back for attribution.

Manufacturing and spare parts. Deep product hierarchies, technical attributes, compatibility and supersession data, and ordering based on the installed equipment. At Franke, the B2B platform we built reduced manual orders by 75% and now serves as the hub for more than ten global channels.

Wholesale and distribution. Customer-specific assortments, volume pricing, quick order entry and punchout into procurement systems such as SAP Ariba or Coupa. Getting the permission model for buyers, approvers and administrators right is a large share of the work.

Automotive and configurable products. Constraint-based configuration, dealer portals with territory-based pricing and after-sales parts commerce with fitment data.

High-tech and subscriptions. Bundles of hardware, software and services, subscription ordering and renewals, connected to SAP’s subscription billing.

Marketplaces with many third-party sellers, commission management and split payments are not part of the standard; they need an additional marketplace solution.

Where does Commerce Cloud sit next to ERP and SAP CX?

Commerce Cloud is the transactional front of the landscape. The other systems feed it or use its data:

• SAP S/4HANA provides the commercial backbone: prices, stock, credit, fulfilment and invoicing.
• SAP Engagement Cloud brings customers to the shop with personalised campaigns and receives purchase data.
• Sales Cloud V2 manages the B2B relationship: quotes, opportunities and account management.
• Service Cloud V2 handles after-sales with full order visibility.
• Customer Data Platform combines the customer profile across commerce, marketing and service.

Most commerce projects that go wrong do not fail in the storefront; they fail at the ERP seam, where an order will not post or a price cannot be resolved. That is why we deliver commerce and the ERP core with one team. How that works for S/4HANA Public Cloud and SAP CX together is described in our post on the integrated S/4HANA Public Cloud and Sales Cloud V2 stack and in our guide to choosing an SAP partner for Cloud ERP and CRM in Switzerland.

Commerce Cloud or SAP Commerce on-premise?

It is the same code base with two operating models. Commerce Cloud runs on SAP’s managed infrastructure with patching, scaling and monitoring included. SAP Commerce on-premise runs on your own infrastructure; its last release is 2205, and mainstream maintenance ended on 31 July 2026. Since then only customer-specific maintenance is available. If you still run on-premise, our post on what to do now that on-premise support has ended covers the options.

When does SAP Commerce Cloud make sense?

It is an enterprise platform with enterprise complexity and cost. If you do not need what it does, you pay for complexity without getting anything back.

Strong fit:

• You run SAP ERP (S/4HANA or ECC) and want prices, stock and orders connected in real time.
• You sell B2B with complex pricing, approval workflows and organisation hierarchies.
• You serve several countries, languages and currencies from one platform.
• You need B2B and B2C on the same platform.
• Your catalogue has complex classifications or configurable products.

Usually not the right fit:

• Direct-to-consumer brands with simple catalogues (Shopify or BigCommerce will do).
• Businesses that need to launch within weeks.
• Companies with no SAP footprint and no plans for one.

Smaller SAP customers should also look at the SAP Commerce Cloud ERP Edition, a leaner B2B commerce layer for mid-market companies on S/4HANA Public Cloud that SAP announced in May 2026. For costs, see our pricing and TCO guide; for the project itself, see what actually happens in a Commerce Cloud implementation. And if you are comparing partners, our overview of the best SAP Commerce Cloud partners in Switzerland explains what to look for. More on our approach is on the SAP Commerce Cloud solution page.

For Swiss B2B and B2C projects, our page on SAP CX consulting in Switzerland explains how we connect Commerce Cloud to the rest of the CX stack and the ERP.

FAQ

What is SAP Commerce Cloud?

SAP Commerce Cloud (formerly SAP Hybris) is SAP’s enterprise commerce platform for B2B, B2C and B2B2C, run by SAP as a managed cloud service. It combines product content management, order management, B2B functions such as organisation hierarchies and contract pricing, the OCC REST APIs and the SAP Composable Storefront, and it connects to SAP ERP for pricing, availability and order processing.

How is SAP Commerce Cloud different from Shopify or Magento?

The difference is depth in B2B and in the ERP connection. Commerce Cloud models organisation hierarchies, approval workflows, customer-specific catalogues and contract pricing in its core data model, and it can take prices, availability and credit checks from SAP ERP. Shopify Plus launches faster and costs less for simple catalogues; Adobe Commerce (Magento) is flexible but needs more integration work around SAP. If you do not run SAP ERP and sell a simple catalogue, a lighter platform is usually the better choice.

What does SAP Commerce Cloud cost?

SAP does not publish a price list. Contracts are negotiated and are typically based on order volume, gross merchandise value (GMV) or a mix of both, with managed hosting included. Implementation and running costs come on top; our pricing and TCO guide breaks down the typical ranges.

Can Commerce Cloud run without SAP ERP?

Yes. It has its own product, pricing and order management and can connect to non-SAP back ends through its APIs. Its strongest advantages, such as real-time ERP pricing, available-to-promise stock, credit checks and an integrated order-to-cash process, only come into play when SAP ERP is connected.

How long does a Commerce Cloud implementation take?

Plan on four to eight months for a typical implementation. A B2C storefront with standard features can go live in three to four months; B2B projects with customer-specific pricing, approval workflows and ERP integration usually need six to eight months. Migrations from SAP Commerce on-premise follow their own plan, because code and data already exist; our 90-day migration playbook describes one approach.

Can I run B2B and B2C on the same Commerce Cloud instance?

Yes. B2B2C is a standard setup: you configure separate base stores and storefronts for B2B and B2C, each with its own catalogue, pricing, checkout and design, while product data, order management and the ERP integration are shared.