# Lowest Price but Still Not Recommended by AI Agents
> Price is necessary but not sufficient: being the cheapest does not win agent selection on its own. An agent weighs price against reviews, endorsement, and whether it can compute your all-in cost, and it weights price differently per model.
## Key takeaways
- Price is necessary but not sufficient: being the cheapest for a query does not win agent selection by itself, so a pricier rival can still get recommended.
- There are four reasons your price edge fails to convert: price is weighted differently per model, a non-price lever (reviews or endorsement) outscores it, your all-in cost is not legible before checkout, or your listing is not comparable enough for the price to be weighed at all.
- Two of the four are directly fixable this week: make your total landed cost readable on a cold product page, and earn genuine review depth and endorsement instead of a self-applied 'best value' tag.
- If none of the four fit, the problem is not price. Stop re-checking your discount and hand the general appear-but-not-picked question to the shown-but-not-selected diagnostic.
## Price is necessary, but never sufficient
The instinct when you lose to a pricier competitor is that the agent got it wrong, or that the number it read was stale. Sometimes that is true, and when the agent is [quoting a wrong price or stock figure](/ai-showing-wrong-price-or-stock/) you have a data-freshness bug, not a selection one. But far more often the agent read your lower price correctly and still chose someone else. Being the cheapest for a query is necessary but not sufficient: a low price keeps you in contention, but on its own it does not win the recommendation.
The reason sits in how agents actually decide. In the ACES framework, a controlled simulation of shopping agents choosing from a mock storefront, price was one of several weighted signals (alongside grid position, star rating, platform endorsement, and description text), and its weight differed from model to model rather than dominating the decision. Price is a lever, not the lever. When you are cheapest and still lose, one of the other levers outscored your discount. The rest of this page is the four ways that happens and how to tell which one is yours. This is the [agent selection](/glossary/#agent-selection) question at its sharpest, and it is why the ACES per-model numbers live on the [how AI agents choose products](/how-ai-agents-choose-products/) cornerstone rather than being repeated here.
## Cause 1: price is weighted differently on every engine
The first trap is assuming a discount that won you the recommendation on one engine will win it on another. ACES found that price sensitivity varied sharply across the models it tested, so the same markdown can move one engine's selection rate noticeably and barely register on another. A price edge is real, but it is not worth a fixed amount of selection everywhere.
The practical read: if you set one price strategy and judge it from a single blended, all-engine number, you can be genuinely winning on a price-sensitive engine and losing on a price-insensitive one, and the blend hides both. The signal to track here is [model-specific price sensitivity](/signals/model-specific-price-sensitivity/), and the discipline is on the [selection checklist](/tools/agent-selection-checklist/#b-price-position-03): test a price change isolated to one engine, then compare that engine's before-and-after win rate. The per-engine differences themselves belong to the [Gemini and Google AI Mode playbook](/gemini-shopping-ranking/) and its siblings, not here.
## Cause 2: a non-price lever is outscoring your price edge
You can be cheapest and still be the thinner listing. ACES reported that star rating and review depth are positive selection levers, and that agents reward legitimate platform endorsements while penalizing a self-applied "Sponsored" tag. Put those together and a pricier competitor with a deep, recent review history and a genuine platform endorsement can outscore your lower price, because the agent is adding up several weighted signals and your advantage sits in only one of them.
The fix is not to drop your price further, which chases the one lever you are already winning. It is to close the gap on the levers you are losing: [review depth](/signals/review-depth/) that is truthful and current, and a real [platform-endorsement signal](/glossary/#platform-endorsement-signal) you actually qualify for. The tempting shortcut, a self-applied "best value" or "sponsored" badge, is the exact move the [earn endorsement, do not self-label](/signals/endorsement-not-sponsored/) signal warns against: it reads as promotional and can cost you selection rather than buy it.
## Cause 3: your "lowest" is not legible as the lowest all-in cost
An agent can only credit a price advantage it can compute. If your sticker price is the lowest but shipping, tax, or fees only surface once the agent starts checkout, the agent cannot compare your landed total against a rival whose all-in cost is readable up front, so it either estimates you high or drops you. Your real advantage exists, but it is invisible at the moment of comparison.
This is a legibility problem, not a pricing one, and it is the most fixable cause on the list. The [offer-cost-legibility](/signals/offer-cost-legibility/) signal and the [make total landed cost readable](/tools/agent-selection-checklist/#b-offer-legibility-01) checklist item both target it: show the current price, any sale window, shipping, and fees as plain, parseable numbers on a cold product page, and make every figure match what checkout later charges. The full field-by-field fix lives in [make your product feed AI-readable](/make-product-feed-ai-readable/); this page's job is only to tell you that a hidden shipping cost, not your price, may be why the cheaper offer loses.
## Cause 4: you are not comparable, so the price is never weighed
The last cause is the quietest: the agent never got far enough to weigh your price at all. If your listing is missing the attributes the top offers in your category expose, the agent has nothing to line you up against, so a lower price on an under-described product loses to a fully-described one it can actually compare. Completeness against your peers, or [facts per token](/signals/facts-per-token/), is what earns you a place in the comparison in the first place.
Grid position can hide a price advantage the same way. ACES found grid position to be a large but provider-specific selection lever, so where an engine renders you can swamp a modest price difference. Both of these, comparability and [position bias](/glossary/#position-bias), are the general appear-but-not-picked problem rather than the price paradox, so this page hands them off. If tightening your price changes nothing and none of causes 1 to 3 fit, that is the signal to switch diagnostics: work the [shown-but-not-selected](/shown-but-not-selected/) decision tree, which owns comparability and position in full.
## How to check which cause is yours
You cannot tell these apart by staring at the result once. Run a small, repeatable check on the engine that is picking your competitor:
1. Ask the buying question the way a shopper would, and record who the agent recommends and, if results render as a grid, where each offer sits.
2. Open the recommended competitor and your own listing side by side, and compare on the four dimensions above: can the agent read each product's all-in cost, its review depth, its endorsement status, and its attribute completeness?
3. Note the one dimension where the competitor is clearly ahead. That is your most likely cause, and it points at the matching fix above.
4. Repeat the query enough times to separate a real pattern from one lucky or unlucky run, and read your [agent win rate](/glossary/agent-win-rate/) per engine rather than reacting to a single answer.
The full sampling-and-error-bars protocol (how many runs, how to log them, how to be sure a change is real) is in [how we test agent selection](/research/methodology/); it is the same protocol you use to confirm any fix below actually moved the result.
## How to fix it, in priority order
Work the cheapest, highest-certainty fixes first:
1. **Make your all-in cost legible** (cause 3): surface price, sale window, shipping, and fees in parseable text that matches checkout. Details in [make your product feed AI-readable](/make-product-feed-ai-readable/).
2. **Close the non-price gaps** (cause 2): earn genuine review depth and a real endorsement, and remove any self-applied sponsored or "best value" styling.
3. **Fill your comparability gaps** (cause 4): list the attributes your top competitors expose, complete yours truthfully, then hand the rest to [shown-but-not-selected](/shown-but-not-selected/).
4. **Test price per engine, not in aggregate** (cause 1): isolate a price change to one engine and read that engine's win rate.
Notice what is not on the list: cutting your price again. When you are already the cheapest, another markdown spends margin on the one lever you are winning and leaves the losing levers untouched.
## When the answer is "price was never the problem"
The uncomfortable finding is often that your discount was fine all along. Because price is only one weighted input, a pricier competitor winning is usually evidence that it is stronger on a different input, not that your price is too high. Chasing a lower number is the most expensive way to not fix that.
If you have ruled out all four causes and still lose, the problem has moved past price entirely: you may be [absent from the engine altogether](/ai-engine-visibility-gap/), or the agent may be [quoting a wrong price or stock figure](/ai-showing-wrong-price-or-stock/) that erases your real advantage. Both are their own diagnostics. The broader "I appear but never get picked" case belongs to [shown-but-not-selected](/shown-but-not-selected/); this page ends where the price question does.
## Frequently asked questions
### If I have the lowest price, why does the AI agent recommend a more expensive product?
Because price is necessary but not sufficient. The agent scores your offer on several weighted signals at once (reviews, endorsement, and whether it can read your full landed cost), and controlled tests show it weights price differently from model to model. A thin listing, or a shipping cost hidden until checkout, can outweigh a lower sticker price.
### Will cutting my price further make the agent pick me?
Not reliably. In the ACES simulation, price sensitivity varied by model, so the same discount moves engines differently and a deeper cut on one engine can barely move another. Test a price change on one engine at a time and read that engine's win rate before rolling it out everywhere.
### Should I add a 'lowest price' or 'best value' badge so agents notice my deal?
No. ACES reported that agents penalize a self-applied 'Sponsored'-style tag and reward genuine platform endorsements, so a promotional badge you apply yourself can cost you selection. Earn a real editor's-pick or verified-seller status, and state your price and shipping as plain, parseable numbers instead.