UCP Implementation
Checkout moved into the answer box. Make your stack answer.
The Universal Commerce Protocol puts product discovery and purchase inside Google Search, AI Mode, and Gemini — with your commerce stack doing the selling. We implement the feed, the callable checkout, and the liability plumbing underneath it.
Where we add value
UCP is an integration contract, not a traffic channel.
Read it as marketing and you will staff it like a campaign. It is 3 mechanical commitments — your catalog becomes a feed contract, your checkout becomes a callable capability, your business rules become things an agent can discover — and it lands on engineering. We do that part.
20+
Retailers, networks, and processors behind UCP at its January 2026 launch
Oct 2026
Salesforce Commerce Cloud UCP checkout general availability
3
Transports the spec supports: REST, MCP, and A2A
Services
Eight pieces of a working UCP integration.
From feed hygiene you can start this week to the dispute playbook you want settled before the first agentic chargeback.
UCP readiness assessment
A stack audit against the spec at ucp.dev: can your catalog feed cleanly, can your checkout be called as a service, where your customizations block the integration. A written map before any build.
Merchant Center catalog feed
The feed contract done properly — attribute coverage, variant mapping, price and availability freshness. Agents can only sell what the feed describes accurately.
Agentic checkout implementation
Exposing checkout as a callable capability on Shopify Plus, Salesforce Commerce Cloud, or a headless build — including the embedded option that keeps your tested flow in the loop.
Discovery profile design
The capability declaration agents negotiate against: payment options, fulfillment promises, and what your storefront supports, over REST, MCP, or A2A.
AP2 payments and dispute readiness
You stay merchant of record, so fraud and chargebacks stay yours. We wire the Agent Payments Protocol, the intent-evidence logging, and the dispute playbook with your finance team before the first agentic chargeback.
Agent traffic management
Your bot defenses were built to block automated buyers; UCP asks you to admit some of them. Edge policy that tells a UCP agent from a scraper without opening the door to either.
Inventory and promotion truth
A committed agent checkout against stale availability is a cancellation, and cancellations in an agent journey are trust you do not get back. Real-time availability and promo state in front of the agent.
Agentic-order observability
Agent-originated orders get their own dashboards — conversion, cancellation, return rate, margin — because the first quarter of data decides whether this channel earns 2027 roadmap.
How Destm runs it
Feed first, checkout second, disputes before they exist.
Readiness audit
2 weeks against the spec at ucp.dev: feed quality, checkout callability, customization drift, edge policy. Output is a written map with the go/no-go per piece.
Feed first
Catalog into Merchant Center — cheap, reversible, and it buys presence in agent discovery while the heavier work runs.
Checkout as a capability
Native activation on Shopify Plus / Commerce Cloud, or the adapter build on everything else. Volume-capped pilot before full traffic.
Operate and measure
Dispute playbook with finance, agent-vs-scraper edge policy, and separate dashboards for agent-originated orders. The first quarter of data decides the 2027 roadmap.
Stack coverage
No native UCP support is a gateway problem, not a lockout.
UCP is an open spec with flexible transports, so the integration path splits by platform — and the second path is ordinary integration engineering, which is our home ground.
Native path
The platform speaks UCP itself; the work is activation, feed quality, and keeping your checkout customizations inside what the integration expects.
- Shopify Plus — co-developed the protocol; Plus stores activate it directly.
- Salesforce Commerce Cloud — catalog feed GA now, UCP checkout GA October 2026.
Gateway path
A thin UCP gateway in front of the platform's existing catalog, inventory, and checkout APIs presents the discovery profile and callable checkout. Your platform keeps doing what it does today.
- Magento / Adobe Commerce — gateway over REST/GraphQL, promo logic stays put.
- BigCommerce — gateway over the management + checkout APIs.
- Custom & legacy stacks — the same facade seam a headless storefront or OMS integration already uses.
What you get
Benefits, by the desk they land on.
For the business
- Products purchasable inside Google Search, AI Mode, and Gemini — where agent-led buying starts
- You stay merchant of record: the order, payment relationship, and customer stay yours
- Early-mover position on an open protocol backed by 20+ retailers and networks
For engineering
- One protocol surface instead of a custom integration per AI shopping channel
- The embedded option keeps your tested checkout flow in the loop
- A checkout that can be called as a service — the same seam headless and OMS work already want
For operations
- Dispute and intent-evidence playbook settled before the first agentic chargeback
- Inventory truth in front of agents, so committed checkouts stop becoming cancellations
- Agent-order dashboards that keep this channel honest: conversion, cancellation, margin
Related
Questions
UCP for retail, answered
- Do we lose the customer relationship to Google?
- You keep the order, the payment relationship, and the service relationship, because you remain merchant of record. What you cede is the discovery moment and part of the presentation layer. Whether that trade is right depends on how much margin your PDP and cart currently carry — which is exactly what the readiness assessment prices out.
- Which platforms can you implement UCP on?
- Shopify Plus and Salesforce Commerce Cloud both speak the protocol natively — Shopify co-developed it, and Salesforce's integration reaches general availability in October 2026. Custom and headless stacks implement the spec directly; that is more work and more control.
- We're on Magento, BigCommerce, or a legacy platform with no UCP support — are we locked out?
- No. UCP is an open specification with flexible transports (REST, MCP, A2A), so a platform without native support gets a thin UCP gateway in front of its existing catalog, inventory, and checkout APIs. The gateway presents the discovery profile and checkout capability; your platform keeps doing what it does today. This is standard integration engineering — the same seam a headless storefront or an OMS connection already uses.
- Should a mid-market brand move before the big retailers prove it out?
- Do the catalog feed now: it is cheap, reversible, and buys presence in agent discovery. Gate the checkout integration on a pilot with volume caps and its own monitoring. Being 6 months behind Walmart on an open protocol is fine; being unable to move in 2027 because your checkout cannot be called as a service is the real risk.
How an engagement starts
Three steps to a partnership
Intake call
30 minutes. We listen, you talk. No deck.
Diagnostic
We audit the surface, name the bottleneck, propose a path.
Kickoff
Senior engineer in your standup by week two.