SAP Commerce Cloud: What Matters in September 2026
SAP Commerce Lead, Spadoom AG
A new storefront can look excellent while showing the wrong contract price. An AI assistant can sound helpful while offering stock that no longer exists. So the useful question about any Commerce release is what it improves in a real buying process, and what you have to test before you rely on it.
This post collects what SAP shipped and announced for SAP Commerce Cloud in 2026, shows where it came from, and lists the checks we put around each item. Research date: 27 September 2026. Where SAP gives no availability date, I say so.
TL;DR: In 2026 SAP moved Commerce Cloud towards AI agents (storefront MCP server announced in January, part of the Q2 release), extended AI product content (details extracted from manuals and spec sheets), introduced an ERP edition for mid-market companies on S/4HANA Public Cloud and partnered with Vercel for Next.js storefronts (templates still in development). On the platform side, Java 17 patch coverage has ended and on-premise mainstream maintenance ended on 31 July 2026. Test each new capability on one representative order before you plan it into a release.
What SAP shipped and announced in 2026
| When | What | Status (as of 27 September 2026) | Source |
|---|---|---|---|
| January 2026 (NRF) | Storefront MCP server: makes products, pricing, stock and promotions usable for AI shopping experiences, including on platforms such as ChatGPT | Announced | SAP News, 8 January 2026 |
| Q1 2026 release | AI extracts details from manuals, spec sheets and PDFs to generate or enrich product descriptions | Released | SAP News, 16 April 2026 |
| May 2026 (Sapphire) | SAP Commerce Cloud, ERP edition for mid-market B2B companies on S/4HANA Public Cloud | Introduced; check availability per deployment | DSAG impulsant |
| Q2 2026 release | Conversational shopping: AI agents query products and availability, manage carts and complete transactions through an MCP server | In the Q2 release | SAP News, 16 July 2026 |
| 31 July 2026 | End of mainstream maintenance for SAP Commerce on-premise (last release 2205) | Passed | SAP Help |
| August 2026 | End of validity of the last JDK 17 update release; regular patches had ended in June | Passed | Release notes for 2211-jdk21 updates |
| 3 September 2026 | Partnership with Vercel: frontend delivery on Vercel, Commerce operations in SAP; Next.js templates in development | Announced, no template date | SAP News, 3 September 2026 |
SAP’s What’s New viewer for SAP Commerce Cloud is the reference for individual features. A news article or partnership announcement is not an upgrade instruction for every tenant.
From NRF 2024 to agentic commerce
The 2026 items did not come out of nowhere. At NRF in January 2024, SAP showed CX AI Toolkit features for Commerce Cloud: AI product tagging, AI-generated product descriptions and bulk editing across large catalogues. The pitch was practical. Merchandisers review and approve suggestions instead of tagging thousands of products by hand.
Two things from that time still matter:
- Product data quality is the foundation. Tags, attributes and descriptions were the first AI use case, and they are now the input for agents. An AI assistant can only recommend what the catalogue describes correctly. The Q1 2026 feature that reads manuals and spec sheets continues exactly this line.
- Recommendations and personalisation remain their own topic. Intelligent Selling Services is still documented as a Commerce Cloud service on SAP Help, and marketing automation sits with SAP Engagement Cloud (formerly SAP Emarsys). We described how ISS works in our post on Intelligent Selling Services.
What changed is the direction. In 2024 AI helped people write content. In 2026 SAP lets AI agents act: search the catalogue, fill a cart, place an order. That shifts the risk from a badly worded description to a wrong order, which is why the checks below matter more than the feature list.
More freedom for the storefront
In its 3 September update, SAP describes separating frontend delivery on Vercel from Commerce operations: preview deployments, global delivery, several brands, regions and languages on one backend. Next.js templates connected to product discovery, content, cart and checkout are described as being developed. Check their availability before committing scope.
You do not have to wait for them. A Next.js frontend on the OCC APIs is possible today; we compare it with Composable Storefront in Composable Storefront vs React/Next.js, and our guide to composable commerce in B2B covers when decoupling pays off.
Our advice: choose one buying journey to assess the approach. A repeat order with customer-specific pricing is a better test than a polished homepage. Include login, account permissions, stock, a failed payment and the order confirmation. Define who operates the frontend and who responds when an API slows down. Separate releases still need shared acceptance criteria.
Commerce actions through AI assistants
SAP’s Q2 release recap describes MCP-based access for AI agents to products, availability, carts and transactions, “within chat or voice interfaces”. We explain the mechanics in our post on the SAP Commerce Cloud MCP server and agentic commerce.
Treat it as an additional buying channel, with the same rules as your webshop:
- Start with product discovery using data you are allowed to expose. Quote requests and ordering come later.
- Test account isolation. An agent acting for buyer A must never see buyer B’s contract prices or order history.
- Require explicit confirmation before anything is ordered, and show the price the ERP will invoice.
- Protect against duplicates. A repeated or interrupted message must not become a second order.
- Keep an audit trail that the support team can actually read when a customer asks what the assistant did.
These are our implementation recommendations, not a claim that every safeguard arrives preconfigured.
An ERP edition for the mid-market
At Sapphire in May 2026 SAP introduced SAP Commerce Cloud, ERP edition: B2B commerce for mid-market companies on S/4HANA Public Cloud, built to feel like an extension of the ERP rather than a separate platform. Spadoom is one of the first partners running a pilot, with a Swiss mid-market B2B customer. Our assessment of what it changes is in SAP Commerce Cloud, ERP Edition for SMEs. For the full Commerce Cloud with S/4HANA Public Cloud, see our post on a B2B webshop on SAP Commerce Cloud with S/4HANA Public Cloud.
The ERP edition matters beyond the product itself: it reflects that in B2B the shop and the ERP are one process. Prices, availability, credit limits and invoices come from the ERP, and the webshop is only as good as that connection.
Platform housekeeping: Java 21 and the on-premise end
Two deadlines have passed, and both still show up in projects.
Java 21 and Spring 6. SAP released the JDK 21 and Spring 6 framework update for Commerce Cloud 2211 in September 2025. The last update release on JDK 17 received regular patches until the end of June 2026, and its validity ended in August 2026. If your project is still on JDK 17, it no longer receives patches. Our Java 21 and Spring 6 migration guide lists the typical breaking changes.
Update releases. Commerce Cloud 2211 receives cumulative update releases, and some new features arrive switched off behind feature toggles (SAP Help: update releases). Switch toggles on deliberately and in time, before SAP removes them.
On-premise. Mainstream maintenance for SAP Commerce on-premise ended on 31 July 2026. Only customer-specific maintenance is available now. Our post on what to do now that on-premise support has ended covers the options.
Turn a feature review into a decision
| Business problem | First experiment | Evidence to collect |
|---|---|---|
| Storefront changes wait for large releases | Release one independent journey | Review time, rollback effort, errors |
| Buyers struggle to identify parts | Assist product discovery with an AI assistant | Correct matches and useful escalation |
| Product data is incomplete | Enrich one product group from spec sheets | Completeness before and after, review effort |
| Checkout creates support tickets | Trace one order across Commerce and ERP | Price consistency and accepted orders |
Agree the baseline before the experiment. Faster development is useful only if customers can still buy correctly and the team can support the result. Include monitoring, access management and ongoing operating costs in the comparison.
Start with your installed landscape
Check editions, entitlements, dependencies and supported versions in SAP’s current release documentation before you plan anything. Keep roadmap items out of a fixed delivery commitment until their availability is confirmed.
At Spadoom we start with one representative order and its exceptions, and we look at the storefront and the ERP side together, because most commerce problems we see sit at that seam. If you are choosing a partner for this work, our overview of SAP Commerce Cloud partners in Switzerland explains what to look for. Or discuss your Commerce setup with us and bring the journey that currently causes the most friction.
Frequently asked questions
What are the most important SAP Commerce Cloud changes in 2026?
Four stand out. SAP announced a storefront MCP server at NRF in January 2026 and included MCP-based access for AI agents in the Q2 2026 release. The Q1 2026 release added AI that extracts product details from manuals and spec sheets. In May SAP introduced an ERP edition for mid-market companies on S/4HANA Public Cloud, and in September a partnership with Vercel for Next.js storefronts.
Is the SAP Commerce Cloud MCP server generally available?
SAP’s Q2 2026 release recap (July 2026) lists conversational shopping through an MCP server as part of the Q2 release. Check availability for your tenant, edition and contract in SAP’s release documentation before planning scope, and test account isolation, explicit order confirmation and duplicate protection before allowing purchases.
Are the Vercel Next.js templates for SAP Commerce Cloud available?
As of September 2026, no. SAP’s announcement of 3 September 2026 says Vercel is developing Next.js storefront templates for Commerce Cloud, without an availability date. You can already build a Next.js frontend on the OCC APIs yourself; the templates would shorten the start.
What happened to the AI announced at NRF 2024?
At NRF 2024 SAP presented CX AI Toolkit features for Commerce Cloud: AI product tagging, AI product descriptions and bulk editing. That line continued: the Q1 2026 release generates or enriches product descriptions from product documents. The newer work goes further, from writing content to letting AI agents search, fill carts and transact.
Do we still need to act on Java 21?
Yes, if you have not moved yet. SAP released the JDK 21 and Spring 6 framework update for Commerce Cloud 2211 in September 2025. The last JDK 17 update release received regular patches until the end of June 2026 and its validity ended in August 2026, so a project still on JDK 17 is outside SAP’s patch coverage.
Ask Spadoom
Answers drawn from what Spadoom has published on this site, with links to the pages they come from.
Try one of these
AI-generated answers. Verify before acting. Questions are stored anonymously, without your IP address, so we can improve our content. Please do not enter personal data.
SAP Commerce Cloud implementation partner
Spadoom is the SAP Commerce Cloud implementation partner across Switzerland, Germany, Austria and Italy. 14-week median go-live. Live customers across DACH.
Related Articles
SAP Commerce On-Premise After 31 July 2026: What Changed and Your Four Options
Mainstream maintenance for SAP Commerce on-premise ended on 31 July 2026. This guide explains what changed, what customer-specific maintenance still covers, where the cost of staying hides, and how the four realistic options compare on time, risk and what you have at the end.
SAP Composable Storefront vs React/Next.js: When to Choose What
SAP's Composable Storefront gives you an Angular storefront with ready-made Commerce Cloud integration; React/Next.js gives you complete freedom. The right choice depends on your team, timeline and long-term plans. Here is how to decide.
Franke's 90-Day SAP Commerce Cloud Launch: What Made It Work
We brought Franke's SAP Commerce Cloud platform live in 90 days, cut manual orders by around 75% and connected more than 10 global channels. The project won the SAP Quality Award for Rapid Time to Value. These are the decisions behind it.