Salesforce officially launched Storefront Next in 2026 — and unlike most "frontend refresh" announcements, this one is a genuine architectural shift for Salesforce B2C Commerce (SFCC). If you're running a storefront on PWA Kit, or you're still on the older SFRA template, this is the release that determines your roadmap for the next two to three years.
Here's what changed, why Salesforce built it now, and how to think about timing your migration.
What Actually Changed
Storefront Next replaces the SFRA-based rendering model that PWA Kit was built on top of with a modern, composable stack:
React 19
instead of the older React versions PWA Kit shipped with
React Router 7
for routing, replacing PWA Kit's routing layer
Vite
as the build tool, replacing the older Webpack-based tooling
A production-ready
Storefront Next Template
for B2C Commerce, positioned as a "speed, simplicity, and conversion" focused starting point rather than a heavily abstracted framework
Salesforce has also published a documented migration path from PWA Kit to Storefront Next, which matters — this isn't a "rebuild from scratch" situation for brands already on PWA Kit, but it also isn't a drop-in upgrade. The rendering model and tooling both change, so component-level and integration-level work is still required.
There's a practical deadline attached to this too: Salesforce Managed Runtime is retiring support for HTTP (non-secure) proxy configurations on August 31, 2026, after which only HTTPS proxy configurations will be supported. If you're on Managed Runtime with legacy proxy config, that's a firm date to plan around regardless of whether you're moving to Storefront Next yet.
Why Salesforce Built This Now
For the last five years, Shopify Plus won a huge share of mid-market and enterprise brands that might otherwise have considered SFCC — largely on the argument that SFCC implementations were slow, expensive, and complex to get live. Storefront Next is Salesforce's direct answer to that objection.
The target audience isn't primarily existing SFCC customers being told to rip and replace. It's brands currently on Magento, Oracle Commerce, HCL, or SAP Hybris who want to modernize but don't want a multi-year re-platforming project. Storefront Next, paired with prebuilt composable patterns, is meant to compress what used to be a quarters-or-years-long build into something far more incremental and controlled.
That combination — enterprise-grade flexibility with a build timeline that's actually competitive — is genuinely new for SFCC.
The AI Layer Isn't a Bolt-On Feature
Storefront Next is being marketed as "AI-ready," but the more accurate framing is that it's a foundation designed so AI-assisted development actually works well against it: cleaner component structure, more predictable patterns, and an architecture that automated tooling can extend without guessing at inconsistent conventions.
This lines up with broader changes across the Commerce Cloud platform in 2026. The B2C Commerce 26.1 release (rolled out December 2025–January 2026) introduced guided shopping experiences, where a shopping agent helps customers narrow down products through conversational questions rather than static filters, plus new reporting inside Commerce Intelligence dashboards that attributes orders and revenue directly to AI shopping agent interactions. The subsequent Agentforce Commerce B2C 26.6 release (May–June 2026) extended this further across shopper identity, catalog operations, search analytics, and Business Manager productivity.
The pattern is consistent: Salesforce isn't just modernizing the frontend framework, it's building the storefront layer to be the thing AI agents and AI-assisted teams operate on top of. A messy, inconsistent implementation will fight that just as hard as it fights human developers — arguably worse, since AI tooling tends to amplify existing architectural problems rather than smooth them over.
Should You Migrate Now?
The right timing depends on where you're starting from:
Already on PWA Kit. You have the shortest path. Salesforce's published migration guidance exists specifically for this case, and most of your integration and data-model work carries over conceptually even though the rendering layer changes. This is the group with the least reason to wait, especially given the Managed Runtime HTTP proxy retirement deadline.
Still on SFRA (no PWA Kit). You're making a bigger jump either way, so it's worth evaluating whether to go straight to Storefront Next rather than migrating to PWA Kit first and then migrating again shortly after. For most brands in this position, skipping straight to Storefront Next is the more efficient path.
Evaluating SFCC for the first time, coming from Magento, Oracle, HCL, or Hybris. This is exactly who Salesforce built the release for. Storefront Next is worth putting on your shortlist alongside Shopify Plus and other composable options — the build-time argument that used to favor Shopify is materially weaker than it was even a year ago.
Where Migrations Go Wrong
A faster, more approachable framework doesn't remove the ways an SFCC implementation can go sideways — if anything, it makes it easier to build quickly and build poorly at the same time. The recurring failure patterns worth watching for:
Over-engineered components
built by teams treating Storefront Next like a traditional, heavily-customized SFRA project instead of a leaner composable one
Misaligned data models
, since the integration layer is still where most of the real implementation work lives, and AI-assisted tooling won't get this right without a team that understands the underlying data structures
Inconsistent, AI-generated code
from teams leaning on AI tooling without the composable-architecture experience to review its output critically
A frontend that's technically modern but operationally fragile
— new stack, same (or worse) performance and maintainability as before
None of these are reasons to avoid the migration. They're reasons to be deliberate about how it's scoped and who's doing the implementation work.
How RStackGro Can Help
We build and migrate SFCC storefronts, PWA implementations, and Next.js/React frontends for ecommerce brands moving toward composable architecture. If you're weighing a PWA Kit to Storefront Next migration, evaluating SFCC against Shopify Plus for the first time, or trying to understand what the Managed Runtime deadline actually means for your current setup, we can help you scope the work before you commit to a timeline or a vendor.
Get in touch for a free consultation on your SFCC or composable commerce roadmap.
Need Help With Your Project?
RStackGro specializes in web, app, and ecommerce development. Get a free consultation.
Get a Free Quote →