Salesforce

Salesforce B2C Commerce

Curated anchor platform in enterprise commerce with material relevance to the Marcom operating stack and a first-party developer surface.

Commerce & paymentsSystem of recordAgent-accessible SaaS

Representative source ↗Product site ↗

System roleSystem of record

Access maturityAgent-accessible SaaS

Agent postureFirst-party provider

Reference updatedNot stated by publisher

BYO-UI reviewedJul 10, 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 shopper tools search products, retrieve details, create/update/read/delete baskets and link to checkout using SLAS-scoped tokens; separate DX MCP covers APIs and development operations

02 · Data you can retrieve

Pilot shopper tools search products, retrieve details, create/update/read/delete baskets and link to checkout using SLAS-scoped tokens; separate DX MCP covers APIs and development operations

03 · Actions and write paths

Salesforce B2C Commerce's first-party MCP/agent surface includes state-changing tools in the documented capability area: Pilot shopper tools search products, retrieve details, create/update/read/delete baskets and link to checkout using SLAS-scoped tokens; separate DX MCP covers APIs and development operations. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Authentication model is documented by the vendor; inspect the cited source before implementation. Official docs explicitly label the shopper service a pilot and require account-executive onboarding.

05 · Monitoring, approval, and recovery

Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions. Official docs explicitly label the shopper service a pilot and require account-executive onboarding. Do not imply current pilot exposes all merchant/intelligence capabilities or that it is Agentforce Shopper Agent.

06 · Gaps and implementation limits

Official docs explicitly label the shopper service a pilot and require account-executive onboarding. Do not imply current pilot exposes all merchant/intelligence capabilities or that it is Agentforce Shopper Agent.

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party provider MCP API ↗Developer access Developer docs ↗SDKs and platform guidance Product ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPHosted B2C Commerce Shopper MCP plus separate B2C DX/developer MCPShopper service pilot; developer tooling current

Role: provider

Read scope: Pilot shopper tools search products, retrieve details, create/update/read/delete baskets and link to checkout using SLAS-scoped tokens; separate DX MCP covers APIs and development operations

Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.

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 interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Salesforce ships these experiences.

Single-platform patterns

Guided-shopping and campaign-to-checkout interface
Revenue reconciliation console
Commerce operations cockpit
Customer-resolution workbench

Use in the brief composer →

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

MCP / agent-role validationRepresentative source

https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/agentic-mcp-shopper-tools-quick-start.html ↗

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

Targeted first-party MCP/agent-role review; broader API inventory retained

MCPSource inventory

https://developer.salesforce.com/docs/commerce/commerce-api/guide/shopper-mcp.html ↗

First-party MCP documentation or product announcement recorded for this platform.

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

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

APISource inventory

https://developer.salesforce.com/docs/commerce/commerce-api ↗

First-party API reference or API overview recorded for this platform.

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

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

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 the representative first-party source or targeted access review.

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.