Agentic Commerce
for E-Commerce Merchants

AI agents are taking over product discovery, advice, and checkout. What this means concretely for online shops — and what you should be preparing now.

Agentic Commerce — AI agent between customer and online shop
Why now

Three movements reshaping the sales channel — sourced, as of September 2026.

January 2026
Universal Commerce Protocol launched
Google with Shopify · ucp.dev
March 2026
Shopify Agentic Storefronts
ChatGPT, Gemini, Copilot, Meta · Shopify Help Center
June 2026
Shopware: full MCP coverage and UCP readiness
Shopware Community Day 2026

The shopping context is shifting faster than most merchants notice day-to-day. Today customers still type "Which hiking boots keep water out at freezing temperatures?" into a search engine and click. Tomorrow they ask Claude, ChatGPT or an assistant embedded directly in the storefront — and it decides which shop delivers the answer. This is not the next search evolution. This is Agentic Commerce.

What is Agentic Commerce?

Agentic Commerce describes shopping interactions where an AI agent — an LLM with tool access — sits between the customer and the shop. The agent understands natural-language queries, searches product catalogs semantically (vector embeddings instead of keyword match), aggregates offers across shops and, if needed, executes the checkout itself. Behind it stand open protocols such as the Agentic Commerce Protocol (ACP) — driven by OpenAI and Stripe — and the Universal Commerce Protocol (UCP), launched by Google with Shopify, which covers the path from search to order. Since March 2026 Shopify has connected shops to ChatGPT, Gemini, Copilot and Meta through Agentic Storefronts; in ChatGPT, the purchase completes in the shop's own checkout. In June 2026 Shopware announced full MCP coverage and UCP readiness.

Why does this hit e-commerce merchants now?

Short version: because visibility is tipping. Three shifts are accelerating it:

  • AI traffic is growing fast. Adobe counted almost five times as many visits from AI assistants to US retail sites in Q1 2026 as a year earlier, and still more than twice as many in May 2026. Consumers are increasingly delegating product research to agents.
  • Shopping widgets are becoming default UX. Embedded on the product page, in the header, in chat — AI answers service questions and sells within the same dialogue.
  • Conversion data is shifting. Semantic search and contextual recommendation are replacing facet navigation. Merchants without structured product data lose to merchants with it.

For online shops this means: the product catalog has to be machine-readable (clean taxonomy, structured metadata), the service FAQ has to be indexable, and a customer-facing AI layer belongs in the storefront — not in a separate support channel decoupled from conversion.

Where MEMOTECH stands

MEMOTECH has been building its own Agentic Commerce platform as a reference implementation since Q1 2026 — Swiss-based, Apache 2.0 platform foundation. Shopware 6 connects natively, any other shop software through its product feed; both read the catalog. We build cart and checkout inside your own shop on request; demos are available too, with your own product feed if you like. Technical details and measurements are published openly on the MEMOTECH Blog (English-language deep dives). If you want to understand the shift before it reaches your own conversion, the material lives there.

What an Agentic Commerce platform has to do

Four architecture principles against which every commerce-AI solution should be measured.

Multi-agent instead of monolith

Specialized agents with clearly scoped roles (e.g. search, recommendation, service FAQ, post-purchase, demand forecast) perform more reliably than a single chat assistant attempting everything at once.

Open protocols

ACP (Agentic Commerce Protocol) and UCP are the emerging standards. Platforms that support both stay connectable to external agents — proprietary SaaS APIs do not.

Platform-native, not parallel

Product catalog sync, storefront widget, and FAQ indexing dock cleanly onto the existing shop infrastructure — instead of creating duplicate data and broken checkouts. Shopware 6 connects natively, any other shop software through its product feed.

Tenant isolation as architecture

Customer data from different shops must never touch inside the vector index. Hence one collection per shop instead of a shared index with a filter: a forgotten filter silently returns another shop's products, a wrong collection fails loudly.

In practice

Six use cases that matter in the next twelve months

Concrete agent capabilities that decide whether e-commerce merchants stay visible — or get filtered out of the next generation of search.

Semantic product search

"Hiking boots that keep water out at freezing temperatures" finds the right product — even without exact keywords. Vector embeddings instead of facet navigation.

Recommendation agent

Contextual recommendation in checkout instead of static "also bought" boxes. Considers cart, season and availability.

Service FAQ agent

Shipping, returns, size charts answered directly inside the storefront widget — no support ticket needed. Indexes the existing FAQ.

Post-purchase agent

Order status, tracking, returns as a conversational flow — relieves the service team and keeps the customer in the brand context.

Demand forecast from queries

Query patterns become signals for sourcing and bundle pricing. Visibility into what customers are looking for — before they buy.

Cross-shop bundle

Multi-storefront setups (e.g. B2B + B2C) sharing one agent layer. Consistent answers across every brand touchpoint.

What we build on

Open standards, documented architecture

Platform foundation on Apache 2.0. We rely on open protocols (ACP, MCP) and tool-neutral components — no SaaS black-box APIs, no proprietary data formats.

OpenAI ACP
Agentic Commerce Protocol
UCP
Universal Commerce Protocol
Stripe
Payment layer
Shopware 6
Native catalog connector
Product feed
Any shop software
MCP
Model Context Protocol
Apache 2.0
Open-source foundation

Comparison of the six protocols relevant to agentic commerce — spec and repo linked directly.

As of: September 2026 — snapshot.

ProtocolInitiatorPurposeCore capabilitiesStatusShopware relevanceSpec / Repo
AXPAgentic Commerce Lab (Hamann-led)Agent-experience layer for storefrontsProduct Data · Quality Signals · Experience EmbeddingDraft (January 2026)Watch — community draft
A2ALinux Foundation (started by Google)Agent-to-agent communicationAgent Discovery · Message Routing · OSSStable, v1.0 (April 2026)Medium — multi-agent setups
ACPOpenAI + StripeAgent-to-merchant transactionCatalog Exposure · Cart API · Checkout HandoffBetaMedium — ChatGPT channel
UCPGoogle with Shopify, Tech CouncilCommerce journey from search to orderCatalog Search · Cart · Checkout · Identity Linking · Order ManagementIn development, Apache 2.0High — Shopware UCP-ready
AP2Google, standardisation at FIDOAgent payment authorisationPayment Auth · Tokenisation · Google-Pay flowv0.2 (announced September 2025)Medium — Google-Pay flows
Store SyncPayPalAgentic shopping via PayPal Commerce PlatformProduct Discovery · Cart Management · Checkout CompletionProprietary, PayPal Commerce PlatformSelective — for PayPal-driven stores
docs.paypal.aiProprietary

Adjacent: NANDA (MIT — agent discovery, early research) and x402 (Coinbase — Web3 payments) sit outside the Shopware mainstream and are not listed here.

Decision guide

Which path fits your shop?

Three paths to Agentic Commerce — depending on your IT team, budget and ambition.

Assess

Audit before you invest

One-time CHF 980–7'200

Before you invest in a solution: we assess whether an off-the-shelf solution is enough or building your own pays off. We analyse your data, conversion paths and use cases, independent of your shop software.

→ Written recommendation with sources, methodology and risk analysis

See the audit

If you already know where you are heading

Rent

Off-the-shelf solution

You want to go live fast and don't need your own development team for it. An off-the-shelf solution is enough as long as AI is not what sets you apart. Suitable vendors by size: Shopware Copilot or Algolia to start, Nosto or Klevu for mid-market, Bloomreach for enterprise. Vendor-independent: we receive no commissions from any of the vendors named.

→ 2–6 weeks integration, then monthly fees to the vendor. The intro call is free and points you to the right path; the sourced vendor recommendation is part of the audit

Book an intro call
Build

Your own agentic platform

Priced by scope, plus ongoing AI costs

You have in-house IT, budget for a multi-month build and a reason to stay in control: compliance, brand risk or AI as a genuine differentiator (e.g. B2B configurators, regulated industries).

→ 3–6 month build on open standards (ACP, UCP, MCP) and an open-source foundation (Apache 2.0). AI operation in Switzerland: under assessment

Book an intro call
MEMOTECH Newsletter

Agentic Commerce updates straight to your inbox

New articles and measurements from commerce-AI practice. GDPR-compliant, unsubscribe any time.

Looking for the full archive? All articles on the MEMOTECH Blog →

Agentic Commerce for E-Commerce Merchants | MEMOTECH