Sharon Gee Urges Retailers to Prepare for Agentic Commerce

Sharon Gee, speaking at Commerce Live, outlined practical steps brands and retailers must take to be ready for Agentic Commerce when it goes live in the UK. The focus is technical preparedness across inventory APIs, payments, identity and consent, and telemetry for accountability. Gee emphasized building transactional APIs, real-time inventory sync, clear policy and approval flows, and fraud controls so autonomous agents can act safely on customers' behalf. For engineering teams this means investing in API-first architectures, stronger instrumentation, agent-aware personalization models, and staged testing in shadow mode before enabling live transactions.
What happened
Sharon Gee spoke at Commerce Live about the latest operational and technical developments in Agentic Commerce and what brands and retailers need to do now to be ready for a UK rollout. She framed the problem as an integration and trust engineering challenge: autonomous agents will be able to discover, negotiate, and transact, which requires merchants to expose dependable, secure transactional endpoints and clear policy controls.
Technical details
Agentic Commerce is the operationalization of autonomous consumer agents interacting with commerce systems, requiring durable agent orchestration, intent schema, and transactional APIs. Engineers must support real-time inventory and pricing, deterministic payment tokenization, and atomic order flows to avoid double-sells and unintended charges. Practically, teams should:
- •Update APIs to be idempotent, versioned, and support agent-specific scopes
- •Normalize catalogs and expose real-time availability and pricing feeds
- •Instrument rich telemetry for intent, decision paths, and outcome auditing
- •Harden payment and fraud systems with agent-aware rules and tokenized flows
Why it matters This is a structural shift from conversational commerce to autonomous execution. Models and agents will depend on high-quality retrieval from product catalogs, embedding-based personalization, and low-latency transactional primitives. Data scientists must adapt ranking and recommendation pipelines to operate under agent-driven queries that optimize for multi-step objectives, not single-click conversion metrics. Operations and legal teams must also define explicit consent models and approval gates so agents can act within merchant and regulatory boundaries.
Practical risks and mitigations Merchant risk expands beyond UX to include liability for agent-initiated purchases, increased fraud surface, and supply-chain inconsistencies. Mitigations include staged rollout using shadow mode simulations, synthetic-agent testing, stricter authentication for high-value intents, and verbose audit logs to support dispute resolution. Monitoring should track conversion integrity, transaction success rate, and a rising incidence of exception flows.
What to watch
Track pilots that open payment and fulfillment APIs to agents, evolving regulatory guidance in the UK on agent consent and liability, and standards for agent metadata and provenance. For practitioners, prioritize API hardening, telemetry, and simulated agent testing in the next 3-6 months to remain operationally ready.
Scoring Rationale
Agentic Commerce introduces notable operational and technical demands for commerce stacks and data teams but is an evolutionary industry deployment rather than a frontier technical breakthrough. It is immediately relevant to merchants, platform engineers, and ML practitioners who manage personalization, payments, and telemetry.
Practice with real Payments data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Payments problemsStep-by-step roadmaps from zero to job-ready — curated courses, salary data, and the exact learning order that gets you hired.


