Adobe Commerce's September 2026 Storefront Release: What B2B and Headless Teams Need to Verify

Adobe shipped its September 2026 Commerce Storefront release with six changes worth a headless or B2B team's attention, and one of them ships with an action item that will break company registration on B2B enabled backends if you skip it. This is a drop in and component release, not a platform overhaul, which means most of it is low risk. The reCAPTCHA change is not in that category.

What shipped

Feature	What changed	Who it affects
Free Gift Selection	Shoppers pick their own complimentary gift when a cart qualifies for a Free Gift cart price rule, instead of one being automatically applied. The gift shows at zero price with a label in order history and returns	Any storefront using Free Gift cart price rules
Payment Services expansion	The Payment Services drop in (v4.2.1) adds Google Pay and PayPal Buttons alongside existing credit card and Apple Pay support. Apple Pay separately gained coupon code support	Any storefront using the Payment Services drop in
Multiple Named Wishlists	Shoppers can create multiple wishlists instead of one default list. Guest wishlists are saved for a defined period so non authenticated users can retrieve previously saved items	Storefronts with wishlist functionality enabled
B2B Company Address Book	B2B buyers get a shared company address book across account management, checkout, and quote workflows, with role based permissions governing who can view, add, edit, or delete addresses	B2B storefronts
Accessibility enhancements	Improvements to cart, account, and search for screen readers and keyboard navigation, supporting compliance with accessibility standards	All storefronts, more directly relevant to teams with WCAG obligations
B2B reCAPTCHA fix	Company registration forms now require an explicit opt in for reCAPTCHA verification, fixing prior failures on non B2B enabled backends	B2B storefronts specifically, action required

The versions behind this release

Component	Version
Drop in SDK	v2.1.0
Cart	v3.4.0
Checkout	v3.4.0
Payment Services	v4.2.1
User Account	v4.2.0
Wishlist	v3.5.0
Company Management (B2B)	v1.5.0

The change that actually requires action

The reCAPTCHA fix is described as fixing prior failures on non B2B enabled backends, which means the underlying behavior changed in a way that requires explicit configuration on B2B storefronts specifically: passing { b2bEnabled: true } to the reCAPTCHA configuration. Skip this on a B2B enabled storefront and company registration forms are the part that breaks, quietly, at exactly the point where a new business customer is trying to sign up.

This is a small configuration line with an outsized failure mode, because it fails silently from the storefront team's perspective until a prospective B2B customer reports they cannot register, and by then it has already cost conversions. Any team running Adobe Commerce with Company Management enabled should treat this as a release blocking check, not a nice to have, before this version reaches production.

Why Multiple Named Wishlists and the B2B Address Book matter beyond the changelog line

Both of these features solve the same underlying problem from opposite sides of the customer base. Multiple Named Wishlists moves consumer facing storefronts closer to feature parity with what shoppers already expect from marketplace scale competitors, where a single undifferentiated wishlist stopped being sufficient once customers started using wishlists for genuinely different purposes: a gift list, a personal shopping list, and a project specific list.

The B2B Company Address Book solves a real operational pain point for any B2B storefront with more than a handful of users per account. Before this release, address management for a company account meant every buyer maintaining their own address book, with no shared source of truth and no way to enforce who could add or modify a shipping location for the company as a whole. Role based permissions on a shared address book is the kind of feature that reads as minor in a changelog and turns out to be the thing an enterprise buyer specifically asks about during a platform evaluation, because it maps directly onto how their actual procurement and shipping approval process works.

What to verify before this reaches production

Check	Why
B2B storefronts pass { b2bEnabled: true } to reCAPTCHA config	Prevents company registration form failures
Payment Services drop in updated to v4.2.1 before enabling Google Pay or PayPal Buttons	New payment methods depend on the updated version
Free Gift cart price rules tested against the new selection flow	Behavior changed from automatic assignment to shopper selection, which affects order history and returns display
Accessibility enhancements spot checked against your own custom cart and account components	Adobe's improvements cover the stock components; custom overrides may not inherit them automatically
Company Management permission roles reviewed after the address book rollout	New shared address book introduces new permission surface that did not exist before this release

When this applies to your stack

If you run a B2B enabled Adobe Commerce storefront, the reCAPTCHA configuration change is not optional and should be treated as a release blocker, not a follow up task. If you run a consumer facing storefront using the Payment Services drop in or Free Gift cart price rules, the new payment methods and gift selection flow are worth testing against your specific checkout customizations before this version reaches customers, since drop in updates can interact unpredictably with theme level overrides.

Contra Collective builds and maintains Adobe Commerce and headless storefront integrations for enterprise clients, including release verification and upgrade planning that catches exactly this kind of configuration dependent breaking change before it reaches production. If your team does not have a standing process for reviewing what a component version bump actually requires, that gap is worth closing before the next release cycle, not just this one.

FAQ

Does the reCAPTCHA change affect storefronts without B2B or Company Management enabled? The fix specifically addresses failures on non B2B enabled backends, and the required action, passing { b2bEnabled: true }, is specific to B2B storefronts. Consumer only storefronts without Company Management enabled are less likely to be affected, but should still verify registration flows after upgrading.

Is this release a required upgrade or an optional one? Adobe Commerce Storefront releases are component level drop in updates rather than mandatory platform upgrades. Whether to take this release depends on whether your storefront needs the specific features it ships, though any B2B storefront planning to adopt Company Management features should be on a version that includes the address book and its associated reCAPTCHA fix.

Do Multiple Named Wishlists require a data migration for existing customer wishlists? The release notes describe existing guest wishlists as remaining saved for a designated retrieval period, which suggests existing wishlist data carries forward, but any team with heavily customized wishlist functionality should verify this against their specific implementation before assuming a clean migration.

What is the risk of skipping the Payment Services drop in update? Storefronts that do not update to Payment Services v4.2.1 simply will not have access to the new Google Pay, PayPal Buttons, or Apple Pay coupon code support. There is no forced breaking change for storefronts that stay on the prior version, making this a lower priority update than the reCAPTCHA fix for storefronts not actively adding these payment methods.