Preparing For UCP: What Marketers Need to Do Before it Goes Live

Google just announced the Universal Commerce Protocol, and if you've read the coverage so far, you've probably noticed something: almost everything is written for developers. Technical specs, API endpoints, checkout integrations. But here's what most articles miss: even though you'll need developers to implement UCP, there's critical preparatory work that falls squarely in marketing's domain. Specifically, your product feed.

The question isn't whether UCP matters (it does). The question is what you need to understand now so you're ready when implementation becomes possible. Let's break down what marketers should be thinking about, even while the technical infrastructure is still being built.

Step 1: Set up a meeting with your developer

Your first move isn't opening Merchant Center or auditing your product feed. It's getting on your developer's calendar.

UCP will require development work when it launches. There's no simple checkbox in any platform yet. Even Shopify, which co-developed the protocol with Google, doesn't have this ready to flip on. Plugins and add-ons will likely emerge to make implementation easier, but we're not there yet.

What this means: you need to coordinate with developers on the technical integration while you prepare the product feed requirements. When they finish their work, you can launch immediately instead of spending weeks getting your product data ready.

The feed adjustments you need to understand

Here's the most important thing to know: products default to excluded from UCP unless you explicitly opt them in. This happens through a single attribute called native_commerce.

Adding native_commerce: true

This is how you tell Google which products should appear in AI Mode checkout flows. While your developers handle the checkout API, you handle the product eligibility decisions. Google made this opt-in so you maintain control over which products appear in conversational commerce experiences.

The recommended way to add this attribute? Supplemental feeds. Google officially recommends this approach because it doesn't risk breaking your existing Shopping Ads performance. You layer UCP attributes on top of your existing feed optimization without touching the primary feed that powers your paid campaigns.

Product restrictions you need to know

Not every product qualifies for UCP. Quick reference:

• ❌ Subscriptions and recurring billing
• ❌ Personalized or customizable products
• ❌ Age-restricted items
• ❌ Pre-orders and final sale items
• ❌ Products requiring special shipping
• ✅ Standard retail products with clear specifications

Consumer warnings and legal compliance

If your products require California Prop 65 warnings or other safety notices, these are mandatory for UCP. Add them through the consumer_notice attribute group in your feed. This matters for legal liability and affects checkout conversion rates.

Product ID mapping

If your Merchant Center product IDs don't match your checkout system IDs, you need the merchant_item_id attribute. This is common when feeds use SKUs but your checkout system uses internal product IDs. Add the mapping in your supplemental feed to prevent order processing issues.

Why feed quality matters more than ever

UCP amplifies existing feed problems. AI agents can't guess what your product is. Missing attributes mean you're invisible to AI Mode. Incomplete data means poor AI recommendations. And AI Mode in Search represents high-intent traffic you can't afford to miss.

This connects directly to how Google's Shopping Graph processes product information. The Shopping Graph handles billions of product updates and uses your feed quality to determine how products are indexed and understood. UCP pulls from this same infrastructure, which means structured data quality affects AI understanding.

Unique product descriptions are critical

One aspect that becomes particularly important for conversational commerce: unique, rich product descriptions. These help users, algorithms, and AI agents differentiate one product variant from another. If you're using duplicate descriptions across similar products, you're missing the opportunity to make each product unique for specific consumer needs.

Think about how an AI agent searches for products. It doesn't just match keywords in titles. It understands context, answers questions, and makes recommendations based on detailed product information. When your red t-shirt has the same description as your blue t-shirt, the agent can't distinguish between them beyond color. Add unique descriptions that highlight fit, material weight, care instructions, or ideal use cases, and suddenly each variant becomes discoverable for different needs.

"Writing thousands of unique product descriptions manually is tedious. That's exactly why Productrise's supplemental feeds feature makes this manageable at scale, helping you generate distinctive descriptions that prepare your catalog for conversational commerce."

Google also announced "dozens of new data attributes in Merchant Center designed for easy discovery in the conversational commerce era." These aren't traditional title and description fields. They're attributes for answering common product questions, identifying compatible accessories, suggesting substitutes, and describing use cases.

Feed optimization is shifting from keyword-focused to question-focused. AI agents ask questions about products differently than humans type search queries. Your feed needs to answer those questions.

The competitive landscape: Google vs. OpenAI

Google's announcement didn't happen in a vacuum. OpenAI is actively building shopping features, and this is fundamentally a race for agentic commerce dominance. Google has massive advantages: the Shopping Graph, Merchant Center relationships, decades of e-commerce infrastructure. But they also have something to lose.

To win this race, Google needs to move fast and move broadly. The initial launch targets AI Mode in Search and the Gemini app for U.S. retailers, but that's just the beginning. Wider rollout has to be a crucial part of their strategy. Every week OpenAI gains in shopping capabilities is a week Google risks losing ground in a category they've dominated for years.

What this means for you: UCP won't stay limited to AI Mode for long. The infrastructure Google is building will almost certainly expand to general Search results, more geographic markets, and additional product categories. Getting your feed ready now means you're positioned for each expansion, not scrambling to catch up.

Merchant Center settings that matter

Beyond your product feed, certain Merchant Center configurations become critical for UCP:

Return policy configuration

UCP requires a clear return policy that displays at checkout. This must include return cost, return window, and a link to your full policy. Configure this in Merchant Center now, even before UCP launches.

Customer support information

The "Contact Merchant" link in order confirmations pulls from your Merchant Center customer support settings. Verify this information is current and accurate.

Account eligibility basics

Your Merchant Center account needs to be in good standing with no policy violations, have free listings enabled, and have approved products. Check these basics now to avoid delays when UCP becomes available.

Get ready before implementation begins

Your developers will handle the technical integration when UCP becomes available. Your job is ensuring the product data is ready the moment that integration is complete.

Productrise helps you generate AI-optimized supplemental feeds, add UCP compliance attributes at scale, and monitor feed quality across your entire catalog. You can start for free to audit which products are UCP-ready and which need work.

Not ready to commit? Read our complete guide to product feed audits to understand which attributes matter most for organic visibility.