SFRA development
Storefront features on the Storefront Reference Architecture, built as cartridges that survive upgrades.
Learn more about SFRA developmentSysStacks builds, migrates and supports Salesforce Commerce Cloud (SFCC) storefronts — SFRA, PWA Kit and Storefront Next — and connects them to the rest of your Salesforce org.
One team for the cartridges, the checkout, the integrations and the peak-season on-call, so the storefront and the org behind it are engineered together.
Implementation, development and support across B2C and B2B Commerce. Each service below has its own page with scope and process.
Storefront features on the Storefront Reference Architecture, built as cartridges that survive upgrades.
Learn more about SFRA developmentA planned rebuild of a legacy SiteGenesis storefront on SFRA, with redirects and SEO carried across.
Learn more about SiteGenesis to SFRA migrationHeadless storefronts on Composable Storefront (PWA Kit) and Storefront Next, including phased rollouts from SFRA.
Learn more about PWA Kit & Storefront NextAccount-based buying: buyer groups, contract pricing, reorders and self-service for business customers.
Learn more about B2B CommerceSalesforce Order Management for fulfillment, splits, returns and order status across channels.
Learn more about Order ManagementPayments, reviews, OMS and back-office integrations as maintainable cartridges and APIs — Stripe and Yotpo among them.
Learn more about Cartridges & integrationsRelease management, performance work, load testing and agreed coverage through the peak trading window.
Learn more about Managed support & peak readinessCommerce Cloud developers embedded in your team, working in your repository and your sprint cadence.
Learn more about Hire SFCC developersSite configuration, catalogs, promotions, and Page Designer components your merchandisers can use without a developer.
Storefront Next is Salesforce's recommended storefront for new builds since it became generally available on June 24, 2026. SFRA and PWA Kit remain supported, and the right choice depends on what you already run.
| SFRA | PWA Kit (Composable Storefront) | Storefront Next | |
|---|---|---|---|
| Architecture | Server-rendered storefront on B2C Commerce, extended with cartridges | Headless React app on Managed Runtime, calling SCAPI | Server-first React app (React 19, React Router 7) on Managed Runtime, calling SCAPI |
| Status | Mature and widely deployed | Supported; Salesforce publishes a migration guide to Storefront Next | Generally available since June 24, 2026; Salesforce's recommended option |
| Cost to build | Lowest — starts from the reference application and existing cartridges | Higher — a separate front-end codebase and skill set | Higher than SFRA — a new front-end stack; server-side SFRA templates do not carry over |
| Speed | Depends on templates, caching and third-party scripts | Fast navigation after first load; first load needs server-side rendering tuned | Built for fast first load through server-first rendering |
| Flexibility | Bound to SFRA templates and the cartridge overlay model | Full control of the front end | Full control of the front end on a Salesforce-maintained foundation |
| Migration path | From SiteGenesis: a rebuild. Onward: a phased hybrid rollout to headless | Onward to Storefront Next using Salesforce's migration guide | Runs alongside SFRA during a phased hybrid rollout |
| Best fit | Existing SFRA sites with cartridge-heavy integrations | Existing PWA Kit storefronts | New builds and replatforms from 2026 |
Before you commit to a new storefront, we audit the one you have and tell you what moving would actually take.
Every custom cartridge, template and third-party script, sorted into what moves, what is rebuilt and what is retired.
Which features already sit on SCAPI, which still depend on OCAPI or server-side controllers, and the work to close the gap.
Which pages move first behind eCDN routing, how sessions stay in sync, and how SEO is protected while both storefronts run.
A scoped plan and estimate you can take to any partner — including us, or nobody, if staying on SFRA is the better call.
Three routes we plan and run, each with redirects, data and SEO treated as part of the build rather than a launch-week task.
SiteGenesis code cannot be converted to SFRA directly, so this is a rebuild — scoped from an inventory of your cartridges and customizations. SiteGenesis is still supported for critical fixes, which buys time to plan it properly.
Learn more about SiteGenesis to SFRAA phased hybrid rollout: high-value pages move to PWA Kit or Storefront Next first, routed at the eCDN, while SFRA keeps serving the rest until the cutover is complete.
Learn more about SFRA to headlessCatalog, customer and order history mapped to B2C Commerce, URL structures redirected, and integrations rebuilt as cartridges or APIs.
Listed only where we have delivered them on a live Commerce Cloud storefront.
Payments on an SFRA storefront, delivered for Silver Jeans.
See it about StripeProduct reviews on an SFRA storefront, delivered for Silver Jeans.
See it about YotpoOrder capture, fulfillment and returns connected to the storefront.
Learn more about Salesforce Order ManagementBack-office systems connected to Commerce Cloud and the CRM through one integration layer.
Learn more about MuleSoftA storefront is one channel. These are the connections that let service, marketing and data teams see the same customer.
Agents see orders, returns and storefront history in the console, instead of switching to Business Manager.
Learn more about Service CloudJourneys triggered by commerce events — browse, cart and purchase — rather than by a nightly export.
Learn more about Marketing CloudStorefront, CRM and loyalty data unified into one profile, for segmentation and for Agentforce.
Learn more about Data 360ERP, OMS and product data connected once, through APIs every cloud can reuse.
Learn more about MuleSoftB2B accounts, quotes and reorders shared between sales reps and the buyer portal.
Learn more about Sales CloudShopper, Buyer and Merchant Agents grounded in your catalog and order data.
Learn more about AgentforceRetail is where Commerce Cloud earns its keep — catalogs with variants, promotions, loyalty and peak trading.
Direct-to-consumer storefronts with loyalty, order tracking and returns on one customer record.
See it about Retail & eCommerceSize and fit, variants by color and inseam, and resale or outlet channels — the shape of the Silver Jeans storefront.
See it about Fashion & apparelShade and variant catalogs, subscriptions, reviews and sampling promotions.
Several brands and locales on one B2C Commerce realm, with shared cartridges and separate site configurations.
Seven stages. Redirects, SEO and load testing are stages of their own, not tasks squeezed into launch week.
Current storefront, cartridges, integrations, traffic patterns and the trading calendar the launch must avoid.
Products, variants, pricing, inventory and customer accounts modeled and migrated, with a reconciliation report.
Templates or components, Page Designer, basket and checkout built against the agreed storefront architecture.
Payments, reviews, order management and back-office systems built as cartridges or APIs, each with its own tests.
URL mapping, redirects, canonical tags and structured data verified before the old storefront goes dark.
Load tests against expected peak traffic, a cutover plan, and the team on call through launch.
Code freeze planning, monitoring and agreed coverage through the peak trading window, then a backlog for the next release.
Straight answers to what buyers ask us first.
Salesforce Commerce Cloud is Salesforce's ecommerce platform. B2C Commerce runs direct-to-consumer storefronts, built on SFRA, PWA Kit or Storefront Next and configured in Business Manager. B2B Commerce runs account-based buying for business customers.
Salesforce renamed it Agentforce Commerce in October 2025 and went back to the Commerce Cloud name in September 2026. It is the same product. Its AI agents — Shopper Agent, Buyer Agent and Merchant Agent — keep the Agentforce name.
For a new build in 2026, Storefront Next is Salesforce's recommended storefront. If you run SFRA with many custom cartridges, staying on SFRA or moving in phases is often cheaper. If you run PWA Kit, Salesforce provides a migration guide to Storefront Next. Our readiness review gives you a written recommendation either way.
It depends on how many custom cartridges, integrations and templates the site has, because SiteGenesis code cannot be converted directly — it is rebuilt on SFRA. We give a fixed estimate after an audit of the current storefront rather than a number before we have seen it.
Cost is driven by the storefront type, the number of sites and locales, and the integrations. We quote after a short discovery, in writing, and the free 30-minute review is where that starts.
Yes. Commerce Cloud developers can join your team through staff augmentation, working in your repository, tools and sprint cadence.
Yes. Peak readiness is part of managed support: load testing ahead of the peak, code freeze planning, monitoring, and agreed coverage through the trading window.
Tell us about your storefront or your Salesforce org, and what is getting in the way. A consultant — not a sales rep — replies within one business day.