Google Universal Cart: the merchant-readiness checklist

Google Universal Cart launched at I/O 2026 this morning — a cross-merchant shopping cart that spans Search, Gemini, YouTube, and Gmail, letting shoppers add items from multiple retailers into a single persistent cart backed by the Shopping Graph's 60 billion product listings and more than a billion shopping interactions per day.

The consumer story is deal tracking, price-history insights, and restock alerts powered by Gemini models. The merchant story is simpler and more urgent: a single Merchant Center attribute — native_commerce — determines whether your products display the Buy button. Miss it and you are invisible to the cart. Nail it and you gain access to a checkout surface that Google says will expand across four of its highest-traffic properties starting this summer.

This guide covers exactly what launched today, how Universal Cart relates to UCP and AP2 (they are three distinct layers — this distinction matters for your engineering roadmap), the 13-item merchant readiness checklist, the 2026 product data specification update, and what is coming next with AP2 and Gemini Spark. Everything is anchored to Google's official announcements, the Merchant Center help center, and the UCP developer docs — retrieved May 19, 2026.

Vidhya Srinivasan, VP/GM Ads & Commerce at Google, announced Universal Cart during the I/O 2026 Day 1 keynote on May 19, 2026. The product is a cross-merchant shopping cart that persists across Google properties — Search, the Gemini app, YouTube, and Gmail — and lets shoppers aggregate items from multiple retailers into a single session.

The cart runs on Gemini models, which means it can reason across SKUs. Google cited an example of flagging PC component incompatibilities across retailers and proactively suggesting alternatives. Background deal monitoring, price-history insights, and restock alerts are core consumer-facing features. Srinivasan was explicit about the merchant relationship: Google facilitates the checkout surface; the merchant retains the seller-of-record status and controls pricing and fulfillment.

The rollout sequence matters for planning: Search and the Gemini app launch first in the US this summer. YouTube and Gmail expand the surface later. Canada and Australia are included in the initial UCP checkout rollout. UK follows in a later wave. Merchants in ineligible markets should still begin feed and UCP profile work now — the qualification pipeline takes time.

The Google Wallet integration is worth calling out separately: the cart understands payment perks, loyalty programs, and merchant offers, and surfaces savings automatically. For merchants who have invested in loyalty programs, this is an incremental acquisition channel for loyalty sign-ups — provided the loyalty_program_label and loyalty_tier_label attributes are set in the feed (see Section 07 below).

Coverage of today's announcement conflates three separate primitives. Getting them right matters for your engineering roadmap — each has a different launch status, implementation owner, and compliance deadline.

Universal Commerce Protocol (UCP) is the open protocol layer — co-developed by Google with retail and payments leaders, launched as an open standard in January 2026, and expanded in March 2026 with multi-item carts, real-time catalog queries, and identity linking. Universal Cart is the consumer-facing product Google built on top of UCP plus Google Wallet — announced today. Agent Payments Protocol (AP2) is the autonomous-payment primitive — v0.2.0 shipped in April 2026 with “Human Not Present” mandate handling, and it ships with Gemini Spark “in coming months,” not in Universal Cart at launch.

The practical implication: everything in this guide from Sections 03-08 is what you need to qualify for Universal Cart today. AP2 readiness (Section 09) is a forward-looking item for Q3 2026 and beyond. Do not let the AP2 backlog block your Universal Cart go-live — they are independent implementation tracks. For the full protocol-ecosystem map, see our deep dive on UCP's March 2026 multi-item cart expansion.

Google Merchant Center's help center is unambiguous on this point. The exact wording, retrieved May 19, 2026: “Only product listings using the native_commerceproduct attribute will display the ‘Buy’ button for this checkout experience.” No other feed completeness metric, Shopping Graph presence, or Performance Max spend level compensates for the absence of this attribute. It is a hard gate.

The native_commerceattribute is set at the SKU level in the Merchant Center product feed. Merchants eligible to participate must submit a UCP integration interest form, have an active Merchant Center account in a supported market (US, CA, AU), and have their products flagged as eligible for checkout. Products must also meet the standard checkout eligibility requirements — which include a return policy declared in Merchant Center, a Google Pay & Wallet Console account configured, and robust product data meeting the 2026 spec (see Section 07).

From a catalog-operations standpoint, the deployment sequence is: confirm market eligibility, update the feed to include native_commerce on each checkout-eligible SKU, publish the UCP business profile at /.well-known/ucp, configure Google Pay, then submit the integration interest form. Skipping any step delays the Buy button appearing on eligible listings.

Universal Cart launched with eight named merchant partners. Six are established retailers with independent Merchant Center footprints; two are Shopify merchants (Fenty and Steve Madden), which highlights that Shopify's UCP stack — which Shopify merchants inherit automatically — was already production-ready at launch. The partner set spans mass-market, specialty beauty, home goods, and fashion, giving the cart immediate catalog depth across the highest-intent shopping categories on Google Search.

The Shopify signal deserves emphasis. If your store runs on Shopify, the UCP profile and transport binding are handled at the platform level. Your implementation work focuses on the Merchant Center side: the native_commerceattribute, feed data quality, and Google Pay & Wallet Console configuration. Read our Shopify agentic commerce and UCP guide for the Shopify-specific checklist.

Universal Commerce Protocol uses a layered architecture inspired by TCP/IP. A Services layer is published at /.well-known/ucp as a JSON manifest — this is the business profile that declares server capabilities, transport bindings (REST API or MCP — Model Context Protocol), and payment-handler configurations. A Capabilities layer defines what the merchant supports: checkout, catalog queries, order management, and identity linking. An Extensions framework allows vertical-specific schemas — which is how hotel booking and food delivery will be added in the coming months.

The UCP profile is a publicly-hosted document. Any agent — not just Google's — can discover your capabilities via the well-known endpoint. This is the open-protocol design intent: the manifest is not proprietary to Google, it is a capability advertisement readable by any UCP-compliant system. Merchants who ship a robust UCP profile today benefit from Universal Cart and from any future UCP-compliant agent that enters the market.

UCP also supports real-time inventory and price queries (sub-500ms response times are recommended for the Catalog Capability), restock webhooks for the order-lifecycle extension, and identity linking for loyalty program recognition. The developer reference is at developers.google.com/merchant/ucp. The architecture deep-dive is at Google Developers blog.

No competitor coverage assembles all 13 items with owner attribution and priority tiering. This is the single artifact a merchant ops lead can hand to engineering this week. Items are grouped into Must (launch blocker), Should (strongly recommended for full feature access), and Nice (quality-of-life / future-proofing). Work them in sequence — each group depends on the one before.

The sequencing is intentional. A merchant that ships Items 1-6 is fully qualified for Universal Cart at launch — the Buy button will display, the checkout flow will work, and the cart will carry the listing across Search and Gemini. Items 7-10 unlock the deal-tracking and restock-alert consumer features, which drive repeat cart engagement. Items 11-13 are forward-looking. AP2 (Item 13) is the most commonly conflated with Day 1 requirements — it is not. Plan it for when Spark expands, not now.

For the broader storefront preparation playbook beyond Universal Cart, our agentic commerce SEO guide covers the full stack — schema markup, structured data, and how AI shopping agents discover and rank products.

The 2026 Merchant Center product data specification update adds five new attributes and raises the minimum image resolution. Warnings were issued April 14, 2026; enforcement begins January 31, 2027. The Universal Cart launch makes these attributes immediately relevant — the Gemini-powered cart can surface loyalty perks and delivery windows only if the underlying feed data exists.

The image resolution change is the most operationally disruptive for large catalogs. 500×500 px is the new hard floor; 1,500×1,500 px is the recommended target for AI surfaces where the Gemini cart may render larger product imagery. If your catalog has legacy imagery at 100-499 px, the January 31, 2027 enforcement date gives you a runway — but given the Universal Cart launch today, beginning the image refresh now means your products display correctly on the new surface from Day 1.

Beyond the new attributes, the 2026 spec reaffirms minimum product title length (≥30 characters) and description length (≥500 characters). According to Dataiads' UCP attribute analysis, adding a promotional price attribute is reportedly associated with +7.6% CTR and +12.3% conversion in their dataset — set the sale_price attribute whenever a promotion is live.

Our eCommerce strategy engagements include a full Merchant Center feed audit — including native_commerce attribute setup, image resolution sweeps, and the 2026 spec attribute rollout — as part of the Universal Cart readiness sprint.

Universal Cart is powered by the Shopping Graph — Google's real-time product knowledge graph that according to Search Engine Land now contains 60 billion product listings, up from 50 billion earlier in 2026. Google also reports more than a billion shopping interactions per day. These figures matter for merchant strategy because they frame the competitive surface: Universal Cart is not a new destination, it is a checkout layer added on top of a search-intent graph that already dominates product discovery at scale.

The practical implication is that Shopping Graph data quality is a Universal Cart ranking input. A listing with complete structured data — GTIN, MPN, brand, isCompatibleWithfor variant relationships, and the 2026 spec attributes — is more likely to be surfaced by the Gemini cart's reasoning layer than an equivalent listing with incomplete data. The cart can flag product incompatibilities across retailers precisely because the graph has structured compatibility data. Merchants who invest in feed quality now benefit from Gemini's reasoning about their products.

Two new Merchant Center tools launched alongside Universal Cart and are worth adding to your analytics stack immediately.

AI Performance Insights is a new Merchant Center feature that lets retailers see their brand visibility across AI surfaces compared to competitors. Rolling out to AU, CA, IN, NZ, and US. This is the first tool that gives merchants direct visibility into how their products perform specifically on Gemini and AI Mode surfaces — previously unmeasurable from the Merchant Center UI.

Ask Advisor is a Merchant Center AI collaborator that completes tasks and surfaces insights using Google Ads and Analytics data. It operates conversationally within Merchant Center, which means merchants can ask it to diagnose feed issues, surface underperforming SKUs, and recommend attribute improvements without leaving the Merchant Center workflow.

Together, these tools close the feedback loop that has historically made Shopping Graph optimization opaque. For a broader view of how AI surfaces are reshaping organic and paid search visibility, see our analysis of AI Mode in Google Search — the same AI Mode surface that hosts Universal Cart for most Search users.

Three forward-looking tracks are confirmed from today's announcements. Each has a different timeframe and different implementation implications.

AP2 with Gemini Spark.Agent Payments Protocol version 0.2.0 shipped in April 2026, introducing “Human Not Present” mandate handling for autonomous agent purchases of time-sensitive items. AP2 has been donated to the FIDO Alliance for industry standardization and has a partner roster exceeding 60 organizations, including PayPal, Mastercard, and American Express. AP2 rolls out first with Gemini Spark “in coming months.” For merchants, AP2 readiness means implementing mandate handling and maintaining an audit trail for autonomous purchases — but this is not a Universal Cart prerequisite today. Plan it for Q3 2026 when Spark expands. Our post on Gemini Spark as an always-on personal agent covers the AP2 integration in detail.

UCP expansion to hotels and food delivery.Google confirmed that UCP's Extensions framework will expand to hotel booking and local food delivery soon. For merchants in adjacent verticals — hospitality tech, restaurant tech, and delivery aggregators — the architectural work is the same: publish a /.well-known/ucp profile, declare the relevant capability extensions, and configure payment handling. The protocol is designed to be vertical-agnostic.

UK rollout and broader geographic expansion. UK is confirmed as a planned market with no announced date. Merchants with UK catalogs should begin feed and UCP profile work now so that they can activate quickly when the market opens. The qualification pipeline — Merchant Center review, UCP integration interest form, Google Pay configuration — takes weeks, not days.

The biggest-picture framing is competitive context. Universal Cart is Google's consumer-facing answer to ChatGPT's in-product shopping rollout. The two approaches differ meaningfully: Universal Cart keeps the merchant as the seller of record and uses a Google Pay checkout surface; ChatGPT Instant Checkout uses a retailer-redirect flow that keeps OpenAI even further out of the merchant relationship. Both are accelerating the shift to AI-assisted and eventually autonomous commerce — and merchants who invest in structured product data and UCP compliance now benefit from both ecosystems. For the full I/O 2026 context, see our complete I/O 2026 AI announcement guide.