Storefront Next: The Upgrade That Changes the Cost of Running SFCC

Storefront Next isn't a frontend upgrade. It's how Salesforce gets cheaper to own.

If you're a director of ecommerce on SFCC and you've been treating the Storefront Next conversation as "another frontend refresh with a fuzzy ROI" that's the wrong filing cabinet. Put it back. This one goes under TCO.

The last piece I wrote on this argued that Storefront Next is the upgrade that finally aligns the SFCC frontend with the toolchain the rest of the software industry is using to extract real productivity from AI. That's the engineering manager's case. This is the ecommerce operator's case. They're the same case looked at from different chairs, and the operator's chair is the one with the budget.

Here's the version of the argument that ought to land in front of you, your CFO, and your CIO at the same time.

The "wait and see" math is wrong, and it's been wrong for about a year

Most SFCC clients I talk to in 2026 are doing some version of the same calculation: We know composable is coming. We know our SFRA stack (or worse, SiteGenesis stack) is accumulating tech debt. We’ve thought about Shopify but we’re starting to hear cautionary tales. The next major SFCC release feels close. Let's wait one more cycle. I get the instinct. I fundamentally disagree with it, and here's why.

The waiting calculus assumes a) the cost of upgrade is going up over time and b) the value of waiting is going up too. Both halves of that are now wrong.

The cost of upgrading is going down.

Two years ago, a composable storefront from a top-tier SI ran $1M+ before you started counting integrations. Salesforce's own internal pricing sizing put composable at a $500K minimum floor; they wouldn't even sell it under that number. 

We are now offering production-grade Storefront Next implementations at 64labs in six weeks, in the $150K–$300K range. Yes, six weeks to development done on about 75% of the project. Full flows. Checkout working. To an outsider the project looks finished. (Insiders know where the 25% lives). 

Your UAT is going to take longer than the project itself. How do we do this? By leveraging the headless SFCC experience we gained off the 12 PWA Kit builds that we've shipped to 10 previous customers. We will have built our first Storefront Next site before Salesforce officially launches Storefront Next. The six-week number comes from experience not bluster.

Look, experience still counts. Storefront Next is new but much of the SFCC composable infrastructure (API infrastructure in particular) is the same. The tooling is mature. The patterns are settled. The migration playbook is no longer being written for the first time on your project. That doesn't mean composable is cheap. But it’s way cheaper than having your current team or partner struggle up the learning curve we have scaled in the past four years. The failed composable builds of the past few years are generally down to overconfidence and under-skilling. Not technical gaps in the product.

The value of waiting is going down too.

Every Salesforce roadmap announcement since November 2025: Agentforce Commerce launch, the Cimulate acquisition in February, the ChatGPT/ACP checkout integration, the PWA Kit MCP Server, has assumed a composable foundation. If you're not on it, you're watching the platform you've paid for accelerate without you. That's not "we're behind on a new front-end." That's "we're paying full Salesforce price for a sub-set of what Salesforce can now do."

You wait six more months and you'll wait twelve. Wait twelve and the next release is "right around the corner," so why not wait again. The perfect moment to upgrade does not arrive. At some point you just jump in. The argument I'm making is that the time will never be perfect, so now truly is as good as any other time and better than 12 months from now.

What "lower TCO" actually means here

I know "lower TCO" is the kind of phrase consultants use when they don't have anything specific to say. So let me be specific. Here are the lines on your operating budget that change when you move to Storefront Next.

Implementation cost: goes down.

Already covered above. The number for a fresh Storefront Next build today is meaningfully lower than it was two years ago, dramatically lower than what large SI partners still quote and about what an SFRA upgrade would cost you. And if you use 64labs it’s all over in a single quarter.

Front-end hiring cost: goes down, stays down.

This is the one almost nobody sizes properly. The labor market for SFRA-fluent (and especially SiteGenesis-fluent) front-end developers is shrinking every quarter. The rate you pay for an ISML specialist in 2026 is not the rate you'll pay in 2028, and it isn't going down. Storefront Next runs on React, Vite, Tailwind, and shadcn, a stack you can hire against from any modern front-end pool, anywhere in the world, at market rates. You stop paying a scarcity premium for a skill set that's actively retreating.

Deployment cost: goes down, stays down.

Storefront Next deployments measure in the tens of seconds, not the minutes-to-hours of a full SFRA push. That changes the unit economics of every merchandising-driven release. Teams that deploy eight times a year start deploying weekly. Teams that already deploy weekly start deploying daily without a war room.

3P cost: goes down, stays down.

A lot of SFRA clients I see have at least considered a paid Algolia or Coveo or Constructor.io contract layered on top of Salesforce because Einstein didn't deliver where they needed it. It makes sense to invest in Search. The post-Cimulate Agentforce Commerce roadmap is built specifically to absorb that layer. To get the absorption, you need the foundation. The foundation is Storefront Next. Translation: every quarter you're not on it is a quarter of paying twice for search and discovery.

Engineering velocity: goes up.

‍This is where the prior article's AI-leverage argument lives. I won't relitigate it here other than to note that the productivity multiplier compounds against every line in the engineering payroll, every quarter, forever.

Add those up and you have the answer to "what's the ROI." It isn't a nice-to-have frontend ROI. It's a structural cost-of-ownership ROI that runs across every year of your contract.

SiteGenesis customers: this paragraph is for you specifically

If you're still on SiteGenesis in 2026, the calculation is different in degree, not in kind. Your tech debt is materially heavier. Your hiring market is materially worse. Your gap to current Salesforce features is materially wider. And the cost of carrying SiteGen another two years while you "evaluate options" is the highest version of the same trap above.

The good news: the migration target is the same as everyone else's. You don't need an SFRA layover. Don't let your agency talk you into that one. The right move is to skip SFRA entirely and go straight to Storefront Next. We've done this for SiteGen clients and the timeline is roughly comparable to a SiteGen-to-SFRA project (about 12 weeks), with the dramatically more important difference that you finish on the platform Salesforce is actually investing in.

If you take one thing from this piece, take this: SiteGen-to-SFRA in 2026 is the most expensive indefensible decision you can make this year. You pay full migration cost to land on a platform that's already a generation behind the one you'll need to migrate to next. Stop with the weird math. Stop listening to partners who don’t know how to build composable sites. Migrate once. Move on.

Cimulate and the foundational nature of this upgrade

Salesforce's acquisition of Cimulate in February changes things. The technology, an intent-aware context engine combining real and simulated shopper journey data for product discovery, is being folded directly into Agentforce Commerce. This is not a minor product release. This is Salesforce closing a long-standing gap between native Commerce Cloud capability and the third-party search/discovery layer many forward-thinking retailers have been bolting on.

For SFCC clients on a composable foundation, Cimulate becomes a native capability. For SFCC clients on SFRA or SiteGen, it becomes a thing you read about. That gap is the gamechanger. The unlock for the entire AI commerce stack: Cimulate, Guided Shopping, ChatGPT catalog syndication, the Merchant Agent, agentic checkout, is composable. The front-end isn't where the value lives. But the frontend is the load-bearing wall the value is built on.

That's what "foundational" means in this context. It's not "nice to have for a fresh look." It's "the prerequisite for accessing the next decade of the Salesforce roadmap."

What to do this quarter

If you're on SFCC and not yet committed to a Storefront Next path, my advice is straightforward.

Don't size a multi-million-dollar SI project. The market has moved past that. Get a prototype, same product catalog, same checkout flow, against your real Salesforce instance, about three weeks and about 70% of the site and use that as the foundation for your business case. The cost of finding out is now small enough, somewhere in the $150k to $300k range, that it shouldn't take a board meeting to greenlight.

Don't wait for the next major Salesforce release before evaluating. Every "next" release between now and 2028 is going to assume you're on the new foundation. The decision is not which Storefront Next release to jump in on. The decision is whether your team is still trying to extract value out of SFRA or SiteGen when your competitors are running Cimulate-powered discovery and conversational checkout.

Don't optimize for zero risk. Optimize for catch-up speed. The risk of a six-week proof build is bounded and quantifiable. The risk of a four-year drift on a platform you're paying full freight for is not.

The window for adopting this technology is now thinner than it has been at any point in this generation of SFCC. That's not because the tech is hard to get. It's because the strategic gap between clients who jump and clients who hesitate is now opening at the speed of a Salesforce roadmap built on assumptions you don't yet meet.

You don't need a perfect moment. You need a six-week leap into the future.