THE BUSINESS CASE / SOURCES & CONTEXT
An emerging channel.
A reasoned decision.
The opportunity deserves attention. The investment still needs a business case grounded in your store, your customers and your platform.
Research reviewed 4 November 2026Primary sources linked below
01 / MARKET FORECAST$3–5TGlobal consumer-goods commerce
potentially orchestrated by agents in 2030.
McKinsey’s October 2025 scenario uses projected adoption and merchant-readiness assumptions. It excludes services and B2B.
How to read itA directional estimate of commerce volume. It is not a market capitalization, a current market measurement or a forecast of your store’s sales.
McKinsey · 17 October 2025 · Original report ↗02 / OBSERVED CUSTOMER BEHAVIOR+71%Year-on-year growth in AI-referred
U.S. retail visits in September 2026.
Adobe measures people clicking through from AI tools. Its October 2026 report draws on U.S. retail web activity.
How to read itA change in acquisition behavior, not a count of autonomous orders. The report does not establish that protocol adoption causes sales growth, or state AI referrals’ share of total traffic.
Adobe · 29 October 2026 · Original research ↗
WHAT THIS MEANS FOR YOUR BUSINESS
Prepare with a clear
commercial objective.
01Understand your exposure.
Look at how your products are discovered, which customers use AI-assisted journeys and what your platform already supports.
02Choose a bounded use case.
Agree whether the first objective is discovery, catalogue access or a supported commerce action. Select evidence that would make the work useful.
03Measure your own results.
Track implementation quality and technical compatibility separately from traffic, conversion and revenue. Review both before expanding the scope.
THE PROTOCOL LANDSCAPE
Different standards.
Different responsibilities.
These examples explain the landscape.
Your architecture determines which are relevant.
They are not a checklist every merchant must implement.
UCPCommerce capabilities
Catalogues, carts, checkout and order interactions through a common interface.
Official overview ↗ACPAgentic commerce interactions
Interfaces for commerce between agents and merchants, with versioned requirements.
Official project ↗AP2Payment authorization
Signed mandates help establish the user’s intent and authority for a payment.
Google’s explanation ↗A2AAgent coordination
Communication and task coordination across agents. It is not itself a checkout standard.
Official specification guidance ↗ WHY CONTINUOUS REVIEW MATTERSUCP’s 2026 release history includes new capability versioning and payment-related changes. Updates can affect an existing integration’s behavior and compatibility.
Official UCP release history ↗
AITHOS’S ROLE
Turn the landscape
into your roadmap.
We help you identify the relevant work, implement it with your team and maintain the resulting integrations.
The first conversation should clarify your platform, the use case you want to support, existing capabilities and who will own the ongoing work.
Read the executive brief ↗