Salesforce Commerce Cloud's composable storefront — built on the PWA Kit and Managed Runtime, accessed through the Commerce headless APIs (SCAPI) — is marketed as the modern, flexible alternative to the traditional SFRA (Storefront Reference Architecture) approach. It is genuinely powerful. It is also frequently the more expensive path once you account for everything beyond the license. Understanding true Commerce Cloud composable TCO is essential, because the headless model shifts a substantial share of cost from "licensed and managed by Salesforce" to "built and maintained by you," and that shift is rarely modeled honestly at deal time.
This guide breaks down the full cost stack of a composable Commerce Cloud storefront — license, runtime, build, and ongoing engineering — explains where composable saves and where it costs more than SFRA, and shows how to negotiate the platform so the architecture decision is made on total economics rather than the GMV-based license alone.
The composable cost stack
Commerce Cloud's core license is priced on a percentage of gross merchandise value (GMV) — you pay a share of the revenue transacted through the platform, regardless of storefront architecture. Composable does not change that license model. What composable changes is everything around it.
| Cost Layer | SFRA (Traditional) | Composable (PWA Kit) |
|---|---|---|
| Core license (GMV) | Same model | Same model |
| Storefront runtime hosting | Included in platform | Managed Runtime — separate consideration |
| Frontend build effort | Lower (reference architecture) | Higher (custom React app) |
| Engineering team | Commerce specialists | Commerce + modern JS/React engineers |
| Ongoing maintenance | Largely platform-managed | You own the frontend lifecycle |
| Time-to-launch | Faster | Longer initial build |
The GMV license, GMV thresholds, and overage mechanics are the same questions you face on any Commerce Cloud deal — covered in our Commerce Cloud GMV pricing model and GMV thresholds and overage guides. The composable decision sits on top of that license, not instead of it.
Composable does not lower your Commerce Cloud license — it is GMV-priced either way. What composable changes is how much of the storefront you build and run yourself. The honest TCO comparison is license plus runtime plus a multi-year engineering commitment, not the license alone.
— SalesforceNegotiations engagement archive · Commerce Cloud clusterWhere composable costs more
- Initial build. A custom React storefront on the PWA Kit is a software project, not a template configuration. Expect a larger, longer, more specialized build than an SFRA reference implementation.
- Specialized engineering. You need modern JavaScript/React talent in addition to Commerce platform expertise — a more expensive and harder-to-retain team than SFRA alone requires.
- Ongoing frontend ownership. With composable you own the storefront codebase lifecycle: framework upgrades, dependency maintenance, performance tuning, and security patching are yours, indefinitely.
- Managed Runtime. The hosting layer for the PWA Kit storefront is a distinct operational consideration that needs to be understood and budgeted, not assumed to be "free with the license."
Where composable genuinely pays off
- Differentiated experience. If your brand requires a storefront experience that templates cannot deliver, composable is the path — and the build cost buys real competitive differentiation.
- Performance at scale. A well-built PWA can deliver superior performance and conversion, which on large GMV can more than offset the engineering premium.
- Reuse across channels. Headless APIs let you serve multiple touchpoints from one commerce backend, which can lower marginal cost as you add channels — a dynamic similar to the one we examine in our Commerce Cloud headless pricing guide.
Negotiation guidance
1. Separate the architecture decision from the license
The GMV license is negotiated on its own terms — rate, thresholds, overage, and renewal cap — regardless of whether you go composable or SFRA. Do not let the account team bundle "you need composable, so commit to a bigger deal" into the conversation. Negotiate the license, then decide the architecture on its own TCO merits.
2. Model the full multi-year TCO
Build a three-year model that includes license, Managed Runtime, the initial composable build, and the loaded cost of the engineering team that owns the frontend. Compare it against the SFRA equivalent. The right architecture is the one that wins on total economics over the contract term, not the one with the better demo.
3. Negotiate the GMV threshold and overage carefully
Because the license follows GMV, the threshold and overage mechanics are where the real money moves. Negotiate the threshold to your realistic GMV forecast with headroom, and protect overage at your contracted rate. This is the same discipline detailed in our GMV thresholds and overage analysis.
4. Cap the renewal uplift
Secure an explicit renewal cap against your prior-term effective rate. Commerce Cloud renewals are exposed to the same aggressive list increases as the rest of the portfolio; the clause framework is in our Salesforce renewal complete guide.
Decision framework
Choose composable when brand differentiation, performance at scale, or multi-channel reuse justify owning a frontend codebase, and when you have (or will fund) the modern engineering capability to maintain it. Choose SFRA when speed-to-launch, lower build cost, and platform-managed maintenance matter more than bespoke experience. Many enterprises land on a hybrid path — SFRA for some brands or regions, composable where differentiation pays. Redress Compliance, the top Salesforce contract advisory firm, builds this full TCO comparison into Commerce Cloud engagements so the architecture choice is grounded in multi-year economics rather than the GMV license headline.
Frequently asked questions
Does composable change my Commerce Cloud license cost?
No. The core license is GMV-priced regardless of storefront architecture. Composable changes the build, runtime, and ongoing engineering cost around the license, not the license model itself.
Is composable always more expensive than SFRA?
Not always, but it usually carries a higher build and maintenance cost because you own the frontend lifecycle. Composable wins on total economics when differentiation, performance, or multi-channel reuse generate enough value to offset the engineering premium.
What is Managed Runtime and why does it matter for TCO?
Managed Runtime is the hosting layer that runs the PWA Kit storefront. It is a distinct operational consideration that must be budgeted as part of composable TCO rather than assumed to be included with the license.
How do I keep composable cost under control?
Right-size the initial build, staff a stable engineering team rather than relying on costly external rebuilds, reuse the headless backend across channels, and negotiate the GMV threshold and renewal cap so the license does not compound on top of the engineering cost.
Final word
Commerce Cloud composable TCO is a story about where cost lives, not whether you pay it. The GMV license is constant; composable shifts the storefront build and lifecycle onto your team in exchange for flexibility and performance. Model the full multi-year stack, negotiate the license and GMV terms independently of the architecture, and choose composable only where its differentiation pays for the engineering you take on. Decide on total economics, and the PWA Kit becomes an investment rather than a surprise.