Beyond PWA Kit: Why Storefront Next is the Future of Salesforce Commerce Cloud
Salesforce
5 MIN READ
July 29, 2026
Salesforce Commerce Cloud has always evolved in bold architectural leaps. SiteGenesis gave way to SFRA, SFRA gave way to headless PWA Kit, and now the platform is taking its most significant leap: Storefront Next, built under the sfnext paradigm.
If your brand is planning a headless transition or maintaining a first-generation PWA Kit build, this shift demands your attention. Storefront Next redefines the frontend developer experience, modernizes data orchestration, introduces streaming capabilities, and embeds agentic AI at the architecture’s core.
This blog breaks down how PWA Kit and Storefront Next compare across every critical layer and what it means for SFCC teams building today.
The Digital Commerce Stack Is Under Pressure
Enterprise retail technology is no longer just about going headless. It is about building architectures that carry AI workloads, stream content at millisecond speeds, and give merchandising teams genuine autonomy without relying on developer cycles.
According to a Harvard Business Review Analytic Services report, “AI: The Secret to a Thriving E-Commerce Business,” 70% of commerce leaders say implementing AI in e-commerce operations is very or extremely important, while 90% believe personalized customer experiences are critical to future success. For many enterprises, that means partnering with a team that has deep Salesforce Agentforce Commerce implementation experience across both legacy and next-generation architectures.
Gen 1 vs. Gen 2 Composable: The Structural Divide
PWA Kit (Gen 1 Headless) was built during the SPA era. It uses a custom Express.js layer to enable SSR, often forcing developers to manually bridge headless flexibility with legacy cartridge synchronization. A major step forward from SFRA, but it carries the technical assumptions of its time.
Storefront Next (Gen 2 Headless) is not an incremental update. It is a complete rebuild, trading legacy technical debt for native modern web standards: Vite, Tailwind CSS 4, and React Router 7. It turns the storefront into a streaming, server-driven asset optimized for speed, AI compatibility, and merchant control.
For a broader look at how Salesforce’s headless options fit together, see our guide to Salesforce Headless 360.
Comprehensive Comparison: PWA Kit vs. Storefront Next
| Architectural Aspect | PWA Kit | Storefront Next (sfnext) |
|---|---|---|
| Core Framework | React 17/18 with custom Express.js runtime | React 19 with React Router 7 (Full Framework Mode) |
| Build Tooling | Webpack + Babel with slower hot reloads | Vite v7 + pnpm workspaces with sub-second hot reloads |
| Styling Pipeline | Chakra UI with runtime JavaScript styling | Tailwind CSS 4 + shadcn/ui with build-time utility CSS |
| Rendering Model | Traditional server-side rendering (SSR) | Streaming SSR with instant structural HTML delivery |
| Page Designer Integration | Manual JSON mapping and cartridge creation | Automated synchronization using code decorators |
| Data Mutations | Client-heavy React hooks via Commerce SDK | Server-side Data Loaders and Actions |
| AI Integration | Limited to standard Einstein API calls | Native Agentforce Commerce integration with typed, structured AI interfaces |
Rendering and Core Web Vitals
PWA Kit structures pages via monolithic SSR: the Express server fetches all catalog, pricing, and inventory data, assembles the page, then sends it down. One slow backend microservice creates a bottleneck for the entire response.
Storefront Next uses React Router 7’s Streaming SSR. Layout and core assets push to the browser immediately. High-latency dynamic calls, such as real-time inventory checks or personalized pricing, stream in over the open HTTP connection while the shopper interacts with what is already visible.
By shifting to compile-time CSS via Tailwind CSS 4 and server-side data fetching via native Loaders, Storefront Next reduces initial JavaScript bundle size by over 40% compared to typical PWA Kit footprints, with measurable improvements in INP and LCP scores.
We saw similar performance and CX gains first-hand while delivering an AI-driven headless commerce PWA Kit implementation for a retail client.
Eliminating the Headless Tax: Page Designer Automation
Getting a custom PWA Kit component into Business Manager’s Page Designer required writing JSON meta schemas, creating a custom cartridge, registering config files, and deploying manually. Storefront Next eliminates this by treating component code as the single source of truth. Developers annotate React components with built-in decorators:
The sfnext CLI scans these decorators, formats the meta-JSON, packages it into SFCC cartridges, and deploys to sandbox automatically. Developers write clean UI code. Merchandisers get immediate drag-and-drop inside Page Designer. No manual handoff required.
Preparing for Agentforce Commerce
Salesforce’s Agentforce Commerce requires a predictable, strictly typed architecture to operate accurately. PWA Kit configurations, often modified with custom client-side fetch flows and mixed routing workarounds, make it difficult for AI agents to accurately predict data flows. Storefront Next separates its data layer into explicit, server-driven Loaders and Actions. This structure allows AI routines to safely interact with components, generate reliable automated test coverage, and interface with backend APIs without ambiguity.
If Agentforce itself is new to your team, our guide to Agentforce’s features and benefits is a useful starting point before evaluating Storefront Next.
Real-World Proof: Salesforce B2B Commerce Cloud in Action
A global tire and fleet service manufacturer operating across hundreds of US and European stores processed over 60% of its B2B orders by phone and email. Fleet operators had no self-service channel, contracted pricing was invisible until a buyer called a rep, and ERP systems were completely disconnected from any customer-facing interface.
Ksolves built a Salesforce B2B Commerce Cloud (LWR) platform with real-time ERP and pricing integration, Mirakl fleet schedule management, Salesforce Scheduler appointment booking, and an Experience Cloud partner portal with role-based access.
See How This Played Out for a Global Fleet Manufacturer
The Strategic Verdict
Starting from scratch today: Choose Storefront Next. Salesforce is actively preparing to phase out the first-generation PWA Kit. Storefront Next sets up your architecture for the next decade.
Running an existing PWA Kit site: PWA Kit remains stable and functional. Avoid adding new large-scale technical debt to it and start budgeting a migration path to take advantage of React 19 streaming and the upcoming Agentforce merchant toolset.
How Ksolves Can Help
As a Salesforce Summit Partner and AI-first company, Ksolves brings deep hands-on expertise to SFCC implementations, migrations, and architecture strategy. Through our Salesforce consulting services, we help enterprises assess their current SFCC footprint, define the right migration path, and build storefronts engineered for performance and AI readiness. Whether you are planning a first Storefront Next deployment or migrating from PWA Kit, our certified team accelerates your timeline and reduces architectural risk.
Conclusion
Streaming SSR compresses Core Web Vitals. Automated Page Designer sync removes the headless tax on merchandising teams. Native Agentforce compatibility positions the platform for the AI era. Teams that act now will build a compounding performance and capability advantage over those still investing in Gen 1 headless architecture.
Planning Your Storefront Next Roadmap?
Frequently Asked Questions
What is Salesforce Storefront Next?
Storefront Next is Salesforce’s next-generation headless commerce framework for Salesforce Commerce Cloud, built on React 19, React Router 7, Vite, and Tailwind CSS 4. It replaces the custom Express.js runtime used by PWA Kit with native streaming server-side rendering and built-in Agentforce Commerce integration. Ksolves helps Salesforce Commerce Cloud teams evaluate whether a Storefront Next build or migration fits their roadmap.
What happens if I keep building on PWA Kit instead of migrating?
PWA Kit remains stable for existing storefronts, but Salesforce is actively preparing to phase out the first-generation headless framework, so new large-scale investment in it adds technical debt that will need to be re-platformed later. Teams that delay risk falling behind on Core Web Vitals gains and losing early access to Agentforce Commerce’s typed AI interfaces.
How do you migrate from PWA Kit to Storefront Next?
A migration typically starts with an architecture audit of existing PWA Kit components, data flows, and Page Designer mappings, followed by a phased rebuild using React Router 7 Loaders and Actions in place of client-side Commerce SDK hooks. Ksolves’ certified Salesforce Commerce Cloud team runs this as a structured assessment-to-deployment engagement to reduce migration risk.
Is Storefront Next the same thing as headless commerce on Salesforce?
Storefront Next is Salesforce’s second-generation (Gen 2) headless commerce implementation, while PWA Kit was the first-generation headless option built during the SPA era. Both are headless architectures for Salesforce Commerce Cloud, but Storefront Next uses modern tooling, Vite, Tailwind CSS 4, streaming SSR, instead of PWA Kit’s Webpack and Express.js-based stack.
When should a brand switch to Storefront Next?
Brands starting a new Salesforce Commerce Cloud build today should choose Storefront Next directly, since Salesforce is positioning it as the long-term standard and is phasing out PWA Kit. Brands with a stable, existing PWA Kit site can keep running it but should start budgeting a migration path rather than adding new large-scale features to the legacy architecture.
Who can help implement Storefront Next for an existing SFCC store?
Storefront Next implementation requires certified Salesforce Commerce Cloud developers familiar with React Router 7’s Loader and Action pattern, Agentforce Commerce’s typed AI interfaces, and Page Designer automation. Ksolves, a Salesforce Summit Partner, provides this expertise for both new Storefront Next builds and PWA Kit migrations.
How much effort does a Storefront Next migration typically take?
Effort depends on how customized the existing PWA Kit implementation is, sites with heavy custom client-side fetch logic or non-standard Page Designer mappings take longer to re-platform than a stock implementation. Ksolves scopes migrations with an architecture audit first, so brands get a realistic timeline and cost estimate before committing to a full rebuild.
Have a question we didn’t cover? Contact our team.
Author
About the Author Editorial Team The Ksolves Editorial Team includes certified Salesforce experts, Big Data engineers, AI/ML specialists, Zoho consultants, and experienced technology writers focused on delivering clear, actionable insights for modern businesses. With hands-on experience across Salesforce, Big Data platforms, AI/ML solutions, application development, software testing, and Zoho ERP/CRM, the team publishes practical guides, real-world use cases, and industry updates that support smarter decisions and faster growth. Every article is created to solve business challenges, guide technology adoption, and keep organizations aligned with evolving digital ecosystems.
Share with