Frequently Asked Questions

• Can any business join the UCP waitlist?
  You can express interest, but onboarding depends on meeting core infrastructure requirements. Our free audit can help you identify gaps and we can fix them for you as well.
• Do I need to migrate to the Merchant API?
  Yes. UCP requires API capabilities not supported by the legacy Content API. The final shutdown date is August 18, 2026
• Will I lose control of my customer data?
  No. You remain the Merchant of Record.
• What is UCP and why should I care?
  UCP stands for Universal Commerce Protocol. It's a system Google is building that lets AI agents discover, evaluate, and purchase products on behalf of consumers without the consumer ever visiting your website. If your store isn't set up for it, AI agents can't find you. Google is rolling access out through a waitlist, and only merchants with the right infrastructure qualify.
• What does the UCP Readiness Audit include?
  We evaluate your product feeds, Google Ads structure, tracking setup, Merchant API readiness, and AI visibility using PDPIQ (which scores 55+ aspects of your product pages across ChatGPT, Gemini, Perplexity, and other AI platforms) and FeedIQ (which evaluates 30+ attributes of your product feed for AI readiness). You receive a readiness score, a detailed gap analysis, and a prioritized action plan.  
• What happens if I miss the Content API deadline?
  Google is shutting down the legacy Content API on August 18, 2026 and requiring migration to the Merchant API. If you haven't migrated by then, your product feeds stop syncing with Google's systems. That includes Shopping ads, free listings, and the upcoming UCP infrastructure.
• How do I make my store UCP-ready?
  It depends on your current setup: your product feed quality, tracking infrastructure, API configuration, and how your product pages are structured for AI readability. The audit evaluates all of this using PDPIQ (55+ page-level factors) and FeedIQ, then gives you a prioritized roadmap of exactly what to fix and in what order.
  
• Can Tribbute implement the fixes, or is this just an audit?
  Both. The audit tells you where you stand. If there are gaps, we handle the implementation: feed optimization, tracking setup, API migration, and ad structure alignment. We're a Google Premier Partner (top 3% in the country) with full-service capability across paid media, organic, and digital commerce.
• What does UCP mean for the shopper?
  The shopper opens an AI mode such as Gemini and types "find me a blue winter jacket under $150." The AI agent contacts the merchant's UCP server, creates a shopping session, adds the item to the cart, retrieves the shopper's stored payment method, processes the payment, and confirms the order. The shopper never leaves the conversation. No new tabs, no typing in the card number, no creating an account.
• What does UCP mean for the Retailer or the Store?
  Retailers remain the Merchant of Record, maintaining full control over their customer relationships and data. So stores don't hand over their business to Google; they just get a new sales channel. UCP-powered checkout works on Google's own surfaces, while the merchant's backend communicates through the UCP API.
• Do I need Google Pay on my site?
  No. UCP uses a payment flow similar to Google Pay's facilitated payment, but you do not need a Google Pay button. Your existing PSP receives encrypted payment details, and most major PSPs already support the token format.
• What integration paths are available?
  There are two distinct paths (Native & Embedded checkouts). The Native integration requires you to build a RESTful API that Google can call to create and manage checkout sessions. To assist with your Native Checkout API implementation, you can find the following resources in the Universal Commerce Protocol GitHub repository:

  • UCP GitHub repository: Explore the main repository (https://github.com/Universal-Commerce-Protocol/ucp) for comprehensive documentation, specifications, and community resources.
  • SDKs: Use the Software Development Kits to accelerate your integration. Language-specific SDKs are available, including:
        •    Python SDK (https://github.com/Universal-Commerce-Protocol/python-sdk)
        •    JavaScript SDK (https://github.com/Universal-Commerce-Protocol/js-sdk)
        •    Conformance tests: Validate your API endpoints against the UCP specification using the conformance test suite (https://github.com/Universal-Commerce-Protocol/conformance)
    This helps ensure your implementation meets the required standards and behaviors.

  Embedded Checkouts has an additional optional path for specific, approved merchants. Best for those with highly bespoke branding or complex checkout flows that require an iframe-based solution. The Embedded checkout integration enables your web-based checkout to be embedded in Google surfaces. Use this path if your product requires complex logic (e.g., customizations) that the Native API cannot support. You will implement a checkout UI that will be embedded in the checkout flow through an iframe. Embedded checkout (EC) allows a host (like Google Search or an AI Agent) to display your existing web-based checkout within their application (using an iframe or webview). Unlike a standard web redirect, this allows for bi-directional communication. The host can "delegate" specific tasks such as selecting a saved address or paying with a stored credential to provide a faster, native-feeling experience, while you remain the Merchant of Record and handle the actual order creation.
• Is this compatible with my existing tech stack?
  UCP is built on open standards and is compatible with AP2, A2A, and MCP. Google provides native SDKs for common development environments and adapters for other protocols.
• How do I prepare for UCP?
  Follow these steps to go live on Google AI surfaces. You can choose to support guest checkouts or deeper account-linked experiences.

  • Prepare your Merchant Center account (https://developers.google.com/merchant/ucp/guides/merchant-center). Configure shipping, returns, and your product feed to enable users to discover and buy your products on Google surfaces.
    Once you're ready join the waitlist (https://support.google.com/merchants/contact/ucp_integration_interest) to get in contact with Google for UCP implementation. Your integration must be approved by Google before you can go live on Google AI Mode and Gemini.
  • Set up your business with Google Pay (https://developers.google.com/merchant/ucp/guides/google-pay). The Google Pay payment handler allows your users to submit payment with Google Wallet payment credentials.
  • Publish your UCP profile (https://developers.google.com/merchant/ucp/guides/ucp-profile). This will allow Google to negotiate services and capabilities and discover your payment handlers and public keys for signature verification.
  • Complete native checkout integration (https://developers.google.com/merchant/ucp/guides/checkout). Implement 3 core REST endpoints for session creation, updates, and completion.
  • Choose a path for user identification:
        •    Guest checkout (default): no extra steps required.
        •    Account-linked checkout (https://developers.google.com/merchant/ucp/guides/identity-linking): implement OAuth 2.0 to sync user profiles.
  • Sync order status (https://developers.google.com/merchant/ucp/guides/orders). Call Google's webhooks to push order updates.