Shopify Compare-at Price: When a Strikethrough Earns Its Keep
How Shopify's compare-at price works, where it shows, why variant mismatches kill the collection sale badge, and when a discount is the better tool.
MerchandisingThe diex team10 min read
A strikethrough price is the cheapest merchandising you can put on a Shopify product page. It is also easy to get wrong, because the number you cross out is a claim about your own past prices, and because one inconsistent variant can stop the sale badge from showing on collection pages. This article covers what Shopify's compare-at price field does, how to set it on a product or a single variant, why collection pages sometimes stay quiet, what makes your reference price defensible, and when a discount is the better tool.
What the compare-at price field is and where it shows
Shopify's compare-at price is the original price of a product that is now on sale. You put the original price in the Compare-at price field and the lower price you are actually charging in the Price field. Shopify's guide to setting sale prices for products explains the split plainly: "both these amounts can be displayed on product pages and collection pages, but only the sale price is displayed at checkout."
Three things follow from that sentence, and they matter more than most merchants expect.
- The compare-at price is display only. It never reduces what the customer pays, and it never appears in the order summary at checkout.
- Whether it shows at all is a theme decision. The same help page notes that "Your theme might add a badge with a message or percentage off to product listing and collection pages," and that sale price styling "can often be customized through your theme settings." A theme that does not render a compare-at price will not show one, no matter what you type in the admin.
- It is a variant-level field. Each variant carries its own compare-at price, which is why mixed variants cause the collection-page problem later in this article.
Compare-at price is one of three ways Shopify frames a markdown. The discounts overview puts it this way: "You can create discount codes or set up automatic discounts, or you can alternatively set sale prices for individual products." Compare-at price is the third option. It edits the product, not the cart.
Set a compare-at price on a product or a variant
For a product without variants, Shopify's sale pricing guide gives these steps:
- From your Shopify admin, go to Products.
- Click the product that you want to edit.
- In the Price section, click Compare at.
- In the Compare-at price field, enter the original price.
- In the Price field, enter the new, lower price.
- Click Save.
For a product with variants, the same guide routes you through the variant list: in the Variants section, click XX variants, then set Compare at price and Price for the variants you are discounting and save.
If you are marking down a whole collection, the bulk editor is faster than opening products one at a time. Shopify's guide to bulk editing explains that you select products with the checkboxes on the Products page and click Bulk edit, and that "Each column in the table represents a product property, such as price, SKU, and compare-at price." Add the compare-at price column, fill it down, and save. The important detail is that you are editing real prices in bulk, so write down the original numbers first. Nothing in the admin remembers them for you once you overwrite the Price field.
That is the hidden cost of compare-at pricing: it is destructive. A sale run this way changes your product data, and ending the sale means changing it back by hand.
Why your sale badge disappears on collection pages
This is the most common compare-at complaint, and it has a documented cause. Sale pricing looks right on the product page but the collection page shows no strikethrough and no badge.
Collection pages show aggregated information for a product, so Shopify needs the variants to agree. According to the sale pricing guide, "If some variants have compare-at prices that are inconsistent (such as some variants having a compare-at price of $0.00 USD, or some being empty, or different values across variants), then the collection page won't display the product as being on sale." Product pages keep working because they render the price of whichever variant the customer has selected.
The fix in the same guide: open the product, review the compare-at prices in the Variants section, and either remove all conflicting compare-at pricing and leave the fields blank, or make sure every compare-at price is higher than that variant's own regular price. Shopify calls out one trap specifically: $0.00 is not the same as an empty field, so clear the field entirely for variants that should not show a compare-at price.
In practice this means a markdown on one color of a six-color product is a product-page-only markdown. If you want the sale to read across the collection grid, discount every variant and give each one a compare-at price above its own price. If a size costs more at list, its compare-at price has to be higher too, not copied from the base size.
Two other reasons a sale can look invisible are worth separating from this one. If your markdown is a discount rather than a compare-at price, the product page has nothing to strike through, which is covered in why your Shopify discount doesn't show on the product page. And if the compare-at price is equal to or lower than the price, there is no sale to display.
What makes a compare-at number defensible
The compare-at field accepts any number you type. Consumer protection law does not. In the US, the FTC's guides on former price comparisons, 16 CFR 233.1, set the standard: a former price gives you a legitimate basis for a comparison when it "was the actual, bona fide price at which the article was offered to the public on a regular basis for a reasonably substantial period of time." Where the former price "is not bona fide but fictitious," for example "where an artificial, inflated price was established for the purpose of enabling the subsequent offer of a large reduction," the guides say the advertised bargain "is a false one."
The rule has some nuance that helps merchants with slow-moving inventory. You do not need sales history at the higher price. The guides say the advertiser should be careful that the price is one at which the product "was openly and actively offered for sale, for a reasonably substantial period of time, in the recent, regular course of his business, honestly and in good faith." But they also warn you to "scrupulously avoid any implication that a former price is a selling, not an asking price, unless substantial sales at that price were actually made."
A practical test before you type a compare-at number:
- Was this the price on your own store, publicly, recently, for a stretch of time you would be comfortable describing to a customer?
- Did you raise the price in order to cross it out? If yes, stop. That is the textbook example in the guides, which describe a seller who lifts a $7.50 pen to $10 for a few days and then advertises "Were $10, Now Only $7.50!"
- Is the reduction meaningful? The guides caution that the amount of a reduction should not be "so insignificant as to be meaningless."
- Can you prove the former price later? A dated screenshot, an export of your price history, or an archived product page costs nothing to keep.
One more: the FTC guides are US rules. If you sell into other markets, reference pricing rules there can be stricter about which prior price you are allowed to show, so check the local regulator's guidance before you run the same strikethrough everywhere.
The compare-at price of a supplier's MSRP you have never charged is a different claim entirely, and it is the one most likely to get a store a complaint. If you have genuinely never sold the item at that number, do not present it as your former price.
When an automatic discount beats editing prices
A discount leaves the Price field alone. That single difference solves most of the problems above. Shopify's guide to amount off products and orders walks through creating one from Discounts and choosing either a discount code or an automatic discount, applying it to all products, specific products, or specific collections. When it applies to all products, Shopify notes that "the discount is applied proportionally across all items in the cart."
Reach for a discount instead of a compare-at price when:
- You have no bona fide former price to cite. A 15% off weekend is an offer, not a claim about history.
- The offer is conditional. Quantity breaks, spend thresholds, and customer-specific pricing cannot be expressed in a price field at all.
- The sale has an end date. Set active dates once and the offer retires itself instead of waiting on a bulk edit.
- You want your list price back intact, with no risk of a typo becoming your new permanent price.
- You care how it stacks. The amount off guide explains that you check the classes of discount in the Combinations section to control what a discount can combine with. Compare-at pricing has no combination settings, because it is not a discount: a code applies on top of the sale price.
The trade-off is visibility. A compare-at price shows on the product page for free; an automatic discount usually does not, until the item is in the cart. That is why conditional offers need something on the page to announce them. diex, our Shopify discount app, runs volume discounts, variable discounts and spend tiers as Shopify Functions so Shopify applies them in the cart and at checkout, and it includes theme app blocks such as a volume pricing table on product pages and a spend tiers progress bar, which you can read about on the storefront blocks page. Your product prices stay where they are.
If you are deciding between the two discount methods, automatic discount vs discount code covers which one suits which campaign.
How to retire a sale cleanly
Ending a compare-at sale takes more care than starting one, because there are two fields to undo on every variant.
- Decide what your price is going back to. If the lower number is now your real price, that is a price change, not the end of a sale.
- Restore the Price field to the original number, from the record you kept before the markdown.
- Clear the Compare-at price field completely. Blank, not $0.00, per Shopify's troubleshooting note.
- Do it for every variant, not just the ones you remember editing. Use the bulk editor with the compare-at price column visible so you can see the whole grid at once.
- Spot check a collection page as a customer. A leftover compare-at price on one variant is how a store ends up advertising a sale that ended three months ago.
The permanent strikethrough is the failure mode to avoid. If a compare-at price sits above a product for a year, the number below it is your regular price, and the number above it is no longer a former price in any meaningful sense. That is exactly the fictitious comparison the FTC guides describe.
What to do this week
- Audit your live compare-at prices. Filter or scan your product list for anything still showing a strikethrough, and ask for each one whether you really charged that price recently and openly.
- Fix one product where the collection badge is missing by making the compare-at prices consistent across all its variants, then reload the collection page to confirm.
- Save a dated record of your current list prices before your next markdown, so you can both restore them and defend them.
- For your next conditional offer, build it as a discount with active dates instead of a price edit, and add something on the product page so customers see it before the cart.
- Before you pick a depth, check the math against your margin using how deep a discount can go.
Sources
Drafted with AI from the sources above and checked automatically against them and our product facts. Spotted a mistake? Email help@diex.app.