SAP Commerce Cloud

What is SAP Commerce Cloud?

SAP Commerce Cloud is SAP’s enterprise e-commerce platform for B2B and B2C selling, hosted as a managed cloud service on Microsoft Azure. Formerly known as SAP Hybris, it ships a product catalogue engine built for millions of SKUs, customer-specific pricing from SAP condition records, multi-warehouse order management, and standard integration content for SAP S/4HANA. Modern implementations use SAP Composable Storefront, an Angular-based headless PWA, formerly Spartacus, to decouple frontend and commerce engine. SAP’s official Commerce Cloud product page is the canonical reference. SAP has been named a Leader in the Gartner Magic Quadrant for Digital Commerce 11 years running (2014–2025).

Spadoom is a Swiss SAP Gold Partner for Cloud ERP and Customer Experience, and implements Commerce Cloud across Switzerland, Germany, Austria and Italy, with the ERP integration delivered by the same team. Our DACH CX practice is led by Dario Pedol, spokesperson of the DSAG (German-speaking SAP user group) CX working group Switzerland. The rest of this page covers which edition fits which buyer, what we deliver, how Cloud Edition compares to the new ERP Edition, what it costs, and where we have put it into production.

Case study, Franke: 90 days from legacy to SAP Quality Award

Our most-cited project. Franke had a stalled custom B2B e-commerce build. We replaced it with SAP Commerce Cloud in 90 days: composable storefront, B2B pricing, full SAP ERP integration. The result: an SAP Quality Award for implementation quality and a platform that now serves Franke’s global distribution network. Read the full Franke story for the timeline, migration approach, and lessons learned.

SAP Commerce Cloud editions: Cloud Edition vs ERP Edition vs on-premise

In 2026 SAP ships three commerce products under similar names. Buyers regularly ask us which one they actually need. The short answer:

Edition	Best for	Architecture	Go-live	Where it lives
SAP Commerce Cloud (Cloud Edition)	Enterprise B2B and B2C with complex catalogues (≥100k SKUs), multi-country, deep ERP integration	Standalone commerce engine, composable storefront, OCC REST APIs	Set after discovery (Franke: 90 days)	SAP-managed cloud on Azure
SAP Commerce Cloud, ERP Edition	SMEs and mid-market on S/4HANA Public Cloud who need B2B commerce without a separate platform	B2B storefront built into S/4HANA Public Cloud, master data via SAP Business Data Cloud, Joule included	SAP targets 90 days	Inside S/4HANA Public Cloud
SAP Commerce (on-premise / Hybris)	Existing customers on the legacy platform	Self-hosted, monolithic	n/a (in end-of-mainstream-maintenance transition)	Customer data centre

Cloud Edition is the right answer for most enterprise scenarios, and the focus of this page. It is what we built for Franke and what we migrate hybris customers onto.

ERP Edition is the credible new SAP answer for the mid-market on S/4HANA Public Cloud, unveiled at SAP Sapphire Orlando in May 2026. Spadoom is one of the first pilot partners delivering it. See our ERP Edition deep dive and the Cloud Edition vs Shopify Plus and ERP Edition vs Shopify Plus comparisons.

On-premise hybris is in transition. If you are still on it, our Hybris end-of-life migration checklist and 90-day migration playbook lay out the path off it.

New for SMEs: SAP Commerce Cloud, ERP Edition

At SAP Sapphire Orlando in May 2026, SAP unveiled the SAP Commerce Cloud, ERP Edition: a lightweight B2B commerce variant built into S/4HANA Public Cloud, with master data flowing through SAP Business Data Cloud and Customer Data Cloud, Joule included, and a 90-day implementation target. It is the first credible SAP commerce answer for the mid-market on cloud ERP, and Spadoom is one of the first pilot partners delivering it. For the full architectural and strategic breakdown, see our DSAG-CX-spokesperson take on the ERP Edition.

What Spadoom delivers

Our track record in SAP Commerce Cloud is long and specific. We built Franke’s award-winning B2B platform in 90 days: a project that replaced a stalled custom build and won an SAP Quality Award. We’ve migrated distributors off legacy hybris accelerators to SAP Commerce Cloud Composable Storefront. We’ve scaled catalogue management for companies with 3+ million SKUs across multiple countries and languages.

As an SAP Gold Partner with offices in Switzerland, Italy, Austria, and Estonia, we bring local presence across the DACH region and Southern Europe. No offshore handoffs. The architects who scope your project are the same people who configure your storefront and train your team. When something breaks at 8 AM on a Monday, you call someone in your time zone.

What we handle end to end:

• Storefront build: composable or accelerator, B2B or B2C, single-brand or multi-brand
• Catalogue setup: product modelling, variant management, classification, and localisation for millions of SKUs
• Pricing and promotions: customer-specific pricing, tiered discounts, and promotion rules that work with your existing SAP condition records
• SAP ERP integration: bidirectional sync with S/4HANA or ECC for pricing, stock, orders, and customer master data
• B2B workflows: punch-out, order approval chains, budget management, and customer-specific product visibility
• Training and hyper-care: we don’t leave after go-live. Four weeks of active support, issue resolution, and adoption tracking

Our delivery follows SAP Activate methodology, five phases from discovery through hyper-care, adapted for SAP Commerce Cloud projects. Discovery takes two weeks. We map your catalogue structure, pricing rules, order workflows, and integration points before a single line of code is written.

For a full technical overview of the platform, from product content management to order orchestration, see our SAP Commerce Cloud A-Z Handbook.

ROI you can measure

E-commerce projects live or die on numbers, so we are careful about which ones we quote. What our own projects show: Franke cut manual orders by 75% after moving to SAP Commerce Cloud, and Distrelec’s headless re-architecture shortened time-to-market by 70% and lifted conversion by 15%. Both are documented in the case studies linked on this page.

Where the gains come from is no secret. B2B buyers who can check stock, see their contract prices and reorder online stop calling or emailing inside sales for routine orders, and the errors of phone and fax entry disappear. What that is worth depends on your order volume, your channel mix and how much of today’s ordering is manual.

We build the business case with your own order data during discovery, not from generic benchmarks.

Independent validation

The analyst community has consistently recognised SAP Commerce Cloud. In the 2025 Gartner Magic Quadrant for Digital Commerce, SAP was named a Leader for the 11th consecutive year. That reflects continued investment in composable architecture, B2B capabilities, and AI-driven personalisation.

SAP Commerce Cloud is also a Leader in both the IDC MarketScape for Enterprise B2B Digital Commerce (2023–2024) and the IDC MarketScape for Enterprise B2C Digital Commerce (2024).

On G2 (based on verified user reviews, 2025):

Category	SAP Commerce Cloud	Shopify Plus	Adobe Commerce
Overall Rating	4.0	4.4	4.0
Ease of Use	8.4	8.9	n/a
Quality of Support	8.6	8.4	n/a

Shopify Plus leads on ease of use: expected for a platform designed for rapid setup and smaller catalogues. SAP Commerce Cloud scores higher on quality of support and matches Adobe Commerce overall despite serving a more complex B2B market. For organisations already running SAP ERP, the integration advantage compounds the platform advantage. For head-to-head comparisons, see our SAP Commerce Cloud vs Shopify Plus and vs Adobe Commerce analysis pages.

Platform reliability at scale: During Cyber Week 2025, SAP Commerce Cloud processed $17.8 billion in gross merchandise value (up 40% year-over-year) with 100% platform uptime. The previous year saw 18.2 million orders during the same peak period, again, zero downtime (source: SAP Commerce Cloud Year in Review, 2025).

Composable Storefront: the modern architecture

If you’re starting fresh or replacing an older hybris accelerator, composable storefront is the right direction. SAP Commerce Cloud Composable Storefront (formerly Spartacus) decouples the frontend from the commerce engine entirely, see the official SAP Composable Storefront documentation for the full architecture reference. The storefront is an Angular-based progressive web app (PWA) that talks to the commerce backend via OCC REST APIs.

What that means in practice:

• Faster page loads. The frontend is a static PWA served from a CDN. Product pages render client-side without round-trips to the commerce server.
• Independent deployments. Your frontend team ships UI changes without touching the backend. Your backend team updates pricing rules without a full storefront release. Two separate release cycles.
• Full design control. No Freemarker templates. No JSP. Standard Angular components with your own design system. Mobile-first by default.
• Future-proof. SAP’s active investment is in the composable architecture. The classic accelerator still works, but new features ship for composable first.

When to use the accelerator instead: If you need an internal B2B portal where function matters more than UX, the accelerator approach still works. It is faster to configure, needs less frontend skill and covers much of standard B2B self-service out of the box. We’ll tell you which fits your situation, not the one that maximises project scope.

For a deeper dive on composable architecture, OCC APIs, and implementation patterns, see our SAP Commerce Cloud A-Z Handbook.

SAP Commerce Cloud on-premise to cloud migration

This is a question we get every week. SAP directs new feature development to SAP Commerce Cloud; the on-premise version still receives maintenance and security patches, but no new capabilities. If you’re running SAP Hybris on-premise, it pays to plan the move before a deadline plans it for you.

Our migration methodology:

We don’t rip and replace. We’ve developed a phased approach based on what we learned migrating Franke, which won an SAP Quality Award:

1. Assessment. Map your current customisations, extensions, and integrations. Identify what transfers directly, what needs rebuilding, and what you can drop.
2. Customer-facing layer first. Launch the new composable storefront on top of your existing catalogue and pricing data. Customers see a modern frontend. Backend stays stable.
3. Catalogue and order management. Migrate product content, pricing rules, and order workflows to the cloud instance. Run both systems in parallel with order routing.
4. Decommission. Cut over remaining traffic. Shut down the on-premise instance.

The new storefront goes live before the backend migration is finished, so customers get the better experience early while the backend moves behind the scenes. Your actual timeline comes out of the assessment.

What trips people up: Data migration is not a copy-paste job. Product classifications, price lists with thousands of condition records, and customer-specific catalogue views all need validation. We build automated migration scripts with data quality checks at every stage. If your legacy system has 50,000 products with incomplete attributes, we catch that in week one, not in week twelve.

The other common mistake is trying to replicate every customisation from the old system. In most migrations, a good share of the legacy extensions turns out to be unnecessary. We help you separate what matters from what was built to work around old platform limitations.

We documented the full playbook, timelines, risk mitigation, and data migration patterns, in our 90-day migration playbook. It’s based on real projects, not theory.

Pricing and licensing

SAP Commerce Cloud licensing is based on gross merchandise volume (GMV) and traffic tiers, not a simple per-user price. That makes direct comparison tricky, but here’s a realistic picture:

	SAP Commerce Cloud	Shopify Plus	Adobe Commerce (Magento)
Pricing model	GMV + traffic tiers	Revenue-based	Licence + GMV tiers
Annual licence (mid-market)	Depends on GMV, traffic and modules	See current vendor price list	See current vendor price list
B2B features	Native: punch-out, account pricing, approval workflows	Limited, requires apps	Available with B2B module
SAP ERP integration	Standard integration content (mapping and monitoring still needed)	Third-party middleware	Third-party middleware
Multi-country / multi-brand	Built-in with shared catalogue	Separate stores (Plus only)	Multi-store with shared backend
Composable / headless	Yes (Composable Storefront)	Hydrogen (newer)	PWA Studio / Hyva
Hosting	SAP-managed cloud (Azure)	Shopify-managed	Self-hosted or Adobe-managed

The real cost question is total cost of ownership. If you already run SAP ERP, SAP’s standard integration content gives Commerce Cloud a shorter path to pricing, stock and orders than a third-party connector layer. It does not make integration free: mapping, error handling and monitoring still have to be built and run. Whether the higher licence pays off depends on your order volume, your B2B complexity and how much of the ERP process the shop has to reach. We work that out with you before you sign.

Spadoom gives you a fixed price for clearly defined scopes and, for larger programmes, a cost range after discovery, covering implementation, training and hyper-care. Change requests are agreed before work starts, not discovered at month four.

Industry use cases

SAP Commerce Cloud is built for catalogue complexity and process depth. Here’s where we’ve deployed it:

Manufacturing and industrial distribution: The core use case. Distributors with 500,000+ SKUs need customer-specific pricing, multi-warehouse stock visibility, and order approval workflows. We configure punch-out catalogues for procurement system integration (SAP Ariba, Coupa) and set up reorder lists that let buyers repeat last month’s order in two clicks. Real-time stock and pricing from S/4HANA means no more “sorry, that price changed” emails after order submission. For companies with field sales teams, the same platform serves both the self-service portal and the sales rep’s order entry: same prices, same stock, one system.

Consumer goods and retail: B2C brands with high SKU counts, seasonal catalogues, and multi-country storefronts. SAP Commerce Cloud handles localised content, currency, tax rules, and shipping per market, all from a single catalogue. The personalisation engine serves different promotions to different customer segments without custom code. One catalogue, one order management system, one integration layer, but each country gets its own storefront, pricing, and fulfilment logic.

Automotive aftermarket: Parts catalogues are a special kind of complex. Vehicle fitment data, supersession chains, and cross-reference lookups on top of standard e-commerce. We’ve built SAP Commerce Cloud storefronts that integrate with TecDoc and ETKA catalogues, serving the right parts for the right vehicle without forcing buyers to know part numbers.

Food and beverage: B2B ordering with minimum order quantities, case-pack logic, delivery window scheduling, and temperature-controlled logistics integration. SAP Commerce Cloud’s order management handles split shipments across multiple warehouses and delivery routes. Route accounting integration with SAP ERP closes the loop from order to delivery to invoice. We’ve configured recurring order schedules that let restaurant and hospitality buyers set up weekly standing orders, so buyers no longer re-enter their regular products by hand.

The integration advantage

SAP Commerce Cloud’s strongest differentiator is how it connects to the rest of your SAP landscape. This is not an abstract benefit: it directly affects your order accuracy, pricing consistency, and operational efficiency.

S/4HANA and ECC integration: Bidirectional, through SAP’s standard integration content. Stock on the storefront comes from S/4HANA, orders land in SAP as sales orders, and prices come from SAP’s condition records, so the price online matches the price in the ERP. That still takes mapping, error handling and monitoring, and we scope it up front. For Meier Tobler we built exactly this backbone on SAP Integration Suite.

SAP CPQ: For complex B2B quoting (configurable products, tiered pricing, multi-step approvals), CPQ plugs directly into Commerce Cloud so buyers configure and price products inside the same storefront session. Essential for manufacturers selling configurable industrial equipment, automotive aftermarket bundles, or any catalogue where price depends on configuration.

SAP Engagement Cloud (formerly Emarsys) (marketing automation): Connect your commerce data to SAP Engagement Cloud for abandoned cart recovery, post-purchase campaigns, and personalised product recommendations based on browsing and purchase behaviour. SAP provides standard integration content. Campaign performance data flows back into commerce analytics.

SAP Customer Data Platform: Unify customer profiles across your storefront, service desk, and marketing channels. CDP collects behavioural data from Commerce Cloud (product views, searches, purchases) and combines it with CRM and service interactions. The result: a single customer view that powers personalisation across every touchpoint.

SAP Customer Identity (CIAM): Enterprise-grade authentication and consent management for your storefront. Single sign-on across multiple brand sites, progressive profiling, and GDPR-compliant consent tracking. Essential for multi-brand or multi-country deployments where customers expect one login across all your properties.

When these systems work together, the storefront knows your customer across sales, service, marketing and ERP. A B2B buyer who called your service desk yesterday can see a follow-up when they log in today, and a campaign for high-value customers uses actual purchase data, not guesses.

Commerce projects rarely fail in the storefront. They fail at the ERP seam: the order that will not post, the price the shop cannot resolve, the stock figure nobody trusts. Spadoom delivers the ERP side with the same team, from SAP S/4HANA Public Cloud to side-by-side extensions on SAP BTP. Still on ECC? The five-day S/4HANA readiness check sets the timeline and cost range, and our transformation guide shows how commerce, CRM and ERP fit together. SAP documents the supported integration capabilities of SAP Integration Suite.

SAP Commerce Cloud implementation in Switzerland

Spadoom is headquartered in Zug, and Switzerland is our home market, not a flag on a coverage map. Our two most-cited Commerce Cloud references are Swiss companies. Franke, the Swiss kitchen and home solutions group, is the 90-day rebuild that won an SAP Quality Award and cut manual orders by 75% across 10+ global channels. Distrelec, the B2B electronics distributor with Switzerland as its home market, is where our headless re-architecture reduced time-to-market by 70% and lifted conversion by 15%. And for Meier Tobler, the Swiss building-technology supplier, we built the SAP Integration Suite backbone that keeps their online shop and S/4HANA in real-time sync: over 1 million messages a month.

Implementing commerce for the Swiss market comes with requirements that standard EU playbooks miss, and we build them in from day one:

• Data protection: dual compliance with the Swiss nDSG (nLPD) and GDPR, consent, privacy texts, and data-residency options covered for both regimes
• Currency and tax: CHF and EUR price lists side by side, with correct VAT determination per destination and cross-border customs handling for a non-EU country
• Languages: German, French, and Italian storefronts (plus English) with per-locale content, category structures, and legal texts
• Swiss payments: TWINT and PostFinance integrated via Datatrans or Saferpay alongside international card processing
• Swiss ERP landscapes: real-time integration with S/4HANA, on-premise or public cloud, the way we delivered it for Franke and Meier Tobler

We documented the full Swiss and DACH delivery approach, payments, VAT corridors, nDSG vs GDPR, logistics, in our Commerce Cloud in Switzerland and DACH implementation guide. How we work with Swiss teams across ERP and CX is summarised on our page on SAP CX consulting in Switzerland.

What good looks like

A well-implemented SAP Commerce Cloud means:

• Fewer order errors. Self-service ordering with pricing and stock from the ERP removes the misquotes and out-of-stock surprises that come with phone and fax ordering
• B2B buyers who actually order online. If your buyers are still calling instead of ordering online, something went wrong in the implementation. We track adoption and fix friction points during hyper-care
• The next country is a configuration exercise. Once the first storefront runs, rolling out to additional markets is mostly content and configuration, not a development project
• Fast pages everywhere. Composable storefront with CDN delivery keeps pages fast in every market, not just at home
• More reorders. B2B buyers who can reorder their regular items in two clicks do it more often. That is revenue you were not capturing before

Six months after go-live, we measure these points with you against the baseline from discovery. We stay accountable through hyper-care and beyond.

Ready to discuss your SAP Commerce Cloud project? Whether you’re building a new storefront, migrating from on-premise hybris, or replacing a platform that’s holding you back, we’ll give you an honest assessment. Start the conversation or explore our CRM in 10 Days package if you’re also looking at SAP Sales Cloud.

Evaluating providers? Our market roundup of the best SAP Commerce Cloud implementation partners in Switzerland shows how we compare, and who else deserves a look.