UCP Merchant Center Onboarding Explained
> UCP Merchant Center onboarding is the process by which a merchant registers their UCP implementation with Google through Google Merchant Center — submitting their product feed with the `native_commerce` attribute, declaring their UCP capabilities, and completing Google's integration approval steps — to make their products eligible for AI-assisted purchasing on Google AI Mode and Gemini.
---
What Is UCP Merchant Center Onboarding?
UCP Merchant Center onboarding is the Google-specific pathway for activating a merchant's UCP implementation on Google's AI-powered shopping surfaces. The Universal Commerce Protocol is an open standard that merchants can implement independently, but to have products appear as purchasable within Google AI Mode and Gemini — Google's AI assistant surfaces — merchants must register their UCP capability set with Google through the Merchant Center.
Google's support documentation describes UCP as a new open standard for agentic commerce that lets eligible merchants offer a seamless checkout experience on Google surfaces. The `native_commerce` attribute in the product feed is the signal that a product is eligible for this experience. Onboarding is the process of establishing that eligibility — by submitting a feed, declaring UCP capabilities, and passing Google's validation checks.
Onboarding is the gate between having a working UCP implementation and having a live, revenue-generating presence in Google's agentic commerce channel. A merchant whose UCP endpoints are correctly implemented but who has not completed Merchant Center onboarding will not appear in Google AI Mode purchasing flows.
---
Prerequisites Before Onboarding
Before beginning Merchant Center UCP onboarding, a merchant must have the following in place:
A working `/.well-known/ucp` manifest. The manifest must be published at the standard well-known URI on the merchant's domain, correctly declaring all implemented capabilities (at minimum `catalog_search` and `redirect_checkout` or `checkout`), with valid endpoint URLs and public key.
A UCP-compliant product feed. The product feed submitted to Merchant Center must include the standard Google Shopping required fields (title, description, link, image link, price, availability, condition) plus the `native_commerce: true` attribute for products that are eligible for AI-assisted purchasing. Products without `native_commerce: true` remain on the standard Google Shopping experience and are not eligible for UCP-powered checkout.
Google Pay configuration (for native checkout). Merchants who want to support native UCP checkout — rather than redirect checkout — must set up with the Google Pay & Wallet Console. This involves verifying that the merchant's PSP supports Google Pay tokenisation, registering the merchant in the Google Pay console, and obtaining a Google Pay Merchant ID to declare in the UCP profile's payment handler section.
UCP profile declaration. The merchant's UCP profile must be complete, including business information, service definitions with correct endpoint URLs and versions, payment handler configuration (for native checkout), and public key. The profile is submitted to or referenced by Google during the onboarding process.
---
The Onboarding Steps
Step 1: Prepare and submit the product feed. Create or update the Google Merchant Center product feed to include all required fields for eligible products. Add `native_commerce: true` to the products that should participate in UCP-powered purchasing. Submit the feed URL to Google Merchant Center as you would for a standard Shopping feed. Google indexes the feed and validates the field structure.
Step 2: Enable UCP in Merchant Center. Within the Google Merchant Center interface, navigate to the UCP settings section and provide the `/.well-known/ucp` manifest URL. Google fetches and validates the manifest, checking that the declared capabilities have functioning endpoints and that the manifest structure conforms to the UCP specification.
Step 3: Declare UCP capabilities. During the Merchant Center setup flow, confirm which UCP capabilities the merchant supports. Google uses the manifest declaration to determine which capabilities to enable on Google surfaces for this merchant. A merchant declaring only `redirect_checkout` will get redirect-based purchasing in Google AI Mode; one declaring `checkout` (native) will get the full in-assistant checkout experience once Google approves the integration.
Step 4: Configure Google Pay (native checkout only). For merchants implementing native checkout, provide the Google Pay Merchant ID in the UCP profile's payment handler configuration. Google validates that the Merchant ID is correctly registered in the Google Pay & Wallet Console and that the merchant's PSP is in the list of processors that support Google Pay tokenisation for UCP checkout.
Step 5: Complete Google's integration approval. Google's UCP implementation guide states that the UCP integration must be approved by Google before going live on AI Mode and Gemini. The approval process involves Google verifying the merchant's endpoint responses against the UCP specification schemas, confirming error handling is correct, and validating webhook delivery for order status updates (for merchants using native checkout). This is the production certification step that gates access to the live channel.
Step 6: Monitor and maintain. After going live, merchants should monitor feed health, endpoint uptime, and order webhook delivery reliability. Google may re-evaluate a merchant's UCP eligibility if endpoint errors or feed quality issues persist. Ongoing feed updates should include prompt availability and pricing changes for products with `native_commerce: true`.
---
Onboarding Checklist
- [ ] `/.well-known/ucp` manifest published at merchant domain with correct capability declarations
- [ ] Product feed includes all required Google Merchant Center fields
- [ ] `native_commerce: true` attribute added to eligible products in feed
- [ ] Feed submitted to Google Merchant Center at stable HTTPS URL
- [ ] UCP manifest URL provided in Merchant Center UCP settings
- [ ] Google Pay Merchant ID obtained and declared in UCP profile (native checkout)
- [ ] PSP confirmed as supporting Google Pay tokenisation (native checkout)
- [ ] UCP endpoint responses tested against Google's schema expectations
- [ ] Error handling verified against UCP standard error codes
- [ ] Webhook delivery configured for `order.created` and `order.updated` (native checkout)
- [ ] Integration approval submitted and received from Google
- [ ] Feed scheduling in place to keep `native_commerce` product data current
Why It Matters for Merchants
Google AI Mode and Gemini represent a significant and growing purchase surface. Merchants who complete UCP Merchant Center onboarding make their products purchasable within Google's AI-powered interfaces — a channel where the buyer has already expressed specific, resolved purchase intent before the agent queries the merchant.
The `native_commerce` attribute is a product-level decision, giving merchants granular control over which products participate in this channel. A merchant can start with a small selection of high-confidence, well-structured products — those with complete data, clear trust signals, and accurate availability — and expand the `native_commerce` eligible set as data quality improves across the catalog. This phased approach reduces the risk of poor product data causing checkout errors on the live channel.
Early onboarding also builds the merchant's operational history with Google's systems — feed reliability, endpoint uptime, and webhook delivery history — which are likely to become factors in how prominently merchant products appear within AI-assisted search and purchase flows as the channel matures.
---
FeedBridge Relevance
FeedBridge supports the Google Merchant Center UCP onboarding process directly through its Google Merchant Center CSV export. This feed format includes the standard Google Shopping required fields and can be extended to include the `native_commerce: true` attribute for UCP-eligible products. The feed is generated from FeedBridge's enriched product catalog and hosted at a CDN-backed URL with configurable scheduling, ensuring that the feed Google indexes stays current with pricing, availability, and `native_commerce` eligibility.
FeedBridge's UCP implementation — including the `/.well-known/ucp` manifest, Catalog Search API, Catalog Lookup API, Cart API, Identity Linking API, and Redirect Checkout — covers the UCP capability stack that Google's Merchant Center onboarding process validates. The UCP Dashboard Hub provides a compliance scorecard and capability checklist showing which UCP capabilities are active and correctly configured, directly supporting the merchant's readiness assessment before submitting for Google's integration approval.
The AI Readiness Score's Protocol Compliance dimension (30% of total score) also includes ACP/UCP validation status, giving merchants a per-product view of how their catalog's protocol readiness compares to the requirements Google will check during onboarding validation.
---
Frequently Asked Questions
Q: Do I need a Google Merchant Center account to use UCP? A: To appear on Google's AI-powered shopping surfaces (AI Mode, Gemini), yes — UCP onboarding is managed through Google Merchant Center. The UCP protocol itself is an open standard that any merchant can implement independently, but Google's distribution channel requires Merchant Center registration.
Q: Can I use redirect checkout instead of native checkout for Merchant Center UCP onboarding? A: Yes. Redirect checkout is a valid UCP capability for Merchant Center onboarding. Products with `native_commerce: true` can be purchased via redirect — the buyer is redirected to the merchant's checkout page with cart contents pre-loaded. Native checkout provides a more seamless in-assistant experience but is not required to achieve UCP eligibility in Merchant Center.
Q: How does the `native_commerce` attribute differ from standard Google Shopping attributes? A: Standard Google Shopping attributes make products eligible for Google Shopping placements (search, Shopping tab). The `native_commerce: true` attribute additionally signals that the product is eligible for UCP-powered AI-assisted purchasing within Google AI Mode and Gemini. A product can have both standard Shopping attributes and `native_commerce: true`.
Q: What happens if my UCP endpoint fails after Google has approved the integration? A: Persistent endpoint failures after going live may affect the merchant's UCP eligibility status with Google. Merchants should implement monitoring and alerting for UCP endpoint availability. FeedBridge provides feed health monitoring and alert preferences (email, Slack, Discord, webhook) that can be part of a broader uptime monitoring strategy.
Q: Is there a cost to participate in UCP via Google Merchant Center? A: The UCP specification is open and free. Google Merchant Center is free to use for feed submission and product listing. Standard Google Pay transaction processing fees may apply for native checkout transactions through Google Pay. This page does not make claims about any additional fees that Google may introduce to the UCP channel in the future.
---
Related Topics
Parent hub: UCP Implementation
Related concepts:
- What Is UCP?
- UCP Capability Discovery Explained
- How UCP Powers Agentic Checkout
- UCP Identity Linking Overview
Breadcrumb:
---
Source Documentation
| Claim | Source | Source Class | Reference | |---|---|---|---| | UCP described as new open standard for agentic commerce; eligible merchants offer seamless checkout on Google surfaces | Google Merchant Center support | T2 – Platform Partner Docs | https://support.google.com/merchants/answer/16837055 | | `native_commerce` attribute signals UCP-eligible products | almcorp.com UCP Merchant Center explainer | T2 – Platform Partner Docs | https://almcorp.com/blog/google-universal-commerce-protocol-ucp-explained/ | | UCP integration must be approved by Google before going live on AI Mode and Gemini | Google UCP Guide | T1 – Official UCP Docs | https://developers.google.com/merchant/ucp/guides | | Google Pay & Wallet Console setup; Merchant ID required for native checkout | Google UCP Guide | T1 – Official UCP Docs | https://developers.google.com/merchant/ucp/guides | | FeedBridge Google Merchant Center CSV export, UCP manifest, Dashboard Hub, Protocol Compliance score | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md |