Platform implementation guide

Salesforce Commerce Cloud: build a controlled agentic-commerce path

Use Salesforce B2C Commerce shopper APIs for the authorized storefront flow, and treat its documented UCP integration as a separate, configuration-dependent capability with explicit regional and platform limits.

Official sources reviewed 2026-08-27. This date records the documentation review, not a test of a specific merchant store.

Capabilities confirmed in official documentation

• SCAPI is a REST API set for storefronts, merchant tools and integrations. Shopper APIs are customer-facing and use SLAS OAuth 2.1; Admin APIs are merchant-facing and use Account Manager authentication.
• Shopper APIs support anonymous users and are generally read-only, with Baskets and Orders documented as exceptions. Admin APIs provide read and write access for moderate, merchant-facing usage.
• Shopper Products returns products that are online, merchandised to the selected site catalog and ready to sell. Shopper Context can personalize pricing, promotions and shipping by customer group, source code or store ID.
• Shopper Orders creates orders from baskets prepared with Shopper Baskets and requires the corresponding SLAS shopper scope. Payment-status updates use the separate Orders API.
• The UCP integration publishes a business profile at /.well-known/ucp and documents checkout-session authentication, hooks, transaction management, platform onboarding and post-purchase synchronization.
• Salesforce documents a Shopper Agents REST API that initializes an Agentforce session with a SLAS shopper token and the sfcc.shopper-agents.rw scope.
• SCAPI is rate limited. Salesforce documents ten-second Shopper API and sixty-second Admin API response limits, request and response body limits, USID routing and CORS configuration.

Implementation sequence

1. Keep SLAS Shopper and Account Manager Admin credentials in separate trust domains. Give each token only the scopes required by the selected Shopper, Admin, Agentforce or UCP flow.
2. Bind discovery and checkout to the correct organization, site and SLAS channel. Supply Shopper Context only when personalization is necessary, authorized and reflected in cache behavior.
3. For a standard SCAPI flow, record the basket, selected products, pricing context and payment handoff separately from order creation and later payment-status management.
4. For UCP, complete the documented technical audit, business-profile configuration, SLAS private-client setup and environment-specific testing before declaring the merchant enabled.
5. Treat Agentforce Shopper Agents, B2C DX MCP tooling and UCP as distinct surfaces. Do not infer that enabling one makes the others available to a merchant or third-party agent.

Scenarios to test before claiming support

• A product is online globally but not merchandised or ready to sell for the selected site catalog and must not be presented as purchasable.
• A guest or registered shopper token expires, lacks the required scope or is reused across the wrong site or channel.
• Customer group, source code or store context changes the quoted price or promotion and the basket must be recalculated before confirmation.
• An order request is retried after a timeout. The client must reconcile the basket and order state before sending another creation request.
• The UCP business profile is absent, has the wrong capabilities or signing keys, or the site locale is not en-US. The integration must not be reported as enabled.
• SCAPI returns rate limiting, maintenance or timeout responses and the client preserves state without converting an unknown outcome into a failed or completed order.

Evidence to retain from the test

• Record the organization, site, channel, API family, SLAS scopes and non-secret client type used for each controlled test.
• Retain redacted product, Shopper Context, basket and order request and response pairs with timestamps, identifiers, totals and observed retry outcome.
• For UCP, capture the business profile, declared capabilities, payment handlers and signing-key metadata, plus sandbox and staging test results. Platform acceptance and production availability require their own evidence.

What the documentation does not establish

• The official UCP guide establishes a Salesforce B2C Commerce integration, but it does not prove that a specific merchant has enabled, passed audit or been accepted by a platform.
• The current UCP documentation says Google is the first live GA platform and that the integration is limited to en-US sites. Availability for another locale or platform is not established here.
• A Shopper Agents endpoint initializes an Agentforce session; it does not by itself establish support for arbitrary third-party agents or every commerce action.
• A successful basket or order API response does not prove payment settlement, fulfillment, refund or production readiness.

Evidence boundary

Salesforce now documents UCP and agent-related surfaces, but merchant configuration, locale, scopes, platform acceptance and end-to-end results remain separate proof requirements.

Use the public signal scanner for a limited external check, then run the test cases above in a controlled environment. Review common failure modes before extending credentials or payment access.