TLDR;
Salesforce says Universal Commerce Protocol checkout is live in B2C Commerce, giving eligible merchants a route into product discovery and buying inside Google's Gemini app and AI Mode. It is not a one-click launch: Google controls participation, and merchants need an en-US site, Merchant Center setup, compatible payments, authenticated checkout APIs and reliable commerce operations. Brands should treat this as a new sales-channel integration with testing and ownership requirements, not a marketing toggle.
What happened
Salesforce announced the live UCP integration in its 26 October B2C Commerce release. Merchants can configure Google as a platform so shoppers discover products and complete purchases on Gemini and AI Mode while the retailer remains merchant of record. The same release adds natural-language catalogue tools for merchandisers and expands agentic search and shopper assistance on the merchant's own site.
Agentic Commerce Search can now filter conversational requests using local store inventory and understand queries in multiple languages. Salesforce's Carter Shopper Agent also gains page awareness, allowing it to use the product, category or cart a shopper is viewing rather than answer from generic context. A Traffic Sources dashboard update separates revenue, orders and conversion from Search, Social, Email and Chatbot sources.
The release notes place these changes in B2C Commerce 26.10, deployed in phases between 29 September and 29 October. The supporting UCP implementation guide says the integration is generally available in B2C Commerce 26.9 and later, but currently supports en-US sites only. Salesforce Payments is not mandatory, though merchants need Salesforce Payments with Google Pay through Adyen or Stripe, or a compatible third-party payment implementation.
Salesforce's January announcement described native UCP support as a roadmap item. The October release changes the stage from planned support to an available integration, but it does not make every merchant visible automatically. Google must accept the merchant into its UCP programme, and a published profile or Merchant Center feed alone does not produce a Buy button.
Why it matters
This closes an important gap between a commerce standard and an implementable enterprise path. Retailers already operating B2C Commerce can expose checkout capabilities without replacing order, fulfilment and customer-service systems. Remaining merchant of record preserves operational responsibility and customer relationships, but it also leaves the retailer accountable for tax, inventory, fraud, returns, service and regulatory obligations.
The platform dependencies are substantial. Google's onboarding requires a Merchant Center account, programme acceptance, checkout API credentials and allowlisted test users. Salesforce needs a private SLAS client, UCP hooks that preserve existing basket and order logic, and a payment path Google can use. Custom promotions, loyalty, shipping, consent and fraud controls must behave correctly when an AI surface creates the session.
The new chatbot-source reporting is commercially useful because AI discovery can no longer be treated as unmeasurable referral noise. Even so, a channel label does not prove incrementality. Brands need consistent attribution from discovery through order, plus controls for cancellations, returns and repeat customers, before comparing the channel with search, affiliates or the owned storefront.
Local inventory and multilingual discovery widen the relevance problem. A conversational result may be semantically strong but commercially wrong if store stock, delivery promises, translated attributes or price data are stale. The value of the agent depends on the freshness and governance of the underlying catalogue more than on polished natural-language responses.
How your brand can benefit / be affected
Begin with Salesforce's technical audit before joining the Google waitlist. Map every basket, order, promotion, tax, payment and fulfilment customization touched by the UCP flow. Decide which environment Google testers should use, create separate credentials for it and confirm that retries and duplicate requests cannot create duplicate orders.
Use a deliberately narrow catalogue for the first pilot. Choose products with clean attributes, stable pricing, straightforward fulfilment and low regulatory risk. Test unavailable variants, split shipments, promotional conflicts, loyalty recognition, cancellations and refunds. Confirm that the customer sees the same total and delivery promise in Google, Salesforce and post-purchase communications.
Instrument the channel end to end. Capture UCP discovery, checkout-session creation, payment authorization, completed order, cancellation, return and support contact. Reconcile Salesforce's Chatbot traffic reporting with Merchant Center and order data. Keep a comparison group so a lift in AI-sourced orders is not confused with demand that would have converted through another channel.
Salesforce's Google onboarding guide is blunt that platform acceptance remains separate from implementation. Plan for that dependency and do not promise a launch date until Google access, payments and end-to-end tests are complete. The opportunity is to make a brand buyable during AI-led discovery, but reliable operations and measurable economics will decide whether it deserves scale.
News date: 26 October 2026. Editorial review: 27 October 2026.