# How AI Shopping Agents Choose Products

> AI shopping agents choose products by scoring structured signals (price, availability, review depth, and how completely your product data is filled in) rather than brand familiarity.

<!-- How AI shopping agents rank products: the structured signals (price, availability, reviews, data completeness) that decide which store gets picked. -->
<!-- Canonical: https://agentmint.net/how-ai-agents-choose-products/ · By Abdalsalaam Halawa · Published 2026-07-07 -->
<!-- Evidence tags below are load-bearing: <Claim type="spec-fact|reported|hypothesis"> marks how each factual claim is sourced. -->

<KeyTakeaways
  items={[
    "AI shopping agents rank on structured signals (grid position, price, rating, endorsement, and description text), not on brand recognition.",
    "The strongest public evidence is the academic ACES framework: a controlled simulation of Claude, GPT-4.1, and Gemini agents choosing from a mock storefront, not real sales data.",
    "Position and layout bias are large but provider-specific, so there is no universal 'top rank' to aim for.",
    "Every signal is weighted differently by each model, and a model update can reshuffle which products win.",
    "The levers you actually control are feed completeness, product schema, titles, and crawler access.",
  ]}
/>

## The short answer (signals, not brand habit)

When an AI shopping agent picks a product, it is reading a scorecard, not recalling a brand. In the strongest evidence available today (the academic ACES framework, covered below), the levers that moved an agent's choice were all structured attributes: where the product sat in the results grid, its price, its star rating, whether it carried a platform endorsement, and how its description was written. That is why the question of [agent selection](/glossary/#agent-selection) (why an agent chooses one store or offer over another) comes down to legible product data, not reputation.

We read the evidence to mean that <Claim type="hypothesis">an agent's pick is driven by machine-legible product signals rather than the brand familiarity that sways human shoppers</Claim>, which is how a small store with complete, well-structured data can beat a household name it would never outrank in a person's memory. This page is the selection chapter of the broader [agentic commerce optimization](/agentic-commerce-optimization/) guide; the [platform playbooks](/platforms/) then show how each engine weights these signals in practice.

## What the evidence shows: the ACES framework

The most rigorous public work on how buying agents choose is a 2025 study whose framework is called **ACES**. <Claim type="spec-fact" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES, introduced in the paper "What Is Your AI Agent Buying?", was authored by Allouah and colleagues across MyCustomAI, Columbia Business School, and Yale, and is a provider-agnostic method for auditing agent decisions: a mock storefront is shown to vision-language-model shopping agents in repeated randomized trials, and their selections are analyzed with regression</Claim>. Because the storefront and every attribute are controlled, the study can isolate what actually shifts a choice.

Two things to hold onto before any figure below. ACES tested a fixed set of frontier models, including Claude Sonnet (up to version 4), GPT-4.1, and Gemini 2.5 Flash, inside a controlled simulation, **not** a record of real-world sales. And every effect it found is model-specific: the same signal has a different weight on each agent. The sections that follow report the paper's numbers exactly, each one carrying that simulation caveat.

## Position & layout bias

The single largest effect ACES found is where a product sits on screen. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">For a Claude Sonnet 4 agent, a product in the bottom-right corner of the grid was selected about 4.5% of the time, and moving that same product to the top row raised its selection rate roughly fivefold</Claim>. Note that this is two-dimensional grid position, not a one-dimensional list rank.

And the effect is not universal. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">Position bias varied by provider and persisted even in text-only, "headless" interfaces, undermining any single notion of a "top" rank</Claim>. For a merchant that means placement inside an agent's result surface is powerful but rarely something you set directly; what you control is being eligible to appear at all, which loops back to feed quality and crawler access. See [position bias](/glossary/#position-bias) in the glossary.

## Price sensitivity

Agents respond to price, and how strongly depends on the model. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES estimated log-price (ln Price) coefficients of −1.623 for Claude Sonnet 4, −1.612 for GPT-4.1, and −2.190 for Gemini 2.5 Flash, negative everywhere (cheaper wins, all else equal), with Gemini markedly more price-sensitive than the other two</Claim>. The practical reading: price competitiveness matters across agents, but the same discount buys more selection lift on some engines than others. Because these coefficients are model-specific and drawn from a simulation, treat them as directional evidence that price is a real lever, not as a pricing formula.

## Ratings & review depth

Star ratings move selection, and they move it most on the most rating-sensitive models. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">Raising a product's rating by 0.1 stars lifted a baseline 10% selection probability to 15.4% for Claude Sonnet 4, 20.3% for GPT-4.1, and 16.0% for Gemini 2.5 Flash, a large swing for a small rating change, with GPT-4.1 the most rating-sensitive</Claim>.

<Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES also models review *count* as a signal distinct from the average score, and reports it as a positive selection factor across the models tested</Claim>, which points to review depth mattering beyond the headline rating. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">In the paper's conditional-logit estimates (Table 2 of the current revision), the log review-count coefficient is positive for every model tested: 0.415 for Claude Sonnet 4, 0.739 for GPT-4.1, and 0.501 for Gemini 2.5 Flash, each statistically significant (p below 0.001), with GPT-4.1 weighting review depth most heavily</Claim>. As with the price coefficients above, these are model-specific logit coefficients from a simulation: directional evidence that more reviews raise selection odds, not a percentage lift you can bank. The takeaway for merchants stands regardless: genuine ratings and review volume are among the few selection levers you can influence honestly and directly.

## The "Sponsored" penalty & endorsement lift

Two counterintuitive findings sit together: agents *penalize* paid-looking tags and *reward* platform endorsements. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">Tagging a product "Sponsored" pushed a baseline 10% selection probability down to 8.9% (Claude Sonnet 4), 8.0% (GPT-4.1), and 7.9% (Gemini 2.5 Flash), a consistent penalty across all three models</Claim>. In the other direction, <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">a platform endorsement such as an "Overall Pick" badge lifted the same baseline 10% to 24.3% (Claude), 19.9% (GPT-4.1), and 42.6% (Gemini), with Gemini rewarding endorsement most strongly</Claim>.

The honest implication (and it is an inference, not a growth hack) is that <Claim type="hypothesis">the winning move is to earn legitimate endorsement signals, not to fabricate them; manufacturing badges or gaming "pick" markers is exactly the dark pattern this result would tempt a merchant into</Claim>.

## Behavior is model-dependent (and changes on updates)

Every effect above has a different size on each model, and the ranking is not stable over time. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES found agents concentrate demand on a handful of "modal" products and never select some brands at all, with the pattern differing by model</Claim>. More unsettling for anyone optimizing to a single engine: <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">the authors documented that a model update can drastically reshuffle market shares, as it did between Gemini 2.5 Flash Preview and Gemini 2.5 Flash</Claim>.

This is why AgentMint.net types every model-behavior claim by source and date: what an agent rewards this quarter it may weight differently after the next release. Treat agent behavior as a moving target: the per-engine [platform playbooks](/platforms/) track where the engines currently diverge.

## What this means for merchants: the practical levers

You cannot set your grid position or force an endorsement, but you can control the inputs those signals are computed from. Four levers translate the evidence above into work you can start this week:

- **[Make your product feed AI-readable](/make-product-feed-ai-readable/)**: completeness and structure are what make you eligible to be scored at all.
- **[Ship product schema (JSON-LD) for AI shopping](/product-schema-for-ai-shopping/)**: the machine-readable layer agents trust when your page and feed disagree.
- **[Write product titles AI agents match](/product-titles-for-ai-agents/)**: because description and title text measurably shifted selection in ACES. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">Query-conditional description rewrites raised market share by an average of +3.66 percentage points (Claude Sonnet 4), +8.37 pp (GPT-4.1), and +14.79 pp (Gemini 2.5 Flash), all statistically significant</Claim>, though <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">the effect was concentrated, not uniform: 67% of category-model pairs saw no significant change, while 33% produced large gains</Claim>, with <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">outliers reaching +52.0 pp for an office lamp on Gemini 2.5 Flash and +30.3 pp for an office lamp on GPT-4.1</Claim>.
- **[Manage AI crawlers, robots.txt and llms.txt](/ai-crawlers-robots-llms-txt/)**: block the crawlers and you delete the supplemental page data agents read beyond your feed.

Together these four are the inputs to the scorecard. The [platform playbooks](/platforms/) then show how ChatGPT, Gemini, and Perplexity weight them differently.

## Caveat: simulation, not sales

Every number on this page comes from one controlled study, and its limits matter as much as its findings. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">ACES is a simulation (vision-language-model agents choosing from a mock storefront in randomized trials, across a fixed model set that includes Claude Sonnet up to 4, GPT-4.1, and Gemini 2.5 Flash), not a record of real purchases on live stores</Claim>. Read these effects as evidence of *what kinds of signals* agents weigh and *how differently* they weigh them, not as guaranteed conversion math for your catalog.

The methodology is inspectable (<Claim type="spec-fact" source="ACES simulator, github.com/mycustomai/ACES" href="https://github.com/mycustomai/ACES">the ACES simulator is released under the MIT license</Claim>), and AgentMint.net's own [research lab](/research/) is replicating the description-rewrite finding on live catalogs, with results held in a "data collection in progress" state until real numbers exist. Until then, treat ACES as the best available map of how agents choose, and your own measured [agent win rate](/glossary/#agent-win-rate) as the territory.