The math looked obvious. A product sitting at $58 on Amazon, the same item at $31 on Walmart — that is a $27 spread before FBA fees. Forty units would clear with margin to spare. So the buy happened.

The problem was not with the Amazon price. The problem was that $31 was not a Walmart sale. It had been $31 since January. It was $31 the previous November. It was $31 in the summer before that. The Walmart price was not depressed — it was structural, the floor the market had settled on, and the Amazon listing was the premium someone had found a way to charge on top of it. There was no spread. There was just a number that looked interesting because the comparative context had not been checked.

This happens more often than people admit. The analysis that led to the buy was not lazy — it checked the right retailer and found what looked like an opportunity. What it did not check was whether that opportunity was real or just a current price without a history attached to it. The difference between those two reads is not a matter of effort. It is a matter of knowing which signals to look for in a price history chart and what each one tells you before you commit inventory.

Duration Is the Signal Everyone Skips

The most overlooked piece of information in any price history chart is not the price itself — it is how long the price has been there. A price that has held for 45 days or more is structural. It is the equilibrium the market has reached for this product at this retailer, and it will not evaporate because demand shifts slightly or a competitor blinks. A price that appeared four days ago is almost certainly a flash event: a clearance move on aging inventory, a temporary response to a competitor's promotion, or a pricing error that will correct itself before the week ends. Looking at only the current price collapses both of those scenarios into a single number and offers no way to distinguish between them.

A price history chart shows you duration as a visual signal: the horizontal stretch of each price band. A flat line running from January to June is telling you something categorically different from a line that dropped two weeks ago with no precedent at that level. Most resellers register the price and miss the timeline. They see $31 and note the spread. They do not ask whether $31 has been there for eight months, which would tell them the opportunity is already priced into every competing reseller's calculation and has been for some time.

The practical implication is straightforward but easy to skip when you are moving fast across a sourcing list. Before any buy decision, the first question is not what the price is. It is how long it has been there. That answer requires price history, not a price check, and it is the read that would have stopped the forty-unit buy before it happened.

Cheap Compared to What, Exactly

Price is only meaningful relative to itself. A Walmart listing at $31 is either a bargain, a standard number, or the expensive end of a normal range — depending entirely on what $31 looks like against its own history. The single most useful question to ask before acting on any buy-side price is whether the current number is actually cheap relative to that product's own record, not just cheap compared to what Amazon is charging.

The 90-day average is the practical reference point. If a product's current price sits above its 90-day average, you are looking at the expensive end of its normal range — there is no margin story there, regardless of what the Amazon listing says. If the current price is at or below the 90-day average, it warrants a closer look; the product is trading toward the cheap end of what is normal. If the current price is below the 90-day minimum — a price level it has not reached in three months — then you may be looking at a genuine anomaly worth acting on quickly. That is the hierarchy: above average means nothing, at or below average merits attention, below the floor means move.

This matters because the most common version of the $31 mistake is not gross inattention. It is a reseller comparing a buy-side number directly against an Amazon listing price and calling the difference a margin. That calculation does not ask whether $31 is an unusual Walmart number or a boring one. Cross-retailer price history answers that question specifically. The resellers who consistently avoid overpaying for inventory are not better at math — they are asking the right comparative question before the buy, not after. For operators managing 50 or more SKUs across multiple retailers, the workflows that keep this question answerable at scale are worth building deliberately, which is exactly what the for resellers page covers in detail.

The Dip That Comes Every March Is Not an Opportunity

Seasonal price patterns are not the same as compression events, and treating them as equivalent is how the same SKU gets mis-sourced repeatedly. If 12 months of price history on a product shows a dip every March — driven by a retailer clearance cycle after a Q4 inventory flush — that dip is not an opportunity. It is the annual floor. It is the price the market has long since priced in, the one every attentive reseller in that category already knows about and has been acting on for years. Jumping on it as a compression event misreads the pattern entirely.

A dip with no prior equivalent is a different story. If a product has traded between $34 and $42 for eight months and suddenly drops to $24 with no historical precedent at that level, something has changed: a clearing of excess inventory, a supplier price revision, a competitive response with no announced end date. Any of these can produce a genuine anomaly. The distinction between "this happens every year" and "this has never happened before" is only visible if you have enough history to see the recurring pattern. Without 12 months of price data, you cannot know whether the dip you are looking at is novel or seasonal. Without that distinction, both scenarios look identical at the moment of decision.

This is part of why building a tracking habit before you need to act matters more than catching a product at the moment it dips. History that you need at decision time has to have been collected before the window opened. You cannot run a price history check on a SKU you first looked at this morning and expect the chart to tell you whether March dips are annual. The chart you pull today shows today's price. The chart you have been building for six months shows the pattern — and the pattern is what tells you whether you are looking at an opportunity or a calendar event everyone else has already put into their sourcing model.

What to Do Once the Framework Is Readable

The three signals above — checking duration, comparing the current price against the 90-day average and minimum, distinguishing seasonal repeatability from genuine compression — require price history that actually exists. That means the tracking has to start before the sourcing decision, not at the moment of it. Most resellers who end up holding inventory they cannot move did not lack analytical ability. They lacked history on that SKU at that retailer, and a current price without historical context is not a basis for a sourcing decision.

PriceTrail builds that history from the moment you add a product. Paste the Walmart or Target URL for any SKU you are evaluating and the tool starts collecting price data and storing it. Over days, weeks, and months, you accumulate the baseline that makes the three signals above readable. The 90-day average becomes a real number rather than an estimate. Seasonal patterns become visible. Duration shows up in the chart as something you can measure rather than guess at.

The logical next step once you have identified a real floor price is to stop watching the chart manually and let an alert handle it. If the analysis tells you a product's genuine floor is $26 — the price it reaches during its annual clearance window and occasionally at other compression moments — you set the alert there and wait. When the price hits $26, the alert fires and the window is still open. Set a floor price alert on a SKU you are evaluating and let the monitoring run in the background while you move on to the next decision.

The broader structural reason why Amazon-only tools cannot close this gap — and why cross-retailer history has to be built somewhere outside those tools — is covered in more depth in why Keepa isn't enough for retail arbitrage. The short version is that no Amazon-native tool stores Walmart or Target price history. Closing that gap is what makes the reading framework above executable rather than theoretical.