Salesforce

SalesforceB2C Commerce

Salesforce B2C Commerce is included for its hosted shopper MCP pilot, which grounds external assistants in storefront product data and supports basket building before handing checkout to the merchant site.

Commerce & paymentsSystem of recordAgent-accessible SaaS
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of record
Access maturityAgent-accessible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Pilot tools cover products, product images and details, shopper baskets, basket line items, and checkout links; merchant data and the separate B2C DX developer surface are outside this catalog.

02 · Data you can retrieve

Search storefront products, retrieve product details and images, and read a guest or registered shopper's basket using site, product, basket, and user-session identifiers.

03 · Actions and write paths

Create a basket, add products, delete a basket, and generate a link into the configured PWA Kit storefront checkout; the pilot does not expose general merchant administration.

04 · Authentication and permissions

Every Shopper MCP call requires a guest or registered SLAS JWT bearing sfcc.shopper-mcpagent, tenant, user, and scope claims. SCAPI Admin APIs instead use Account Manager and are not generically exposed by this service.

05 · Monitoring, approval, and recovery

Validate the SLAS JWT on every shopper-agent call and maintain one SSE connection per shopper. Confirm basket deletion and checkout handoff; keep merchant operations on separately authorized SCAPI Admin surfaces.

06 · Limits and caveats

The service remains a pilot requiring Salesforce account-executive onboarding. Current performance is demonstration-only, Agentforce integration is unsupported, and the pilot exposes shopper tools rather than the advertised future merchant or intelligence capabilities.

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP support

Official MCP serverHosted B2C Commerce Shopper MCP plus separate B2C DX/developer MCPShopper service pilot; developer tooling current

Support: Official MCP server

Read scope: Search products and retrieve product details, images, and basket state for the authenticated guest or registered shopper; this hosted service does not expose the full SCAPI suite.

Write scope: Create or add to baskets, remove a basket, and return a merchant-storefront checkout link. It does not document payment capture, order placement, or merchant catalog writes.

Authentication: Bearer SLAS JWT from a guest or registered shopper flow, with sfcc.shopper-mcpagent added to the client scopes; tenant, user, and scope claims travel through each request.

Approval boundary: Require shopper confirmation before deleting a basket or leaving the assistant for checkout. Do not let the pilot's product and basket tools imply authority over payment, orders, inventory, or merchant operations.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Salesforce ships them.

Single-platform patterns

  • Guided-shopping and campaign-to-checkout interface
  • Revenue reconciliation console
  • Commerce operations cockpit
  • Customer-resolution workbench
Use in the brief builder →

Multi-platform compositions

  • Salesforce B2C Commerce + CRM or support system: revenue reconciliation console
  • Salesforce B2C Commerce + lifecycle platform + analytics or finance system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
Developer docsSource inventory
https://developer.salesforce.com/docs/commerce ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.salesforce.com/commerce/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
May 19, 2026
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.