The Agentic Commerce Stack: Product Data, Discovery, Checkout, Payments and Fulfillment
The layers of agentic commerce, from shopping agent and discovery to product data, APIs, checkout, payments, orders and post-purchase, mapped to protocols.
Quick answer
The agentic commerce stack is the set of layers that let an AI agent shop for a person: the shopping agent, discovery, product data, the commerce API, cart, checkout, payments, order, fulfillment and post-purchase service. Protocols connect the agent side to the merchant side: UCP and ACP for commerce capabilities such as cart, checkout and orders, MCP as a tool and transport layer, and AP2 and network token programs for payment authorization.
Ownership is clear. Agent platforms own the agent and its interface. The merchant owns product data, prices, checkout state, orders and fulfillment, and stays merchant of record. Payment providers and networks own credentials and authorization.
The stack at a glance
AI SHOPPING AGENT assistant UI · intent · user rules
│
DISCOVERY search over catalogs and feeds
│ (Merchant Center, Shopify Catalog,
│ ChatGPT feeds, UCP catalog)
PRODUCT DATA IDs · variants · price · stock ·
│ shipping · policies
COMMERCE API REST · MCP tools · UCP / ACP adapters
│
CART UCP cart · ACP cart (2026-04-17)
│
CHECKOUT ACP checkout sessions · UCP checkout
│ (merchant state is authoritative)
PAYMENTS delegated tokens · payment handlers ·
│ AP2 mandates · network agentic tokens
ORDER order creation · signed webhooks
│
FULFILLMENT OMS · WMS · carriers · tracking
│
POST-PURCHASE status · cancel · return · refund ·
support (UCP order, ACP order events)Layer 1: the AI shopping agent
The agent interprets the shopper's intent, applies their constraints (budget, size, delivery date, preferred brands), compares options and presents choices and confirmations. It belongs to the agent platform (an assistant such as ChatGPT or Gemini, a retailer's own agent or a third-party app). Merchants do not control it, but they influence it through data quality, policies and how easily their checkout can be completed. How this changes the classic funnel is covered in how AI agents change the ecommerce funnel, and the business overview in agentic commerce and AI shopping agents.
Layer 2: discovery
Agents discover products through catalogs and feeds the platforms index (Google Merchant Center, Shopify Catalog, OpenAI's product feeds), through UCP catalog search on merchants that support it, and through web search and page reading. Visibility depends on eligibility, data quality and the platform's own ranking. Content and search visibility for AI answers are covered in making your site discoverable in AI search.
Layer 3: product data
Agents act on structured data: stable IDs that match checkout, per-variant options, price, availability, shipping, return and seller policies. This is the layer merchants control most directly and the one that most often decides success. See AI product feeds, product data for AI search and, for Shopify stores, Shopify agentic commerce.
Layer 4: the commerce API
Behind every agent channel sits the merchant's commerce logic: catalog, inventory, pricing, tax, cart, checkout, orders and returns. Build it once with agent-grade guarantees (typed schemas, idempotency, delegated authorization, signed webhooks) and expose it through protocol adapters and MCP tools. See agent-ready ecommerce API.
Layers 5 and 6: cart and checkout
Carts collect items; checkout sessions turn them into an order with authoritative totals, tax, fulfillment options and status. ACP and UCP both define checkout operations (create, update, retrieve, complete, cancel) with explicit statuses, escalation when the shopper must act and strict idempotency on completion. See agentic checkout and ACP vs UCP vs MCP.
Layer 7: payments
Payment authorization stays with payment providers, networks and issuers. Agent channels use scoped credentials (delegated or shared payment tokens, wallet credentials, network agentic tokens) and, increasingly, signed mandates that record what the user authorized. Keep agent authorization, purchase consent and payment authorization separate. See AI commerce payments.
Layers 8 and 9: order and fulfillment
Agent orders enter the same order management and fulfillment systems as any other order, tagged by channel. Signed webhooks keep the agent platform informed of creation, shipping and delivery; UCP defines an order capability with webhook-based updates, and ACP defines order and fulfillment event structures. Operations, fraud signals and confirmation accuracy for these orders are covered in orders placed by AI agents, and order flow design in ecommerce order management.
Layer 10: post-purchase
After purchase, the shopper may ask the same agent where the order is, to cancel a line or to start a return. That requires order lookup, cancellation and return capabilities with the shopper's delegated authorization, and clear handoff to human support when needed. See orders placed by AI agents and the ecommerce post-purchase experience.
Protocols and APIs mapped to layers
| Layer | Relevant protocols and interfaces | Owner |
|---|---|---|
| Shopping agent | Assistant UI; MCP Apps for in-chat UI | Agent platform |
| Discovery | Merchant Center, Shopify Catalog, OpenAI feeds, UCP catalog | Platforms index; merchant supplies |
| Product data | Feed specs; structured data on pages | Merchant |
| Commerce API | REST, MCP tools, UCP/ACP adapters | Merchant or commerce platform |
| Cart | UCP cart capability; ACP cart (2026-04-17) | Merchant |
| Checkout | ACP checkout API; UCP checkout capability | Merchant (authoritative) |
| Payments | ACP delegated payment; UCP payment handlers; AP2 mandates; network tokens | PSP, networks, issuers |
| Order | UCP order capability; ACP order events; webhooks | Merchant |
| Fulfillment | OMS, WMS, carrier APIs | Merchant and logistics partners |
| Post-purchase | Order lookup, cancellation, returns APIs; support handoff | Merchant |
Worth noting
Protocol versions referenced here were checked on 8 October 2026 (ACP 2026-04-17, UCP 2026-08-25). Expect changes; build to capabilities and keep protocol adapters thin.
Measuring agentic commerce
Measurement spans layers: AI referral traffic to your site, orders placed inside assistants, assisted journeys that end on your site, and post-purchase outcomes such as returns and support contacts by channel. See tracking AI-referred ecommerce sales for a reporting framework.
Where to start
- Fix product data: IDs, variants, prices, availability, shipping, policies
- Turn on the agent channels your commerce platform supports, deliberately
- Make order operations ready: channel tagging, fraud tuning, confirmation accuracy
- Build or upgrade your commerce API with agent-grade guarantees
- Add protocol adapters (ACP, UCP) and MCP tools where channels justify them
- Support scoped payment credentials through your PSP
- Measure by channel, including returns and support
Planning your store's agentic commerce roadmap?
ZSpace Labs works on product data, commerce APIs, checkout integrations and order operations for Shopify and custom stores. See Shopify development and CRO.
Conclusion
Agentic commerce is not one technology but a stack. Agent platforms own the conversation; merchants own data, checkout, orders and fulfillment; payment systems own authorization; and protocols connect them. Strengthen the layers you control, starting with product data and order operations, build commerce capabilities once behind your own API and adopt protocols as your channels require.
Common questions.
The set of layers that let an AI agent shop on a person's behalf: the shopping agent, discovery, product data, the commerce API, cart, checkout, payments, order management, fulfillment and post-purchase service, with protocols such as UCP, ACP, MCP and AP2 connecting them.