Short product page for Storefront Next. It describes a storefront built with React 19 and Tailwind CSS and hosted on Managed Runtime, with Business Manager setup and AI-assisted development called out as headline points.
Salesforce Developers
Search the curated set. Filters stay in the URL, so a shared link opens the same slice.
47 of 47 resources
Short product page for Storefront Next. It describes a storefront built with React 19 and Tailwind CSS and hosted on Managed Runtime, with Business Manager setup and AI-assisted development called out as headline points.
Salesforce Developers
The guide's front door. It describes server rendering with React Router 7 framework mode, Tailwind, and shadcn/ui, then points at setup, shopping flows, Managed Runtime, hybrid SFRA or SiteGenesis, go-live, and migration material.
Salesforce Developers
Explains the request path from the shopper through Managed Runtime to SCAPI, Business Manager, and the Salesforce platform. The stack table lists React 19, React Router 7 framework mode, Vite, TypeScript, Tailwind CSS, and shadcn/ui. Initial HTML is server-rendered; later navigations stay on the client.
Salesforce Developers
A short fork in the docs. Business Manager can create the storefront in a GitHub repository, or create the resources and leave code generation to your machine. A third path generates code against the demo instance from the terminal.
Salesforce Developers
Generates a project with pnpm dlx @salesforce/storefront-next-dev create-storefront and tells you to accept the demo defaults for the SLAS client, organization, short code, and site. The guide says this procedure is for exploring the code, not for creating your own storefront. The dev server example is http://localhost:5173.
Salesforce Developers
Business Manager creates the storefront plus API and Managed Runtime resources, and you generate the code locally with the CLI. The guide limits setup to one storefront per site and says a failed setup has to be deleted and recreated. Download env.txt from the completion page; the client secrets are not offered again.
Salesforce Developers
Business Manager connects to GitHub, creates a repository for the generated storefront, and sets up the API and Managed Runtime resources. You pick an organization or a personal account, grant the integration access, and download env.txt once for the local credentials.
Salesforce Developers
Compares the built-in templates you pick in Business Manager or the CLI: Foundations with no industry theme, Retail Next as the base retail layout, Beauty Next for shade and ingredient attributes, Footwear Next for fit and size systems, and Furniture Next for dimensions, materials, and delivery options.
Salesforce Developers
Monthly product notes for Storefront Next. The 1.4.0 section covers SCAPI authorization for selected CLI commands, saved payment methods, shared SCAPI response caching, descriptive product and category URLs, and a renamed Shopper Agent environment variable. Earlier sections cover delivery dates, passkeys, site management, and the later templates.
Salesforce Developers
The engineering changelog for the retail template mirror. Release titles put the SDK version and the template stamp side by side, which is why 1.4.0 and 2026.10.0 refer to the same October 2026 drop rather than two competing products.
Salesforce Commerce Cloud
A small table that keeps the template date stamp separate from the SDK SemVer used by @salesforce/storefront-next-dev and @salesforce/storefront-next-runtime. It tells you the minimum SDK a template release was built and tested against.
Salesforce Commerce Cloud
Reference for the sfnext CLI shipped in @salesforce/storefront-next-dev. Documented commands include create-storefront, dev, preview, push, create-bundle, and extensions. The page says not to install the package globally.
Salesforce Developers
Describes config.server.ts as the type-checked place for project settings, with environment overrides and a split between public and server-only values. getConfig() is the API for loaders, actions, and utilities. The page groups commerce, hybrid, auth, sites, images, and related options.
Salesforce Developers
How merchants' Page Designer pages render in Storefront Next. Pages, regions, and components come from the Shopper Experience API, and headless metadata tells Page Designer to load the Managed Runtime storefront. The guide notes that preview does not update until you save, and that hybrid storefronts cannot link across SFRA and Storefront Next in the link builder.
Salesforce Developers
Hybrid Auth keeps the SFRA or SiteGenesis dwsid and the SLAS JWT in sync so some routes can stay on the older storefront. You set hybrid.enabled and list legacyRoutes such as cart and checkout. eCDN sends the routes you choose to Managed Runtime or back to the B2C instance.
Salesforce Developers
Maps PWA Kit habits onto Storefront Next: client-heavy hooks and Webpack give way to React Router 7, Vite, and TypeScript. API calls move into route loaders and actions. Routing moves from React Router 5 route arrays to file-based routes.
Salesforce Developers
Lists official places Salesforce employees can speak for the product, and the independently run B2C Commerce Slack. It separates those from Salesforce Support for urgent issues.
Salesforce Developers
Template
Public fashion and retail starting point, CLI identifier fashion. The README describes a React Router 7 and React 19 storefront and tells you to copy .env.default, then run pnpm install and pnpm dev. The package name on branch latest is template-retail-rsc-app. Official architecture docs describe React Router 7 server rendering. This repository is not a Next.js application.
Salesforce Commerce Cloud
Template
Public beauty and cosmetic vertical, CLI identifier cosmetic, package name storefront-cosmetic. It is a separate mirror from the retail template, with its own demo data. The template-features guide describes shade, ingredient, and how-to-use attributes for Beauty Next.
Salesforce Commerce Cloud
Template
Public footwear vertical, CLI identifier footwear, package name storefront-footwear. Release notes for B2C Commerce 26.10 introduce Footwear Next for fit, size guides, and activity browsing. The template-features page lists the size, width, cushioning, and terrain attributes.
Salesforce Commerce Cloud
Template
Public furniture vertical, CLI identifier furniture, package name storefront-furniture. Release notes for B2C Commerce 26.10 introduce Furniture Next for dimensions, materials, and delivery options. The features guide lists width, depth, height, and assembly attributes.
Salesforce Commerce Cloud
Template
Public unthemed vertical, CLI identifier foundations, package name storefront-foundations. The features guide says Foundations keeps the commerce toolkit without an industry theme and omits several retail-only category fields. Its README is also the table of the other public vertical repositories.
Salesforce Commerce Cloud
Template
Public repository listed by the foundations template as the luxury vertical, CLI identifier luxury, package name storefront-luxury. The same October 2026 stamp and SDK 1.4.0 pin were in package.json on branch latest. The Business Manager feature comparison does not document a luxury layout.
Salesforce Commerce Cloud
Instruction files a coding agent can load while you work in a Storefront Next project. The README groups them from sfnext-overview and project setup through routing, SCAPI, Page Designer, deployment, and tests. The skills directory contained 24 sfnext-* folders on 8 Nov 2026. Two sibling plugins target Figma and need a Figma connection this directory does not set up.
Salesforce Commerce Cloud
A symptom-by-symptom article for Page Designer on Storefront Next: a missing Storefronts menu, a missing local-preview module, Shopper Experience API 403s and 404s, manifest sync, and a crash the author ties to cloning branch latest during one week in September 2026.
Rhino Inquisitor
Five-day class, role Developer, titled Develop a B2C Storefront with Storefront Next. The outline covers local setup, Business Manager and Managed Runtime, multi-site work, Page Designer, Commerce APIs, caching, and a hybrid look at SFRA. The Level field on the page did not show a value in the text retrieved.
Trailhead Academy · Paid
Tutorial
A beginner course page that says 2 sections and 9 lessons, duration 1 hour, language English. The listed lessons cover benefits, architecture, the technology stack, browser compatibility, and creating a project with Business Manager, the CLI, and demo credentials.
SFCC Learning · Access unknown
SFCC Learning's product page for a free PDF study guide covering architecture, setup, configuration, routing, data fetching, caching, and deployment, with a stated length of 573 pages. Only the product page was read.
SFCC Learning
A partner hub that gathers enablement videos, a technical learning journey, sandbox prework, and workshop activities for B2C Storefront Next. Dates printed on the hub run from July 2026 through September 2026 for individual assets. Collaboration links include the Partner Community and a Partnerblazer Slack channel.
Salesforce · Access unknown
64labs' case study of a See's Candies move from PWA Kit onto Storefront Next. It covers three sites, a phased rollout, multi-site redirect pitfalls, and rebuilding Dynamic Yield, Bazaarvoice, Amplience, Cybersource, Experian, and OneTrust. Those details are the publisher's. This directory did not re-run the build, and the page does not document an SDK version.
64labs
64labs argues a Storefront Next migration should build to parity before a redesign. The article also comments on scoping an AI-assisted migration and on Salesforce's partner timeline and cost claims. Those claims are the publisher's.
64labs
A 64labs explainer of Storefront Next compared with SFRA, PWA Kit, and Composable Storefront, written for decision-makers. Comparisons in the article are the publisher's.
64labs
64labs makes a total-cost-of-ownership argument for upgrading an SFCC storefront to Storefront Next. Cost figures in the article are the publisher's and are not checked here.
64labs
64labs' note on the general-availability launch: what the author says it means for SFCC and Shopify Plus buyers, and the role given to AI enablement. Buyer comparisons are the publisher's.
64labs
64labs argues that the React stack lowers the total cost of owning SFCC and makes more of the work automatable. The cost argument is the publisher's.
64labs
64labs' recap of Connections 2026 as it touches Storefront Next, the Commerce Apps extension model, and Page Designer coupling. Event claims are the publisher's.
64labs
64labs describes Storefront Next together with Salesforce's Cimulate acquisition as an AI-first commerce architecture. The architecture claim is the publisher's.
64labs
64labs describes running the live See's Candies Storefront Next site with AI agents for triage, pull-request generation, and regression planning. The operating model is the publisher's account.
64labs
64labs extends lessons from agent-driven operations on See's Candies beyond the commerce storefront. The lessons are the publisher's.
64labs
64labs' accelerator for Storefront Next and Next.js: prebuilt UX patterns, state management, CMS, search, and payment connectors, and infrastructure templates. 64labs says it shortens a typical 9-month launch to 4-5 months. That timeline is the publisher's.
64labs · Access unknown
64labs' service page for Storefront Next work, including an FAQ. The FAQ includes the partner's view that hybrid launches are not worth it, and the page offers a composable readiness assessment that 64labs calls free.
64labs · Access unknown
Studio Science's launch post for Black Magic on Storefront Next: a net-new site in 30 days with two developers, described as AI-assisted, with CI/CD on Managed Runtime. The schedule and team size are the publisher's.
Studio Science
Studio Science post of a reference demo: Storefront Next with Contentful, a Cimulate shopper agent, and a Claude merchant agent in Slack. It is a demo, not a merchant launch.
Studio Science
A build log of Après Studio, an AI-written Storefront Next storefront on a sandbox, covering OCAPI, SCAPI, WebDAV, and Managed Runtime, including failures and interventions. No public storefront URL is given.
Studio Science (Aaron Hutten, personal site)
A field note on building a Claude shopping concierge that uses Storefront Next and SCAPI for catalog, cart, and checkout. The concierge is the author's experiment.
Studio Science (Aaron Hutten)
A field note on a Stripe Payment Element checkout inside Storefront Next, used with an AI concierge. The author describes a sandbox with test payments.
Studio Science (Aaron Hutten)
A field note on a merchant agent that applies B2C Commerce promotions from Slack, with approval and a verification step. The workflow is the author's.
Studio Science (Aaron Hutten)