Frequently asked questions.

The acronym UCP now covers two things. First, an open standard: the Universal Commerce Protocol launched by Google and Shopify at NRF in January 2026. Second, the reading framework proposed by this hub, which aggregates and reorganizes the standards (UCP, ACP, AP2, MCP, A2A, schema.org, GS1) into four committee-usable layers. This site documents the former and proposes the latter as an arbitration grid.

A feature powered by the UCP standard, expanded at Google Marketing Live in May 2026: a multi-retailer cart where shoppers save products from several merchants and complete the purchase via Google Pay or the retailer's checkout. Details and milestones on the standard reference page.

Because each standard answers a partial question: schema.org covers semantics, MCP covers agent protocol, Stripe ACP covers payment. An operator needs a cross-cutting grid for making decisions. UCP provides that grid.

SEO aims to be rankable by a search engine for a human. UCP aims to be retrievable, citable and transactionable by an agent. SEO remains necessary (LLM crawlers still use the same signals), but it is no longer sufficient.

No. The framework is platform-neutral by design. Stripe, Shopify, Amazon, Google, OpenAI, Anthropic are cited when they contribute a building block. None is privileged.

Yes. This hub is available in both English and French. The French version stabilizes the French-language vocabulary for this emerging field. Use the language switcher in the header to switch.

No. News, analysis and long-form comparisons are published on the editorial outlet universalcommerceprotocol.blog. The .fr is not a blog: it carries the brand, the framework and the method.

A French-speaking operator and author with a B2B founder background in e-commerce customer service automation. Identity details are shared during contact exchanges.

Yes, with attribution. Content is under CC BY-NC 4.0 license. Internal use: free with attribution. Commercial use: contact us.

Through the Contact page. Each audit is preceded by a scoping call to validate alignment with your situation, timeline and teams.

We are happy to discuss. An observatory partnership or a co-published paper can be a good starting format.

Not by default. UCP's Checkout capability requires an order to be finalized manually by the user, through a trusted UI, unless the AP2 Mandates extension is supported. Without mandates, the agent assembles the cart and a human approves. With them, the buyer signs an intent up front carrying limits, and the agent executes once they are met. This is the single place where the degree of autonomy is set. See AP2.

No. The specification is explicit: the Merchant of Record does not change. It further notes that the Checkout capability introduces no PCI DSS compliance obligation for card payments. The real issue is commercial rather than legal: visibility and the customer relationship move to the agent's surface.

By negotiation. The business publishes a profile describing its capabilities and services, and the platform dynamically discovers what it can do with that business. Capabilities are named using reverse-domain notation, which allows an extension to be added under one's own namespace with no central approval committee. Services are defined in REST and JSON-RPC, across several possible transports.

Through the requires_escalation state in the checkout session lifecycle, which is the standardized hand-off to a human. Age checks, signature thresholds, supporting documents, pricing exceptions: these are not breaks to work around, they are states the protocol anticipates. Errors are separately graded by severity, from recoverable to unrecoverable.

Through eligibility verification: claims must be resolved before a transaction completes. This is the mechanism behind contract pricing, geographic restrictions and per-customer terms. It still requires those terms to be expressed in a typed, machine-readable form. See B2B agentic commerce.

Both engines now expose this, and they do not measure the same thing. On 3 June 2026 Google launched generative AI performance reports in Search Console, counting impressions in AI Overviews and AI Mode, with views by page, country and device, on a subset of sites only. In February 2026 Bing opened "AI Performance" in Webmaster Tools, counting citations and exposing grounding queries, the phrases the model used to retrieve the content. That second signal is the more actionable of the two. See GEO and catalog readability.

No, but the effort gap is real. Shopify exposes two catalog interfaces implementing UCP's Catalog capability: a Global Catalog spanning every merchant on the platform, and a Storefront Catalog scoped to one store. A merchant on a custom stack has to publish its own profile and its own checkout handler. The groundwork is the same; the path differs. See the implementation guide.