Signal
UCP profile and order-management readiness
Whether a store reaches UCP surfaces at all, by either route the protocol now has: a public /.well-known/ucp profile declaring real capabilities, which is Google's path, or UCP-ready feeds in Microsoft Merchant Center, which is Copilot's.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Unknown | Not documented by this platform. | - |
| Gemini / Google AI Mode | Supported | Google documents UCP for merchants: native and embedded checkout with the merchant as merchant of record, built on existing Merchant Center shopping feeds. Post-purchase and returns are flagged roadmap, not shipped. | Source (opens in new tab) · verified 2026-09-18 |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Supported | Support for UCP-ready feeds in Microsoft Merchant Center is generally available in the US. Microsoft's path is feed-based rather than the well-known manifest Google describes. | Source (opens in new tab) · verified 2026-04-21 |
| Claude | Unknown | Not documented by this platform. | - |
Evidence and sources
This signal is typed spec-fact (Very high confidence).
How to act on this
For Google, publish an unauthenticated /.well-known/ucp profile with real capabilities and signing keys, and back any capability you declare with an endpoint that answers. For Copilot, send UCP-ready feeds through Microsoft Merchant Center instead. Do not build against post-purchase order tracking yet: Google lists it as roadmap, not shipped.
Related checklist items
Handbook chapters