The Argument
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 navigating visual interfaces. Every integration point between the merchant and the agent customer is a trust interface: a point where trust is established, maintained, or broken. The essay examines the merchant's commerce stack through the lens of agentic experience design, arguing that each system component must be redesigned as a trust interface rather than merely exposed as an API endpoint.
The Evidence
The essay maps six stack components. Commerce platform integration requires structured product data, real-time inventory APIs, and machine-readable pricing - the foundation on which all agent interactions depend. Order management must handle agent-initiated orders that arrive without a browsing session, without a cart accumulation phase, and potentially without a human in the loop at all. The OMS becomes the point where the merchant's operational envelope meets the agent's delegation scope.
CRM must be reconceived: when the customer is an agent, the CRM must track both the agent entity and the human principal behind it, maintaining relationship history across multiple agents acting for the same human. Fulfilment and logistics must provide machine-readable status updates, predictable delivery windows, and API-accessible exception handling. Customer support must adapt to handle agent-to-agent support interactions where the "customer" is a machine following programmatic escalation protocols. The essay concludes with change management - the organisational transformation required to shift from human-centric to agent-ready operations, arguing that the technology changes are the easy part and the cultural and process changes are where most merchants will struggle.
The Implication
The merchant's stack is not a technology problem. It is a trust architecture problem. Every system in the stack - OMS, CRM, ERP, fulfilment, support - is a trust interface that either builds or erodes the agent's confidence in the merchant. The merchants who approach agent-readiness as a series of API integrations will build fragile, inconsistent experiences. The merchants who approach it as a trust architecture redesign - where every system component is evaluated against its contribution to agent trust - will build the durable, compounding relationships that define commercial success in the agentic economy. The stack audit is not optional. It is the first step.