Salesforce Storefront Next: What a 30-Minute Storefront Actually Means for Frontend Ownership

Salesforce shipped its biggest Agentforce Commerce release yet with the B2C Commerce June '26 update, and the headline feature is the one worth sitting with: Storefront Next is now generally available, a production-ready storefront that Salesforce says you can stand up in under 30 minutes, included in every B2C Commerce SKU. Alongside it comes an Agentic B2C Developer Toolkit (CLI, MCP server, IDE extension, and Advanced Agent Skills) and confirmed GA dates for external agent channels: ChatGPT in July 2026, Google Search AI Mode and the Gemini app this summer. Here is the sober read on what the storefront part of that release means if you run on Salesforce Commerce Cloud.

What actually shipped

Three verified pieces matter for the frontend conversation. First, Storefront Next reaches general availability as a storefront you can provision in under 30 minutes, positioned by Salesforce as "enterprise power with out-of-the-box simplicity," and it now comes bundled into every B2C Commerce SKU rather than as a separate purchase or a build-it-yourself reference app. Second, the Agentic B2C Developer Toolkit unifies a CLI, an MCP server, an IDE extension, and Advanced Agent Skills into one workflow, which is Salesforce's answer to "how do developers and agents work on this storefront together." Third, Shopper Agent gets native gross-tax configuration directly in cart and checkout, folding a piece of commerce logic that used to require custom work into the core product.

The external-channel dates are the other half of the announcement, and they matter for context even though they are not this post's focus: ChatGPT commerce integration reaches general availability in July 2026, with Google Search's AI Mode and the Gemini app following this summer. We are naming those dates because they are verified and because they explain why Salesforce is racing to ship a storefront this fast, not because this post is making the multi-channel argument. That thesis, and how a storefront becomes transactable across agent surfaces you do not control, is a separate piece; here we are staying with what the Salesforce release itself means.

The convenience case is real

Give Salesforce credit for the honest part of this pitch. A 30-minute, production-ready storefront bundled into every SKU removes a real cost center: the months some B2C Commerce customers previously spent on a custom storefront build, or the reference-app-plus-customization path that ate developer time before a single product page shipped. For a merchant who wants a functioning, on-brand storefront fast and does not have deep frontend engineering capacity to spend, that is a legitimate improvement over what came before. The Agentic Developer Toolkit is a genuinely useful move too: an MCP server means AI clients and internal agents can operate against the storefront and its data without custom glue code, which is table stakes for any Commerce platform in 2026.

None of that is bashing-territory. It is a well-built release that does what it says.

The re-bundling question underneath it

Here is the part worth being clear-eyed about. A 30-minute, in-the-box storefront is also a storefront whose defaults, update cadence, and extension model live inside Salesforce's release train. When your storefront ships as part of the platform SKU, decisions about how it renders, which components exist, and how fast a new capability reaches production are Salesforce's decisions on Salesforce's schedule, not yours on yours. That is a fundamentally different arrangement than a frontend you own and can change the day you decide to, independent of any vendor's release calendar.

This is not a Storefront Next-specific flaw. It is the trade every platform-bundled storefront makes: convenience now, in exchange for the frontend and the backend moving as one unit going forward. If your commerce roadmap depends on Salesforce Commerce Cloud staying exactly as your backend while your storefront evolves on your own timeline (a new checkout flow, a market-specific layout, a component your competitors do not have) the bundled path re-couples something Composable Commerce spent years decoupling. Storefront Next make that trade easy to make without necessarily making it visible.

What this means if you already run Salesforce Commerce Cloud

If you are evaluating Storefront Next for a new storefront or a migration, the practical question is not whether it works. It clearly does, and the 30-minute claim is a real capability, not marketing filler. The question is whether you want your frontend's release cadence, extension surface, and component ownership tied to Salesforce's own roadmap, or decoupled from it while you keep Salesforce Commerce Cloud as the backend that holds your catalog, pricing, and orders.

That second path, Composable Headless Frontend, keeps Commerce Cloud exactly where it is today and lets the storefront layer, layout, components, checkout experience, and agent-operability, be a system you fully own and can change independent of any vendor's release train. Our headless frontend for Salesforce Commerce Cloud is built for exactly this: backend stays, frontend decouples.

This is also the second Salesforce move in a month worth reading through the same lens. Back in June, Salesforce's Contentful acquisition closed a content-layer gap by buying a vendor; here, Salesforce closes a storefront-layer gap by building one in-house and bundling it. Different mechanism, same pattern: more of the experience layer moving inside the platform boundary. Our read on Salesforce Headless 360 earlier this year flagged the direction; Storefront Next is that direction, now shipped and GA.

The verdict

Storefront Next is a genuinely convenient release, and Salesforce earns the "biggest Agentforce Commerce release yet" framing on substance, not hype. It also, correctly read, moves the frontend further into the platform's release cycle rather than out of it. Whether that trade works for you depends entirely on how much you value owning your storefront's roadmap independent of your backend vendor's roadmap. If frontend ownership matters to your team, "in every SKU" is worth reading as "in the platform's release train," not just as "free."

We build the Agentic Frontend Management Platform for teams that want that ownership on Salesforce Commerce Cloud without giving up agent-readiness in the process. See what that looks like, or browse the Insights blog for the rest of how we read the platform landscape, or start from the Laioutr homepage.

FAQ

What exactly is generally available in the Salesforce B2C Commerce June '26 release? Storefront Next (a production-ready storefront Salesforce says can be provisioned in under 30 minutes, now included in every B2C Commerce SKU), the Agentic B2C Developer Toolkit (CLI, MCP server, IDE extension, Advanced Agent Skills), and native Shopper Agent gross-tax configuration in cart and checkout.

When do the external agent channels go live? Salesforce confirmed ChatGPT commerce integration reaches GA in July 2026, with Google Search AI Mode and the Gemini app following this summer. Those dates are verified but are a separate topic from the Storefront Next verdict in this post.

Does Storefront Next mean I lose frontend ownership if I stay on Salesforce Commerce Cloud? Not automatically, but it does mean the in-box storefront's cadence and extension model follow Salesforce's release train. If you want the backend without that coupling, a decoupled frontend keeps Commerce Cloud as your backend while your storefront stays independently ownable. See our headless frontend for Salesforce Commerce Cloud for how that works.

Is this the same story as the ChatGPT and Google agent-channel news? No. Those GA dates are real and cited here for context, but the multi-channel, vendor-neutral transactability question is a separate thesis we cover elsewhere. This post is specifically about what Storefront Next means for Salesforce Commerce Cloud customers.

Next steps

If you run Salesforce Commerce Cloud and are weighing Storefront Next against a decoupled frontend, the useful next step is to separate the questions: does the backend stay, and does the frontend's roadmap stay yours. See how that works on our Agentic Frontend Management Platform page.

About the author: Marcel Thiesies is Co-Founder of Laioutr. He writes about the frontend management category, composable commerce, and where the experience layer is headed.