ACP vs UCP
Which commerce integration path matches your target surface?
Both address commerce interactions, but matching their labels is not enough. Compare released operations, merchant onboarding and the enabled provider implementation. Choose a target surface, then map its documented data and checkout route to your existing platform. An ACP feed approval and a UCP profile solve different pieces of the merchant onboarding problem.
What this establishes
A practical way to inspect evidence and make the next merchant decision.
What it cannot establish
An unresolved dependency remains. Treat affected claims as provisional. Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
The overlap
Both address commerce interactions, but matching their labels is not enough. Compare released operations, merchant onboarding and the enabled provider implementation.
The merchant decision
Choose a target surface, then map its documented data and checkout route to your existing platform. An ACP feed approval and a UCP profile solve different pieces of the merchant onboarding problem.
Where they overlap.
Where they complement.
Compare roles and implementation work. A shared capability does not make two systems interchangeable.
| Decision dimension | ACP | UCP |
|---|---|---|
| Layer | Commerce | Commerce |
| Role | Defines commerce interactions; OpenAI also documents structured product feed ingestion. | Connects catalog, cart, checkout and related commerce capabilities across implementations. |
| Status | beta specification | released |
| Version | 2026-04-17 · repository identifies specification as beta | 2026-08-25 |
| Discovery | Product feeds documented | /.well-known/ucp profile; optional catalog capability |
| Checkout | Specified; merchant deployment conditional | Commerce checkout capability |
| Payment | Handler integration; not itself a payment network | Payment handlers; complements authorization protocols |
| Authorization | Integration-specific; confirm chosen flow | Can work with AP2; capability-specific |
| Transport | HTTP APIs; released repository includes MCP work | REST, MCP and A2A bindings documented |
| Adoption | Public spec and partner access docs; store-level use not inferred | Google and Shopify describe scoped implementations |
| What it does not solve | Does not guarantee ChatGPT placement or automatic merchant approval. | Does not make every declared capability live on every shopping surface. |
| Evidence | 6 source record(s) Checked 2026-09-28 public-preview; scope-dependent | 5 source record(s) Checked 2026-09-28 live; scope-dependent |
Unknown ≠ unsupported. Announcements and product documentation are not proof of your live integration.
Overlap and replacement risk
These entries occupy a related layer. Test their exact operations, data paths and eligibility before treating one as a substitute. Keep your source of product truth, fulfillment responsibility and payment obligations explicit.
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Specification version and scope
Latest stable shown as 2026-04-17; development branch is not a release.
Claim scope: Structured catalog and inventory ingestion for ChatGPT
Claim scope: Product feed access
Approved partners; file and API delivery. This is not evidence of universal checkout availability.
Claim scope: Full snapshot feed delivery
At least daily delivery recommended; not a scanner protocol endpoint.
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: 6b58fb81a436890ede612af94779b0b60a127d95aa0a44b8179d20bb605ca8ea
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: a427ed74696286be7804bb3a4c5dc4c9461b4862da1ed461eeb3e723b03bca9a
Claim scope: Discovery profile and commerce capabilities
Version-pinned profile discovery; declared capabilities do not prove successful transactions.
Claim scope: Commerce semantics and interoperability
Claim scope: UCP merchant integration hub and AI performance insights
US rollout; later markets are future plans. Scale/performance statements are Google claims.
Claim scope: Developer UCP and Catalog access
Self-serve developer access. Conversion metrics in the article are vendor claims, not our results.
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: a554d5a172bb62d0d22abda152b99817fddd9735f434866d1c49863274dc049c