Enabling Google as a Platform

The enablement process is split between making yourself a UCP-compliant business and onboarding with each platform. Salesforce publishes your business profile from Business Manager. Google as a platform discovers your products in Google Merchant Center (GMC) and must also accept you into Google’s UCP program before shoppers see a Buy button in Gemini or AI Mode in Search.

Join Google’s UCP waitlist first — even before your Salesforce implementation or Merchant Center feed is finished. Waitlist, GMC, and Salesforce UCP setup can proceed in parallel. Complete Configuration & Discovery and Checkout Session Authentication as you go. You still publish a business profile from Business Manager; for now Google calls the checkout URL you submit on their secrets form rather than fetching that profile.

• Onboard with Google
• Google Merchant Center (GMC) Setup
• End-to-end testing
• Get support

Google’s own developer and Merchant Center guides are the source of truth for Google’s program, waitlist, and sandbox. Start with Getting started with UCP on Google and How to onboard to UCP in Merchant Center.

Publishing a Salesforce business profile and a GMC feed does not by itself put a Buy button on Gemini. Google gates access to their UCP surfaces (Gemini and AI Mode in Search). Submit Google’s forms to Google — Salesforce does not collect these values.

1. Join Google’s UCP waitlist. Follow How to onboard to UCP in Merchant Center and Google’s UCP developer guide. Do this first, even if Business Manager and the Merchant Center feed are still in progress.
2. When Google selects you, they notify you and give you the Merchant Center UCP onboarding experience — including a sandbox to validate your UCP profile and native checkout APIs.
3. In parallel, complete the Salesforce UCP implementation in this guide (Business Manager, checkout APIs, payment path) and Google Merchant Center (GMC) Setup. Create the SLAS private client you will later share with Google — Checkout Session Authentication.
4. After Google accepts you, submit the MC UCP Checkout API Secrets form so Google can authenticate to your checkout APIs. See Share checkout API credentials.

Google rolls that Merchant Center experience out gradually. You may see a UCP integration tab in Merchant Center as it becomes available for your account. Google’s checkout feature is currently limited to participating merchants; Salesforce UCP on an en-US site does not skip Google’s waitlist.

When transacting with Google as a platform, Google Merchant Center is the source of truth for your products. Checkout still happens on Salesforce; Google uses GMC for product data and inventory for discovery. Finish this setup before you test the Buy button — Gemini can only offer SKUs that are in GMC with native_commerce set. You do not need to wait for waitlist acceptance to start the feed.

Also complete Google’s Merchant Center account requirements in Prepare your Merchant Center account:

• Return policy — required on the checkout screen. Include return cost, return window, and a link to the full policy.
• Customer support info — at least one of website, email, or phone. Google uses this for the “Contact Merchant” link on the order confirmation page.

Ensure your GMC account is verified and your product feed is active. The feed must target the en-US locale.

Your products must be synced to GMC to be eligible for discovery. This can be via the Salesforce Commerce Cloud (SFCC) GMC integration, third-party integration, or manually. If you already have an existing feed integration into GMC via a third-party feed aggregator, you are welcome to continue using that.

There are two additional net-new product fields required for UCP that aren’t in existing GMC feeds today:

• native_commerce - A boolean attribute that indicates whether a product is available for purchase directly through Google as a platform
• consumer_notice - Optional consumer-facing notices or disclaimers

For products to be eligible for UCP checkout, they must have the native_commerce attribute set to true. Only listings with that eligibility signal show the Buy button. Google documents this as native_commerce(checkout_eligibility) in Prepare your Merchant Center account.

The product id in your GMC feed must match the product ID your checkout APIs expect. If they differ, Google’s merchant_item_id custom attribute maps them.

Add those two fields to your feed via a supplemental feed as suggested by Google’s UCP documentation.

Configure those fields in your catalog and map them in the field mapping table. They are included in your feed file automatically.

Because UCP uses a Dynamic Checkout model, the platform pulls real-time tax and shipping costs directly from Salesforce during the checkout session. Static settings in GMC cause price mismatches and checkout failures.

Tax and shipping rates are calculated dynamically by B2C Commerce using your existing platform hooks:

• Tax calculation: dw.order.calculateTax hook

  • Integrates with your tax provider (Avalara, Vertex, etc.)
  • Uses real-time tax rates based on shipping address

• Shipping calculation: dw.order.calculateShipping hook

  • Uses your configured shipping methods and rates
  • Applies real-time carrier rates if integrated

Make sure that these hooks are properly configured and tested before enabling UCP. See Technical Audit for what to check, including logic that today lives on other SCAPI endpoints.

Some product categories cannot check out through Google (subscriptions, personalized goods, age-restricted items, and others). Leave native_commerce unset or false for those SKUs. See Google’s product restrictions.

To make specific products unavailable for UCP purchase:

1. Set the native_commerce attribute to false for those products in your catalog
2. Update your product feed to GMC
3. Products remain discoverable in Google but won’t be available for checkout

End-to-end testing means an allowlisted Google account, signed into Gemini or AI Mode in Search, sees a Buy button on your GMC products and can complete checkout. Getting there has four parts: share checkout credentials so Google can call you, allowlist tester accounts, use live payments for the Buy-button walkthrough, and validate from sandbox up to production.

Use Google’s MC UCP Checkout API Secrets form after you are accepted off the waitlist. Google uses the checkout URL and client credentials when an allowlisted user clicks Buy.

Copy the checkout API endpoint from the published business profile: the endpoint on the dev.ucp.shopping service. That is the checkout API base URL (the host that serves /checkout-sessions). Do not submit the /.well-known/ucp discovery URL.

As of August 2026, Google does not fetch your business profile for checkout. They call the checkout URL you specify on this form, with the client ID and secret you provide. Keep publishing the profile from Business Manager — other platforms and your own validation still use it — but Google’s Buy button path is the URL on the form until they move to profile-based discovery.

Tell Google which environment should be live for testers (sandbox, staging, or production). Google switches that toggle as you move from environment to environment. See Validate by environment.

Before you test the Buy button in Gemini, add the Google accounts that should see it. Do this in addition to the checkout API secrets form — credentials let Google call your APIs; allowlisting controls who sees the button.

Use personal Google accounts (@gmail.com). Corporate Google accounts are often blocked from UCP, so personal accounts are the reliable path.

Submit testers at https://sfdc.co/ucp-test-users. Allowlisting with Google takes a day or two after you submit, so add testers early — before you need them for an end-to-end walkthrough.

Google supports live mode payment testing only. The end-to-end Buy button flow in Gemini or AI Mode in Search requires live payment credentials on the environment Google is calling (a live Adyen or Stripe account, with live Google Pay). You cannot complete that walkthrough with test or sandbox payment credentials.

Headless testing of Checkout Session APIs — Postman or a similar tool — can use test payments. Use that path to validate hooks, tax, shipping, and the session lifecycle before you click Buy on Google’s surfaces.

Validate the Buy button in Gemini from the lowest environment up. Do not skip ahead.

1. Sandbox — validate the full Gemini walkthrough first.
2. Staging — after sandbox passes, validate again on staging.
3. Production — after staging passes, run a pre-production go-live check on production.

Google must change their environment toggle and allow lists for you to move from one environment to the next, and again for final go-live. Salesforce cannot flip that. When you are ready to progress, tell Google which environment should be live (and which tester Gmails apply) using the same channels as Share checkout API credentials and Allowlist test users.

Use the channel that owns the problem:

Google’s intake is for questions that sit on the Google side. Salesforce Support is for the Commerce Cloud integration.

j

Announcements

Choose Your B2C Commerce Storefront Type

Universal Commerce Protocol (UCP) Integration

Configuration & Discovery

Checkout Session Authentication

Technical Audit

Implementation Considerations

Transaction Management

Enabling Google as a Platform

Connect a Third-Party OMS

B2C Commerce

SCAPI

Storefront Next

Composable Storefront

Storefront Reference Architecture (SFRA)

Commerce Apps ISV Developer Guide

B2C Commerce Solutions

B2C Commerce Release Notes

B2C Commerce Reference Information

Ask the Community