Universal Commerce Protocol (UCP) Integration

Enable Universal Commerce Protocol (UCP) for your site so platforms that support UCP can discover and sell your products, while you remain Merchant of Record. Google is the first live platform at general availability (GA). The Salesforce implementation is platform-agnostic—one business profile, checkout lifecycle, and post-purchase webhook sync for any compatible platform.

UCP Overview

The Universal Commerce Protocol (UCP) is a common language for platforms, agents, and businesses to conduct agent commerce across industries. Within UCP there are two main players:

The platform: any entity that consumes capabilities—an app, an AI agent, a procurement system, or another business
The business: any entity that exposes capabilities—this is you (the merchant) powered by Salesforce Commerce Cloud

The protocol defines a common language and functional primitives so these two parties can interoperate securely and reliably across commercial verticals. A business declares what it offers and how it operates; any compatible platform can discover and use that without a bespoke, per-platform implementation. For example, enabling UCP for your site lets buyers on platforms such as Google Gemini programmatically discover your products and complete checkout without leaving the platform.

Platforms find your business by fetching the business profile Salesforce publishes from your Business Manager UCP settings—they don’t start at checkout. Configure that profile in Configuration and Discovery. Each platform can also have its own product-discovery setup; for Google, see Enabling Google as a Platform.

Business Benefits

New sales channel: Reach customers where they’re already shopping—in conversational AI, search, ads, and other surfaces
Integrated experience: Customers complete purchases without leaving the platform (for example, Gemini), boosting conversion
Merchant control: Merchants remain the Merchant of Record with full control over pricing, inventory, and fulfillment
Dynamic pricing: Real-time tax and shipping calculations make pricing accurate
Native integration: Uses existing B2C Commerce infrastructure and business logic

Audience

This guide is for developers and technical architects who are implementing the UCP integration with Salesforce B2C Commerce.

Guide Contents

Configuration and Discovery - Business Manager setup, business profile, Order Management System (OMS), Payment Provider Support
Checkout Session Authentication - SLAS private client and dev.ucp.shopping.checkout:manage scope for Checkout Session APIs
Technical Audit - Decide what checkout logic you must move or bridge onto UCP hooks
Implementation Considerations - Hook architecture, extensibility, and code examples
Transaction Management - Transaction boundaries for Checkout Session hooks
Enabling Google as a Platform - Google onboarding, Merchant Center product discovery, test users, and Google UCP support
Order Post-Processing Events - How shipment, cancellation, and return updates reach the agent platform as signed full-order snapshots

Implementation Workflow

Follow these phases to enable UCP for your organization:

Phase 1: Prerequisites and Planning

Review these prerequisites and restrictions:

Generally available (GA) in B2C Commerce 26.9 and later
UCP is currently limited to en-US sites only
Salesforce OMS is optional—or connect a third-party OMS via Connect a Third-Party OMS if you want lifecycle events on the platform. See Order Post-Processing Events for how those events become UCP snapshots.
Salesforce Payments (SFP) SKU provisioned—or a third-party payments implementation
If using SFP—Adyen or Stripe via Salesforce Payments, with Google Pay enabled in the gateway
Native Salesforce Payments advertises Google Pay; Google as a platform still expects Google Pay today

Phase 2: Technical Audit

Complete the Technical Audit to:

Confirm which Basket/Order hooks already run in the UCP flow
Remap Shopper Baskets, Shopper Orders, SFRA controller, or other resource-specific logic onto UCP hooks
Select a payment path (Salesforce Payments vs DIY) and note headless side effects (email, OMS, Continue URL)

Phase 3: Implementation

Review Implementation Considerations and:

Implement custom hooks if needed
Add address verification or custom validation
Configure third-party Adyen webhooks if you share an Adyen merchant account with Salesforce Payments
Test hook execution flow

Phase 4: Configuration

Complete Configuration and Discovery:

Configure Business Manager UCP settings
Set up chosen Payment Provider
Configure OMS event sync. See Order Post-Processing Events
GET /.well-known/ucp and confirm the published business profile

Complete Checkout Session Authentication:

Create a SLAS private client with the dev.ucp.shopping.checkout:manage scope

Complete Enabling Google as a Platform if you are transacting with Google:

Join Google’s UCP waitlist (do this first—even before Salesforce UCP or the Merchant Center feed is finished)
Configure Google Merchant Center product feeds and enable the native_commerce attribute on products
After Google accepts you, complete End-to-End Testing (checkout API secrets, tester allowlisting, live payments, sandbox → staging → production)

Phase 5: Validation

Confirm the business profile at /.well-known/ucp (version, capabilities, payment handlers, signing keys)
Request a SLAS guest token with dev.ucp.shopping.checkout:manage and test the Checkout Session APIs using Postman or similar API testing tools. Headless testing can use test payments. See Checkout Session Authentication.
After Google allowlists your testers, walk through discovery and checkout in Gemini with a personal @gmail.com account. Start on sandbox, then staging, then production—Google must retarget their toggle and allow lists between environments. Google supports live mode payments only for that Buy-button flow. See End-to-End Testing.
Verify order creation and fulfillment events
Confirm pricing, tax, and shipping calculations