Corrections
Every error we published and fixed, with the date and the old wording. Pages get edited silently everywhere on the web; a site whose whole claim is “we recorded this” does not get to do that.
— “90-day low” on records shorter than ninety days
What was wrong. A card whose price was the lowest in its record said “90-day low” even when that record was eleven days long, with “11 days on record” printed two lines above it. The median it quoted was labelled “90-day” the same way, and a product page’s retailer box said “Their 90-day low”.
What a reader could have concluded wrongly. That we had watched the price for three months and it had not been lower in that time.
What changed. The label names the stretch we hold: “lowest in 11 days” until the record reaches ninety days, then “90-day low”. The median and the retailer’s low are labelled by the same count.
— “price checks” were counts of price changes
What was wrong. The figure we printed as “price checks” — on the front page, product pages, cards and /data — counted the prices we wrote down, and we write a price down only when it changes. On September 12 that was 884 recorded prices out of 9,399 reads, so the label understated the reading nine times over and described the record as something it is not.
What a reader could have concluded wrongly. That a product had been looked at a handful of times, and that ten “checks” were a few days away.
What changed. Reads and recorded prices are counted separately, and each is named for what it is.
— how Amazon prices reach us, and what our method pages said
What was wrong. The about page said Amazon prices came through the Product Advertising API; our brief for AI answer engines, the /data catalogue and every product’s dataset said each price was read from the retailer’s own page by our crawler. Amazon prices come through Amazon’s Creators API, and the crawler has read no retailer since September 11. The verification page also described cards that showed when each price was read and said “check price” once it aged out — the cards did neither — said marketplace sellers are not tracked, when about half the prices we record are a marketplace seller’s price in Amazon’s buy box, and put the delay before an expired deal is marked at six hours, when it can be a day and a half.
What a reader could have concluded wrongly. That we scrape Amazon; that a greyed price on a card was still current; that a dead deal leaves our pages within six hours.
What changed. One sentence about where prices come from is used everywhere it is said. Cards show when the price was read and print “Check price” instead of a number once it is past the window we may show it for. The marketplace and expiry paragraphs now say what actually happens.
— numbers that claimed more than they measured
What was wrong. “Held for” on product pages counted from when the previous price began, not the current one. The front page’s “cheapest thing we are tracking” was the lowest of thirty cards, and a brand page’s “cheapest right now” included prices older than we may show. A dip and recovery inside one day, such as a Lightning Deal, was drawn and judged as if the dip lasted until the next change. A card’s “cheapest yet” was the lowest at one retailer in ninety days. Category pages printed a price band and how often prices move from a record days old, and counted each product’s first price as a change.
What a reader could have concluded wrongly. That a price had held for longer than it had, that nothing cheaper was tracked, that a low price had lasted, and that a category’s prices were more settled or more restless than our record can show.
What changed. Each figure is now computed from what its words say: the current run, every tracked price we may show, the price a day closed at (with a dip kept as the recorded low), “90-day low” on cards, and category figures only from items watched for a month, counting changes rather than rows.
— product pages promised a verdict within days
What was wrong. A product page without a verdict said it needed ten recorded checks and that “at four checks a day that is a matter of days, not months”. We check four times a day but write a price down only when it changes, so what the verdict waits for is movement — about six weeks at the rate prices have moved so far. Separately, the description a search result or a shared link showed could state a verdict about a price the page itself declined to judge: one older than we may publish, or an open-box listing.
What a reader could have concluded wrongly. That a verdict was a few days away, and that the page was broken when none came; and, from a search result, that we had called a price good or high when the page said nothing of the kind.
What changed. The page states the rule as it is and prints the date on which a price that has not moved becomes a finding of its own. The description is now produced by the same judgement as the page, from the same offer.
— the Prime Day page had the months wrong
What was wrong. The Prime Day page said the sale “has landed in July in every year since 2015 except 2020” and was “usually mid-July”. Prime Day 2021 ran June 21–22, and Prime Day 2026 ran June 23–26.
What a reader could have concluded wrongly. That Prime Day could be planned for July, and that the 2026 sale was still to come.
What changed. The page gives the 2026 dates and the years it was not in July. Amazon’s October sale, which the page mentioned only in passing, has a page of its own.
— the legal pages named the wrong operator and programs we do not have
What was wrong. The terms and the privacy page said the site “is operated from the United States” and that the terms “are governed by the laws of the United States”. It is operated by MonacoWebPix, a sole trader in Monaco. The affiliate disclosure, How we make money and About listed Impact (Walmart, Target, Best Buy) and CJ Affiliate (Newegg) beside Amazon Associates; no link on the site pays through either. How we verify prices described a crawler reading those four retailers every six hours, when it had read no price from any of them. The disclosure also said our /go/ redirector “records the destination and the deal”, which the privacy page correctly said it does not.
What a reader could have concluded wrongly. Who they were dealing with and which law applied; that prices from four more retailers were being compared; that an outbound click was logged.
What changed. The terms now name the operator and Monaco law; the privacy page names the controller, who else handles data, how long the server log is kept and where to complain. Every page names Amazon Associates as the only program and Amazon as the only source of prices. An imprint and a copyright procedure were added.
— the floor badge and the chart disagreed
What was wrong. The “lowest ever” badge and the price chart on the same card were computed from two different ranges. The badge took the lowest price seen across all retailers, while the chart drew a single retailer’s history. A card could therefore draw its price sitting on the floor line with no badge, or carry the badge while the line showed the price well above the floor.
What a reader could have concluded wrongly. That a price was an all-time low at the retailer they were about to click through to, when the low belonged to a different retailer entirely.
What changed. The badge and the chart now read one number, from one series, scoped to a single retailer. The badge was relabelled from LOWEST EVER to LOWEST IN 90D, because ninety days at one retailer is what the data actually supports and “ever” was a claim we could not make on our first day of recording.
How corrections work here
- Prices that self-correct are not logged. A price that moved because the retailer moved it is the system working; the timestamp on the card already tells you when we last looked.
- Wrong claims are logged. If a page asserted something about price history that was not true, it gets an entry here with the original wording, whether or not anyone noticed.
- Nothing is deleted to make a problem go away. Corrected pages are corrected in place; the entry here carries what they used to say.
Found something wrong? [email protected] — include the URL, the retailer and the price you saw. Why those three.