Your store, renewed
one page at a time
We build and renew storefronts on the Agentforce Commerce platform (formerly Commerce Cloud), from long-running sites to Storefront Next and B2B stores, moving one part at a time, so your store keeps selling while it changes.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When the next storefront looks like a rebuild
Many B2C Commerce sites still run on the storefront they launched with, the Storefront Reference Architecture or the older SiteGenesis, with years of cartridges layered on top. A cartridge is a package of storefront code: some are Salesforce’s, some come from other companies, and many are the site’s own.
Salesforce now recommends Storefront Next for B2C Commerce storefronts, and has marked the Open Commerce API deprecated, the older API that many integrations and headless front ends still call.
Done all at once, a rebuild can mean a long stretch with two storefronts to keep in step, and one switch-over day that carries most of the risk. So the move gets put off, while the current site gets harder to change.
What we build
What we build on the Agentforce Commerce platform, each part with a named owner on your side and ours, and every change tried in a sandbox, a separate environment for building and testing, before shoppers see it.
Storefronts on Storefront Next
Salesforce’s recommended storefront for B2C Commerce: a React storefront rendered on the server for each first page load and deployed on Managed Runtime, Salesforce’s hosting for it. Components are built and tried one at a time in Storybook, Page Designer serves the pages your team arranges itself, and Composable Storefront (PWA Kit) sites move to it with Salesforce’s migration guide.
Long-running sites, kept in order
Sites on the Storefront Reference Architecture with every change kept in cartridges of their own, never in Salesforce’s base cartridge, as Salesforce’s docs ask, so its security fixes and new features can still be brought in. Page Designer components for what your merchandisers, the people who arrange products and promotions, change themselves.
A group of pages at a time
Browsing pages moved to the new storefront first and cart and checkout when they’re ready, all at the same address, with Hybrid Auth, the platform’s own sign-in across both storefronts, keeping shoppers signed in with the same cart.
B2B stores on the Salesforce platform
B2B Commerce stores on the template Salesforce recommends, built on the Lightning Web Runtime with Lightning web components, in the same org, your company’s own instance of the platform, as your sales and service teams. Aura stores move to it as Salesforce’s migration guide sets out, the current store running until the new one is ready.
Integrations through the B2C Commerce API
Order management, ERP, product data and payments connected through the B2C Commerce API, with custom APIs, endpoints of your own on the same API, for logic only your business has. Each integration signs in as its own API client, a login of its own, with only the scopes it needs, as Salesforce’s authorization guide sets out.
Integrations moved off the older API
Integrations and headless front ends that still call the Open Commerce API moved to the B2C Commerce API one at a time, each mapped with Salesforce’s own table of where each older resource now lives, and one sign-in token working with both while they move.
Online and in store
Store pickup, the stock each store holds and order management connected to the storefront, on the products your business licenses, such as Omnichannel Inventory and Salesforce Order Management, so shoppers can see what a store has and choose to collect it there.
Moves onto the platform
Your catalog, customer accounts and order history imported through Business Manager’s import tools and the B2C Commerce API. Records are compared with the old system before anything goes live, and each old page address is sent on to its new one with a redirect.
AI where it helps
Shopper Agent, Buyer Agent and Merchant Agent, which Salesforce made generally available in June 2026, set up for the jobs you choose. And assistants of your own, connected through the B2C Commerce API, each with only the access it needs.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Sales and service on the same platform:CRM development
- Developers in your own team:Hire storefront developers
Two storefronts, one shopper
A site doesn’t have to move to Storefront Next all at once. Salesforce’s hybrid setup lets the new storefront serve some pages while the current one, on the Storefront Reference Architecture or SiteGenesis, serves the rest.
Shoppers keep the same address: the platform’s own content delivery network sends each page request to the storefront that serves it. Hybrid Auth, the platform’s own sign-in across both, keeps the shopper’s session in step, so shoppers move between the two without signing in again or losing their cart.
So a store can move its browsing pages first, keep cart and checkout where they are, and move the rest when each is ready. That’s the split Salesforce’s own guide shows, and where the line falls can differ from store to store.
Where the line falls
Not started: the current storefront serves every page, as it does today.
Browsing pages moved: shoppers browse on the new storefront and check out on the current one, signed in throughout, with the same cart.
Cart and account too: only checkout stays on the current storefront, and shoppers reach it signed in, with the same cart.
Every page: the new storefront serves the whole path, and the current one’s pages are no longer used.
Wherever the line falls, shoppers see one store: signed in once, with one cart.
{{ hyStatus }}
Where new features arrive
B2C Commerce has two APIs. Salesforce marked the older one, the Open Commerce API, deprecated as of April 2026: under its policy, it stays available for two more years with security updates, but gets no new features. New endpoints and features go to the B2C Commerce API only, and Salesforce asks new projects to use it alone.
Existing integrations don’t have to move at once. The Shopper Login and API Access Service gives one sign-in token that works with both, so each integration can move on its own, and Salesforce lists a few tasks still best handled through the older API for now, such as system information.
Two more changes come with their own guidance. From B2C Commerce version 25.3, Hybrid Auth replaced the older plug-in cartridge for hybrid storefronts: storefronts still on the cartridge are still supported, and Salesforce encourages the move. For B2B stores, Salesforce recommends the template built on the Lightning Web Runtime and suggests existing Aura stores consider moving to it.
So every integration is listed with the API it calls, and each moves on its own, tried in a sandbox first.
Start with what your storefront calls
The review covers each site and its storefront, whether the Storefront Reference Architecture, SiteGenesis, the Composable Storefront or Storefront Next, with what Salesforce states about each; its cartridges: which are your own, which change Salesforce’s code, and which come from other companies; each integration and headless front end: which API it calls, its client and access, and whether it signs in through the Shopper Login and API Access Service; a hybrid site’s sign-in, on the older plug-in cartridge or Hybrid Auth; its Page Designer components, and what merchandisers change without a code release; its B2B stores, if any, on Aura or the Lightning Web Runtime, and what they share with your sales and service org; store pickup, inventory and order management connections; and Business Manager roles, and who can release code.
The first step is one group of pages moved to the new storefront in a hybrid setup, or one integration moved to the B2C Commerce API, tried in a sandbox first.
You get a written review and a proposal for the first step.
Questions worth asking
Should we move to Storefront Next, or keep improving our current site?
The answer turns on your site, your team and how much of the site lives in its own cartridges. Salesforce recommends Storefront Next for B2C Commerce storefronts, a React storefront deployed on Managed Runtime. The Storefront Reference Architecture suits a team building on the code and skills it already has, and Salesforce’s hybrid setup lets a site move a group of pages at a time. We look at your cartridges and integrations first, then suggest a path.
Can we move one part of the site at a time?
Yes. Salesforce’s hybrid setup lets Storefront Next serve some pages while the current storefront serves the rest, at the same address, with Hybrid Auth keeping the shopper’s session and cart in step across both. Salesforce’s own example moves the browsing pages first and keeps checkout on the current storefront until the new one is ready for it.
Our integrations use the Open Commerce API. What changes?
Salesforce marked the Open Commerce API deprecated as of April 2026. Under its policy, the API stays available for two more years with security updates, but gets no new features, which go to the B2C Commerce API only. The Shopper Login and API Access Service gives one sign-in token for both, so we move your integrations one at a time, each mapped with Salesforce’s own table and tried in a sandbox first.
We built on the Composable Storefront. Where does that leave us?
Salesforce now recommends Storefront Next and publishes a guide to migrating from PWA Kit, the toolkit the Composable Storefront is built on. Both are React storefronts deployed on Managed Runtime, so a team that knows one will recognize much of the other. We check what your own changes would need before any move is planned.
Our B2B store runs on Aura. Should we move it to the Lightning Web Runtime?
Often, yes, when it suits your plans. Salesforce recommends the store template built on the Lightning Web Runtime for new B2B stores and suggests existing Aura stores consider moving. The new store is built from that template while the Aura store stays as it is, and its Aura components are replaced with Lightning web components, the only kind it supports. We start with a list of your components.
Do B2C Commerce and B2B Commerce work the same way?
Not quite. B2C Commerce runs on its own platform, with Business Manager for your merchandisers and storefronts built on its storefront options and APIs. B2B Commerce runs on the Salesforce platform itself, in the same org as your sales and service teams, with stores built from Salesforce’s templates. We work on each as Salesforce documents it.
Can our merchandisers change pages without a release?
Yes, within the components a developer builds for them. Page Designer lets merchandisers arrange pages from those components in Business Manager, on Storefront Next as on the Storefront Reference Architecture, and campaigns and promotions are set up there too. We build the components with your team, so they can change what they need without new code.
Can you connect our storefront to our order management, ERP or other systems?
Yes. The B2C Commerce API carries most connections, and custom APIs cover logic that only your business has, with every integration limited to the access it needs. We connect one system at a time, starting where the most work is done by hand, settle which system owns each record, and test each connection in a sandbox before it goes live.
Can shoppers order online and pick up in store?
Yes, with the platform’s in-store pickup. Each store keeps its own inventory list, shoppers can see what a store has and choose to pick up there instead of having it delivered, and orders can go on to Salesforce Order Management where your business licenses it. We set it up store by store and test each step with your team.
Can AI assistants shop our store?
Salesforce made Shopper Agent, Buyer Agent and Merchant Agent generally available in June 2026. We set up the ones that fit your store, and connect assistants of your own through the B2C Commerce API, each with only the access it needs, for the jobs you agree.
Can you move us onto the platform from our current one?
Yes, with Business Manager’s import tools and the B2C Commerce API. Your catalog, customers and orders are compared with the old system in a trial run your team checks, and each old address gets a redirect to its new page before launch.
Can you take over our existing storefront?
Yes. The review comes first, so each cartridge, integration and sandbox has a name against it, and then we pick up the work in the order that matters most to you.
How do you keep our store secure?
We give every API client its own scopes and nothing more, set Business Manager roles to match each person’s work, and review any cartridge from another company before it joins the site. Client secrets stay on the server side, out of the storefront’s code, and Salesforce’s security guidance is followed throughout.
What does it cost?
It depends on your sites, your integrations and the first step you choose. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.
Can we hire developers for our own team?
Yes. We introduce developers who know B2C Commerce and B2B Commerce within 48 hours of your request, working in your time zone. You meet them first, and decide who joins.
Salesforce, Agentforce, Agentforce Commerce, Commerce Cloud and Lightning are trademarks of Salesforce, Inc., and the other Salesforce product names on this page may be too. Webair is independent of Salesforce, Inc., and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us which storefront your site runs on and what your integrations call. We’ll agree on a first step in a short call.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}