Agentforce Commerce, the platform Salesforce previously sold as B2C Commerce Cloud, connects to Service Cloud (now Agentforce Service) through Salesforce Order Management. Once that connection is live, a support rep opens a customer record in the Service Console and sees the order summary, fulfillment status, and return history in the same screen, no second login, no separate order system.
That single sentence is worth more than most vendor pages give it credit for, because the integration itself has moved a long way since it was first pitched as “commerce and service in one CRM.” Here’s what actually changed, how the connection works today, and where it still trips teams up.
Commerce Cloud and Service Cloud Have New Names
Two rebrands changed the vocabulary here, and both matter if you’re searching Salesforce’s own site for documentation.
Salesforce renamed Commerce Cloud to Agentforce Commerce. The shift followed the September 2024 announcement of a next-generation commerce platform that folds B2C, direct-to-consumer, and B2B commerce, order management, and payments into one architecture, with three purpose-built AI agents, Merchant, Buyer, and Personal Shopper, running on top of it. Salesforce’s own commerce pages now carry the note plainly: Commerce Cloud is Agentforce Commerce.
Service Cloud went through the same change. Salesforce Help now states outright that Service Cloud is Agentforce Service, though the older name still shows up across the admin console and documentation while the transition finishes.
For anyone writing search queries or briefing a consulting partner, both names are correct right now. Salesforce hasn’t fully retired either one, and most buyers still search “B2C Commerce Cloud” and “Service Cloud” out of habit. This guide uses the current names first and the legacy names in parentheses, because that’s how the platform itself is labeled today.
Why a Disconnected Storefront and Support Desk Still Costs You Customers
The original problem this integration solves hasn’t changed, even though the tooling has. When your storefront and your support desk run on separate systems, a service agent working a case has no direct line to order history, fulfillment status, or prior interactions. The agent asks the customer to repeat an order number that already exists in another database. The customer waits. The case takes longer to close than it should.
Salesforce’s own research puts a number on how widespread that gap is. According to the fourth edition of Salesforce’s “State of Service” report, 79% of service professionals say delivering good support without a full view of customer interactions is not possible. That’s not a hypothetical risk, it’s the majority experience of the people doing the job.
How Agentforce Commerce Actually Connects to Service Cloud
Here’s the part most outdated write-ups get wrong: Agentforce Commerce and Service Cloud aren’t wired together directly. The connection runs through Salesforce Order Management, which sits between the storefront and the service desk and natively supports both.
Order data lands directly in the Service Console
Once Order Management is connected, a service rep can locate a customer account and see the full order history without leaving the Service Console or switching to a separate order system. That includes order summaries, line-item status, and the actions a rep can take directly from the case: process a cancellation, apply a discount or price adjustment before an item ships, or trigger a reshipment for an item lost or missing in transit. Each of those actions writes back to Order Management as a change order, so the order record and the case stay in sync.
The connection is self-provisioned, not a support ticket
This is a genuine improvement over how the integration used to work. Salesforce now lets teams self-provision the connection between Agentforce Commerce and Order Management directly from the B2C Commerce Business Manager, using the Order Management Integration Administration page. Businesses no longer need to file a request with Salesforce Support to turn the connection on or manage it going forward; admins handle provisioning and deactivation themselves.
Data Cloud is the layer that makes it a true 360 view
Order Management handles the transactional link: orders, fulfillment, returns. The broader customer view, marketing engagement, loyalty status, past service history, and product usage comes from Data Cloud, which Salesforce positions as the shared data layer beneath Commerce, Service, Marketing, and Sales. A connected Data Cloud implementation is what turns “the agent can see the order” into “the agent can see the whole relationship,” which is the difference between a lookup and genuinely informed support.
What the Integration Delivers Today
The four benefits from the original pitch are still real, but each one looks different in 2026 than it did when this integration first launched.
- Self-service that resolves before a case opens. Agentforce Self-Service, released as part of Salesforce’s Summer ’26 update, replaced the old FAQ-and-search-box pattern with a Help Agent that a team can configure in a handful of clicks, running on a conversational portal rather than a static page. The goal isn’t a better knowledge base, it’s fewer cases reaching a human at all. We covered the mechanics of building that kind of deflection-first service portal in a separate breakdown.
- Case management with an AI layer underneath it. Case records are still the backbone of Agentforce Service, but routing, wrap-up, and next-step recommendations now run through Agentforce rather than static rules. Cases route to whichever combination of human rep and AI agent fits the query, and reps get real-time suggestions grounded in the case, the order, and the customer’s history.
- Agentic order support, not just order visibility. The newest layer here is agentic skills embedded directly in the service workspace that can resolve order exceptions, a delayed shipment, a mismatched inventory count, a fulfillment routing conflict, without a rep manually digging through the order timeline. Salesforce frames this as cutting the “integration tax” of stitching commerce and service together with custom middleware.
- Omnichannel support on one record. Chat, email, phone, and in-store contact still consolidate into a single case history, and Multi-Agent Orchestration, also part of the Summer ’26 release, lets several specialized agents share context on that case so the customer isn’t repeating themselves across channels.
Commerce–Service Integration: Then vs. Now
| What changed | Original state (pre-2024) | Current state (2026) |
|---|---|---|
| Product names | B2C Commerce Cloud, Service Cloud | Agentforce Commerce, Agentforce Service |
| How commerce and service connect | Custom integration or middleware, often partner-built | Native connection through Salesforce Order Management |
| Provisioning the connection | Required a Salesforce Support request | Self-provisioned from Business Manager |
| Self-service | Static FAQ pages and knowledge search | Agentforce Help Agent, conversational and configurable in minutes |
| Order actions from a case | Limited to viewing order status | Cancel, discount, and reship directly from the Service Console |
| AI involvement | Minimal — mostly rule-based routing | Agentforce case routing, wrap-up, and agentic order-exception resolution |
Where This Kind of Project Actually Goes Wrong
Most of the disappointing rollouts we see trace back to a handful of avoidable decisions, not to the platform itself.
- Treating Order Management as optional. Without it, there’s no native path from the storefront to the Service Console, and teams end up rebuilding a version of the same integration Salesforce already ships.
- Skipping Data Cloud and calling it “connected” anyway. Order visibility alone gets a rep the shipment status. It doesn’t get them loyalty tier, prior complaints, or marketing engagement and those are usually what separates a fast case close from a genuinely good one.
- Turning on Agentforce agents before the knowledge base and order data are clean. An agent grounded in thin or outdated content will still answer confidently, just wrong. That’s a support-quality problem hiding behind an AI rollout.
- Never reassigning the connection once it’s provisioned. Self-service provisioning is a one-time setup step, but the connection needs an owner who monitors it as order volume, catalog changes, and new sales channels get added.
Measuring Whether the Integration Is Actually Working
A dashboard that only tracks case volume will miss most of what this integration is supposed to change. Track these instead:
| Metric | What it tells you |
|---|---|
| First-contact resolution on order queries | Whether reps have enough order context to close a case without escalating |
| Time from case open to order action taken | Whether cancellations, reships, and discounts are happening inside the case, not in a separate system |
| Self-service deflection rate on order status queries | Whether the Help Agent is actually answering “where’s my order” before it becomes a case |
| CSAT on cases involving an order | Whether the unified view is improving the interactions that matter most to retention |
The Cloud Odyssey View
Most of the vendor content on this topic still describes the 2019 version of the integration, a nice-to-have data sync between two separate clouds. That’s not what this is anymore. Agentforce Commerce and Agentforce Service now share a transactional backbone through Order Management and a data layer through Data Cloud, and the newer pieces- self-provisioned connections, agentic order exception handling, Multi-Agent Orchestration are built for teams that already expect commerce and service to behave like one system, not two that happen to talk to each other.
The gap we see most often in the field isn’t the platform capability. It’s sequencing. Teams turn on the AI layer before the order data and knowledge base underneath it are trustworthy, and the result is a support agent that sounds confident and answers wrong. We’ve walked a fintech through the exact rework of getting that sequencing right, and the pattern holds for commerce brands too, get the data foundation solid first, then layer in the automation.
If your storefront and support desk still feel like two separate systems that happen to share a logo, that’s a sequencing problem, not a platform limitation. Talk to Cloud Odyssey about what a proper Agentforce Commerce and Service Cloud connection looks like for your catalog and case volume.
Frequently Asked Questions
Salesforce has renamed B2C Commerce Cloud to Agentforce Commerce. Both names are still in use across Salesforce’s documentation and admin tools during the transition, and either term works in Salesforce’s search and support channels.
Yes, for the native path. Order Management is the layer that natively supports both Agentforce Commerce and Service Cloud, giving service agents direct access to order summaries in the Service Console. Without it, you’re building a custom integration to replicate what Salesforce already ships.
You can self-provision it. The B2C Commerce Business Manager includes a Connections page and an Order Management Integration Administration page that let admins activate, manage, and deactivate the connection without filing a support request.
Order Management carries transactional order data: status, line items, returns, cancellations. Data Cloud unifies that with everything else about the customer, including marketing engagement, loyalty, and prior service history, giving reps a full relationship view rather than just an order lookup.
No. Agentforce agents handle routing, case wrap-up, and lower-complexity order exceptions, but the platform is built around agents and human reps sharing context on the same case, not replacing the human entirely. Multi-Agent Orchestration is specifically designed for handoffs between AI agents and people on complex issues.
