Key Takeaways
- Google’s native_commerce attribute is a product-level Merchant Center setting that determines whether your products appear with a Buy button inside AI Mode and the Gemini app.
- Products without native_commerce set to true are invisible to Google’s checkout layer, regardless of how well-optimised the rest of your feed is.
- Adding native_commerce via a supplemental feed, not your primary feed, protects existing Shopping Ads performance while enabling AI Mode checkout eligibility.
- Your payment service provider must support Google Pay token-based transactions for UCP checkout to complete, and Merchant Center will not alert you if this is missing.
- Most brands are currently missing at least one of the three required components: the attribute, accurate supplemental feed data, and PSP token support.
- Starting with your top 20% of products by revenue is the lowest-risk way to test UCP checkout eligibility before expanding across your catalogue.
General Summary
Google’s Universal Checkout Protocol (UCP) is reshaping how purchases happen inside AI search. When someone searches in AI Mode or the Gemini app and Google recommends a product, the checkout experience no longer requires leaving Google. But access to that checkout layer is controlled by a single Merchant Center attribute most brands have never heard of: native_commerce. Set to true, it makes a product eligible for the Buy button inside AI Mode. Missing or set to false, that product does not exist in Google’s checkout system, no matter how clean the rest of the feed looks. This is not a ranking signal. It is a binary gate. Beyond the attribute itself, two further dependencies determine whether checkout actually works: the supplemental feed must carry accurate, current product data, and the brand’s payment service provider must support Google Pay token-based transactions through the Agent Payments Protocol. Google’s own documentation recommends handling this through supplemental feeds rather than primary feed edits, specifically to avoid disrupting existing Shopping Ads campaigns. For Amazon sellers with Shopify storefronts, getting into UCP checkout represents a meaningful shift in where conversions can happen, but only if all three components are in place before the protocol’s wider rollout.
Extractive Summary
Google’s native_commerce attribute is a product-level Merchant Center setting that controls whether a product is eligible for UCP checkout inside AI Mode. Editing a primary feed to add native_commerce carries real risk of disrupting existing Shopping Ads performance, which is why Google recommends using supplemental feeds. Google’s Agent Payments Protocol processes UCP transactions through Google Pay tokens, which means payment service provider compatibility is a hard dependency for checkout to function. Most brands entering AI Mode are missing at least one of three required components: the native_commerce attribute, a properly structured supplemental feed, and PSP support for Google Pay tokens.
Abstractive Summary
The shift from search-driven to AI-driven commerce is not just about visibility — it is about where the transaction happens. Google’s UCP is an early signal of a broader structural change: the checkout moment moving from the merchant’s site into the AI interface itself. For brands that have spent years optimising product pages and checkout flows on Shopify, this represents a genuine inversion. The conversion environment is now partially outside their control, governed by Google’s protocol and their PSP’s compatibility. Brands that treat UCP readiness as a technical box-tick rather than a strategic priority risk building a growing gap between AI Mode impressions and actual revenue. The brands that move earliest, get the attribute right, validate the payment chain, and monitor performance through Merchant Center will have a structural advantage in the period before UCP becomes standard practice.
What Is the native_commerce Attribute and Why Does It Matter?
The native_commerce attribute is a product-level Merchant Center setting that controls whether a product is eligible for Google’s Buy button inside AI Mode and the Gemini app. When set to true, Google’s system recognises that product as available for checkout within its own interface. When it is missing or set to false, that product does not exist in the checkout layer at all.
This is not a ranking signal. It has no effect on where your products appear in standard Shopping results or how often they show in AI Mode recommendations. It is a binary gate: either a product is eligible for UCP checkout or it is not.
Google did not include native_commerce in the default Merchant Center feed specification. It has to be added manually. Most brands running well-optimised feeds right now have never seen this attribute because it is new, specific to UCP, and not surfaced in the standard feed diagnostics interface.
The practical consequence is significant. A brand could have perfect feed health, strong conversion rates, and consistent Shopping Ads performance, and still have zero UCP checkout eligibility because one attribute is missing. Merchant Center will not flag this as an error. The products will appear in AI Mode recommendations. The Buy button simply will not appear.
Understanding why Google structured it this way requires a brief look at how UCP checkout actually works. When a user searches in AI Mode and Google’s system decides to recommend a product, it queries the Merchant Center feed for that product’s attributes in real time. If native_commerce is true, the Agent Payments Protocol initiates a checkout session and Google surfaces the Buy button. If the attribute is absent, the system skips to the next eligible product. Not to a redirect. Not to a fallback. It moves on.
This is worth sitting with for a moment. You can rank in AI Mode and still lose the sale at the exact point of purchase because a single attribute is missing from your feed.
Why Should You Use a Supplemental Feed Instead of Editing Your Primary Feed?
Adding native_commerce via a supplemental feed, rather than editing the primary feed directly, protects existing Shopping Ads performance from disruption during the update process. This is Google’s own recommendation, and the reasoning is practical.
A supplemental feed in Merchant Center is a secondary data source that adds or overrides attributes for products already in the primary feed. It references products by ID. Google merges the two feeds automatically, pulling attributes from the supplemental source where they exist and falling back to the primary feed where they do not.
The primary feed drives Shopping Ads. Any structural change to it, including adding new attributes, introduces risk: data processing delays, temporary disapprovals, or performance fluctuations while Google re-indexes the updated data. For brands running significant ad spend through Shopping campaigns, that window of instability carries real cost.
A supplemental feed sidesteps this risk entirely. The primary feed stays exactly as it is. The supplemental feed lists only the products you want in UCP checkout, with native_commerce set to true. Upload it, and Google handles the merge without touching the existing Shopping Ads infrastructure.
There is a second advantage to this approach: selectivity. Not every product in a catalogue makes sense for UCP checkout. Out-of-stock SKUs, products with complex variant structures, custom items, and seasonal lines may create poor checkout experiences or inventory problems if included. A supplemental feed lets you choose exactly which products go into UCP checkout, rather than applying the attribute globally across thousands of SKUs.
The recommended starting point is the top 20% of products by revenue. These are the products with proven demand, stable inventory, and accurate pricing. Get those into the supplemental feed with native_commerce set to true, validate them in Merchant Center, and confirm they are being picked up correctly before expanding further.
What Is the Agent Payments Protocol and How Does It Affect Checkout?
Google’s Agent Payments Protocol is the underlying system that processes UCP transactions, using Google Pay tokens stored in Google Wallet to complete purchases without the customer leaving the AI interface. For a UCP checkout to complete, the brand’s payment service provider must support these Google Pay tokens.
This is the dependency most brands discover too late. The native_commerce attribute makes a product eligible for UCP checkout. The supplemental feed gets the data into the right place. But if the PSP cannot process Google Pay tokens, the transaction fails at the final step. The Buy button exists. The customer taps it. Nothing completes.
Google Pay token support is not universal among payment processors. Stripe supports it. Adyen is a launch partner, so compatibility is confirmed. Many smaller PSPs and regional processors either have not implemented the specific token flow UCP requires, or they support Google Pay in general terms but not the precise implementation the Agent Payments Protocol uses.
The critical distinction is between general Google Pay support and Google Pay token-based UCP support. These are different implementations. A PSP can pass a standard Google Pay compatibility check and still fail at UCP checkout. The question to ask the PSP directly is whether they support Google Pay token-based transactions for UCP. Not Google Pay in general, specifically the token flow.
Merchant Center will not surface this problem. Shopping Ads will continue running normally. The only indication that something is wrong is that UCP checkout attempts fail silently. There is no error notification, no disapproval, no flag in the interface.
For brands whose PSP does not yet support the token flow, the conversation needs to happen before the UK rollout, not during it. PSP implementation timelines vary. Some processors move quickly once the request is formal. Others treat it as a roadmap item with no committed date. Finding out where your PSP stands now gives you options. Finding out during a live rollout does not.
How Do You Set Up native_commerce Without Disrupting Your Existing Ads?
Setting up native_commerce for UCP checkout requires three steps: creating a supplemental feed in Merchant Center, populating it with the target product IDs and the native_commerce attribute set to true, and validating that Google has processed the merge correctly before expanding the product set.
Start in Merchant Center. Navigate to Products, then Feeds, and create a new supplemental feed. The file can be a standard CSV or spreadsheet format with two required columns: id (matching the product IDs in the primary feed exactly) and native_commerce (set to true for each row).
The product ID match is critical. If the IDs in the supplemental feed do not match the primary feed exactly, including any prefix formatting Google uses, the merge will not work and the attribute will not apply. Check the primary feed’s product ID format before building the supplemental file.
Once uploaded, Merchant Center processes the supplemental feed on its standard schedule, typically within a few hours for smaller files. After processing, check the Product diagnostics view for the specific products included. The native_commerce attribute should appear in the product detail alongside the primary feed attributes.
Validation at this stage matters. Confirm that the attribute is being applied to the intended products and that no feed errors have been generated. A common issue is ID formatting mismatch, which causes the supplemental feed to upload successfully but apply to zero products.
Only after confirming successful merge for the initial product set should you expand. Add the next tier of products, upload, validate again. This incremental approach keeps the process manageable and ensures each batch is confirmed before the next is added.
What Does the Full Dependency Chain Look Like for UCP Checkout?
UCP checkout eligibility depends on three components working correctly in sequence: the native_commerce attribute must be present and set to true in the Merchant Center feed, the product data in that feed must be accurate and current, and the payment service provider must support Google Pay token-based transactions. All three must be in place for a checkout to complete.
Most brands entering AI Mode are currently missing at least one. The attribute is the most common gap, simply because it is new and not included in standard feed specifications. The PSP compatibility issue is less common but harder to resolve quickly. Data accuracy is often assumed to be fine but rarely verified against the specific fields UCP checkout pulls.
The sequence matters because each layer builds on the one before it. An accurate PSP and valid attribute do nothing if the product data is stale or the price in the feed does not match the current storefront price. Google cross-references feed data at the moment of checkout initiation. Price discrepancies between the feed and the actual checkout URL cause session failures.
For Amazon sellers running Shopify storefronts, the Shopify product catalogue is typically the source of truth for the Merchant Center feed. Any lag between Shopify inventory updates and Merchant Center feed refreshes creates a window where the feed data is inaccurate. During that window, UCP checkout attempts on affected products will fail.
Checking the feed refresh schedule and ensuring it aligns with inventory update frequency is a practical step that sits alongside the attribute and PSP work. A feed refreshing every 24 hours is not adequate for a catalogue with frequent price or inventory changes.
The brands that will perform well in UCP checkout early are those that treat it as an infrastructure problem, not a campaign problem. The attribute is the entry ticket. The data accuracy is the customer experience. The PSP support is the revenue capture. All three need attention before the rollout, not after.
What Should Amazon Sellers Do Right Now to Prepare?
Amazon sellers with Shopify storefronts should complete three actions before the UCP rollout expands: confirm PSP compatibility with Google Pay token-based transactions, build a supplemental feed with native_commerce set to true for the top revenue products, and verify feed refresh frequency against inventory update cycles.
Start with the PSP conversation. This is the step most likely to have a long lead time. Contact the PSP directly and ask specifically whether they support Google Pay token-based transactions for Google’s Universal Checkout Protocol. Document the response. If they do not currently support it, ask for a timeline and escalate internally if the timeline is unsatisfactory.
While that conversation is in progress, build the supplemental feed. Pull the top 20% of Shopify products by revenue. Export the product IDs in the format Merchant Center uses. Create the supplemental feed file with those IDs and native_commerce set to true. Upload it and validate the merge.
After validation, check the feed refresh schedule in Merchant Center. If the feed updates less frequently than inventory changes in Shopify, adjust the schedule. Most Shopify-to-Merchant Center integrations support scheduled refreshes; some support near-real-time sync. For high-velocity catalogues, the refresh frequency needs to match the pace of price and inventory changes.
The final step is monitoring. Once the supplemental feed is live and validated, watch the Merchant Center diagnostics for any product-level errors that emerge. Pay attention to price mismatch flags and inventory discrepancies. These are the early indicators that something in the data chain is breaking.
The brands that complete this groundwork now will have a functioning UCP checkout setup when the rollout expands. The brands that wait will spend the early rollout period troubleshooting instead of capturing revenue.
