Four weeks ago, I was with Timm at Adobe’s Commerce Partner Days in Barcelona; one week earlier, I was at Adobe’s Commerce EMEA Tour for Partners in Munich. Adobe had already shown us under NDA what was now officially announced at Adobe Summit 2026 in Las Vegas. Early takeaway: Adobe Commerce is pivoting clearly — away from the isolated storefront system, toward an AI-first commerce infrastructure that also wants to win in foreign discovery channels.
This post is a condensed recap of what was announced at Summit, and of the four topics from it that will make a difference in my view. The official Commerce-highlights session is available on-demand. Deep-dives on individual products to follow.
What Adobe Commerce Announced at Summit 2026
The announcements group along two opportunities: AI-driven Product Discovery (visibility and actionability in LLM channels like ChatGPT, Gemini, Perplexity) and Elevated Owned Experiences (storefront, conversion, loyalty).
The most important new product building blocks:
- Commerce MCP Server – a Model Context Protocol server that accelerates the development of integrations and extensions around catalog, cart, pricing, inventory, promotions, checkout, order management, and post-purchase. Currently tightly coupled with the Commerce Integration Starter Kit, forming the ideal bridge for integrations built on Adobe AppBuilder.
- Commerce Developer Agent (coming soon) – an AI-powered tool suite that analyzes existing Commerce implementations, maps the migration path to Adobe Commerce as a Cloud Service (ACCS), and transforms legacy code and storefronts into event-driven apps and modern storefront components.
- Brand Concierge × Adobe Commerce – integration of the conversational Brand Concierge experience directly into the storefront. Shoppers get real-time catalog and inventory data in a chat interface; merchants gain visibility into what shoppers are searching for and how AI responds.
- B2B Drop-ins – new native components for complex B2B journeys: company account management, negotiable quote management, requisition lists, and purchase order workflows. Replaces custom builds previously required in many enterprise B2B scenarios.
- Native LLM visibility features – capabilities that ensure product data is structured and context-rich enough to be correctly interpreted and recommended in AI assistants.
- UCP / ACP Support – Adobe Commerce commits to Universal Commerce Protocol and Agentic Commerce Protocol as open standards, so AI agents don’t just recommend but can directly buy, track, and return.
- Partnerships with PayPal, Stripe, and Adyen – checkout standards and frictionless transactions in AI and marketplace contexts. PayPal extends its existing product-data and checkout integration to LLM-driven surfaces like Perplexity and Copilot.
Two building blocks from last year set the context: Adobe Commerce as a Cloud Service (ACCS) as the new cloud-native platform, and Adobe Commerce Optimizer (ACO) as a composable layer for mono-to-multi-storefront scenarios. All Summit 2026 announcements build on this foundation.
Four Topics That Left the Strongest Impression in Barcelona
From antegma’s perspective — we work daily on Adobe Commerce implementations — four building blocks stand out:
Commerce MCP is Adobe's Most Honest AI Bet
The Commerce MCP Server is, for me, the most significant announcement. The MCP standard (Model Context Protocol) accelerates the development of integrations and extensions that access Adobe Commerce core objects — the finished integrations then have the actual API access; the MCP server itself is a developer accelerator. Currently the server is tightly coupled with the Commerce Integration Starter Kit, forming the ideal bridge for integrations built on Adobe AppBuilder. We’re already using Commerce MCP in a live client project. Less hype, more concrete developer infrastructure — an accelerator for building ACCS extensions and integrations, not a customer-facing feature.
The Commerce Developer Agent Makes Migrations Calculable
Every Magento / Adobe Commerce migration to ACCS has been a risk-and-effort estimate with wide uncertainty. The new Commerce Developer Agent analyzes existing implementations, proposes a migration path, and progressively migrates legacy code into event-driven apps and modern storefront components. In Barcelona, we saw the Agent running hands-on against real migration projects. If quality holds up to the early-access demo, the ROI math on any migration shifts noticeably forward — not because the features become better, but because project risk and team hours come down measurably.
Brand Concierge Changes How Shoppers Start Product Discovery
The integration of Brand Concierge into Adobe Commerce means that conversational shopping experiences happen directly on the storefront — not in a third-party chatbot widget, but with real-time access to catalog, pricing, and inventory. From my perspective, this is the serious counterpart to the “shopping is moving to ChatGPT” trend: Adobe says discovery can also happen on your own brand, if your own experience is conversational enough. How well it gets adopted depends on two factors: product data quality and the merchant’s willingness to use shopper conversations as a learning source.
B2B Drop-ins Close an Enterprise Gap
The new B2B Drop-ins — company account management, negotiable quote management, requisition lists, and purchase order workflows — close an enterprise gap that previously had to be custom-built in almost every B2B project. We’re already using the drop-ins in the design of a live antegma client implementation. The productivity gain: developer teams focus on actual differentiation — pricing logic, approval hierarchies, ERP integration — instead of commodity features now coming out-of-the-box. For merchants with complex B2B operations, this is a concrete TCO lever, not just a feature announcement.
What This Means for E-Commerce Teams
For most Adobe Commerce customers we work with, two recommendations crystallize from these announcements:
- Product data quality becomes commerce infrastructure. If you don’t currently look at your product data layer in a structured way — attributes, categories, rich content, metadata — you won’t perform well in LLM discovery or in the Brand Concierge context. The topic moves out of the PIM / DAM silo and into the commerce-core responsibility. A structured audit of product-data readiness is the obvious next step, regardless of whether you’re already on ACCS.
- The migration calculation should be redone. If you’re still on Adobe Commerce 2.x (formerly Magento) or an older Commerce Cloud variant and have deferred migration on cost grounds: with the Commerce Developer Agent, the business case shifts meaningfully. We recommend triggering a fresh effort-and-risk estimate as soon as the Agent is generally available — ideally preceded by a migration-assessment phase.
What stays true: actual value creation doesn’t live at the feature level but at the setup level. Agentic commerce doesn’t fix poorly structured catalogs — it only scales their weaknesses.
Our Follow-ups
Because the topic has more substance than a single post can carry, we’ll publish deep-dives over the next weeks on:
- Commerce MCP in practice: which developer use cases and integration paths make sense first — with insights from our live client project
- B2B Drop-ins in action: what works out-of-the-box, where custom work is still needed
- Commerce Developer Agent: migration-readiness assessment for existing customers
- Product data readiness for LLM discovery — where most teams are stuck today
- Brand Concierge on your own storefront: setup, governance, measurability
The full Summit Commerce announcement is available on the Adobe Business Blog.
