Hello everyone! Today I’m going to share something that’s not widely known yet in the Google Merchant Center community – how to enable UCP (Universal Commerce Protocol) payments for your product feed.
This information isn’t publicly available in the standard Google Merchant Center documentation, but I discovered it in the developer logs for the Content / Merchant API. Since most merchants who don’t work on the technical side of feed management wouldn’t know about this yet, I wanted to share how I figured it out. And honestly? It was quite easy to do once you knew where to look.
What is UCP (Universal Commerce Protocol)?
Before we dive into the technical setup, let’s talk about what UCP actually is and why you should care about it.
The Universal Commerce Protocol is a groundbreaking new open standard developed by Google and industry partners, announced in January 2026. The core purpose of UCP is to enable AI agents to directly complete purchases on behalf of users. This means AI moves beyond just providing product recommendations – it can actually buy products for users from start to finish.
Key Functions of UCP
Standard Machine-Readable Language: UCP provides a universal language that allows AI to communicate with retailer systems for discovery, inventory checks, checkout, and payments. The beauty of this is that it doesn’t require custom integration for each individual store.
Agentic Shopping Experience: AI can handle the entire customer journey while you, as the retailer, retain full ownership of customer data. This is a crucial distinction, you’re not losing control of your customer relationships.
Enabling UCP in Your E-Commerce Platform
For Shopify Users
If you’re using Shopify, there’s a new option in your settings that allows you to enable UCP. If you don’t see it yet, don’t worry, just wait a little bit. I’m assuming that Shopify is rolling this out periodically to more and more merchants over time.
For Other Platforms
If you’re using a different e-commerce platform, I recommend contacting your platform provider directly to ask about UCP enablement options.
Important: Make sure UCP is enabled on your e-commerce platform before proceeding with the Google Merchant Center setup. This is a critical first step.
How to Add UCP to Your Google Merchant Center Feed
Now, here’s where it gets interesting. Even if you have UCP enabled in your e-commerce platform, you need to prepare your Google Merchant Center data feed to support it.
The Native Commerce Attribute
The key to enabling UCP in Google Merchant Center is adding a specific attribute called native_commerce (or native commerce – I’ll explain the difference in a moment).
Why I Recommend Using a Supplemental Feed
I’m going to show you how to do this using a supplemental feed because that’s the most reliable method right now. You can also potentially use feed rules if you prefer, but here’s the catch – feed rules are not enabled yet for this specific attribute.
I tested this myself by going to Data Sources, clicking on my feed, going to Attribute Rules, and trying to add the “native” attribute. It’s simply not available in the feed rules interface yet.
Since we’re still in the early stages of UCP rollout, I recommend adding this attribute through one of two methods:
- Google Sheets supplemental feed (my recommended approach)
- Primary feed with custom attributes (if your feed management tool supports this)
Most feed management applications, like Mulitfeeds for example, allow you to add your own custom attributes without any issues. This is actually a very cool feature that many merchants don’t take advantage of.
Setting Up the Attribute
Here’s exactly what you need to do:
Step 1: Choose Your Naming Convention
You can use either:
native_commerce(with underscore)native commerce(with space)
Important: Whatever you choose, be consistent! If you’re using attributes like size_system or product_type with spaces, then use native commerce with a space. If you prefer underscores, use native_commerce with an underscore. Make sure every single attribute in your feed follows the same concept.
Step 2: Add the Boolean Value
For each product, you’ll add either:
1(to enable UCP for that product)0(to disable UCP for that product)
This boolean value tells Google whether that specific product is ready to accept UCP transactions.
My Personal Setup
In my case, I use a special supplemental shopping feed that improves data based on lots of different data points. This is something I’ve built for internal use only to optimize customer data and create dashboards. Within this feed, I simply added the native commerce attribute with a space, following my existing naming convention.
How to Verify Your Setup is Working
After you’ve added the attribute to your feed, here’s how to test if it’s working correctly in Google Merchant Center:
Step 1: Refresh your feed update by clicking the “Update” button.
Step 2: Check for errors or warnings.
When I tested this (and yes, the date shows the 18th because my account is US-based, but I’m actually in Thailand where it was already the 19th when I tested), I saw something important:
The feed showed “4 unrecognized attributes” – but this is not an error! This is absolutely fine. These unrecognized attributes are things I use for internal setups. For example, I have an old reference called lifestyle_image_link that points to where certain images are located.
Step 3: Look for the important indicators.
What you want to see is:
- No issues in the errors section
- No items in the “Needs Attention” area
If you see this, it tells you that the native_commerce attribute is already supported directly in Google Merchant Center, even though it’s not publicly documented yet!
Understanding Unrecognized Attributes
Let me clarify something important about “unrecognized attributes” because this confuses a lot of merchants.
Just because an attribute shows as “unrecognized” doesn’t mean it’s causing problems. You can add custom attributes to your feed for your own purposes. For example, let’s say you want to identify what a “top performer” product is, but you don’t want to use the standard custom labels. You can just create an attribute called top_performer in your feed.
It won’t be processed as a native Google value, but you can use feed rules to then make changes based on that attribute. This is very, very cool functionality that gives you a lot of flexibility in how you manage your product data.
Why This Matters for Your Business
You might be wondering – why should I bother setting this up now?
The answer is simple: early adoption. We’re at the very beginning of the AI commerce revolution. By preparing your feeds now for UCP, you’re positioning your products to be discoverable and purchasable by AI agents as this technology becomes mainstream.
Think about it – as more consumers start using AI assistants to make purchasing decisions and complete transactions, you want your products to be ready. The merchants who set this up early will have a competitive advantage.
Troubleshooting Tips
If you don’t see the UCP option in Shopify yet: Be patient. The rollout is happening gradually. You can still prepare your Google Merchant Center feed in the meantime.
If you’re getting errors: Double-check your naming convention consistency. Make sure you’re using either all spaces or all underscores, not mixing them.
If you can’t add custom attributes: Check with your feed management tool or platform provider. Most modern solutions support custom attributes.
Final Thoughts
Setting up UCP in Google Merchant Center is surprisingly straightforward once you know what to do. Even though the official documentation hasn’t been released yet, the functionality is already there and working.
The key takeaways are:
- Enable UCP in your e-commerce platform first
- Add the
native_commerceattribute to your feed (via supplemental feed or primary feed) - Use a boolean value of 1 or 0
- Be consistent with your naming conventions
- Don’t worry about “unrecognized attributes” warnings
As this technology continues to evolve, I expect we’ll see more official documentation and easier setup methods, including proper feed rules support. But for now, this method works perfectly.