Google UCP for Ecommerce: What Sellers Must Set Up

Google UCP for ecommerce, Google's Universal Commerce Protocol, lets AI Mode and Gemini complete purchases through a merchant's systems.

I tested both of my Shopify stores against Google's requirements when the updated implementation guide appeared. UCP requires a clean Merchant Center feed, technical endpoints, payment support, and Google's approval.

This guide combines those requirements in one checklist. It shows which gaps you can fix now and which block depends on Google's account rollout.

Mark each requirement passed or blocked. An average score hides the missing part that stops onboarding. Each blocked row should name the next task and the person who owns it.

Key takeaways

What is Google UCP, and how does a transaction work?

Universal Commerce Protocol is Google's open standard for letting AI Mode and Gemini transact with a merchant's backend. Google describes the merchant, AI surface, and payment handler as separate roles in the purchase. The merchant keeps the customer relationship and remains the merchant of record.

A UCP purchase moves in this order,

1. The merchant publishes its profile and checkout endpoints.
2. The AI surface sends the order and receives live totals.
3. Google Pay sends payment details through the configured handler.
4. The merchant confirms the order and sends later status updates.

Google's implementation overview places feed setup before this transaction flow.

The merchant's system still sets the final price, stock, shipping, tax, and policy terms. It receives the order, fulfills it, and handles support. The AI surface presents the response and carries the shopper's choices between steps.

Google's protocol explanation says UCP works with Agent Payments Protocol for secure agent-led payments. It can also use Agent2Agent and Model Context Protocol as connection methods. Those standards handle narrower parts of the system.

OpenAI's separate checkout standard assigns similar duties through its own protocol. An integration built for one won't cover the other by default.

Google says its surfaces support only part of the public UCP specification. A developer can build a valid feature that Google hasn't enabled for merchants.

Start with the capabilities shown in Merchant Center. Add an optional feature only when the validation flow offers it.

Run the UCP Readiness Check on your own store

Apply for UCP when your account, integration, payment setup, and program eligibility all have evidence behind them. The first three checks sit below. The final eligibility check depends on Google's rollout and appears in the next section.

Work through the store-controlled checks in order,

1. Feed readiness: Confirm Merchant Center can supply the product and policy details used at checkout.
2. Technical readiness: Give Google a working profile and checkout path it can test.
3. Payment readiness: Confirm Google Pay tokens can reach your payment processor.

The checklist maps each requirement to its evidence. Google's account approval remains a separate decision.

1. What your Merchant Center account must cover

Your account needs approved products, complete policies, and the product-level UCP checkout setting before technical work starts. Google's Merchant Center preparation guide requires an account in good standing with products approved for free listings.

Check these checkout records in Merchant Center,

• Add the return window, cost, and full policy link.
• Provide a service URL, email address, or phone number.
• Keep price, availability, identifiers, and brand assets current.
• Mark only supported products for UCP checkout.
• Exclude products Google lists as ineligible for this checkout path.

Google uses those records to calculate checkout totals and show policy information. A general feed can still miss fields needed for an agent-led purchase. Use our cross-platform feed checklist for the full audit.

If the product still needs evidence, start with our AI product research guide.

On my stores, I'd start with the return policy and product identifiers. Both connect the feed to what a customer sees.

Use the UCP preparation page as the final completeness check. It tests details that a clean diagnostics screen may not cover.

Some common dropshipping products fail before the technical work begins. Google excludes personalized goods, final-sale items, and preorders from this checkout path. Products with special shipping needs are also excluded. The same is true for recurring subscriptions and age-restricted products.

Compare your catalog with the current restriction list. Pass this check only when each product marked for UCP is supported and approved for free listings.

2. What a UCP profile and checkout endpoint require

Your developer must publish a UCP profile and working endpoints for creating, updating, and completing checkout. The profile normally sits at /.well-known/ucp. It tells Google which capabilities, payment handlers, public keys, and service URLs your store supports.

Google's Merchant Center integration guide tests the implementation in a sandbox. Your team provides separate credentials for test and production systems. The sandbox simulates each checkout action before Google validates the same features in production.

Checkout endpoints return facts that change during the purchase. They check inventory when Google asks, then match shipping and tax to the address. They must reject an unsupported destination clearly and send order updates after purchase.

I'd ask a developer to show the sandbox results because a readable profile proves discovery only. Use these acceptance records,

• Completed create, update, and checkout actions in the sandbox.
• Matching core results from the production test.
• Named owners for the profile, API keys, and webhooks.
• Named alert recipients for checkout, payment, and order failures.
• The current version, test URL, and last working endpoint.
• A rollback owner for failed releases.

A platform partner may build this layer for you. Keep its ownership and support contacts with those records.

If no partner supports Google's current flow, budget for custom work. A normal checkout app may not cover it.

Plan version changes before launch. Google recommends a separate test endpoint so live traffic stays on the working build.

3. What Google Pay requires from you and your processor

You need a Google Pay & Wallet Console merchant account and a processor that can handle Google Pay tokens. Google's payment guidance says the Google Pay button on your own site or app is optional for UCP.

Confirm the payment path with your processor before development starts,

• Create or reuse a merchant account for the UCP profile.
• Put the supported payment settings in the UCP profile.
• Prepare encryption and compliance records if you don't use a processor.

Google's current AI surfaces use PAN_ONLY for the allowed authentication method. The checkout flow ignores other methods listed in your profile. This value can change, so copy it from the live payment page when your developer configures the handler.

Require written processor confirmation and a successful sandbox payment before funding API work. If you process payments directly, include the added encryption and compliance work in the estimate.

Ask the processor for the gateway name and merchant ID. Confirm that the account works in both systems. Your developer also needs a support contact because Google can validate the handler while the processor rejects the payment.

Run one test with the same currency and country planned for launch. Save the transaction result with the profile. This gives the next developer a known working case instead of a settings screenshot.

Where UCP is available and stores can be blocked

Eligible products in the United States, Canada, and Australia can be in scope, while the integration hub is still rolling out in the United States and access remains selective. Google's Merchant Center help page names those three markets and says the feature is available to select merchants.

Google's current interest form describes a narrower account rollout. It says the U.S. integration hub is gradually becoming available, with Canada and Australia following later.

A valid product in a covered market may pass the feed checks. The account can still lack the UCP integration tab or approval.

Google's public UCP FAQ gives no promised approval time, application fee, or account-size threshold. That means I can't tell whether your store will be accepted. Prepare the account and submit the form while keeping technical work limited.

Match the next move to the account state,

• Apply when the integration tab is visible.
• Join the waitlist when the tab is missing.
• Keep prices, availability, returns, support, and identifiers current outside the present scope.

Google added cart, catalog access, and identity linking in March 2026, then changed the guide again in August. Scope only the capabilities shown in your live validation flow.

Fix feed and policy gaps now because they support normal listings too. Build checkout when Merchant Center provides the integration path. That order keeps development tied to an account Google can test.

FAQ

These answers cover the eligibility questions that the readiness check leaves open.

Do I need to be a large retailer to use Google UCP?

Google's public UCP requirements set no minimum retailer size. Its form asks about active offers, platform providers, and implementation resources, yet it gives no public pass mark or promise of acceptance. A small store faces the same product, policy, checkout, and payment checks as a larger retailer, and Google makes the final account decision.

Does UCP replace my Google Merchant Center feed?

Merchant Center supplies product, return, support, and eligibility records, while UCP adds the profile and transaction endpoints used during checkout. You need both parts for Google's purchase flow. Feed fixes can improve the data shoppers see before a UCP build is available, while endpoint work begins after the feed can support a live total and valid order.

What if my store isn't accepted into UCP yet?

Your account can keep using its regular Google listings while UCP access is pending. Keep the feed, return policy, and support details current, then start the integration when Google exposes the validation path. Record the application date in your readiness sheet and check for the integration tab before each development sprint, so a pending application doesn't become an open-ended project.

Is Google UCP free to join, and how long does approval take?

Google doesn't list an application fee or promise an approval time. Your costs may include platform support, developer work, payment processing, and security work, so ask each provider for its part of the estimate. Treat the application and build as separate commitments by completing feed and policy work first, then funding checkout after Google gives the account a test path.