Salesforce B2C Commerce has long powered some of retail's most complex ecommerce businesses. But the expectations placed on the storefront have changed: faster experiences, richer personalization, greater flexibility for business teams, and development velocity that does not come at the expense of maintainability.
Salesforce Storefront Next is Salesforce's answer to that shift: a modern storefront architecture built for B2C Commerce using React 19, React Router 7, TypeScript, Tailwind CSS, and Salesforce Commerce APIs.
For teams running Salesforce Commerce Cloud, it creates a more modern path to delivering the experiences customers expect without disconnecting the storefront from the commerce platform, merchandising tools, and operational workflows they already rely on.
Why storefront architecture has become a revenue issue
The storefront is where commerce strategy becomes customer experience. Every delay, layout shift, broken interaction, irrelevant recommendation, and cumbersome publishing workflow has a cost.
For enterprise teams, the problem is rarely a lack of ideas. It is the inability to deliver, test, and improve those ideas quickly enough. Older storefront approaches can push too much work into the browser, make performance difficult to sustain, and force business users and developers into disconnected workflows.
Storefront Next is designed to address those constraints with an architecture that puts server rendering, performance, personalization, and modern development practices at the center.
What Storefront Next is
Storefront Next is a production-ready React storefront foundation for Salesforce B2C Commerce. Its open-source Storefront Next template includes React 19, React Router 7, server-side rendering, SCAPI integration, TypeScript, Tailwind CSS, Storybook, automated testing, internationalization support, and deployment tooling for Salesforce Managed Runtime.
It is not simply a new theme. It is a new implementation model for teams that want more control over the customer experience while continuing to use Salesforce B2C Commerce as their commerce engine.
The architectural choices matter.
React Router 7 in framework mode supports server rendering for initial page loads. Streaming SSR and intelligent hydration reduce the amount of browser-side processing required to render a page. Tailwind and shadcn/ui help keep the front end lighter. Together, these choices create a stronger foundation for faster customer experiences and improved Core Web Vitals.
That is important because performance is not a technical vanity metric. Faster storefronts support discovery, engagement, conversion, and revenue. They also make it easier for teams to keep improving the experience without accumulating avoidable front-end weight and complexity.
Performance that supports conversion
Storefront Next is built with a server-first approach to rendering. Rather than asking the browser to assemble the entire storefront after a customer arrives, the server can deliver useful content earlier and reduce the client-side work needed to make the experience interactive.
For shoppers, that can mean faster perceived load times, more stable pages, and less friction moving from landing page to product discovery to checkout.
For commerce teams, it creates a better foundation for performance engineering. Teams can focus on the work that genuinely affects customer outcomes: reducing unnecessary JavaScript, optimizing images and third-party integrations, improving page rendering paths, and monitoring real-user performance over time.
The architecture does not guarantee good Core Web Vitals. No framework can compensate for excessive tags, poorly managed personalization, oversized assets, or undisciplined releases. But it gives teams a much stronger starting point than a client-heavy storefront built without modern performance principles.
Personalization without defaulting to a slower experience
Personalization has often created an uncomfortable tradeoff in ecommerce: deliver a more relevant experience, or preserve page performance.
Storefront Next is designed to reduce that tradeoff. Its server-side personalization and cookie-based user-state management allow tailored content and data to be delivered without relying entirely on expensive client-side processing.
That matters for retailers that want to personalize content, merchandising, promotions, and customer journeys without turning every page into a collection of third-party scripts and delayed browser calls.
The opportunity is larger than showing a customer's name or swapping a hero banner. Better personalization can support more relevant category experiences, product discovery, offers, and content—all while preserving the speed and stability required to convert.
The key is discipline. Personalization should be treated as a measured revenue lever, with clear hypotheses, test plans, performance guardrails, and a way to determine whether it is actually improving conversion or average order value.
Better workflows for business and engineering teams
Enterprise commerce teams need both speed and control. Business users need the ability to manage content and campaigns. Developers need a clean, testable, maintainable way to build differentiated experiences.
Storefront Next is built to bridge those needs. It supports Salesforce Page Designer for business-managed content while giving developers pro-code routes and components for experiences that require more control.
That is a practical improvement over forcing every experience into one system or the other.
A merchandising team should not need an engineering release to update every campaign module. An engineering team should not need to force complex product discovery, account, or conversion flows into a visual content tool that was not designed for them.
This split allows each group to work where it is strongest, while preserving a shared storefront system and visual language.
A modern foundation for delivery velocity
The Storefront Next template brings together the practices modern engineering teams expect: TypeScript, file-based routing, component development in Storybook, unit testing with Vitest, code quality tooling, and a clear deployment path through Salesforce Managed Runtime.
These are not merely developer conveniences. They help teams move faster with less risk.
A well-structured component library reduces reinvention. Storybook helps teams develop and review interfaces before they become full pages. Automated testing and type safety help catch defects earlier. Clear configuration and environment-variable support make implementations easier to manage through multiple environments.
The result should be more predictable delivery: faster iteration on revenue opportunities, fewer regressions, and a storefront that remains understandable as the business grows.
Storefront Next also has an AI-ready dimension. Salesforce positions it for AI-assisted development through the B2C Developer Toolkit and AI-assisted shopping through Shopper Agent. The value will depend on the use case and implementation quality, but the architecture gives teams a more current foundation for incorporating these capabilities responsibly.
Who should evaluate Storefront Next now?
Storefront Next deserves consideration from Salesforce Commerce Cloud teams that are:
- Building a new B2C Commerce storefront
- Modernizing a storefront with performance, maintainability, or delivery-velocity constraints
- Evaluating the path forward from PWA Kit
- Struggling to balance Page Designer flexibility with differentiated pro-code experiences
- Investing in personalization, AI-assisted commerce, or a broader frontend modernization program
The right decision depends on the current storefront, business priorities, integrations, delivery model, and migration risk. A team with a stable storefront and no near-term experience roadmap may not need to move immediately. A team facing slow releases, poor mobile performance, mounting front-end complexity, or aggressive growth goals should take a closer look.
What Storefront Next does not solve on its own
Storefront Next is a stronger foundation. It is not an automatic growth program.
It will not fix weak UX, unclear merchandising, fragmented customer data, poor analytics, excessive third-party scripts, or a backlog with no prioritization discipline. It will not create a testing culture, establish performance governance, or turn technical releases into measurable commercial outcomes by itself.
Those capabilities must be built into the operating model.
The greatest value comes when a modern storefront architecture is paired with continuous performance engineering, conversion optimization, analytics discipline, and a delivery team that can connect technical decisions to customer and revenue outcomes.
Considering Storefront Next?
Storefront Next gives Salesforce B2C Commerce teams a more modern foundation for performance, personalization, delivery velocity, and continuous storefront improvement.
If you are considering a migration to Storefront Next—or want help assessing the architecture, planning the migration, improving performance, optimizing conversion, modernizing UX, or establishing a stronger delivery model—contact Space Dinosaurs to schedule a discovery call.