Adobe Commerce Is Now Agentic Commerce — Here's What That Actually Means
Recent deep dives into digital commerce trends, along with extensive discussions with enterprise clients, partners and Adobe product teams, have highlighted a crucial shift. These collaborative exchanges have revealed two key insights, and their connection is significant.
The first conclusion is nearly revolutionary: the buying journey is shifting away from your storefront. Instead, it now starts in ChatGPT, Claude, Gemini or whatever AI assistant your customer is using when they are looking for something.
By the time they reach your product page, if they reach it at all, an agent has already shortlisted options, compared pricing and formed a recommendation.
The second conclusion, while less radical, might be even more surprising: many enterprises still don't know what to do with the platform they already have. Years of layered customizations, multi-brand, multi-region… Companies want to innovate; the ambition is real, but they're at a fork in the road with no clear direction. Common questions arise: Do we replatform? Do we optimize what we have? Do we go headless? Do we wait?
These two conclusions kept colliding. But Adobe's new solutions aren't just about the agentic future. They were, intentionally or not, also an answer to many companies’ platform questions.
This is important for any enterprise feeling stuck and uncertain about the next steps. The solution is becoming more apparent: you don't need to fix your entire platform before beginning to build for the agentic era. You can add new layers gradually. Start with the discovery surface. Progress in the right direction without committing to a two-year replatforming overhaul.
Unlocking Your Agentic Future
As search behavior changes, with over 60% of Google searches being zero-click in 2025, Adobe Commerce’s new capabilities appear to be purpose-built to help businesses maintain relevance in a crowded market. Several key product advancements indicate that Adobe Commerce’s agentic capabilities are about to become much more powerful, and the impact could be huge:
Product Discovery & AI-Ready Catalog Data
These features will be native capabilities that help automatically enrich product data quality, generate structured feeds for LLMs and search engines and ensure product detail pages are AI-ready without storefront changes. This is the SEO discipline of the agentic era and structured, enriched, machine-consumable catalog data is the new ranking signal.
UCP & ACP Protocol Support — From Visibility to Execution
Adobe committed to supporting Universal Commerce Protocol (UCP) and Agentic Commerce Protocol (ACP), cross-platform protocols from Google and OpenAI that enable brands to gain visibility across AI-driven shopping channels while maintaining control over customer relationships, first-party data, branding and commerce data. This crucial support allows companies to maintain quality, brand identity and messaging while still participating in the faster-paced agentic era.
Brand Concierge — Conversational Commerce on Your Storefront
The upcoming Adobe Commerce integration with Brand Concierge brings conversational shopping experiences directly to the storefront, with real-time catalog data, accurate pricing and inventory and AI-powered conversations that guide shoppers from questions to purchase, providing additional control for brands at critical touchpoints.
Commerce MCP Server — Your Instance as an Agentic Surface
The new Adobe Commerce MCP server gives developers secure, real-time access to core commerce data and capabilities, essentials like catalog, cart, pricing, inventory, promotions, checkout, order management and post-purchase flows, enabling merchants to build a variety of agents, like shopping assistants, voice agents, upsell agents and more.
The Impact on Architecture
If we take a step back and look at these releases as a single coherent picture rather than a feature list, there's a pattern. These aren't just four separate features — they're four layers of the same architecture.
Product discovery and AI-ready catalog data addresses the top of the funnel, making sure your products exist, accurately and structurally, in the surfaces where AI agents are doing research.
UCP and ACP protocol support addresses the transaction layer, making sure that when an agent is ready to act, your Adobe Commerce instance can respond, execute and fulfill without a human in the loop.
Brand Concierge addresses the owned-experience layer, bringing conversational intelligence directly to your storefront for shoppers who land there.
The Adobe Commerce MCP server ties it together at the integration layer, exposing your catalog, cart, pricing, inventory and order flows as callable capabilities to any agent or system that needs them.
Adobe’s Agentic Future for Business
What will this new, layered architecture mean in practice? Commerce architecture conversations need to change.
For years, the core questions were about the storefront: headless or not; PWA or EDS; monolith or composable. These questions are still relevant because owned experience continues to drive conversion and loyalty. But the perimeter of what you're architecting for has expanded.
Machine-readable catalog data is now a first-class requirement rather than a “nice-to-have.” Organizations need a position on agentic protocols, including UCP and ACP, as well as others like MCP, just as they once needed a position on REST versus GraphQL. And if you're running a global or multi-brand operation, the platform choice, ACCS, Adobe Commerce Optimizer or a hybrid, directly determines how quickly you can activate these layers without starting from zero.
Enterprises that treat this as a standard platform upgrade cycle will fall behind, but companies that view these advancements as an architectural inflection point will have a head start. Having meaningful conversations about your or your client’s agentic capabilities and readiness today is how you position yourself to thrive in an agent-driven future.
