THE SHORT ANSWER
The most useful AI commerce vocabulary separates product information from transaction capability and local validation from destination acceptance. These fifteen terms help merchandising, marketing and engineering teams discuss the same project without assuming that every green check means the same thing.
Product, variant, offer, feed and snapshot
A product is the underlying item a shopper recognizes. A variant is a purchasable selection such as a specific size and color. An offer adds a seller’s commercial terms to an item. A feed is a structured collection of records shared with a destination. A snapshot is the catalog state represented at a particular time.
These five terms answer different identity questions. Two sizes can belong to the same product while requiring distinct item records. The same item may have different offers from different sellers. A new snapshot changes data without necessarily changing any of those identities.
Discovery, checkout, capability, profile and transport
Discovery helps a shopper find and understand an item. Checkout is the transaction flow. A capability is a defined action a service supports. A profile describes supported services and capabilities. A transport is the mechanism used to communicate with them.
Do not use transport as a synonym for business capability. An endpoint being reachable does not prove that its checkout behavior works. In UCP specifically, capabilities and versions are declared and negotiated. Teams still need to test the behavior they intend to advertise.
ACP, UCP, mapping, enrichment and release
ACP is the Agentic Commerce Protocol associated with OpenAI’s commerce integration resources. UCP is the Universal Commerce Protocol. Mapping connects source fields to target fields. Enrichment adds or improves supported product detail. A release is a selected, versioned output prepared for use beyond the working draft.
These terms describe a path, not interchangeable certifications. A mapped file can still contain false facts. An enriched draft can still need approval. A released artifact can still be awaiting destination delivery or acceptance. Specify the state whenever a project update uses one of these words.
Turn the glossary into a working agreement
Put the definitions next to your project’s status vocabulary. Define imported, validated, approved, released, delivered and accepted separately. Ask each supplier or internal team to demonstrate what their use of ready means in that sequence.
Then apply the vocabulary to one real product family. This quickly reveals whether a disagreement is about language or about implementation. A shared glossary is most valuable when it prevents an unsupported assumption from becoming a purchase decision or launch promise.
ILLUSTRATIVE WORKED EXAMPLE
Make it concrete.
Illustrative meeting note: “The feed was imported and locally validated. Three descriptive enrichments remain pending. No release has been delivered. Checkout is out of scope.” This is more useful than “The catalog is AI-ready” because every team can identify its next action.
Your practical checklist
- Agree on product, variant and offer identity.
- Separate capability from transport.
- Define each release status.
- Ask what ready means in evidence.
- Use the glossary on a real variant group.
Common questions
Are ACP and UCP the same thing?
No. They are distinct protocol ecosystems and should be evaluated against the current official documentation and the capabilities your project needs.
Does enrichment mean AI-generated copy?
Not necessarily. It can involve mapping existing facts, extracting supported attributes or reviewing proposed changes.
Sources & scope
Official references checked 29 October 2026. Examples are illustrative, not customer results. Platform requirements can change; use current destination documentation for implementation decisions.
Our editorial method & corrections ↗