What Happens When AI Agents Start Choosing Which Products to Buy? (2026)

AWS lifecycle notice (June 30, 2026) — Amazon Bedrock Agents Classic is in maintenance for new customers after July 30, 2026. If you host a shopping copilot, use Bedrock AgentCore. Full matrix: lifecycle roundup. Third-party agents that choose products do not run on your Classic stack.

On June 17, 2026, AgentCore Harness reached general availability (What’s New). Useful when your agent compares SKUs with tools. Irrelevant as a magic ranking layer for everyone else’s agent.

This post is strategic, not speculative: what merchants should optimize when an AI system is the intermediary in discovery, comparison, and merchant selection. It is grounded in current-channel data (Adobe, July 2026) and in catalog contracts — not in a story that autonomous checkout is already the median order. It is not an anonymized client engagement. We do not invent conversion lifts.

First-party signals we reuse (not eCommerce outcomes) — Gateway server-side tools cut median tool round-trip ~180 ms → ~95 ms on a B2B CRM assistant (12 tools, ~8k turns/day) — Gateway post. Platform TCO silhouette: support-style AgentCore at 50K sessions/mo ~$791/mo platform + model (decision guide). Those numbers size your host. They do not measure agent-choice share of GMV. Model your mix on the AgentCore pricing calculator.

Reproduce this — Copy agent-choice-optimization-signals.md. Run the 10 golden questions on one category. Fail closed if stock, price, or a discount is asserted without a feed/tool result. Channel score: agentic-commerce-merchant-readiness.md. Contract: ai-ready-catalog-contract.md.

Opinionated take: optimize decision inputs (attributes, offer truth, delivery, reviews, policy) rather than a prompt you do not own. Trade-off: brand storytelling gets less budget on the PDP that machines read. You remain a candidate when the intermediary never sees your hero video.

What is already true vs what is emerging

Adobe Analytics, via Digital Commerce 360 (19 Aug 2026), 1T+ U.S. retail visits, July 2026:

• AI-referral traffic +62% YoY, +1,219% versus October 2024
• Those visits converted 60% higher than non-AI traffic and generated 53% more revenue per visit (11th straight month of conversion outperformance in that series)
• +14% engagement, +59% time on site, −33% bounce, +28% add-to-cart versus non-AI (same article)
• Expanded cohort: 39% of homepages not machine-readable; apparel 76% LLM visibility

That is humans arriving from generative tools — AI search as a channel. It is not proof that agents already complete purchase unattended. Intent mix bias is likely; do not copy 60% / 53% as a FactualMinds or campaign target.

Baymard 70.22% still describes what happens when totals, stock, and confidence break at checkout. An intermediary that chooses a SKU increases the volume of claims checkout will test.

Your next customer may be an AI agent is the executive readiness post. This post is the choice post: what the intermediary weighs. Your copilot is a different scorecard.

The decision layer (what to optimize)

flowchart TD
  req[Shopper requirements]
  attrs[Structured attributes]
  rank[Retrieval / ranking you do not own]
  rev[Reviews as data]
  price[Checkout-true price]
  avail[Honest availability]
  ship[Delivery promise as data]
  trust[Policy and identity]
  pick[Selected SKU]
  pay[Your checkout]
  req --> attrs
  attrs --> rank
  rank --> rev
  rev --> price
  price --> avail
  avail --> ship
  ship --> trust
  trust --> pick
  pick --> pay

GEO is not a guaranteed ranking technique. Packaging: post 34. You do not control the agent’s ranker. You control whether a honest SKU exists for it to pick.

There is no native Shopify AgentCore connector. External choosers will not wait for one. Your Harness copilot (GA 17 June 2026) can use the same contract. Skip Agents Classic after 30 July 2026.

FactualMinds helps retailers connect storefronts, catalogs, and back office so those inputs stay true — see retail / eCommerce on AWS.

What broke

What broke — Competitive “agentic merchandising” brief: increase brand adjectives on titles so assistants would “prefer us.” Width and waterproof remained unstructured; inventory asOf was 18 hours stale. Sampled queries picked a competitor with a worse review average and a complete spec. Detection: 10 golden questions — we lost on constraint match, not on storytelling. Fix: stop title stuffing; fill the catalog contract; fail in_stock when asOf exceeds SLA. Lesson: agents choose on fields. Copy is not a spec.

A second failure: issuing a one-off 15% code in the prompt so the “agent would win.” That is ungoverned discounting — same ban as the 15-automations map.

Gateway ~95 ms does not help if the offer is wrong.

What to Do This Week

1. Open agent-choice-optimization-signals.md. Run 10 golden questions on one category.
2. Fail any answer that asserts stock, price, or a discount without a tool/feed result.
3. Score merchant channel readiness and the catalog contract — do not start with a ranking vendor.
4. Pull AI-referrer metrics from post 33. Keep Adobe 60% / 53% as context, not an OKR.
5. Confirm checkout still owns payment. No unbounded discount tool.
6. If you also want your copilot, use post 10 separately.
7. Contact FactualMinds, Generative AI on AWS, retail / eCommerce.

What This Post Doesn’t Cover

• Autonomous payment, wallets, or AgentCore Payments / x402
• How to rank inside a named third-party assistant
• Measured FactualMinds GMV from agent-choice — we are not inventing it
• On-site copilot 13-check list — post 10
• PIM extract/publish — post 9
• Speculative AGI shoppers

FAQ

When should you NOT optimize for AI agents choosing products?

Skip a dedicated program when required attributes are missing, stock is stale, or feed price disagrees with checkout. You are not in an honest comparison set. Score readiness and contract first. Do not invent coupons.

What could go wrong if you treat Adobe’s AI-referral conversion lift as proof agents already buy for shoppers?

Adobe measures click-through from generative tools (July 2026, 1T+ visits). +62% YoY, 60% higher conversion, 53% more revenue per visit, +1,219% vs October 2024 is channel mix — with likely intent bias. It is not autonomous checkout. Instrument referrals; optimize decision inputs separately.

What could go wrong if merchandising optimizes “brand love” copy instead of decision signals?

Agents match constraints. You lose to a cleaner GTIN and honest availability. Trust that matters is versioned policy, not a slogan.

Do we control how a third-party agent ranks us?

No. You control candidate-set truth. GEO is not a guaranteed ranking technique. Accurate representation is the job.

Should we let an agent invent a discount to win merchant selection?

No. Eligibility is an OMS rule. Invented 15% off is ungoverned margin leak. Hand off to checkout.

Is AgentCore required for agents to choose our products?

No. External agents need the catalog contract. Harness (GA 17 June 2026) is for your copilot. Skip Agents Classic after 30 July 2026.

Need the decision inputs — catalog, offer, policy — honest enough that an intermediary can choose you without lying? Contact FactualMinds or see Generative AI on AWS and retail / eCommerce.