This summary was created with AI and reviewed by an editor
.svg)
How to capture value today without replatforming and prepare for what's coming next?
Agentic commerce, AI-powered discovery and Storefront Next are changing how retailers think about their Commerce Cloud investments. But for existing SFCC customers, the question isn't simply "Should we move?"
It's:
"What should we adopt now, what should we prepare for and what can wait?"
The good news is that the Salesforce roadmap gives existing retailers room to evolve without treating replatforming as an immediate requirement.
Here is a practical view of what existing SFCC customers can adopt today and how to plan for what comes next.
The most reassuring message for existing customers is that the biggest near-term wins land on the storefront you already run. Shopper Agent with Cart & Checkout is generally available on SFRA today, so you can add conversational, discovery-to-checkout shopping without a migration.
Agentic Commerce Search (the former Cimulate) integrates into B2C Commerce and Merchant Agent brings natural-language merchandising into Business Manager. None of these require Storefront Next. The platform is investing in your current architecture, not deprecating it.
For existing retailers, this means the SFCC roadmap should not be treated as a binary choice between staying on the current platform and undertaking an immediate replatforming project. Instead, retailers can assess which new capabilities can deliver value within their existing Salesforce Commerce Cloud environment.
For years, SFCC merchandising has meant maintaining search synonyms, no-results reports and lots of manual rules. Agentic Commerce Search replaces much of that with AI-native discovery and agentic merchandising.
This shift is an important part of the move towards AI commerce. Instead of relying primarily on manually maintained rules, retailers can increasingly use AI to understand shopper intent and improve product discovery.
Plan to retrain merchandisers around intent and curation rather than manual maintenance.
A quietly significant thread is Answer Engine Optimisation (AEO) and AI platform integrations, product feeds into ChatGPT and into Google’s AI Mode and Gemini, with checkout.
Discovery is moving beyond your own storefront onto conversational AI surfaces. Existing customers should start treating product-data quality, structured attributes and feed readiness as a growth channel, not back-office hygiene.
For SFCC retailers, this also creates an operational challenge. Product feeds often need to be created, updated and distributed across multiple channels, each with different requirements.
TCTG Product Feed Generator addresses this layer by automating product feed creation and updates for channels including Google Shopping, Meta, Amazon, TikTok and Pinterest. It provides a way to centralise feed management within the Salesforce Commerce Cloud environment, with customisation and scheduled or real-time updates.
The bigger opportunity is not simply better feed management. It is making product data more consistent, accessible and ready for the next generation of commerce discovery.
Storefront Next is the strategic direction for the B2C front end: a modern, headless, AI-first storefront on React Router 7, React 19 and Tailwind.
It is not a forced migration. The continued investment in SFRA proves that. But it is where new capability (Modern Page Designer support, the fastest performance, the developer toolkit) will concentrate.
For existing SFCC customers, this makes Storefront Next an important part of the longer-term SFCC modernisation conversation rather than an immediate migration requirement.
Treat it as a planned, evaluated move.
Perhaps the biggest change is cadence. Salesforce now ships B2C features roughly monthly (10x a year), surfaced through release notes and an innovation hub.
That is a real advantage. You stop waiting for big-bang upgrades, but it demands a lighter, continuous change-management process: someone owning release-note triage, a cadence for enabling new features and regression testing that keeps pace.
For existing customers, the Salesforce B2C Commerce roadmap therefore has implications beyond technology. Teams need to adapt their operating model so they can continuously assess, test and adopt relevant platform capabilities.
The Agentic B2C Developer Toolkit, a unified CLI, MCP server, IDE plugins and Agent Skills for assistants such as Claude Code, Cursor and Copilot is aimed squarely at existing dev teams.
Even without Storefront Next, adopting these can cut onboarding and routine build time, and it positions your engineers for the AI-assisted workflow the platform is standardising on.
For organisations planning SFCC modernisation, developer workflow should therefore be considered alongside storefront architecture, integrations and customer experience.
The SFCC Roadmap: What Should You Do Next?
Next 90 Days — Understand and prepare
Next 6 Months — Pilot and assess
Next 12 Months — Build the roadmap
What the Salesforce B2C Commerce Roadmap Means for Existing Customers?
The right approach is to understand which capabilities can create value today, identify where your current architecture can support them and build a measured roadmap for what's next.
For retailers already invested in Salesforce Commerce Cloud, the opportunity is not simply to decide whether to replatform. It is to understand how Salesforce agentic commerce, AI commerce, Shopper Agent, Agentic Commerce Search and Storefront Next fit into the evolution of your existing commerce estate.
