Google's Universal Cart Picks Winners Before You Arrive

May 19. Google I/O. Universal Cart goes live with agentic checkout built in. No beta waitlist. No phased rollout announcement. The tool selects products, populates a cart, and initiates checkout—without the shopper browsing your PDP. If your catalog isn't structured to answer an agent's purchase criteria at query time, your SKU doesn't make the shortlist. That's the decision point your brand is already inside.

What the Agent Actually Evaluates

Agentic commerce tools don't scroll. They query. Google's Universal Cart is resolving purchase intent against structured data signals: price, availability, shipping SLA, return policy, and product attribute completeness. A missing size chart or an unformatted ingredient list isn't a minor gap anymore. It's a disqualification flag. The agent moves to the next eligible SKU. Your competitor gets the cart slot. You get no impression, no click, no conversion—and no visibility into why.

This is a different failure mode than losing a PPC auction. You can audit ad spend. You cannot easily audit where an agent declined to surface your product. That invisibility is the actual risk operators should price into their catalog roadmap right now.

The Catalog Gap Most Brands Are Sitting On

Pull your top 40 revenue-generating ASINs or SKUs. Run each one against six fields: structured product type taxonomy, machine-readable pricing with no PDF-locked promo layers, real-time inventory signal accessible via API, fulfillment SLA stated at the SKU level, return window in structured metadata, and at least one trust signal—rating count, certification, or verified seller status. Count how many pass all six. Top-decile operators in early agentic surface testing are reporting 70-plus percent pass rates on their core catalog. The median brand is closer to 31 percent. That gap is where market share moves.

Fulfillment SLA is the field most brands miss at SKU level. They state it at the brand or site level. Agents querying Universal Cart need it attached to the individual product. A hoodie that ships in 2 days and a wall mirror that ships in 9 days cannot carry the same metadata. The agent will either reject the ambiguous record or select a competitor who answered the question directly.

Your 72-Hour Operator Move

Don't audit your entire catalog this week. Triage by velocity. Identify the 15 SKUs that drove the highest unit sell-through in the last 30 days. These are your agentic commerce candidates—the products with enough demand signal that an AI purchasing agent is likely to encounter them. Get those 15 fully structured and cart-eligible before you touch anything else. This is triage logic, not perfectionism.

If your catalog lives inside a PIM, flag the Universal Cart eligibility criteria as a required field set—not a recommended one. If you're operating on SP-API feeds to retail partners, check whether your feed schema is pushing SKU-level fulfillment windows or defaulting to a brand-level placeholder. That placeholder is costing you slots on surfaces you're not even tracking yet.

One more thing. Pricing layers. If your promotional pricing lives in a separate system and doesn't resolve in real time against the API your products surface through, an agent may pull a stale price, create a checkout discrepancy, and abandon the cart. That's a landed cost problem masquerading as a tech problem. The fix is a pricing-to-feed sync with sub-hourly refresh on your top-velocity SKUs. Not glamorous. Entirely necessary.

Three Questions to Pressure-Test Your Cart Eligibility

Does your SKU-level data answer a purchase agent's criteria without requiring a human to interpret a PDF, navigate a FAQ, or click into a PDP? If a competitor's equivalent SKU passes all six structured fields and yours passes four, which one does the Universal Cart select—and do you have any visibility into that outcome today? When your pricing or inventory changes, how many hours does it take for that change to propagate into every surface an agent might query, and is that number under four?

Run the 15-SKU audit today. Fix the fulfillment SLA field first. Everything else is secondary.