What we do
Tools
Industries
Department
How we workLet's talk →
Home/Salesforce Commerce Cloud/Salesforce Headless Commerce
Salesforce Commerce Cloud

Salesforce Headless Commerce: What Changes When the Storefront Leaves SFRA

Headless on B2C Commerce means your shoppers see a React app instead of SFRA's templates, and that app reaches the commerce engine only through the API. The catalog, prices, promotions and orders stay where they are. What has to move is everything your old storefront code did on the way to checkout, and that's the part most project plans undercount.

The pieces, named plainly

Composable Storefront is Salesforce's headless stack: the PWA Kit React storefront, hosted on Managed Runtime.

Storefront Next is the newer starting point, with a migration guide from PWA Kit. It keeps the same backend (SCAPI, SLAS and Managed Runtime) and swaps the build tooling, Vite in place of Webpack.

SCAPI is the API both of them call. Auth, API families and the OCAPI move are on our SCAPI page.

What survives going headless, and what doesn't

What you run on SFRA today After the move What to do about it
Order export, inventory and catalog jobs in Business Manager Keep running. Orders are still placed in the same B2C Commerce instance. Check the custom attributes on orders. If your SFRA checkout set them, the new checkout has to set them too, or the ERP mapping breaks quietly.
Checkout logic in SFRA controllers and hooks: address checks, loyalty, fraud calls Stops running. The headless app talks to SCAPI, not to your controllers. Move the server-side rules into SCAPI hooks or a custom API, and keep anything shopper-facing in the new front end.
Partner cartridges for payments, tax and reviews The back-office half usually carries on. The storefront half written for SFRA does not. Ask each vendor whether they ship a PWA Kit or SCAPI version, and budget for building the front end piece where they don't.
Tags, pixels and consent scripts added in ISML templates Gone with the templates. List every script before you start and re-add each one in the React app or your tag manager, or analytics drops the day you launch.
Content built in Page Designer Needs matching React components on the new storefront. Count the page types and components early. Content teams notice this gap before anyone else does.

One cutover weekend, or a hybrid rollout

Full cutover

Every page moves at once

  • One storefront to run and test after launch.
  • Checkout, payments and every partner integration must be ready on day one.
  • A late problem in checkout holds up the whole launch.
Hybrid

Page types move in phases

  • Salesforce's eCDN sends some routes to Managed Runtime and the rest to SFRA. Its own example moves home, category, product and search first, and leaves cart and checkout on SFRA.
  • Hybrid Auth keeps the SFRA session and the SLAS login in step, so the basket follows the shopper.
  • Salesforce warns that every extra month in hybrid adds operating work, so set an end date.

Hybrid suits a store whose checkout carries a lot of custom logic. Browse pages go first, and checkout moves once its rules have been rebuilt and tested.

Where headless Commerce Cloud projects stall

The basket empties between the two storefronts

How you'll know: A shopper adds items on a PWA product page, clicks through to SFRA checkout, and arrives at an empty cart or logged out.

Fix: Set up Hybrid Auth (or Plugin SLAS on older setups) and test the handoff in both directions. PWA Kit 3.14 and later has a hybrid proxy, so developers can reproduce it locally without the eCDN.

Nobody listed what the old controllers did

How you'll know: Two weeks before launch, someone finds that SFRA checkout also checked stock at the warehouse or applied a loyalty discount.

Fix: Read through every custom controller and hook in the storefront cartridge at the start, and write down each outside call it makes. That list is the integration backlog.

Tests only cover the old storefront

How you'll know: Integration tests pass, and orders from the new checkout still reach the ERP with missing fields.

Fix: Run the same order scenarios through both storefronts and compare the order records field by field before checkout moves.

Let's talk

The storefront rebuild is planned. Is the checkout logic?

n-frames takes the part of a headless Commerce Cloud move that sits behind the React app: listing what your SFRA cartridges do, rebuilding checkout rules as SCAPI hooks or custom APIs, setting up hybrid routing and session handoff, and checking that ERP and order feeds still get every field. We work next to your storefront agency or in-house team.

Rebuild our checkout rules →

Questions people ask

What is PWA Kit?

Salesforce's React storefront toolkit for headless B2C Commerce. It comes with a starter storefront, the Commerce SDK for React for calling SCAPI, and tooling to deploy to Managed Runtime. Together, PWA Kit and Managed Runtime are what Salesforce calls Composable Storefront.

Is headless Commerce Cloud the same as composable commerce?

Not quite. Headless means the storefront is separate from the commerce engine and talks to it through the API. Composable goes a step further and swaps other parts too, such as search or the CMS, with Commerce Cloud still handling catalog, pricing and orders.

Does going headless with Commerce Cloud replace SCAPI?

No. A headless storefront depends on SCAPI completely, because the API becomes the only way the front end reaches baskets, products and orders. Our SCAPI page covers how its auth works.

Do I need Managed Runtime to go headless on Commerce Cloud?

For PWA Kit and Storefront Next, Managed Runtime is the hosting Salesforce builds them for, and it's what the hybrid eCDN routing expects. A front end you write yourself against SCAPI can run elsewhere, but then hosting, CDN and support are yours to manage.

Is PWA Kit being replaced by Storefront Next?

Salesforce now offers Storefront Next as the newer path and publishes a migration guide from PWA Kit. Both sit on the same backend, so starting on PWA Kit doesn't lock you out. Check Salesforce's current guidance before starting a new build.

Can we go headless one page type at a time?

Yes, that's the hybrid rollout above: the eCDN sends chosen routes to the new storefront and the rest to SFRA. Most teams move browse pages first and checkout last.

Who rebuilds the integrations when the storefront goes headless?

The storefront agency usually builds the React app. The rules hiding in SFRA controllers, partner front-end pieces with no headless version, and the order feeds downstream often fall between teams. That's the work n-frames picks up.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.