Salesforce has introduced Storefront Next, a modern React-based storefront template for Salesforce B2C Commerce (SFCC).
Currently available as a pilot/beta offering, Storefront Next gives teams a composable storefront architecture built with React 19, React Router 7, Vite, Tailwind CSS, and SCAPI integrations.
Rather than replacing Commerce Cloud’s backend capabilities, Storefront Next modernizes the presentation layer while Commerce Cloud continues managing:
- cart and checkout
- pricing and promotions
- customer identity and sessions
- order orchestration
- catalog and inventory services
For commerce teams evaluating modern frontend architectures, Storefront Next represents an important shift toward API-driven, React-native storefront development within the Salesforce ecosystem.
What Is Storefront Next?
Storefront Next is a Salesforce-published React storefront template and toolkit for building composable B2C Commerce experiences.
According to the official repository, it is:
“A production-ready React storefront template for Salesforce B2C Commerce, built with React Router 7 and React 19.”
The stack includes:
- React 19
- React Router 7
- Vite
- Tailwind CSS 4
- SCAPI integrations
- TypeScript
- SSR support
- Storybook
- Vitest
Unlike traditional SFRA implementations, Storefront Next separates frontend rendering from backend commerce operations.
The storefront becomes a standalone React application while Commerce Cloud remains the commerce engine and system of record.
Key Architectural Shift
The biggest change is architectural.
Traditional SFRA storefronts tightly coupled templates, controllers, and backend logic inside Commerce Cloud cartridges.
Storefront Next moves toward a composable model where:
- frontend rendering happens in React
- commerce operations are exposed through APIs
- teams can adopt modern frontend tooling and workflows
- deployments align more closely with modern JavaScript ecosystems
This creates more flexibility for teams building:
- experience-led storefronts
- component-driven UI systems
- headless integrations
- content-rich commerce experiences
- multi-channel frontend strategies
Core Technology Stack
React 19 + React Router 7
Storefront Next uses React 19 with React Router 7 for routing and rendering.
This allows teams to use modern React patterns while supporting server-side rendering (SSR) for performance and SEO.
For React teams already familiar with modern frontend architectures, the development experience feels significantly more aligned with current industry standards than legacy commerce templating systems.
Vite-Based Development
The framework uses Vite for builds and local development.
This improves:
- local development speed
- hot module reload performance
- frontend tooling compatibility
- developer experience
Compared to older enterprise storefront stacks, the setup feels much closer to mainstream React application development.
Tailwind CSS 4
Styling is built around Tailwind CSS 4.
This encourages:
- utility-first styling
- rapid prototyping
- component consistency
- scalable design systems
For teams already operating in Figma-to-component workflows, this model can reduce frontend handoff friction considerably.
Commerce Cloud Still Handles Core Commerce Logic
Even though the storefront is decoupled, Commerce Cloud still manages critical commerce operations.
That includes:
- checkout flows
- promotions
- pricing
- customer data
- sessions
- inventory
- order orchestration
The frontend communicates with Commerce Cloud primarily through SCAPI APIs.
This means brands can modernize the experience layer without rebuilding core commerce infrastructure.
Managed Runtime and Deployment
Storefront Next supports deployment through Salesforce Managed Runtime using the Commerce Cloud CLI.
Typical workflows include:
pnpm build
pnpm pushThe repository also includes built-in support for:
- environment-driven configuration
- staging/production deployment flows
- B2C CLI tooling
- TypeScript enforcement
- Storybook workflows
- testing and linting pipelines
Because the storefront is fundamentally a React/Vite application, teams may also evaluate external hosting strategies depending on architectural requirements.
Why This Matters for Commerce Teams
Modern Frontend Hiring
One practical advantage is talent availability.
React developers are significantly easier to hire than deeply specialized SFRA developers.
That lowers onboarding friction and expands the available frontend talent pool for Commerce Cloud projects.
Better Component-Driven Development
Storefront Next aligns more naturally with:
- design systems
- component libraries
- Storybook workflows
- frontend CI/CD pipelines
- modern testing practices
This is especially valuable for enterprise teams standardizing frontend engineering practices across platforms.
Improved Flexibility
A composable architecture makes it easier to integrate:
- headless CMS platforms
- personalization engines
- experimentation tools
- analytics platforms
- search services
- AI-assisted experiences
The framework itself is not inherently “AI-first,” but its API-driven architecture makes those integrations easier to implement cleanly.
Important Reality Check: It’s Still Pilot/Beta
One thing teams should not ignore:
Storefront Next is currently a pilot/beta offering.
That matters because storefront architecture decisions impact:
- deployment pipelines
- QA processes
- caching strategies
- ownership models
- integration layers
- operational complexity
For many enterprise brands, the technology itself is only part of the challenge.
Migration planning, coexistence with SFRA, governance, and operational maturity will matter just as much.
Is It a Replacement for SFRA?
Not directly.
Storefront Next is better viewed as a modern composable storefront direction rather than a drop-in replacement for every SFRA implementation.
Many existing SFRA storefronts will continue operating for years.
However, for new builds and modernization initiatives, Storefront Next clearly signals Salesforce’s broader move toward React-native and API-first storefront architectures.
Key Takeaways
- Storefront Next is a modern React storefront architecture for Salesforce B2C Commerce
- The stack uses React 19, React Router 7, Vite, Tailwind CSS, and SCAPI
- Commerce Cloud still manages core commerce operations and backend business logic
- The framework supports composable, API-driven storefront development
- Managed Runtime and Commerce Cloud CLI remain central deployment components
- It is currently a pilot/beta offering and should be evaluated accordingly
For commerce teams exploring frontend modernization inside the Salesforce ecosystem, Storefront Next is an important release worth watching closely.
Sources
- SalesforceCommerceCloud/storefront-next-template GitHub repository
- @salesforce/storefront-next-dev NPM package
FAQ
Where should teams host Storefront Next?
If you want Salesforce-managed operational simplicity, start with managed runtime using the Commerce Cloud CLI.
If you need deeper cloud-standard control (observability, networking, edge patterns), consider external hosting — while keeping Commerce Cloud APIs as the backend.
What’s the biggest mistake teams make going headless?
Treating it as a “frontend rewrite” only.
Headless succeeds when you also define API contracts, caching, identity/session strategy, and operational ownership.
If you need a baseline for that model, our headless commerce architecture guide covers the core patterns.
Posted by Beenu, Tailored Intelligence
Date: May 2026
