Mobile Checkout 2026: How 7-Field Forms Lift DACH ConversionA typical German mobile checkout asks fo…
Salesforce Commerce Cloud headless, when is the switch worth it?
Salesforce Commerce Cloud is the enterprise platform for multi-brand corporations and international brands: deep Salesforce ecosystem integration with Service Cloud, Marketing Cloud, Data Cloud, and Einstein AI, B2C plus B2B editions, multi-site and multi-region native. All of this in the backend. But the frontend remains a separate question. SiteGenesis, SFRA, PWA Kit, custom build, or a Frontend Management Platform?
Anyone who started their SFCC frontend stack two or three years ago with SiteGenesis or SFRA often sees symptoms today that argue for a switch. Anyone who set up PWA Kit notices after six to twelve months of build that maintenance and Managed Runtime costs are just the beginning.
This guide helps you make the decision cleanly.
What does "SFCC headless" mean?
SFCC headless decouples the frontend, everything your buyers see, from the Salesforce Commerce Cloud backend with products, pricing books, promotions, Einstein AI, and B2B workflows. Instead of SiteGenesis or SFRA, the frontend connects through the Shopper API Platform (SCAPI). A complete overview of the options is on our hub page on Headless for Salesforce Commerce Cloud.
Five symptoms that argue for a switch
1. Multi-brand rollouts are engineering sprints per brand
You operate multiple brands on one SFCC realm. With SiteGenesis that means theme forks, with PWA Kit a separate build pipeline per brand. Marketing waits for engineering, new brand storefronts need 6 to 12 months.
With an FMP that ships multi-storefront setup as standard, new brands go live in 4 to 6 weeks.
2. Managed Runtime costs grow with revenue
PWA Kit Managed Runtime is revenue-based. As GMV grows, costs grow linearly, without engineering effort decreasing. In the CFO meeting the TCO question becomes strategic.
With an FMP SaaS license, you have predictable hosting costs independent of GMV.
3. PWA Kit maintenance binds three or four engineers per brand
For multi-brand setups, that means a double-digit engineering team just for the frontend. Each brand has its own build pipeline, every Salesforce update wave means frontend adjustments across all brands.
With an FMP, maintenance is bundled, one platform for all brands, updates run centrally.
4. Marketing can't iterate independently
Every new landing page, every microsite, every seasonal campaign per brand is an engineering ticket. Marketing iterations need sprints, A/B tests are realistically only monthly.
With a visual builder, marketing iterates independently, without an engineering sprint per page.
5. EU sovereignty becomes a strategy question
Salesforce Managed Runtime is not necessarily EU-sovereign. For DACH multi-brand corporations with GDPR requirements, this becomes relevant in the procurement process.
An FMP with EU hosting (Frankfurt) solves that as standard.
When a switch is (still) not worth it
Three constellations where we actively advise against switching:
You are deep in the Salesforce ecosystem (Service Cloud, Marketing Cloud, Data Cloud, Einstein AI). If your storefront strongly relies on Salesforce-native features, PWA Kit is the more native solution.
You are mid PWA Kit launch. Switching mid-build is double risk, finish the launch, then switch iteratively.
No architect on staff. An FMP migration without a technical owner rarely goes well.
Three rules of thumb for the decision
- More than three brands or markets on one SFCC realm? Clear signal toward an FMP.
- Managed Runtime costs discussed as a CFO risk? Clear signal toward an FMP.
- PWA Kit maintenance binds three or more engineers per brand? Clear signal toward an FMP.
If two of these three apply, the question is no longer "if" but "how".
What a frontend switch concretely changes
From the SFCC projects we have supported, three effects emerge:
Multi-brand time to launch drops from months to weeks per brand because multi-storefront setup is standard.
Total cost of ownership over 5 years typically lies 40 to 60 percent below PWA Kit plus Managed Runtime.
Marketing velocity rises significantly because page iterations are Studio configuration.
Pragmatic entry point
A complete migration in one step is rarely the right path. What works: start with a single storefront, for example for a new brand or a new market. The complete migration path is described in the post Salesforce Commerce Cloud headless migration, step by step.
Conclusion: frontend strategy is an architecture decision
Anyone with more than two hits on the symptom list should seriously consider the switch. Anyone with zero or one hit who is deep in the Salesforce ecosystem is often better served by PWA Kit.
If you are unsure, we are happy to walk through it with you. We show Laioutr live on your SFCC setup and tell you honestly whether a switch makes sense for you.