Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    Adobe Commits Adobe Commerce to the Universal Commerce Protocol and Agentic Commerce Protocol

    On 18 February 2026, Adobe committed to supporting the Universal Commerce Protocol and Agentic Commerce Protocol for Adobe Commerce. Here's what these standards actually do, and what's real versus roadmap.

    Adobe Commits Adobe Commerce to the Universal Commerce Protocol and Agentic Commerce Protocol

    On 18 February 2026, Adobe announced that Adobe Commerce will support two emerging industry standards for AI-driven shopping: the Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP). It builds on a commitment Adobe had already made to Google's Agent Payments Protocol (AP2). In plain terms: Adobe is working to make merchant catalogues, pricing and inventory machine-readable in a standard way, so AI shopping agents (including ChatGPT and Gemini) can discover and eventually transact with Adobe Commerce stores directly, instead of merchants needing a bespoke integration for every AI platform that comes along.

    It's a sensible, if slightly reactive, move. None of these three protocols are Adobe's own invention, and none of them are Adobe Commerce features you can switch on today. This is a standards commitment, not a shipped product: the actual tooling came a couple of months later, at Adobe Summit (see our Summit 2026 recap).

    Three protocols, three different authors

    It's worth being precise about who's actually behind each of these, because none of them came from Adobe:

    • Agentic Commerce Protocol (ACP) was published by OpenAI and Stripe in September 2025. It governs the actual transaction layer (cart management, promotions, checkout and order fulfilment) for an AI agent acting on a shopper's behalf.
    • Universal Commerce Protocol (UCP) is Google's, launched on 11 January 2026 and developed jointly with Shopify, Etsy, Wayfair, Target and Walmart, with more than 20 further partners (including Visa, Mastercard, Stripe and American Express) signed up to it. UCP standardises how an AI agent discovers a merchant's catalogue, pricing and purchasing rules across different commerce platforms, and is explicitly designed to be compatible with AP2, Google's Agent2Agent protocol, and Model Context Protocol (MCP). It isn't a rival to those; it's meant to sit alongside them.
    • Agent Payments Protocol (AP2), also Google's, is the payment-authorisation layer underneath both: it uses cryptographic "mandates" (signed digital receipts) so a merchant can verify that a given transaction genuinely reflects what the shopper authorised an agent to do.

    So when Adobe says it supports "UCP and ACP," it's really saying: our stores can be discovered the way Google's coalition has standardised, and can be transacted with the way OpenAI and Stripe's coalition has standardised, not that Adobe built either of these.

    Why now

    The honest read is competitive pressure as much as conviction. Shopify had already been moving in this direction with its own agentic storefront work (see our piece on Shopify's agentic storefronts), and UCP itself launched with Shopify as a founding partner. If AI agents are going to become a meaningful shopping channel (and the protocol list above, with Visa, Mastercard and Walmart all signed up, suggests the industry is betting they will), no commerce platform can afford to sit outside the standards that decide whether its merchants are visible to those agents at all.

    What this actually means for merchants today

    Not much yet, and that's worth saying plainly rather than overselling it. Adobe's February announcement didn't ship a feature, an MCP endpoint, or a new setting in the admin. It's groundwork. The useful, usable thing merchants actually got came in April, when Adobe introduced the Commerce MCP Server at Summit: a real, specific piece of infrastructure that exposes catalogue, cart, pricing and checkout data in a structured way.

    If you're running Adobe Commerce, the practical takeaway for 2026 is: there's nothing to configure today, but it's worth keeping your product data clean, complete and well-structured, because that's the raw material any of these agent-discovery standards will eventually read from. We'll flag it clearly on the blog if and when UCP/ACP support becomes something you can actually turn on.

    Further reading

    Sources: Digital Commerce 360, Google's Universal Commerce Protocol announcement, agenticcommerce.dev.

    FAQ

    Do I need to do anything today to benefit from UCP/ACP support? No. There's no admin setting to enable yet. The best preparation is making sure your product data (titles, descriptions, variants, availability) is accurate and complete.

    Is this the same thing as the Commerce MCP Server? No. UCP/ACP are open, multi-vendor standards for discovery and transactions; the Commerce MCP Server is Adobe's own concrete implementation that exposes Commerce data to AI tools. The MCP Server is a step towards supporting protocols like these, not the protocols themselves.

    Does this work with ChatGPT and Gemini specifically, or any AI agent? Adobe has named ChatGPT and Gemini as target platforms, but because UCP and ACP are open standards rather than proprietary integrations, the intent is for any compliant agent to be able to use them.

    Last updated 20 February 2026.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.