Google's Buy button in AI Mode and Gemini is not a setting you switch on. It shows only on listings that carry the native_commerce attribute, from merchants Google has selected, after a technical integration. Google announced the Universal Commerce Protocol (UCP) on 11 January 2026 with five co-developers (Shopify, Etsy, Wayfair, Target and Walmart) and more than 20 endorsers. Since then the checkout has opened slowly and only to selected merchants.
This guide is for e-commerce teams and agencies who are deciding whether to fill in Google's UCP interest form now or later. It gives you a 10-point scorecard, scored 0 to 2 per item, built only from Google's own Merchant Center and developer documentation. By the end you will know your score, which gaps block you, and the exact feed values to fix first.
What UCP checkout needs from your product feed
UCP checkout lets eligible merchants show a checkout button on product listings in AI Mode in Google Search and on Gemini. Shoppers pay with Google Pay, and you stay the seller of record (Google Merchant Center Help). Merchant Center is still where the product data lives (see our Google Merchant Center feed setup page for the basics). The checkout itself runs against your own APIs.
So readiness has two layers. The feed layer covers the native_commerce attribute, ID mapping, return policy, support contact and consumer notices. The backend layer covers a UCP profile, checkout APIs and a payment provider that accepts Google Pay tokens. A feed tool can fix the first layer but not the second, so the scorecard covers both.
Status as of November 2026: Google's help page covers products eligible in the United States, Canada and Australia, with checkout open to select merchants only (source). The onboarding page says the US is rolling out gradually and Australia and Canada follow "next year" (source), which PPC Land reported on 7 October 2026 as a slip into 2027 (source).
The UCP checkout readiness scorecard
Score each item 0, 1 or 2. Items marked gate must score 2, or the total does not matter.
| # | Item | 2 points | 1 point | 0 points |
|---|---|---|---|---|
| 1 | Account standing (gate) | Account in good standing, products approved for free listings | Approved, with open account-level warnings | Suspended or no free listings |
| 2 | Market (gate) | Products eligible in the US, and you can accept the US checkout terms | Canada or Australia only (wait for onboarding) | Other markets only |
| 3 | native_commerce syntax | Both flags sent on every update | Only the legacy single flag | Attribute missing |
| 4 | Restricted product logic | Rule sets checkout off for every restricted type | Manual exclusions only | No exclusions |
| 5 | ID mapping | id matches checkout API, or merchant_item_id set | Matches for most SKUs | Not checked |
| 6 | Return policy | Cost, window and policy link, per sub-account | Policy set, a field missing | No return policy |
| 7 | Customer support info | URL, email or phone in Merchant Center | On site only | None |
| 8 | consumer_notice | Sent wherever a warning applies | Partly covered | Warnings exist but are not sent |
| 9 | Price and stock freshness | API or supplemental price and inventory updates | Scheduled feed, prices rarely change | Daily feed, prices change intraday |
| 10 | Checkout backend | UCP profile, checkout API, PSP accepts Google Pay tokens | In development | Not started |
How to read the total: 17 to 20 with both gates at 2 means submit the interest form now. 12 to 16 means fix the feed items first. Below 12, or any gate under 2, means the backend or market is the blocker, not the feed.
Items 1 and 2: the two gates
Google's Merchant Center implementation guide asks for an account in good standing with approved products for free listings (source). If free listings are off or the account carries a misrepresentation warning, stop here and fix that first.
The market gate is stricter than it looks. The Universal Commerce Protocol Checkout Terms of Service state that they apply to the United States only (source). For Turkish and Gulf brands that already ship to the US with a US-targeted feed, the feed side can qualify. But as seller of record, your return cost, return window and support contact must work for a US shopper. A Turkish-language returns page fails items 6 and 7 even when every attribute is valid.
Item 3: writing the native_commerce attribute correctly
The attribute is a group with two sub-attributes, separated by a colon (source):
checkout_eligibilityis a boolean. Missing orFALSEmeans the product is not eligible for checkout. It defaults toFALSE.cart_eligibilityis opt-out. Omitted orTRUEkeeps the product eligible for cart. Products in cart also need thedev.ucp.shopping.cartcapability in your UCP profile.
In a text feed the header is exactly native_commerce(checkout_eligibility:cart_eligibility) and a value looks like TRUE:TRUE or FALSE:TRUE. Google's XML example prints the checkout flag as <g:checkout_eligibility>TRUE</g:checkout_eligibility>.
The detail that is easiest to miss: the group does not support incremental updates. If a supplemental feed sends only the checkout flag, the cart flag is cleared. Every update has to carry every flag you use. If you set this attribute in more than one place, such as the primary feed and a supplemental source, decide which one owns it and remove it from the other. A single supplementary feed that owns all UCP attributes is the simplest way to keep the flags together.
Older setups that already send a plain native_commerce value still work. Google keeps it as an alias for checkout eligibility. That earns 1 point, not 2, because you cannot control cart eligibility with it.
Item 4: switching checkout off for restricted products
Google lists product types that must have checkout_eligibility empty or FALSE (source): subscriptions and installment plans; personalized, non-new or final-sale items; pre-orders; items with bundled services or special shipping; gifting and in-store activation items; age-restricted items and prohibited content; services, rentals, virtual items and goods that need software installed.
Do not do this by hand. Write one rule that defaults to TRUE and turns checkout off when any signal is present. A worked example from a mixed electronics and home catalog:
| id | availability | condition | signal | native_commerce(checkout_eligibility:cart_eligibility) |
|---|---|---|---|---|
KB-1042 | in_stock | new | none | TRUE:TRUE |
KB-2210 | preorder | new | pre-order | FALSE:TRUE |
KB-3307 | in_stock | refurbished | non-new | FALSE:TRUE |
KB-4415 | in_stock | new | engraving option | FALSE:TRUE |
KB-5520 | in_stock | new | installation service bundle | FALSE:TRUE |
The rule logic in plain terms: if availability is preorder, or condition is not new, or the product carries a personalization, service, subscription, final-sale or age-restriction flag from your catalog, set FALSE for checkout. Send FALSE:FALSE only if you also want it out of cart transfer.
The weak point is signals that are not standard feed attributes. "Final sale" and "engraving available" usually live in custom shop fields, so score 2 only when those fields feed the rule. In Feedance this is a feed rule on the Google channel that reads the custom field and writes the attribute, so the source catalog stays untouched.
Item 5: making the product ID match your checkout API
When Google sends an agentic checkout request, it uses the product id. That ID must match what your checkout API expects. If it does not, for example because your feed IDs carry a country prefix or a feed tool rewrote them, add the custom attribute merchant_item_id. When it is defined, it takes precedence over id in agentic requests (source). Google's Merchant API example is:
"name": "merchant_item_id", "value": "some_checkout_item_id_1"
Test it by calling your own checkout endpoint with 20 random IDs from Merchant Center. Any miss loses the sale after the shopper has already chosen to buy.
Items 6 to 8: returns, support contact and consumer notices
A return policy is required as a merchant-of-record condition and is shown on the checkout screen. It must include return cost, return window and a link to the full policy. Policies apply to the whole account by default. Use return_policy_label to limit one to a subset, or send product-level policies with the returns attribute. Advanced accounts must configure return policies in each sub-account (source).
Customer support information needs at least one contact method in Merchant Center: a customer service URL, email or phone number. It powers the "Contact Merchant" link on the order confirmation page.
consumer_notice carries legal and safety text into checkout. Its notice_type must be legal_disclaimer, safety_warning or prop_65. Its notice_message allows up to 1,000 characters with <b>, <br>, <i> and <a href>. In feed files, escape the colon in URLs as http\://, and repeat the header for multiple notices on one product. Proposition 65 is a California requirement, so prop_65 matters for US-bound catalogs.
Item 9: keeping price and stock fresh enough for checkout
Google recommends the Merchant API for real-time catalog sync, and supplemental price and inventory updates if you use scheduled feeds, to prevent checkout price mismatches (source). Its FAQ also requires real-time inventory checks in your checkout API, returning out_of_stock for unavailable items (source).
Feedance is not a real-time sync. Feed updates run up to daily on Essentials and up to hourly on Business, with Enterprise scoped per catalog (pricing). Score yourself honestly:
- 2 points: your shop platform pushes price and stock to Merchant API directly, and the feed carries slower attributes such as
native_commerce. - 1 point: hourly feed refresh, and prices change only at planned times.
- 0 points: daily refresh and prices that move during the day.
Item 10: the backend a feed cannot replace
To onboard, you complete the technical implementation in Google's UCP developer guide first, then submit the interest form. If you are selected, Google opens the onboarding experience in Merchant Center, with a sandbox to test your UCP profile, cart transfer and native checkout APIs (source). PPC Land's reading of the Cart API guide adds that the profile sits at /.well-known/ucp and that the Cart API needs UCP version 2026-04-08 or later (source).
On payments, your site does not need the Google Pay button, but your payment provider must process Google Pay tokens, and only PAN_ONLY is used for allowed_auth_methods (source). Native checkout is the default; embedded checkout is reserved for approved merchants with complex flows (source).
What this scorecard does not cover
- It does not predict ranking. Google's FAQ says native integration does not affect how offers rank.
- It does not cover multi-variant structure. Google strongly recommends
variant_optionwithitem_group_idfor multi-variant items. We leave variant structuring out of this guide on purpose. - It does not build the backend. Feedance, like any feed platform, can write the attributes in items 3 to 8. It does not build UCP profiles, checkout APIs or payment integrations. If you run on Shopify, a UCP co-developer, check your platform's own path first. Google itself tells merchants on third-party platforms to ask their provider about UCP plans.
- Some details are secondary. The 2027 timing and the Cart API version come from PPC Land's reading of Google pages we could not open ourselves. Verify before planning dates.
- The program changes fast. PPC Land's March 2026 summary of the help page described US-only eligibility (source). The same page now lists the US, Canada and Australia. Re-score every quarter.
Frequently asked questions
Does adding native_commerce to my feed show the Buy button?
No. The attribute is needed but not enough. Google must select you through the interest form, and you must complete the technical integration first.
Can merchants outside the US use UCP checkout today?
The checkout terms apply to the United States only, and Google says Canada and Australia follow next year. A non-US brand with a US-targeted feed and US-ready returns and support can qualify on the feed side.
What happens if my supplemental feed sends only checkout_eligibility?
The cart flag is cleared, because the attribute group does not support incremental updates. Send both flags in every update, and set the attribute in only one data source.
Do I need merchant_item_id?
Only if your Merchant Center id differs from the ID your checkout API expects. When set, Google uses it instead of id in agentic requests.
Which products must have checkout switched off?
Google's list covers subscriptions, installment plans, personalized, non-new, final-sale and pre-order items, age-restricted items, services, rentals and virtual goods, among others. Set checkout_eligibility to FALSE or leave it empty for these.
Does UCP checkout make my products rank higher in AI Mode?
No. Google's FAQ states that native integration does not affect offer ranking. It adds a direct purchase option to offers that already show.
Is a daily feed refresh good enough?
Only if your prices and stock change rarely. Google recommends Merchant API sync or supplemental price and inventory updates, and your checkout API must check stock live.
Check the feed half before you apply
Items 1 and 3 to 9 depend on clean product data: approved items, correct IDs, valid conditions and availability, and stock that matches the site. Run your catalog through the free product feed audit tool to see where your feed stands before you score the rest and submit the interest form.

Co-founder of Feedance, where he leverages his background as a computer engineer and marketer to drive analytical insights. With a strong focus on transforming data into actionable strategies, he is dedicated to helping brands achieve significant growth in the digital landscape.
LinkedIn



















