Sale Price — the strike-through nobody configures properly.

Sale Price is the listing field that powers the strike-through reference price on your detail page. Strictly, it isn't a promotion — it lives on the pricing tab next to your regular Price and your List Price, not under the promotions menu — but it controls the single most visible piece of merchandising shoppers see, and treating it carelessly is one of the most common reasons promo programmes underperform.

This episode covers what Sale Price actually does, how it interacts with the other pricing fields, and how to use it without quietly cannibalising your reference price.

The three price fields

• List Price — your published "manufacturer suggested" or shelf price. The highest-anchor figure in your pricing stack.
• Price — what shoppers pay when no promotion is active.
• Sale Price — a temporary lower price, scheduled with a start and end date, that overrides Price for the configured window.

When Sale Price is active, the detail page shows the Sale Price as the live price, and the regular Price as the crossed-out "Was" figure next to it. The shopper sees both, and the percentage saving is calculated and displayed.

What Sale Price actually displays

The strike-through pricing surface — that crossed-out number — is where most of the perceived discount on Amazon is communicated. Coupons render a green flag, but the crossed-out number is what tells the shopper how good the deal is. A Sale Price that produces a clean "Was €29.90, Now €19.90 — Save 33%" reads as a much stronger offer than a 33% coupon that only shows the live price.

For pre-Black-Friday and pre-Prime-Day windows, a Sale Price scheduled to start at the event and end a day after is usually the cleanest way to display the discount, paired with the relevant promotion mechanic (Lightning Deal, 7-Day Deal, or PED) on top.

The reference-price trap

Amazon recalculates the reference price (the price used for deal eligibility, for the strike-through display, and for Lightning Deal qualification) based on the lowest Featured Offer price over the last 30 days. A long Sale Price window pulls that average down.

Practical consequence: a 30-day Sale Price at €17.90 on a product whose regular price is €22.90 will, over time, teach Amazon that €17.90 is the regular price. The next Lightning Deal you submit against the €22.90 figure will be rejected because the discount evaluates against €17.90 instead.

Use Sale Price as a tactical instrument for short windows — typically up to 7 days — and reserve longer-term price changes for an actual Price update. The two fields look interchangeable in the interface. They are not interchangeable to Amazon's reference-pricing engine.

Sale Price with no promotion mechanic on top

A standalone Sale Price — no coupon, no PED, no Lightning Deal — gets you the strike-through display and nothing else. No SERP badge, no Today's Deals placement, no Prime carousel. It is the quietest possible discount: existing traffic sees the lower price, new traffic sees nothing different.

That makes standalone Sale Price useful in exactly one scenario: when you want a temporary lower price visible to existing detail-page traffic for operational reasons (a soft launch, a category-specific window, a B2B push) without pulling Amazon's promotional surfaces into it.

Stacking with promotions on top

Sale Price stacks with everything. A Lightning Deal calculates its discount from the Sale Price, not from the regular Price. A coupon applies to the Sale Price. A PED applies to the Sale Price.

The downstream consequence — and this is where things go wrong — is that a 15% coupon on top of a Sale Price that's already 25% below the regular price produces a 36% combined discount. Add an evergreen 5% Subscribe & Save and you're at 40%. None of these mechanics announced themselves as deep promotions individually, but the stack is.

Apply Episode 04's rule mechanically here: when Sale Price is active, treat it as the headline mechanic and remove or pause the others for its duration unless you've explicitly modelled the combined discount.

Configuration discipline

• Always schedule Sale Price with an explicit end date. A Sale Price with no end is the single most common cause of permanent reference-price erosion.
• Keep windows short. 7 days or less is the default; 14 days is the upper bound; 30+ day Sale Prices belong in the regular Price field instead.
• After any Sale Price window, let the regular Price run unmodified for at least 14 days before scheduling the next one. The reference-pricing engine needs the breathing room.