Stall library · Compare
Feed price and storefront price disagree
A pricing disagreement is when your product feed and your product page state different prices for the same item, which means an AI agent may quote a shopper a number your checkout will not honour. The failure surfaces at the worst possible moment: the shopper has already decided, and the price changes in front of them.
Why the agent stops
Agents read whichever source they reached first and treat it as authoritative. There is no reconciliation step, because from outside there is no way to know which of two published numbers is correct.
A quoted price that does not survive to the cart is a specific kind of damage. It reads to the shopper as a bait price, and it teaches the assistant that your quotes are unreliable, which is a harder thing to undo than a missing field.
How often we see this
Not stated here. A frequency means nothing without the cohort it was counted over, and this page is about one stall rather than one category. Where a category has enough stores measured at every stage, the share of them showing this stall is published on its benchmark page, with the methodology beside it.
See it for yourself
- Take ten products, weighted towards ones on sale, and compare the feed price with the price in the page structured data.
- Then compare both against the price actually charged in the cart.
- Repeat with a discount code applied at the catalogue level, and in a second currency or market if you run them. Those paths diverge first.
What to change
- Make the feed a projection of the same source of truth the page renders from, rather than a separate export with its own pricing logic.
- Apply catalogue level discounts in both places or in neither.
- Regenerate the feed on price change, not on a timer.
- Where market specific pricing exists, publish per market feeds rather than one feed with the base price.
What Ottom looks at
Ottom compares the feed price with the page price for every product it read both ways, and names the product, the feed price and the page price in the finding. Only products present in both sources are compared, so a missing product is reported as a coverage issue rather than a disagreement.
Questions
When feed and page prices differ, which should win?
The one your checkout charges. Both published sources should equal it, and if they cannot, the feed should be the one you correct, because it is the one an agent trusts without loading a page.
Is a feed that lags sale prices by minutes a problem?
A few minutes is a much smaller problem than a permanent skew, and it is the kind of gap most stores can live with. What matters is the direction of the error and how long it lasts: a feed that is behind during a sale advertises a price you are no longer charging, which is the version that produces a complaint. The fix is the same either way, and it is not a shorter schedule: trigger regeneration on the price change rather than waiting for the next scheduled run.