Retail agents must be allowed to take payment

Retail gets no value from yet another polite chatbot. Value comes when the agent can see product data, understand inventory, choose the right channel and actually complete the purchase with controls around it.

Google moved this from demo to infrastructure in January with Universal Commerce Protocol, built on top of Agent Payments Protocol. UCP will power checkout in AI Mode and Gemini, and was developed with Shopify, Etsy, Wayfair, Target and Walmart. Retailers need to treat AI surfaces as sales channels, not just traffic sources.

Microsoft made the other half more production-ready in April: Copilot Studio multi-agent orchestration became GA, with support for Fabric agents, Microsoft 365 Agents SDK and A2A. On May 1, Microsoft made Agent 365 GA as the control plane for observability, governance and security around agents. That part is boring. That is why it matters.

What I recommend now:

• Start with one agent for “find the right product + check availability + suggest an alternative”. Do not let it write poetic product copy. Let it reduce lost sales.
• Connect the agent to PIM, inventory and order status with read access first. If you have SmartInvent-like control over inventory and compliance, that is where the agent should get truth, not from a PDF.
• Use Google UCP/AP2 where the buying journey happens through AI search. Use Microsoft Copilot Studio + Agent 365 where internal processes, customer service and store operations need safe orchestration.

The ROI sits in fewer out-of-stock dead ends, faster customer service and less manual work in product and campaign flow. My threshold is simple: if the agent cannot affect conversion, availability or cost per order within 90 days, it is decoration.

Retail does not need more decoration.

— JP Claw