Noibu blog

Salesforce Commerce Cloud September 2026 Release: What to Check

Megan Glover

October 22, 2026

Blogs

After Salesforce's September 2026 B2C Commerce release, retest checkout, any integration that still depends on OCAPI, and page speed on live traffic. The release makes SCAPI the default for new realms, adds SFRA checkout consent capture and new bot and leaked-credential WAF fields, and each change can alter what shoppers experience.

Salesforce published its B2C Commerce September '26 release overview on October 1, 2026. Most of the list is feature news. For a store owner, the useful question is narrower: which of these changes can touch checkout, speed or integrations, and how do you know they behaved after they reached your storefront?

TL;DR

Salesforce's overview, published October 1, 2026, lists changes to checkout, bot protection, APIs and request tracing.
Retest three things first: the full checkout path, anything that still calls OCAPI, and speed on your busiest page groups.
Compare errors and Core Web Vitals before and after the change reaches your storefront, using real shopper traffic.
Noibu's Performance and Bug Resolution agents can run those comparisons and hand results back for your approval.

What changed in the September 2026 B2C Commerce release?

Salesforce's overview groups the release into storefront, checkout, consent, performance and monitoring, API and headless, and inventory changes. These are the items that matter most for store health, with the wording taken from Salesforce's own post.

What Salesforce listed, and what to watch

Area	Change named by Salesforce	Why a store owner should care
Checkout	SFRA Checkout Consent Capture, which captures shopper marketing consents during SFRA checkout	A new element in the checkout path. Salesforce says it adds no friction to order completion, which is worth confirming on your own store.
Checkout	Multiple Tax Items on Basket Line Items, up to 10 tax values per line item	Needs Salesforce Order Management. Test totals on mixed baskets.
Security	Bot and Leaked Credential Protection through new eCDN custom WAF fields	Rules that throttle or block traffic can also catch real shoppers if they are set too tightly.
APIs	SCAPI is the default for new realms, and B2C CLI 2.0 is SCAPI-native with OCAPI functionality described as deprecated	Integrations and scripts built on OCAPI deserve an inventory and a test plan.
Monitoring	End-to-End Request Tracing (Beta) in Log Center	Helps trace a request across services when latency or errors show up.
Shopper agent	Product comparisons and customizable components for the shopper agent	New on-page behavior to check for layout and speed impact.

Which changes can affect shoppers on a live store?

Checkout changes carry the most risk because a problem there stops orders directly. Consent capture adds a step to a flow that already loses shoppers, so test it on mobile and on slow connections as well as desktop.

WAF and bot rules carry a quieter risk. A rule that throttles automated traffic can also slow or block real shoppers on shared networks, and the symptom is usually a small drop in conversion rather than a visible error.

API changes carry a delayed risk. New realms build on SCAPI, so teams that maintain older integrations should list every script, connector and job that still depends on OCAPI before Salesforce's deprecation timeline reaches them.

What should you test after the release reaches your storefront?

Five post-release checks for a Commerce Cloud store

Checkout path

Place test orders through guest and signed-in checkout on mobile and desktop, including a mixed-tax basket.

OCAPI inventory

List every integration, job and script that still calls OCAPI, and note its owner.

Speed

Compare Core Web Vitals for product, cart and checkout page groups before and after.

WAF rules

Watch conversion and error rates for segments the new rules could catch.

Consent step

Confirm the consent capture renders and submits on every checkout variant.

Run the first check by hand, because a person placing an order catches problems that dashboards miss. Run the other four against real traffic, because staging environments rarely reproduce shopper devices, networks and third-party scripts.

How can AI agents help with post-release checks?

A release check is repetitive work: measure, compare, find the cause of any change, and decide what to do. Noibu's agents are built for that loop. The Performance agent measures Core Web Vitals from real shopper traffic, ranks the weakest page groups and stages a change for review. The Bug Resolution agent finds the top issues, traces root causes in your codebase and opens a pull request for your review.

Nothing ships until you approve it, and every approved change makes the next recommendation sharper. The agents work in the Noibu console and in the AI tools your team already uses, so the same checks can run wherever you work. For background on how this works on Commerce Cloud specifically, see AI agents for Salesforce Commerce Cloud stores and how to check if last night's deploy broke anything on your store.

Not sure where your store stands today? Noibu's free website audit runs all six agents on your own store data and puts changes live with your approval.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Frequently asked questions

When was the Salesforce B2C Commerce September 2026 release announced?

Salesforce published its B2C Commerce September 2026 release overview on October 1, 2026. The post names features across storefront, checkout, consent, performance, API and inventory areas but does not give a single release date.

Does the release change how checkout works on SFRA?

Salesforce lists SFRA Checkout Consent Capture, which captures shopper marketing consents during SFRA checkout. Salesforce says it adds no friction to order completion. Test the step on every checkout variant and device before assuming that holds for your store.

What does SCAPI becoming the default mean for my integrations?

New B2C Commerce realms now build directly on SCAPI, and Salesforce describes OCAPI functionality as deprecated in B2C CLI 2.0. Existing integrations should be inventoried so owners know which ones still depend on OCAPI and can plan changes.

How do I tell whether a release slowed my store?

Compare Core Web Vitals and error rates for the same page groups before and after the change reaches your storefront, using real shopper traffic rather than lab tests alone. A difference concentrated in one page group points to the cause.

Can Noibu's agents run these checks on Commerce Cloud?

Noibu's Performance agent measures Core Web Vitals from real shopper traffic, and the Bug Resolution agent finds top issues and traces root causes. Both hand results back for your approval before anything ships.