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

SAP used the Sapphire Orlando opening this week to put something on the table the mid-market has been asking about for years: a Commerce Cloud variant that does not require an enterprise budget to deploy. It is called SAP Commerce Cloud, ERP Edition, and the early shape of it is more interesting than the headline suggests.

I write this with two hats on. As CEO of Spadoom we are one of the first pilot partners shipping 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 spent the last two years asking exactly this question. Both perspectives say the same thing: this is the first credible SAP answer for mid-market B2B commerce on cloud ERP, and it is worth taking seriously.

TL;DR: SAP Commerce Cloud, ERP Edition is a stripped-down B2B commerce layer that runs invisibly behind the S/4HANA Public Cloud UI. Users work in ERP-native screens; commerce data sits in SAP Business Data Cloud and Customer Data Cloud; Joule is included; SAP targets 90-day implementations. Public Cloud was announced at Sapphire Orlando (May 2026), Private Cloud follows end-2026. The DSAG has flagged real open points around BDC/CDC migration and Private Cloud delivery — we agree, and we have built custom solutions for similar gaps before. As pilot partners we already know which parts of the story hold up under project conditions.

What was actually announced at Sapphire Orlando

Strip the keynote glitter away and the substance is short. SAP introduced a new edition of Commerce Cloud aimed at small and mid-sized B2B companies that already run S/4HANA Public Cloud. The Public Cloud variant was announced for Sapphire 2026, and the Private Cloud target is end of 2026.

Technically it is a different architecture decision from the classic Commerce Cloud. Commerce becomes a backend layer rather than a front-end product. Users do not log into a separate Commerce console — they open S/4HANA and see order intake, catalogue access, contracts, invoices, and service tickets as native ERP screens. SAP handles the data plumbing through SAP Business Data Cloud (master data) and Customer Data Cloud (identity, consent, segmentation), and Joule sits across the stack for the AI-supported tasks.

The DSAG impulsant write-up captures the architectural intent well — it is worth reading the full piece on DSAG impulsant if you want the user-group view in detail.

The honest answer to an old question

Mid-market companies have been told for years that they had two real B2B commerce choices on the SAP side: take the full Commerce Cloud and accept enterprise scope and budget, or take nothing SAP-native and stitch together a third-party shop that talks to S/4HANA over middleware.

Neither answer was good. Full Commerce Cloud is excellent at what it does — we have shipped it for Franke and global distributors, and it remains the strongest enterprise B2B platform in the market. But for a Swiss industrial KMU doing CHF 50M in B2B revenue, the platform was too much. The middleware route worked technically but cost the buyer the very integration story that drew them to SAP in the first place.

The ERP Edition is the answer that should have been on the table the whole time. Commerce capability where ERP already lives, with SAP carrying the integration burden instead of the customer.

How the ERP Edition works in practice

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

Commerce is invisible. There is no separate storefront framework, no Composable Storefront project, no Spartacus repository to maintain. The customer experience surface is the S/4HANA UI, extended with commerce-native screens for order placement, contract and invoice access, and B2B self-service. From a project perspective this collapses the largest cost driver of a classic Commerce Cloud rollout — the front-end build — to zero.

Master data flows through BDC and CDC. SAP Business Data Cloud handles the master-data product, pricing, and order-related synchronisation. SAP Customer Data Cloud handles identity, consent, and segmentation. The customer no longer integrates Commerce with ERP — SAP integrates them by design. This is the cleanest part of the architecture in my view, and Thomas Henzler from the DSAG executive board called the integration approach via BDC data products “novel and fundamentally sound”, which I think is the right read.

Joule is included by default. Business AI is wired into the new screens rather than added on. For the order-intake and service-portal flows that matter most in B2B mid-market, the AI assist is genuinely useful — order entry suggestion, contract clause lookup, ticket triage. It is not a separate product to license.

The 90-day implementation target 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, the work that remains is configuration and adoption.

What this changes for buyers

Three things change in a way that matters for buying decisions.

The economics work. Removing the storefront build and the integration project changes the project cost profile fundamentally. We are not yet able to share final pricing — SAP will publish that closer to general availability — but the cost shape of the project is now compatible with mid-market budgets, not just enterprise ones.

Time-to-value drops to weeks, not quarters. A 90-day target means a customer who decides this quarter can be in production this year. That is a real shift. The classic SAP Commerce Cloud answer for the same scope would have been 6–9 months minimum.

The buying decision moves up the stack. When commerce is a feature of ERP rather than a separate platform, the conversation moves out of the CIO/digital-team silo and back to the operations and commercial leadership where these decisions actually live in SME organisations. That is healthy.

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

I want to be precise here, because honesty matters more than spin and the DSAG has already raised the right questions.

The first open point is migration for existing SAP CDC and BDC customers. If you already run those platforms in a non-ERP-Edition setup, what is the path forward? SAP has signalled the right intent but the public migration playbook is not yet there. We are tracking this directly through the DSAG working group.

The second is Private Cloud delivery at end-2026. The Public Cloud variant lands at Sapphire — the Private Cloud variant is committed for late this year. For the Swiss and DACH mid-market this matters: a meaningful share of the relevant customers will want the Private Cloud option. The roadmap is right, but the delivery has to land on time. We will know more in the second half of 2026.

These are real points and worth raising openly. They are also exactly the kind of gap that Spadoom has filled in past SAP launches — through custom extensions, transitional integration patterns, and our own tooling where SAP’s first-release scope falls short. We will do the same here if it is needed. Our job as a partner is not to wait for SAP to be perfect, it is to deliver outcomes for our customers regardless.

What we learned from the pilot

We are running the first pilot project for SAP Commerce Cloud, ERP Edition with a Swiss industrial mid-market customer. I can share the lessons even though we are not yet ready to name the customer.

Configuration discipline matters more than custom code. With no storefront to build and no integration layer to design, the project succeeds or fails on how disciplined the team is about scope. The 90-day target is real, but it requires the customer to accept 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 assist is included, but the prompts and grounding need configuration to deliver useful answers in a specific industry. We invested meaningful pilot time on this, and it was worth it.

The ERP team becomes the commerce team. Because commerce screens live in S/4HANA, the people who own them after go-live are the ERP power users, not a separate digital team. That is structurally healthier for SMEs but requires upfront alignment with the customer organisation.

Roadmap discipline counts. Some features that exist in 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. This is where partner experience pays back.

Who the ERP Edition is for

This is not a generic answer. The ERP Edition fits if:

• You sell B2B, not consumer
• You run or are moving to S/4HANA Public Cloud
• You have a manageable catalogue — thousands of SKUs, not hundreds of thousands
• You want commerce to feel like an extension of ERP, not a separate platform
• You can accept a standardised process model in exchange for speed

If you need multi-storefront, multi-brand B2C, complex marketplace logic, or millions of SKUs with deep merchandising — stay on full SAP Commerce Cloud. The ERP Edition is not trying to replace it. It is opening up the segment underneath that the full edition was never the right shape for.

What comes next

Two near-term moments matter.

SAP Sapphire Madrid, 19–21 May 2026. The European chapter of the Sapphire announcement happens at IFEMA Madrid. Pascal Strnad, our Chief Revenue Officer, will be there. If you want to talk about whether the ERP Edition is right for your business, or whether your S/4HANA Public Cloud journey should now include commerce, that is a good week to start the conversation. Reach out to schedule a meeting.

Swiss Customer Relations Forum, 21 May 2026, Zürich. I will be there on the same week, speaking from the DSAG CX perspective on what this announcement means for the Swiss mid-market. If Madrid is not your trip but you are based in CH/DE/AT, this is a closer venue to compare notes.

The Private Cloud variant lands toward the end of the year. We expect more concrete pricing, the migration playbook for existing CDC/BDC customers, and the first publicly-named pilot stories to appear between now and then. We will keep this blog up to date as that picture sharpens — and if your team is evaluating mid-market B2B commerce options, the next six months are a good window to be in the conversation early.

For the full SAP Commerce Cloud portfolio context — pricing, architecture choices, and how the classic edition fits B2B — see our SAP Commerce Cloud Pricing & TCO Guide and the E-Commerce solution overview.