What happened
On July 29, Google Merchant Center Help published the merchant side of the Universal Commerce Protocol — an open standard for agentic commerce. A shopper sees your product listing inside AI Mode in Search or in Gemini, taps Buy, and completes the purchase right there through Google Pay, using the card and shipping details already saved to their Google Wallet. The whole flow stays inside Google's secure Pay experience, running on the standard funding card numbers (FPANs) users have stored.
The Buy button appears only on listings carrying the native_commerce(checkout_eligibility) product attribute — a per-product opt-in, not an account-wide switch. And you remain the seller of record: Google handles the payment credentials, but the order, the customer, and the fulfillment are yours.
Getting in takes real paperwork. Onboarding runs through verifying technical requirements, submitting an interest form, creating a Google Pay & Wallet Console account, and implementing against the developer docs — with Merchant Center product data kept current underneath it all. Eligibility currently covers products in the US, Canada, and Australia, and participation is limited to selected merchants while the early-access program rolls out in phases.
Why this matters
Per-product opt-in lowers the cost of finding out. You can put agentic checkout on a controlled slice of the catalog — proven sellers, simple variants, stable pricing — and watch margin, return rates, and support load before exposing anything else. Compare that to marketplace launches where the choice is all-in or out. Google built the pilot program into the spec.
Seller of record stays with you. This is not a marketplace grab; the customer relationship, the order data, and the post-purchase experience remain yours. That makes UCP closer to a new payment-enabled placement than a new intermediary — a meaningfully better deal than most agentic-commerce arrangements sketched so far.
For BigCommerce merchants, the path runs straight through your feed. The attribute lives on the product listing, so eligibility is decided by the same Merchant Center feed you already maintain for Shopping ads, fed through your BigCommerce catalog or Feedonomics. Every hour spent on feed hygiene over the past two years now also counts here. Early access is selective and phased, so filing paperwork guarantees a queue position, not a launch date.
What to do about it
File the interest form this week
If you sell into the US, Canada, or Australia, submit Google's UCP interest form now. Phased early-access programs reward early paperwork, and the form commits you to nothing — you decide later which products, if any, get the attribute.
Pick your pilot slice on paper
Choose the products you'd flag with native_commerce(checkout_eligibility) first: simple variant structures, stable pricing, healthy margins, spotless feed data. Skip anything with complex options, frequent price changes, or shipping exceptions. Write the list now so the technical work has a target when access opens.
Get Merchant Center airtight first
The Buy button sits on top of your product data, so disapprovals, mismatched prices, and stale availability disqualify products before eligibility is even a question. Clear your Merchant Center diagnostics for the pilot SKUs — identifiers, images, availability accuracy — before you touch the attribute.
Stand up the Google Pay & Wallet Console account early
It's a separate account from Merchant Center and a hard onboarding dependency. Create it now and sort out who in your org owns it, so an admin formality isn't the thing holding your queue position when Google comes calling.