Run free audit

Journal

Shopify UCP Is Open: Prepare for AI Commerce, Then Prove What It Drives

Shopify's Universal Commerce Protocol makes AI shopping more concrete for merchants. Here's how to prepare product data, policies, schema, and attribution without overclaiming what UCP exposes today.

Key takeaways

What to remember

  • UCP makes agentic commerce more practical, but it does not remove the need for clean product data, schema, policies, and FAQs.
  • Merchant attribution should distinguish confirmed AI referrers, AI-assisted orders, and possible agentic handoffs instead of labeling all direct traffic as AI.
  • Public Shopify docs show agent profiles and UCP negotiation with Shopify, but merchant apps should not assume every order webhook contains UCP agent identity.
  • The practical near-term standard is: prepare for AI commerce, then prove what detectable AI signals actually drive.

Shopify’s opening of the Universal Commerce Protocol (UCP) and Shopify Catalog to developers means merchants need to prepare for agentic commerce. While UCP provides a technical framework for agents and merchants to interact, the practical focus is on how merchants can make their products understandable to AI agents and measure the impact of AI-driven shopping experiences.

UCP enables four key stages in the shopping journey: discovery, cart, checkout, and orders. Agents can now search broader catalogs, build carts, manage checkouts, and track order status for facilitated purchases. This expands product discovery beyond traditional channels like search engines and marketplaces to include AI assistants and shopping agents.

However, AI agents require structured data, unlike human shoppers who can interpret context more flexibly. Merchants should ensure:

  • Clear Product Data: Titles, descriptions, variants, and identifiers are specific and unambiguous.
  • Structured Data Accuracy: Product JSON-LD, offer details, variant information, and schema markup are complete and accurate.
  • Comprehensive Policies: Shipping, returns, warranties, sizing, and compatibility information are easily accessible.
  • Effective Discovery Files: robots.txt, sitemaps, and AI-specific files like llms.txt guide agents to relevant content.

Attribution is crucial. Since direct checkout from AI flows might lack clear referrers, merchants should:

  1. Encourage AI partners to append UTM parameters and agent identifiers to handoff URLs.
  2. Utilize Shopify’s available source fields (landing_site, referring_site, etc.) and cart/checkout token stitching where possible.
  3. Focus on measuring identifiable AI signals (UTMs, referrers, user agents) rather than assuming all direct traffic is AI-driven.

Eventabee’s approach emphasizes conservative, evidence-based attribution, distinguishing AI-referred visits, AI-assisted purchases, and potential agentic checkouts based on detectable signals. Merchants should prioritize preparing their stores for AI commerce now and then measure its impact accurately as the ecosystem evolves.

Flags: …

Frequently asked questions

Can Shopify merchants automatically see every UCP-driven order?

Not necessarily. Shopify docs describe agent profiles, negotiation, checkout handoff, and order flows, and Shopify says AI-channel attribution appears in Shopify Admin. Public docs do not guarantee that every standard merchant app webhook includes UCP agent profile metadata, so app-level reporting should rely on detectable referrers, UTMs, source fields, cart or checkout stitching, and any future Shopify-exposed metadata.

What should merchants do first for AI commerce readiness?

Start with top products: clear titles, concrete descriptions, accurate variants, identifiers where relevant, valid Product JSON-LD, complete shipping and return policies, useful FAQs, and accessible discovery files like sitemaps or llms.txt where appropriate.

How should AI agents preserve attribution?

When an agent or partner sends a buyer to cart or checkout, it should append explicit parameters such as utm_source, utm_medium=ai_agent, utm_campaign, eb_agent, and an opaque eb_agent_session so the merchant has a better chance of connecting discovery to checkout and order outcomes.

← More from the blog Start a project