SAP Commerce Cloud, ERP Edition: What the New SME Variant Actually Changes

In May 2026, around Sapphire Orlando, SAP put something on the table the mid-market had been asking about for years: a Commerce Cloud variant that does not need an enterprise budget. SAP calls it SAP Commerce Cloud, cloud ERP edition; I use “ERP Edition” for short. The shape of it is more interesting than the headline suggests.

I write this with two hats on. As CEO, I run Spadoom, one of the first pilot partners implementing the new edition. As spokesperson of the DSAG Customer Experience working group in Switzerland, I sit close to the conversation between SAP and customers who have asked exactly this question for the last two years. Both perspectives point the same way: this is the first credible SAP answer for mid-market B2B commerce on cloud ERP.

TL;DR: SAP Commerce Cloud, ERP Edition is B2B commerce built for S/4HANA Public Cloud. The commerce engine connects to the ERP in the background, buyers get self-service, master data flows through SAP Business Data Cloud data products, identity through Customer Data Cloud, and Joule is included. SAP aims for implementations in under 90 days. Status as of September 2026: the Public Cloud variant was announced in May 2026; the Private Cloud variant is targeted for the end of 2026. The DSAG has raised real open points on existing BDC/CDC customers and on delivery. As a pilot partner we already know which parts hold up under project conditions.

Key facts at a glance (status September 2026)

• Product: SAP Commerce Cloud, cloud ERP edition
• Target: small and mid-sized B2B companies on SAP S/4HANA Public Cloud
• Architecture: commerce engine connected to the ERP in the background; no custom storefront build in the standard scope
• Master data: SAP Business Data Cloud data products, provided and managed by SAP; identity via SAP Customer Data Cloud
• AI: SAP Joule included
• Implementation target: under 90 days (SAP’s target)
• Public Cloud: announced May 2026
• Private Cloud: targeted for the end of 2026 (per SAP, subject to change)
• Pilot partners: Spadoom is one of the first

What SAP announced in May

Strip away the keynote language and the substance is short. SAP introduced a new edition of Commerce Cloud for small and mid-sized B2B companies that already run S/4HANA Public Cloud. The Public Cloud variant came first; the Private Cloud variant is targeted for the end of 2026.

Architecturally it is a different decision from the classic Commerce Cloud. The commerce engine becomes a layer that connects to the ERP through SAP interfaces and stays in the background for the people who run operations: they keep working in S/4HANA. Buyers get self-service for prices, order status, invoices and their account. SAP handles the master data through data products in SAP Business Data Cloud, identity and consent through SAP Customer Data Cloud, and Joule runs across the stack. SAP’s own introduction to the cloud ERP edition describes it as commerce “built for the SAP Business Suite”. Our Joule navigator shows which Joule assistants are available and which SAP has only announced.

The DSAG impulsant article of 12 May 2026 is the best summary of the user-group view if you want the detail.

An old question finally gets an answer

For years, mid-market companies had two real B2B commerce options on the SAP side: take the full Commerce Cloud and accept enterprise scope and budget, or skip SAP-native commerce and stitch a third-party shop to S/4HANA over middleware.

Neither was good. Full Commerce Cloud is excellent at what it does. We implemented it for Franke and global distributors, and it remains one of the strongest enterprise B2B platforms on the market. But for a Swiss mid-market B2B company, the platform was often too much. The middleware route worked technically, but cost the buyer the very integration that drew them to SAP. We describe that trade-off in more detail in our post on SAP Commerce Cloud with S/4HANA Public Cloud for B2B.

The ERP Edition is the answer that should have been there all along: commerce capability where the ERP already lives, with SAP carrying more of the integration work.

How the ERP Edition works in practice

Three things differ from the classic Commerce Cloud, and they shape everything else.

No storefront project in the standard scope. There is no custom storefront to build and no Composable Storefront (formerly Spartacus) repository to maintain. Internal users work in S/4HANA; buyers use the self-service that comes with the edition. For a classic Commerce Cloud rollout the front-end build is usually the largest cost block; in the ERP Edition’s standard scope it is not part of the project. If you need a fully branded, custom buyer experience, that is a different project.

Master data flows through BDC and CDC. Data products in SAP Business Data Cloud carry master data such as products and prices; SAP Customer Data Cloud handles identity, consent and segmentation. Thomas Henzler, DSAG board member for sales, production and logistics, called this approach “new and fundamentally sensible”, and because SAP provides and manages the data products, the customer builds no integration of their own. I agree with that reading, with one caveat from the pilot: mapping, data quality, configuration and monitoring remain customer work. SAP removes the integration build, not the integration responsibility.

Joule is part of the package. Business AI is wired into the new flows rather than added later. For order intake and service in B2B mid-market companies, that matters: order suggestions, contract lookups, ticket triage. It still needs configuration to be useful (more on that below). Which AI features SAP offers today, how they are licensed and where they already run in production is summarised on our SAP Business AI page.

SAP’s target of under 90 days makes sense in that context. If you do not build a storefront, do not build an integration layer and do not stand up a separate identity platform, what remains is configuration, data and adoption.

Classic SAP Commerce Cloud vs ERP Edition

Dimension	Classic Commerce Cloud	ERP Edition
Architecture	Standalone platform	Built for S/4HANA Public Cloud
Buyer surface	Composable Storefront or custom front end	Self-service included; no custom storefront build in the standard scope
Integration to ERP	Customer project (weeks to months)	SAP-provided data products via BDC and CDC; configuration and operations stay with the customer
AI	Joule and AI features, depending on licence	Joule included
Implementation	Typically several months	SAP target: under 90 days
Catalogue and complexity	Millions of SKUs, multi-storefront	Mid-market B2B catalogues, standard processes
Best fit	Enterprise B2B/B2C, multi-storefront	Mid-market B2B on S/4HANA Public Cloud
Pricing	Quoted individually (see our pricing guide)	Not yet published as of September 2026

For a side-by-side against Shopify Plus, see our SAP Commerce Cloud, ERP Edition vs Shopify Plus comparison.

What this changes for buyers

The project cost profile changes. Removing the storefront build and the integration project changes where the money goes. SAP has not yet published pricing, so I cannot give you a licence figure. What I can say is that the implementation work shrinks to configuration, data and adoption.

Time to value shrinks. A target of under 90 days means a company that decides this quarter can be live the next. For the same scope, the classic Commerce Cloud usually meant a considerably longer project.

The decision moves closer to the business. When commerce is part of the ERP rather than a separate platform, the conversation leaves the digital-team silo and goes back to operations and commercial leadership, where it belongs in a mid-sized company.

Where SAP still has to deliver, and where we step in

The DSAG has already raised the right questions, and they deserve a precise answer.

The first open point is existing SAP CDC and BDC customers. If you already run those platforms outside the ERP Edition, how do you bring them in? SAP has not yet answered that publicly. We follow it through the DSAG working group.

The second is reliable delivery, including the Private Cloud. The Public Cloud variant came first; the Private Cloud variant is targeted for the end of 2026. For the Swiss and DACH mid-market this matters, because a meaningful share of relevant companies runs Private Cloud. Check the SAP Roadmap Explorer for the current status before you plan around a date.

These gaps are real. They are also the kind Spadoom has closed in earlier SAP launches: with custom extensions, transitional integration patterns and our own tooling where the first release falls short. Because we implement S/4HANA Public Cloud and the CX stack with one team, we see both sides of the seam the ERP Edition sits on. Our job as a partner is to deliver for our customers, not to wait for SAP to be perfect.

What we learned from the pilot

We are one of the first partners running a pilot of SAP Commerce Cloud, ERP Edition, with a Swiss mid-market B2B customer. I can share the lessons even though we cannot name the customer yet.

Configuration discipline matters more than custom code. With no storefront to build and no integration layer to design, the project succeeds or fails on scope discipline. The 90-day target is realistic only if the customer accepts standard processes for things they previously customised. That conversation is the new project-management skill for this product.

Joule needs to be set up, not assumed. The AI assistance is included, but grounding and prompts need configuration to give useful answers in a specific industry. We spent real pilot time on this, and it paid off.

The ERP team becomes the commerce team. Because the commerce processes run through S/4HANA, the people who own them after go-live are ERP key users, not a separate digital team. That is healthier for mid-sized companies, but it needs early alignment in the customer’s organisation.

Roadmap discipline counts. Some features of the full Commerce Cloud are not yet in the ERP Edition. Knowing which are coming, which are out of scope and which we can extend ourselves is the difference between a clean go-live and a stalled project.

Who the ERP Edition is for

The ERP Edition fits if:

• You sell B2B, not to consumers
• You run, or are moving to, S/4HANA Public Cloud
• You have a manageable catalogue and a lot of repeat ordering
• You want commerce to feel like part of the ERP, not a separate platform
• You can accept a standard process model in exchange for speed

If you need multi-storefront, multi-brand B2C, marketplace logic or very large catalogues with deep merchandising, stay with the full SAP Commerce Cloud. The ERP Edition does not replace it; it opens the segment underneath that the full edition never fitted.

Since the announcement

After Orlando, the announcement moved on to Sapphire Madrid and to the Swiss Customer Relations Forum in Zurich in May 2026, where the conversation with Swiss mid-market companies started in earnest. Three things are still outstanding as of September 2026: published pricing, a migration path for existing CDC/BDC customers, and the Private Cloud variant, targeted for the end of the year. We will update this post as they land.

If your team is evaluating mid-market B2B commerce on SAP, now is a good time to join the conversation. Our overview of SAP partners for cloud ERP and CRM in Switzerland explains why commerce, ERP and CRM from one team matters here, and how S/4HANA Public Cloud and Sales Cloud V2 work as one stack shows the same principle on the sales side. Talk to us about the ERP Edition.

Sources and further reading

• DSAG impulsant: Commerce Cloud for SMEs, the DSAG user-group article (12 May 2026, German)
• SAP Learning: Introducing SAP Commerce Cloud, Cloud ERP Edition, SAP’s product introduction
• SAP Roadmap Explorer, current delivery dates
• Our news post on the Sapphire 2026 announcement
• SAP Commerce Cloud pricing and TCO guide, context on the classic edition
• E-commerce solution overview, Spadoom’s SAP Commerce Cloud delivery