Skip to content
Universal Commerce Protocol Protocol registry / en
The UCP standardUCP vs ACPImplementAgentic commerceFramework
ConceptGEOllms.txtGlossaryAgentic paymentsAP2Visa and MastercardB2B agentic commerceMethodologyUse CasesWhy NowFor WhomManifestoFAQResourcesSourcesEcosystemValidatorAboutContact
FR Get in touch →

Use Cases

Six scenarios, six business types.

Each scenario describes the starting setup, the agent involved, what the UCP framework unlocks, and the asymmetric risk of not being ready.

01 DTC

DTC brand with a dedicated catalog

Single-brand retailer, 200 to 2,000 SKUs, Shopify or custom commerce stack.

Agent scenario

A replenishment assistant (home or business) such as ChatGPT tasks, Operator or Copilot receives a recurring intent: "order my coffee filters, size M, before Friday."

What UCP unlocks

  • Typed product attributes (sizes, materials, compatibility) readable by agents.
  • Price, availability and geographic eligibility exposed deterministically.
  • Agentic payment compatible with recurring intents and cadence-based limits.

Risk without readiness

Without a proper semantic layer, the brand gets substituted by a competitor with better indexing.

02 Omnichannel retail

Multi-store retailer, click-and-collect

Catalog with 300K SKUs, centralized PIM, network of physical stores.

Agent scenario

A travel or home assistant combines purchase intent with geographic constraints: "available today within 5 km."

What UCP unlocks

  • Per-store availability exposed in near-real-time.
  • Typed return and reservation policies.
  • Audit of agent refusals (stock, zone, eligibility) for executive review.

Risk without readiness

An agent ignores the offer when availability is not retrievable, even if the product is physically in stock.

03 Marketplace

Marketplace with third-party sellers

3P model, seller integration via API, internal curation rules.

Agent scenario

External agents (e.g. Operator, Perplexity Shopping) want to compare identical offers across sellers.

What UCP unlocks

  • GTIN normalization + offer per seller with explicit policies.
  • Machine-readable seller trust scoring (delivery, support).
  • MCP surface for post-purchase recommendations and dispute management.

Risk without readiness

Variant ambiguities mean the agent picks an offer at random, often the cheapest, penalizing premium sellers.

04 Commerce SaaS

Commerce SaaS platform (B2B vendor)

Vendor serving thousands of merchants (PIM, CMS, OMS, checkout).

Agent scenario

Merchant clients' agents need a homogeneous rail to be agent-ready without custom development.

What UCP unlocks

  • MCP exposure packaged as a native feature.
  • Policy engine template delivered with gradual rollout.
  • Agent intent observability on the merchant side.

Risk without readiness

A vendor that fails to expose this layer becomes an obstacle to its clients' readiness and loses ground in RFPs.

05 Payments

Payment platform / acquirer

PSP, acquirer, card network or BNPL seeking positioning against Stripe ACP / Visa IC.

Agent scenario

Payment agents need typed intents and stable agent identity to lift limits.

What UCP unlocks

  • Standard intent envelope, compatible across multiple rails.
  • Agent-aware risk scoring (delegation, limits, revocation).
  • Merchant SDK to transform an existing checkout into agent-compatible.

Risk without readiness

Getting outflanked on the recurring delegated payments segment.

06 B2B

B2B distributor / wholesale

Technical catalogs, negotiated pricing, quotas and contractual commitments.

Agent scenario

A procurement agent on the buyer side automates replenishment under budget constraints.

What UCP unlocks

  • Per-client typed offers (contract price, quota, lead time).
  • Agent decision traceability, integrable with the buyer's ERP.
  • Pre-authorization for recurring orders with thresholds and signatures.

Risk without readiness

Losing accounts at the first supplier portfolio restructuring by a procurement agent.

What the six scenarios have in common

The configurations differ; the protocol constraint does not. Three points recur across every scenario, and they are written into the specification rather than inferred from the market.

The Merchant of Record never changes. Whatever the agent, whatever the surface, the merchant is the one selling. UCP's Checkout capability states this, and adds that it introduces no PCI DSS compliance obligation for card payments. The disintermediation debate is therefore about visibility and customer relationship, not about losing seller status.

An agent's degree of autonomy is decided in exactly one place. An order must be finalized manually by the user through a trusted UI, unless the AP2 Mandates extension is supported. Automatic replenishment or recurring purchase therefore presupposes mandates. Assisted discovery does not.

Business friction has a dedicated state. A checkout session moves through incomplete, requires_escalation, ready_for_complete, complete_in_progress, completed or canceled. Age verification, signature thresholds, supporting documents, pricing exceptions: all of it lives in requires_escalation instead of breaking the journey. That is what makes regulated and B2B scenarios workable.

Source: UCP specification, Checkout capability, version 2026-04-08. For the B2B breakdown, see B2B agentic commerce.

Choose a scenario

Your case is not listed?

These six scenarios cover the most common configurations. For a specific positioning (luxury, pharma, regulated marketplace, service platform), a short diagnosis can anchor the framework to your precise value chain.

Request a diagnosis