SAP Commerce Cloud: What Matters in September 2026

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. The useful question about a Commerce release is what it improves in a real buying process.

Here are two recent developments worth evaluating, followed by the checks we would put around them. Research date: 13 September 2026.

More freedom for the storefront

In its 3 September update, SAP describes separating frontend delivery with Vercel from Commerce operations. Next.js templates are described as being developed; check their availability before committing scope.

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 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 assistants to products, availability, carts and transactions.

Treat that as an additional buying channel. Start with product discovery using permitted data. Before allowing purchases, test account isolation, explicit confirmation and recovery after interrupted requests. A repeated message must not become a second order. Keep an audit trail that the support team can actually use. These are our implementation recommendations, not a claim that every safeguard arrives preconfigured.

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	Correct matches and useful escalation
Checkout creates support tickets	Trace one order across systems	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. A partnership announcement is not an upgrade instruction for every tenant. Keep roadmap items out of a fixed delivery commitment until their availability is confirmed.

At Spadoom, we would start with one representative order and its exceptions. Discuss your Commerce setup and bring the journey that currently causes the most friction.