fk✳Fredrik
Kridahl
EN / SV
PROTOCOL WATCH · REVIEWED 7 NOV 2026

The interface is evolving. The merchant still matters.

A decision-oriented introduction to ACP and UCP. Use the official specifications to investigate capabilities, eligibility and responsibilities for a specific integration.

· Perspective & practice
PRODUCT VARIANTAurora Air 141.2 kg · 16 GB · €1,100Fictional product
01 / CUSTOMER INTENT

“A lightweight laptop for work trips.”

↗
03 / EVIDENCE

Right specification. Right variant.

04 / OFFERSeller + stock✓ Verify delivery
✳+
ILLUSTRATIVE JOURNEY · NO LIVE DATA
01 / Commerce protocols

Read the specification at the capability level

OpenAI documents the Agentic Commerce Protocol and a checkout specification for exchanging checkout state with merchants. The Universal Commerce Protocol describes a framework for discovering and negotiating commerce capabilities. These documents describe interfaces; they do not prove that every merchant or market has a live integration.

TopicWhat to verify
DiscoveryHow product and merchant information is made available.
CheckoutSession state, final totals, eligibility and customer authorization.
PaymentsSupported payment methods, provider responsibilities and failure handling.
After purchaseOrder events, customer service, delivery and returns.
02 / Commerce protocols

A feed and a transaction are different projects

OpenAI’s product-feed documentation distinguishes product discovery from separately enabled checkout. Treat feed preparation, merchant onboarding and transactional integration as distinct workstreams with their own acceptance criteria.

Before committing engineering time, verify the target platform, market, access requirements, supported capabilities and current specification version. An attractive demo may depend on conditions that do not apply to your business.

03 / Commerce protocols

Prepare the parts that stay useful

Accurate product identity, reliable offer information and clear operational ownership are useful across integration choices. Map the systems that hold prices, stock, taxes, shipping and order state. Decide which system is authoritative and how conflicts are resolved.

  • ↗Write an explicit customer-authorization and error-recovery journey.
  • ↗Test retries, duplicate requests and changed totals in a safe integration environment.
  • ↗Revisit official documentation before every implementation decision.
SOURCES & FURTHER READING

Original documentation and published evidence. The working approach and priorities on this page are editorial recommendations, not platform guarantees. Reviewed 7 November 2026.

OpenAI · Commerce documentation↗OpenAI · Checkout specification↗Universal Commerce Protocol · Specification↗OpenAI · Product feed specification↗