The compare-at price is the small field that decides whether a product looks reduced. It is also the field most likely to be wrong, because it is set during a promotion by whoever is in a hurry and removed by nobody afterwards. Left in place it does two things: it tells customers forever that the product is on sale, which erodes the reference price they hold in their heads, and it tells your own reporting that every single sale of that product is a discount, which quietly inflates one line of the statement and deflates another.
- A stale compare-at price makes every ordinary sale look like a markdown, in the shop and in the reports.
- It inflates the ticket value of what was ordered and invents markdowns nobody granted.
- A compare-at below the selling price is bad data and should count as no reduction rather than a negative one.
- Hygiene is a routine, not a rule: promotions end, and somebody has to clear the field.
What it does to the statement
Gross merchandise value is computed at the ticket price, which is the compare-at price where one is set. So a stale field raises the top line and creates price reductions that never happened underneath it, and the two cancel out at gross revenue while making both lines fiction.
The damage is to the ratios rather than the totals. A store watching reductions as a share of the ticket value will see a discount habit it does not have, and will either relax about real discounting or panic about imaginary discounting, both of which are worse than knowing.
The safeguard in the arithmetic
One rule handles the worst version. When a compare-at price sits below the selling price, the reduction is treated as zero rather than as a negative, because a negative would inflate revenue above what was actually charged. Bad catalogue data can therefore never make a statement look better, which is the direction that matters.
The lines are still flagged, because a compare-at below the price is a product record that needs attention rather than a pricing strategy nobody remembers choosing.
Why the field erodes pricing power
Customers form a reference price from what they see, and a product permanently shown as reduced teaches them that the lower number is the price. The reduction stops persuading anybody, and the next real promotion has to go deeper to be noticed, which is how a store ends up in a permanent sale it never intended.
In several markets there are also rules about how a reference price may be advertised, including how recently it must have been charged. That is a question for your own legal advice rather than for a profit tracker, but it is one more reason to treat the field as a dated claim rather than as decoration.
The variant trap
Compare-at prices are set per variant, and promotions are usually applied to a product. So a sale that covered every size in a range routinely leaves the field set on two sizes and clear on the rest, which is why a catalogue audit finds stale values in odd, scattered places rather than in tidy blocks.
It also produces the version customers notice: the same product showing a strikethrough in one size and not in another, on the same page, at the same time. That is a trust problem before it is a reporting one, and it is discovered by looking at the product page rather than at a spreadsheet.
The hygiene routine
- Set compare-at prices only for the duration of an actual promotion, with an end date somebody owns.
- Clear them when the promotion ends, as a step in ending it rather than as a separate task nobody schedules.
- Audit quarterly for products where the field has been set for more than a season.
- Fix any product where the compare-at sits below the selling price; that is data damage, not a discount.
- Watch the reduction line as a share of the ticket value, and treat a sudden move as a data question before a pricing one.
The version worth aiming at
A catalogue where the compare-at field is empty most of the time, and where it is set deliberately for a dated promotion, with how deep a promotion goes computed in a discount impact calculator before it ran. That store can read its own price reduction line as information, and can run a real sale that customers actually notice, both of which are worth more than the small honesty of a permanent strikethrough.