Amazon's Rufus Just Made Pre-Prime-Day Price Hikes a Two-Click Tell
Amazon expanded Rufus's price-history view to 365 days on May 1, 2026, putting a full year of price data in front of more than 50 million shoppers who already use the feature roughly three times a month. The expansion lands about six weeks before Prime Day moves into June. Sellers running the standard pre-event hike-then-discount play now ship that play with an audit trail attached to the buy box.
The mechanic is small. The norm shift is not.
The pre-event hike isn't a rumor anymore
For years the "Prime Day discount inflation" story sat in trade press and academic papers. As of late 2025 it's also in court filings and structured retail data. Omnia Retail tracked European Prime Day 2025 pricing and found average product prices climbed from €142.78 to €148.28 in the weeks leading up to the event. About 14.8% of products got a price bump greater than 5% in the two to three weeks before, and 7.1% jumped more than 10%.
The week of the actual event was even more telling. DataWeave's Prime Day 2025 retrospective reports that 54.9% of products didn't drop in price during the event window, and 45.5% were actually more expensive during Prime Day than the week before. For nearly half the catalog, the "deal" was a return to a price the SKU had been at a month earlier, dressed up as a percentage off a reference price the algorithm had quietly raised.
That pattern is now the subject of a proposed class action filed in October 2025 alleging Amazon used "fictional" list prices to exaggerate percentage-off claims and pressure shoppers into buying inside a short event window. Amazon disputes the framing, but the data has been ahead of the litigation for at least two cycles.
That's the environment the May 1 announcement just dropped into.
What 50 million shoppers can now see in two clicks
Per Amazon's own announcement, the price-history view is reachable two ways: a "Price history" link directly next to the price on the product detail page, or by asking Rufus a question like "Has this item been on sale in the past 30 days?" The chart now covers 30, 90, and 365 days, up from 30 and 90 last November. Rolling out across the US, UK, and India, with full availability in the next few weeks.
The numbers Amazon shared with PPC Land are the ones to internalize. Over 50 million customers have used the feature since the 2024 beta. The average shopper checks price history three times a month. That's somewhere on the order of 150 million price-history checks per month if usage holds, almost certainly more once the 365-day chart starts surfacing in Rufus answers.
This isn't a third-party tool tucked behind an extension. It's first-party, on the buy box, free, with zero install friction. Digital Trends framed it as a long-overdue feature, which is true, but the framing misses the timing. CamelCamelCamel has existed for years. What changed is that Amazon decided to put the same data inside the conversion flow.
Why the timing isn't accidental
Prime Day shifted from July to June for 2026. The 365-day chart shipped May 1. That gives sellers roughly a five to six week runway, which is exactly the window the data shows pre-Prime-Day price hikes usually happen in. By exposing the full year right at the start of that window, Amazon is essentially telling its third-party sellers: don't try it this cycle, because shoppers will see the bump as it happens.
There's also a defensive read. Class-action exposure and a slowly building wave of pricing-transparency rules in the EU and UK both push toward disclosure. Shipping a first-party price chart lets Amazon argue, in any future regulator conversation, that shoppers had the data and chose to buy anyway. The compliance pressure shifts to the seller making the deal claim.
None of this is fatal to Prime Day. It's just the first cycle where the dominant pricing tactic has a labeled scoreboard above it.
The two audiences this actually moves
For brands selling on Amazon, the reference price strategy is now externally legible. "MSRP $99.99, Prime Day $59.99" only works if the 365-day chart supports both numbers. If the SKU spent eight months at $69.99, the implied "savings" against MSRP is going to read as marketing, not a deal. From what I've seen on accounts that bumped list prices 10 to 15% in late May historically, that buffer is now visible on the buy box and is a one-star-review risk if shoppers feel set up.
For the ad team running Sponsored Products and Sponsored Brands, the alignment problem is creative-side. If your Prime Day ad screams "biggest savings of the year" and the price-history chart shows three deeper discounts in the last six months, you're paying for clicks that convert worse and earn worse reviews. Pull your event creative against the chart before it ships, not after.
The agentic side of Rufus is where this gets more interesting. Amazon has been building toward auto-buy at target prices, where a shopper says "buy this if it drops below $79" and Rufus does it. A reliable 365-day price chart is the calibration data that makes those thresholds usable. Once shoppers start setting target prices off the chart, the addressable audience for Prime Day inflation gets smaller, because a chunk of demand is queued at year-low thresholds your event price won't clear.
Amazon's ad business has been quietly rewiring around exactly this kind of data, which I wrote about in our $70B ad business breakdown. The retail side and the ad side are pulling in the same direction.
A 90-minute audit before June Prime Day
If you sell on Amazon and your team is mid-planning Prime Day, this is the work I'd do this week, in this order:
- Pull your top 50 SKUs by trailing-90-day revenue. Anything below that is noise.
- For each SKU, chart the 365-day low and median price. CamelCamelCamel exports work; Helium 10 and Jungle Scout both have this too. You only need three numbers per SKU: current list, 365-day median, 365-day low.
- Flag any SKU where the current list price is more than 8% above the 365-day median. Those are the ones where the Rufus chart will visibly contradict your deal copy.
- For each flagged SKU, choose: lower the list price now and accept thinner margin in exchange for a deal claim that survives the chart, or pull the SKU from your Prime Day promo set entirely and let it run at base price.
- Re-brief Sponsored Products creative against the surviving promo set. No "biggest savings ever" copy on a SKU whose 365-day low was lower than your event price.
Benchmark: 45.5% of Prime Day 2025 products had higher prices than the week before. If you can get your top 50 to the other half of that line, you've removed the part of your event that the chart will undercut. That's a real number to manage to.
The chart is small. The default it changes is bigger.
A first-party price history is technically minor. The thing that should make pricing leads at brands a little nervous is what it implies about every other AI shopping surface that's coming. Once an assistant inside the conversion flow can pull a full year of SKU pricing on demand, every "limited time" and "lowest price ever" claim has to clear a forensic check the moment a shopper asks for one. Rufus is just the first one with the install base to make that the default.
I don't think the brands that get burned here are the ones with the cheapest products, or even the ones with the most aggressive promos. From what I've seen, it tends to be the ones that treated reference pricing as a creative-team problem instead of a data problem. The chart turns that into a buy-box problem now, which is a different team and a different deadline.
Notice Me Senpai Editorial
