catalog
Agent-readable product data
Product identity, variants, availability, price, shipping, returns, loyalty offers, and merchant-of-record facts need to be consistent across feed, page, and checkout.
tate@programs
~/services/universal-cart-readiness
catalog / cart / checkout / receipt
Universal Cart readiness / May 2026
Before Google's Universal Cart reaches your channel, prove your checkout is agent-ready.
Google introduced Universal Cart at I/O 2026 as the next layer of agentic shopping across Search, Gemini, YouTube, and Gmail. Retailers and commerce platforms now need evidence that catalogs, carts, payment delegation, checkout handoff, and receipts work when the buyer is represented by an agent.
- entry
- $750
- fit
- retailers
- mode
- private first
Why now
Universal Cart turns agentic commerce from abstract protocol work into a retailer deadline.
Google says Universal Cart will roll out across Search and Gemini in the U.S. this summer, with YouTube and Gmail to follow. That compresses the timeline for retailers, Shopify teams, agencies, and checkout providers: product data, offers, loyalty, payment perks, merchant-of-record handling, and order proof all need to survive a buyer path that may not start on the merchant site.
cart
Cart and handoff behavior
When an agent builds or transfers a cart, the merchant should preserve item identity, price freshness, stock state, discounts, and checkout intent without silent drift.
ap2
Payment boundaries
Agent-initiated purchases need explicit user authority, amount limits, recipient checks, payment method constraints, retry rules, and a clear failure story.
proof
Receipt and reconciliation
The launch packet should show exactly what the agent, buyer, merchant, and partner can prove after checkout: order id, amount, payment status, fulfillment state, and refund path.
Proof base
The same checks have already moved public agent-payment surfaces.
Universal Cart is commerce-specific, but the reliability questions are the same ones showing up in live x402, MCP, and paid-agent work: discovery, payment challenge readability, retry behavior, spend limits, and proof after the action finishes.
merged
Paid API and MCP fixes
Recent public loops include Apify MCP x402 metadata, DCP spend accounting, Boson x402B paywall behavior, and Nansen pay-skills review. The pattern is repeatable: find the launch blocker, prove it safely, then reduce it to a patch order.
private first
Agency-safe delivery
The paid packet stays private unless both sides approve public wording. Agencies can use it as outside proof for a client, a launch-readiness appendix, or a white-label engineering handoff.
The $750 map
One private readiness packet for the surface that will matter first.
Best fit: Shopify Plus agencies, marketplace teams, checkout orchestration platforms, retail brands, catalog infrastructure, wallet/payment providers, and UCP/AP2 partner pilots.
Readiness map
$750One public or authorized surface. Includes catalog map, checkout handoff notes, payment-boundary review, receipt evidence table, failure/retry notes, and ranked patch order.
Scope mapLaunch sprint
$2.5k+Authorized implementation help after the map: feed proof, machine-readable checkout docs, CORS/API readiness, receipt shape, partner packet, or demo hardening.
Scope sprintMonitor
$4.5k/moRecurring route, catalog, checkout, and receipt checks for teams with changing product feeds, multiple brands, live partners, or agent-shopping commitments.
Scope monitorReadiness questions
What a partner, client, or merchant reviewer will ask.
01
What can the agent buy?
Exact products, variants, bundles, subscriptions, exclusions, regions, and cart constraints are visible before checkout.
02
What can go wrong?
Out-of-stock, stale price, coupon mismatch, loyalty conflict, payment failure, duplicate purchase, return, and refund states have predictable messages.
03
Who authorized payment?
The proof separates shopper intent, agent action, merchant acceptance, payment method, limits, and any human approval step.
04
What can be proven later?
Order, payment, receipt, fulfillment, cancellation, and refund evidence can be traced without relying on screenshots or ambiguous event logs.
Start with one commerce surface