Tony Wood examines how merchants must redesign their commerce stack for agent customers. OMS, CRM, fulfilment, and support as trust interfaces in agentic commerce..
| Dimension | Traditional UX | Agentic Experience Design (AXD) |
|---|---|---|
| Primary material | Attention and affordance | Trust and delegation |
| User state | Present, navigating | Absent, delegating |
| Design output | Screens and interfaces | Outcomes and constraints |
| Temporal model | Session-based | Relationship-based |
| Success metric | Task completion | Trust calibration |
The organisational transformation required for agentic commerce is as significant as the technical transformation. Merchants need: new roles (agent relationship managers, trust infrastructure engineers, machine-readable data specialists), new KPIs (agent conversion rate, agent trust score, API response time, SLA compliance rate), new training (staff must understand how agents evaluate merchants and what trust signals matter), and new processes (agent-initiated orders follow different workflows t
Becoming agent-ready is not a strategy decision. It is a systems integration challenge. The merchant's existing commerce stack - the order management system, the customer relationship platform, the enterprise resource planning system, the fulfilment infrastructure, the support operation - was built for human customers. Every workflow, every data model, every integration point assumes a human being who browses a website, fills a checkout form, receives a confirmation email, and contacts support when something goes wrong. When the customer is an This essay examines the merchant's commerce stack through the lens of The commerce platform is the merchant's primary interface with the market. Shopify, Magento, Salesforce Commerce Cloud, BigCommerce, and the growing ecosystem of headless commerce platforms all share a common assumption: the customer interacts through a browser. The storefront is a visual interface. The product catalogue is designed for human browsing. The checkout flow is a sequence of web forms. The API layer, where it exists, was built for internal integrations and mobile apps - not for autonomous agents making purchasing decisions. Agent-ready commerce platforms must expose a fundamentally different interface. The product catalogue must be available as structured, machine-readable data - not HTML pages with embedded product information, but API endpoints that return specifications, pricing, availability, return policies, trust credentials, and fulfilment SLAs in a format that agents can process programmatically. The The platform integration challenge is not merely technical. It is a trust design challenge. The data that the commerce platform exposes to agents must be accurate, current, and verifiable. An agent that queries a product's price and receives stale data will make a purchasing decision based on incorrect information. An agent that queries availability and receives an optimistic estimate will commit its principal to a purchase that cannot be ful