MEDIUM
See’s Candies Just Went Live on Storefront Next. Here’s What Nobody’s Telling You About the Build.
See’s Candies is running on Storefront Next now. Three production storefronts: Retail, Fundraising, and Volume Sales. First production deployment of Salesforce’s new composable framework, full stop.
We started this build before Salesforce had finished the codebase. Most SIs were still waiting on GA. We were already in it, working alongside the platform team, shipping real code against a framework that was still being written.
1,800+ pull requests later, here’s what the docs don’t tell you.
Multi-site breaks things a single-site build never surfaces. Same relative path, different target URLs across sites: redirects that worked fine on one MRT fall apart the second you’re running multiple. Nobody warns you about this until you hit it in production.
Get 64labs’s stories in your inbox
Join Medium for free to get updates from this writer.
The backend isn’t the hard part. SFCC and the API layer carry over mostly intact. The frontend is a different animal: server-side rendering, React Server Components, a routing model that doesn’t map cleanly to what you knew from PWA Kit. If your team has composable reps under its belt, that’s a real curve but a climbable one. If it doesn’t, this is exactly where projects stall.
Third-party integrations ate more of the timeline than the framework did. DynamicYield, Bazaarvoice, Amplience, Cybersource, Experian, OneTrust. Every one rebuilt from scratch for the new architecture. Nobody puts this on a conference slide because it’s not sexy. It’s also most of the work.
We shipped the low-risk sites first on purpose. Fundraising and Volume Sales are simpler, lower-traffic B2B properties. We proved stability there before putting Retail, the site that actually matters for revenue, through a live cutover.
The framework didn’t create the speed. The workflow did. Ask our product owner where the velocity came from and he won’t point at Storefront Next. He points at the AI harness and delivery workflows we spent six months building before this project started. The platform gave us better foundations. The operating model is what compressed the timeline.
Storefront Next holds up under real enterprise complexity, real integrations, and real revenue on the line. We know because we’re the ones who put it there first.
Full breakdown, including the parts that only come from being first: 64labs.com/articles/the-sees-candies-storefront-next-build-from-pwa-kit-to-production
