Google Ads

Universal Commerce Protocol and Google Universal Cart for Online Stores

How Google's Universal Cart and the Universal Commerce Protocol work, how to choose between cart transfer and native checkout and what to fix in Merchant Center before Black Friday.

Key Takeaways

  • The universal commerce protocol lets Google's Universal Cart send a shopper's saved items to your cart or sell them with Google Pay inside AI Mode and Gemini.
  • Cart transfer needs a UCP profile and one create cart call, while native checkout adds 3 REST endpoints, order webhooks and Google Pay setup.
  • Feed data decides eligibility, so return policies, support contacts and variant attributes come before any integration work.
  • You stay the merchant of record on both paths, and Google says native checkout doesn't change how your products rank.
On This Page
  1. Google Universal Cart for Shoppers
  2. The Universal Commerce Protocol Behind Checkout
  3. Cart Transfer vs Native Checkout
  4. Choosing Between the 2 Paths
  5. Merchant Center Checklist for Google UCP
  6. Products That Can't Use Native Checkout
  7. Setup Steps in Merchant Center
  8. Small Shopify and WooCommerce Stores
  9. Google Agentic Checkout in Ads and Other Countries
  10. Pre Black Friday Checklist
  11. Frequently Asked Questions
  12. Sources

The universal commerce protocol (UCP) is the open standard Google uses to let shoppers buy from your store inside Search and Gemini. It powers checkout in Google Universal Cart, which launched in the U.S. on October 15, 2026. Merchants join in 1 of 2 ways, by sending carts to their own site (cart transfer) or by letting shoppers pay on Google with Google Pay (native checkout), and both depend on clean Merchant Center data. This article explains what each path requires, how to choose between them and what a small Shopify or WooCommerce store should fix before Black Friday.

Google Universal Cart for Shoppers

Google launched Universal Cart in the U.S. on October 15, 2026 across Google Search, AI Mode and the Gemini app, after previewing it at I/O in May (TechCrunch covered the launch). A shopper can save products from different retailers anywhere on Google, and the cart keeps their progress so they can come back later and pick up where they stopped.

The cart sends price drop and back in stock alerts, shows relevant promo codes and, through Google Wallet, suggests which card to pay with based on card perks. Product details come from the Shopping Graph, which Google says holds more than 60 billion listings.

At the end, the shopper either pays with Google Pay in a few taps at participating stores or sends the items to the merchant's own cart to finish on the merchant's site. Google's launch post names Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair among the retailers, along with many Shopify merchants. Either way, the retailer stays the merchant of record and sends the order confirmation and customer support itself. A shopper may compare your product with competitors inside Gemini and buy without ever landing on your product page, so your feed data does the selling.

The Universal Commerce Protocol Behind Checkout

The universal commerce protocol (UCP) is the open standard that lets Google's AI surfaces talk to a store's systems. Google says checkout in Universal Cart is powered by UCP, and TechCrunch describes it as a standard Google introduced earlier in 2026 so AI agents and retailers can work together, including at checkout.

A store declares its UCP capabilities in a profile file at /.well-known/ucp on its own domain, and Google reads it to learn where to send requests. The 2 capabilities that matter for Universal Cart today are cart transfer and native checkout, and a store can support one or both. Google lists identity linking as a third option that is still coming soon.

Turning on UCP doesn't change how your products rank. Google's UCP FAQ says choosing the native integration doesn't influence how offers rank in product listings. What changes is the action on your listing, either a buy option or a transfer to your cart.

Cart Transfer vs Native Checkout

Cart transfer Native checkout
Where the shopper paysOn your websiteOn Google, with Google Pay
API workA one way create cart call to your site3 core REST endpoints plus order webhooks to Google
UCP profile/.well-known/ucp declaring dev.ucp.shopping.cart, on version 2026-04-08 or later/.well-known/ucp declaring native checkout
Payments setupNone beyond your own checkoutGoogle Pay & Wallet Console account and a payment provider that supports Google Pay
Feed attributeIncluded by default, set cart_eligibility to FALSE to excludenative_commerce(checkout_eligibility) must be TRUE
Product limitsProducts approved for free listingsExcludes subscriptions, personalized and final sale items and more
Your own checkout pageUsed, with your usual upsellsNot used, since payment happens on Google

Cart transfer moves the cart a shopper built on Google to your site in one direction. Google sends it through a create cart call and doesn't update, delete or sync it afterward. It requires UCP version 2026-04-08, since the Cart API only exists from that version on, and a profile at /.well-known/ucp that declares the dev.ucp.shopping.cart capability. It doesn't need payment handlers or order lifecycle work. Cart eligibility is opt out, so once the capability is in your profile, products approved for free listings are included.

Native checkout keeps the whole purchase inside AI Mode or Gemini. Products need native_commerce(checkout_eligibility) set to TRUE, and a missing or FALSE value makes them ineligible. If you run both paths, use the combined format native_commerce(checkout_eligibility:cart_eligibility), such as TRUE:FALSE for a product you want sold on Google but kept out of cart transfer. Google replaces the whole native_commerce group on every upload, so any flag you leave out is erased. Send both values every time.

On payments, the Merchant Center Help Center says you need a Google Pay & Wallet Console account and a payment provider that works with the Google Pay API. Right now only standard card numbers (FPANs) stored in Google Wallet are accepted. You don't need to add a Google Pay button to your own checkout pages.

Choosing Between the 2 Paths

Start with cart transfer if any of these describe your store.

  • Your average order relies on add-ons, bundles or a post-purchase offer that your own checkout shows.
  • You don't have a developer who can build and maintain checkout endpoints and order webhooks.
  • A large share of your catalog falls into the product types native checkout excludes.
  • You want to test whether Universal Cart sends any orders before committing more engineering time.

Plan for native checkout, often on top of cart transfer, if these fit better.

  • Your best sellers are simple, single items where the product page does little work after the shopper decides.
  • Your payment provider already supports Google Pay, so the payments setup is mostly paperwork.
  • Your traffic is mobile heavy and you lose shoppers between cart and payment.

You can also run both and set each product's combined flag to suit it, then compare orders from each path for a few weeks. Google's FAQ notes that you keep ownership of customer relationships and data as merchant of record, while Google keeps standard order data shown in the shopper's My orders page until the shopper asks for it to be deleted. Read the UCP Program Addendum before you agree to it, since native checkout requires it.

Merchant Center Checklist for Google UCP

Google's Merchant Center guide for UCP lists the account and product data that has to be in place before integration work starts.

  1. Merchant Center account in good standing with products approved for free listings
  2. Return policy set in Merchant Center with the return cost, the return window and a link to the full policy (advanced accounts set it per sub-account)
  3. At least one customer support contact (website, email or phone), which powers the Contact Merchant link on Google's order confirmation
  4. variant_option submitted with item_group_id and item_group_title for every product that has sizes or colors
  5. Consumer notices added where a warning is required, such as Prop 65, using notice_type and notice_message
  6. Feed id matches the product ID your checkout API expects, or merchant_item_id maps the two
  7. UCP attributes sent through a supplemental data source or the Merchant API so your primary feed stays untouched
  8. Every native_commerce upload includes both flags, since partial updates erase the missing one
  9. Excluded product types set to FALSE for checkout

If a product shows in Universal Cart without a buy option, check its variant data first. The Content API is deprecated, so new attribute work belongs in the Merchant API.

Products That Can't Use Native Checkout

Google excludes several product types from native checkout. They can still appear on Google, and cart transfer can send them to your site, but the buy button won't show for them.

Group Excluded items
Recurring and financedSubscriptions and installments
Custom or special fulfillmentPersonalized goods, items that aren't new, final sale items, pre-orders, bundled services, special shipping, gifting and in-store activation
Policy and safetyAge restricted items and prohibited content
Digital and servicesServices, rentals, virtual items and products that need software installed before purchase

Setup Steps in Merchant Center

The UCP integration hub sits under Settings > UCP integration in Merchant Center. Google says the hub is gradually rolling out in the United States, with Australia and Canada to follow early next year.

  1. Build the UCP endpoints and profile using Google's developer guide, or confirm your platform or app has done it for you.
  2. Test in the sandbox. For cart transfer you simulate create cart. For native checkout you simulate creating, updating and completing a checkout. Sandbox and production use separate API keys.
  3. Validate in production. Pick your capabilities, add your UCP profile URL (the capabilities it declares must exactly match the ones you picked) and complete the checklist for each one.
  4. For native checkout, validate the 3 core REST endpoints for session creation, updates and completion, set up order webhooks to Google and agree to the UCP Program Addendum.
  5. Wait for Google Support to review the integration and tell you whether the account is live or needs fixes.

To stop, remove the UCP card under Add-ons in Merchant Center. You can turn it back on later.

The Help Center page frames availability differently. It says the checkout button can appear on eligible listings in AI Mode and Gemini for products in the U.S., Canada and Australia, through a phased early access program open to select merchants, with an interest form to request a place.

Small Shopify and WooCommerce Stores

Google's launch post names many Shopify merchants among the stores in Universal Cart, but neither the post nor Google's merchant documentation explains how a Shopify or WooCommerce store turns UCP on. Before you plan any custom work, check your platform's admin, its Google sales channel or app and your payment provider for UCP support. If they offer it, most of the profile and endpoint work is done for you, and your job is the Merchant Center data.

For a small store, fix variant groups, return policy details and support contacts first, since those decide eligibility on either path. Then choose a path by catalog. A store selling simple single items with a Google Pay ready payment provider is a good fit for native checkout. A store whose margin depends on bundles, quantity breaks or a checkout upsell should start with cart transfer and keep its own checkout in charge.

Watch the FAQ's point on geography. Google says it can't guarantee requests come from a specific country, so it recommends authenticating requests with mTLS, OAuth 2.0 bearer tokens or signatures instead of blocking by IP. If your store only ships domestically, control that with shipping rules and request authentication and leave IP blocking off, or legitimate Google requests may fail.

Shopify's Fall '26 Edition from October 28, 2026 adds Shop Pay checkout inside personal AI agents (starting with Muse from Meta, Claude Duet and Instinct) and lets merchants connect Shopify to 9 AI agents, including ChatGPT, Microsoft Copilot and Google Gemini, to manage products, inventory and orders from the chat. It also adds an admin view that shows whether your store is eligible for Shopify Catalog, where agents such as ChatGPT and Copilot get product information, and a knowledge base under Sales channels > Agentic where you review the store facts agents receive before they're published.

For organic visibility in AI answers, see our article on AI Overviews and AI Mode, and for OpenAI's paid option see ChatGPT ads.

Google Agentic Checkout in Ads and Other Countries

At I/O and Google Marketing Live in May, Google described what comes next for UCP. Brands with UCP integrations will be able to run Direct Offers with exclusive promotions that shoppers can buy on the spot. Shopping ads on YouTube and Demand Gen campaigns with product feeds will also let people buy on the spot when the brand has a UCP integration. Google gave no dates beyond soon.

On countries, the May post said UCP checkout would reach Canada and Australia in the coming months and the U.K. later. Google's developer page now says early next year for Australia and Canada. Treat the developer page as the more recent of the 2.

Your Merchant Center data now feeds both Shopping campaigns and agentic checkout, so the same feed fixes help both. Our Google Ads updates page tracks these launches as they reach accounts, and our Google Ads management team can check your Shopping and Performance Max setup against them.

Pre Black Friday Checklist

Black Friday falls on November 27, 2026, which leaves a few weeks. Google Support reviews each integration before it goes live, so most stores should aim to have their feed and policies ready this season and treat full native checkout as a 2027 project unless they already have early access.

  1. Check Merchant Center diagnostics and fix disapproved products in your top 50 sellers
  2. Confirm sale prices and promotion dates in the feed match your site exactly
  3. Add holiday return windows to your Merchant Center return policy if they differ from the standard window
  4. Fill missing variant data on products sold in sizes or colors
  5. Mark gift sets, pre-orders and personalized items FALSE for checkout if you're live with native checkout
  6. Freeze changes to the native_commerce group for the holiday week, and if you must change it, send both flags
  7. Test a full cart transfer or checkout yourself from AI Mode before November 20
  8. Brief your support team on orders placed through Google, since shoppers reach you through the Contact Merchant link on Google's order confirmation
  9. Confirm your order webhooks send every order update to Google
  10. Submit the Help Center interest form now if you want native checkout early next year

Ecommerce brands that want help with the feed, Shopping campaigns and holiday budgets can see our ecommerce and DTC marketing work.

Frequently Asked Questions

Does Google charge merchants a fee for UCP checkout?

Google's UCP documentation and launch posts don't list a fee for cart transfer or native checkout. The terms you accept for native checkout are in the UCP Program Addendum, so read it before you agree, and ask your payment provider how it charges for Google Pay orders.

Can I see orders and analytics from Universal Cart in Merchant Center?

The UCP integration page in Merchant Center has an Analytics tab next to Overview. Native checkout orders also reach your own systems through the endpoints and webhooks you build, so you can report on them alongside the rest of your sales.

Is Google Universal Cart available outside the U.S.?

The shopper cart launched in the U.S. only. Google's developer page says the Merchant Center integration hub reaches Australia and Canada early next year, the Help Center lists the U.S., Canada and Australia for its early access checkout program and Google said the U.K. comes later.

Do I need a Google Pay button on my own website?

No. The Merchant Center Help Center says native checkout doesn't require a Google Pay button on your own checkout pages. You do need a Google Pay & Wallet Console account and a payment provider set up for the Google Pay API.

Sources

  1. Google Universal Cart Launch in the US blog.google
  2. TechCrunch on the Universal Cart Launch techcrunch.com
  3. Google UCP Cart Transfer Overview developers.google.com
  4. Google Merchant Center Setup for UCP developers.google.com
  5. Google UCP Integration in Merchant Center developers.google.com
  6. Google Merchant Center Help on UCP Checkout support.google.com
  7. Google UCP FAQ developers.google.com
  8. Google Shopping Updates From Google Marketing Live 2026 blog.google
  9. Shopify News, Fall '26 Edition shopify.com
Global Group One Team

We manage Google Shopping, Performance Max and Merchant Center feeds for ecommerce brands.

Sell More From Google This Holiday Season

Request a free proposal and we'll plan your feed fixes, Shopping campaigns and UCP path around your catalog.

CallRequest a Free Proposal