Storefront Next Release Notes
Learn about Storefront Next features that are part of the Storefront Next monthly releases.
Because the Storefront Next v1.0.0 release was a major launch, the initial release notes of Storefront Next are in Storefront Next Version 1.0.0 Release in the Salesforce Release Notes.
To check out detailed changes in Storefront Next releases, see the releases page in the storefront-next-template GitHub repository. The changes listed in the releases page correspond to merged pull requests, which are the underlying changes of Storefront Next features.
The Load More button replaces numbered pagination on product listing pages, appending products without page reloads or scroll position loss. Shoppers stay in a continuous discovery flow as they click to load more products. A progress indicator shows “Showing X of Y products” to maintain context while browsing. The load more behavior offers a better shopper experience than numbered pagination, which breaks browsing flow because of full page reloads. The Load More button is enabled by default. Use the uiConfig.pages.category.pagination configuration to set pagination properties or switch to numbered pagination.
Where: This feature is available in Storefront Next 1.2.0.
See Also
Save time by choosing the new Beauty Street template for storefronts that offer beauty and cosmetic products. The Beauty Street template is customized for the beauty industry. It provides attributes that are specific to beauty products, a custom layout, theme, and style. As part of storefront setup in Business Manager, select the template that’s most suitable to your storefront’s products and industry.
When: This change is part of B2C Commerce 26.8.
How: In Business Manager, click App Launcher and then select Administration > Sites > Storefronts > New Storefront. Click Use Template for the selected template.
See Also
- Create Storefront Next in Business Manager with a GitHub Repository
- Create Storefront Next in Business Manager with Local Code
- Beauty Street Demo Site
Streamline the checkout experience by offering shoppers multiple payment methods and third-party payment gateways, including Adyen, Stripe, and PayPal, with Salesforce Payments. Simplify the cost and complexity of payment implementation.
Where: This change applies to Storefront Next for B2C Commerce.
When: This feature is available after the B2C Commerce 26.7 release and is in Storefront Next version 1.1.0.
How: In Business Manager, click App Launcher, and then select Merchant Tools > Site > Ordering > Commerce Apps. In the Providers section, for Payments, click Get Started. Install and configure Salesforce Payments.
See Also
- Commerce Apps for B2C Commerce
- Configure Salesforce Payments for B2C Commerce Storefront Next
- Salesforce Payments for B2C Commerce
Configure a shared parent cookie domain to keep shoppers logged in with their baskets preserved when navigating between different subdomains. The domain-level cookie applies to storefronts that use multiple subdomains, such as www. and shop. on the example.com domain. It also applies to hybrid PWA Kit and SFRA storefronts that serve different paths under one parent domain. Without this configuration, shoppers lose their login status and shopping baskets when crossing subdomain boundaries. The loss of login status happens because browsers isolate cookies to individual hosts by default. Prevent frustration and abandoned carts by setting up domain-level cookies.
See Also
As part of upgrading your storefront to Storefront Next 1.1, you must upgrade React Router 7.12 to 7.18. React Router 7.18 provides improved security and stabilized APIs. It fixes an unauthenticated remote-code-execution vulnerability plus four additional security advisories in the turbo-stream dependency. The upgrade replaces several unstable_* API symbols with their stable counterparts, reducing breaking changes in future updates. Pin React Router and every @react-router/* package to 7.18.0 in package.json to prevent using an untested patch. Use the migration guide to perform the upgrade.
Where: This change applies to Storefront Next storefronts that use React Router 7.12 or earlier.
Why: The migration guide organizes the eight API stabilizations by how they surface—silent failures, typecheck-caught issues, and prefix swaps—so you can address high-risk changes first. For instance, the unstable_instrumentations export rename is silent at compile time but causes OpenTelemetry spans to fail at runtime if missed. The guide flags this upfront. You also get fixes for two React Router 7.16+ behavioral changes: an MRT streaming-drain issue that caused long responses to hang, and a fetcher idle-race condition that prevented checkout actions from firing. Both fixes ship in the SDK, so most projects inherit them automatically.
How: To learn more about the migration steps, check out Migrating to React Router 7.18 in the storefront-next-template GitHub repository. The migration guide includes step-by-step instructions, a Claude Code integration, code examples for each rename, and a verification checklist. To automate the migration, paste the guide into a Claude Code session with the framing prompt provided in the “7. Using this guide with Claude Code” section. Claude Code drives the entire rename set while skipping changes your project doesn’t need, such as SDK-internal fixes or test-only updates. After the migration, run the verification checklist to confirm all packages pin exactly to 7.18, typechecking passes, and no instrumentation warnings appear in your dev log.