On Friday just gone, five of the largest technology companies in the world quietly joined the governing body of the Universal Commerce Protocol. No press release. No blog post. Just a commit to MAINTAINERS.md in the spec repository.

Amazon. Meta. Microsoft. Salesforce. Stripe. All now have seats on the UCP Tech Council — the body that reviews, debates, and approves every change to the protocol that AI shopping agents use to buy things.

We know this because we read the meeting minutes. Every week, the TC meets to debate spec changes, vote on PRs, and argue about how agent commerce should work. Most people in the industry don't read these minutes. We do — and what they reveal about where UCP is heading is more interesting than any announcement.

This is what the minutes tell us.

The expansion: who joined and why it matters

The Tech Council grew from roughly 12 seats to 16 members across 8 companies:

This isn't ceremonial. The TC has binding authority over spec changes — every PR that ships in a UCP release has been reviewed and voted on by this group. When Amazon and Stripe join that table, it changes what gets prioritised, what gets debated, and ultimately what the protocol becomes.

The meeting minutes from March 13 first mentioned the election process: seats rotating every six months, with growing partner interest. By March 27, six nominations had been received. The final review was scheduled for April 10. The MAINTAINERS.md update landed April 24.

The new members are already contributing. James Andersen (Meta) submitted PR #367 on April 17 — a documentation PR clarifying network token usage and PCI scope in card credentials. Patrick Jordan (Microsoft) contributed documentation accuracy fixes the same day. These aren't advisory seats. They're engineering seats.

What the meeting minutes actually say

We reviewed the six TC meetings from March 6 through April 17. Here's what's being debated, decided, and built — translated for a merchant audience.

Identity linking is the top priority — and it's hard

The single most discussed topic across all six meetings is identity linking — how an agent knows who the customer is across sessions, stores, and platforms.

The April 17 minutes show an active debate about OAuth 2.0 scope design: nested scopes vs flat scopes vs config maps. The TC favoured flat. PR #354 implements OAuth 2.0 as the foundation for identity linking with capability-driven scopes.

Why this matters for merchants: Identity linking is the missing piece that would let an agent complete a purchase without a checkout-page handoff. Right now, agents can browse and cart — but paying requires redirecting the customer to a human checkout flow. Identity linking + payment handlers would close that loop. Until then, agents rely on the transport layer to reach the store and the manifest endpoint for discovery. Our April state-of-commerce report showed only 3 stores out of 4,024 currently declare identity linking capability. The spec work happening now is what will eventually bring that number up.

Loyalty is being trimmed to ship faster

The TC has been debating loyalty schemas since March. PR #340 implements a loyalty extension for the checkout capability. The April 10 minutes note that the extension is being "trimmed to baseline use cases" — a pragmatic decision to ship something that works for simple loyalty programs now, rather than waiting for a comprehensive solution that handles every edge case.

Why this matters: If your store has a loyalty or rewards program, the spec is building the infrastructure for agents to verify loyalty status and redeem points as part of the checkout flow. This is early — don't build against it yet — but understand that it's coming and it's being shaped by people at Google, Shopify, Etsy, and Target who run real loyalty programs.

Local commerce is on the roadmap

The April 3 minutes list Q2 priorities. Among them: local commerce. PR #375 proposes store-based local inventory and fulfilment options — the infrastructure an agent would need to answer "is this product available at a store near me?"

This is Target and Wayfair territory. Both have TC seats. Both have store networks. The fact that local commerce is a Q2 priority with retail representation on the council suggests it's not theoretical.

Returns are "incredibly complicated"

The April 17 minutes include the most honest assessment we've seen in any spec discussion: returns are acknowledged as an "incredibly complicated domain." This is refreshing. Most protocol specs pretend returns are simple. UCP's TC is saying out loud that they're not, and that getting them right will take time.

PR #257 from the February cycle introduced a returns extension. It's still in review. The complexity is in modelling return windows, refund methods, partial returns, and eligibility rules — all of which vary by merchant, product, and jurisdiction.

Why this matters: Don't expect agent-managed returns in 2026. But understand that the protocol is building toward it, and the merchants who implement return policies as structured data (not just PDF links) will be ahead when it ships.

The spec itself just shipped its biggest release ever

v2026-04-08 landed with 60+ merged PRs — the largest release since the protocol launched. Key additions:

• Cart capability — basket building for agents, a prerequisite for multi-item flows
• Catalog search + lookup — formalised product discovery as a spec capability
• Request/response signing — cryptographic integrity for agent-store communication
• Error handling overhaul — first-class errors, business logic error types
• Eligibility claims — for loyalty, membership, and verification-gated pricing
• Discount extension to cart — discounts now apply pre-checkout, not just at checkout
• Risk signals — authorization and abuse metadata for fraud prevention

Our crawler showed Shopify migrating its entire fleet to v2026-04-08 in four days. 99.4% of verified stores are now on the latest spec.

What this means for you

If you're a merchant

The governance expansion doesn't change what you need to do today. Your UCP requirements are the same: valid manifest, declared capabilities, clean variant data. Check your store, fix any common errors, compare against competitors, and set up alerts so you know if anything breaks.

What it does change is the timeline and the confidence. When Amazon, Microsoft, and Salesforce have engineering seats on the governing body, the protocol is not going away. If you've been waiting for a signal that UCP is "real enough" to invest in — five of the ten largest technology companies joining the TC in a single commit is that signal.

If you're a platform

If you run Shopify, you're covered — platform-level UCP support is mature. If you run BigCommerce, WooCommerce, Magento, or a custom stack, watch the identity linking and loyalty PRs. These are the capabilities that will differentiate agent-ready platforms from agent-compatible ones in H2 2026.

Salesforce Commerce Cloud now has a seat at the table. If you're on SFCC, this is the clearest signal yet that platform-level UCP support is coming. Our April report noted that we've already seen SFCC engineering work in progress.

If you're building agents

The Build an Agent quickstart still works — the protocol surface you're building against is stable. But start tracking the identity linking PRs. When that capability ships, the agent flow goes from "browse + cart + redirect to checkout" to "browse + cart + pay" — end-to-end autonomous purchasing. That's the step change.

Check the store leaderboard to find the highest-performing targets, understand how product discovery works, and test your agent against real stores in UCP Playground and use UCP Registry for production discovery. Both will surface the new capabilities as they ship.

The reading list

For anyone who wants to follow the protocol's evolution themselves:

• Meeting minutes: github.com/Universal-Commerce-Protocol/meeting-minutes
• Spec repo: github.com/Universal-Commerce-Protocol/ucp
• v2026-04-08 release notes: github.com/Universal-Commerce-Protocol/ucp/releases/tag/v2026-04-08
• MAINTAINERS.md: github.com/Universal-Commerce-Protocol/ucp/blob/main/MAINTAINERS.md
• Active PRs: github.com/Universal-Commerce-Protocol/ucp/pulls

We'll continue monitoring the spec, the TC minutes, and the 4,500+ merchants building on the protocol. If any of the Q2 priorities (identity, loyalty, local commerce) ship in spec form, we'll cover them in the May state-of-commerce report.

---

Check your store's UCP status at UCPChecker.com. Browse verified stores at UCPRegistry.com. Test agent performance at UCPPlayground.com. Read the full protocol stack: MCP vs UCP vs AP2.