The Shopify compare at price field is the strikethrough number on a product variant: set it higher than the selling price and the theme renders a was/now pair, calculates a percentage off, and in most themes slaps a sale badge on the collection tile. That part hasn't changed in a decade. What changed on 9 October 2026 is where that number goes. Shopify now passes compare-at prices into Catalog, the data layer feeding agentic shopping surfaces, which means the number you typed into a spreadsheet at 11pm during last year's sale is now being read by software that compares your discount depth against everyone else's.
For Australian merchants that lands about six weeks before Click Frenzy and Black Friday. A field that used to be a merchandising habit is now a discoverability signal and an ACCC exposure at the same time.
How compare at price works on Shopify, precisely
It's a per-variant field, sitting directly under Price in the admin. Three things follow from that:
- It's variant-level, not product-level. Size L can be on sale while size M isn't, and your theme will usually show the discount for whichever variant loads first. We see this break constantly on apparel stores running partial markdowns.
- It does nothing to the order. Compare-at is display only. The customer pays the Price field. No discount code, no order-level discount line, nothing in your reports marks the order as discounted unless you also use a discount.
- It has no schedule. There is no start date or end date on the field. Something has to change it — you, a CSV, Shopify Flow, or an app.
That last point is why half the stores we audit in January still have compare-at prices left over from Boxing Day. Nobody cleared them, because clearing them requires a deliberate act.
What AI shopping agents do with the number
Agentic surfaces don't browse your collection page. They ingest structured product data — title, description, variant price, compare-at price, availability, shipping terms, returns policy — and reason over it to answer something like "find me a merino base layer under $150 that ships to Broome before the 20th". Shopify's Catalog is the pipe that carries your product data to those surfaces, and compare-at is now in the payload.
Two consequences worth sitting with. First, discount depth becomes a comparable, machine-readable attribute. If your $129 item carries a $179 compare-at and a competitor's near-identical item carries a $299 compare-at on the same $129, an agent asked to find the best deal has a reason to prefer them. Inflated anchors get rewarded, which is exactly the incentive the ACCC exists to counter.
Second, and more useful to you: stale compare-at data makes you look wrong. An agent that has your product indexed at 28% off and then hits a landing page at full price has an inconsistency to resolve. Nobody has published how these surfaces penalise that, so I won't pretend to know. But feed quality has mattered to every automated channel that came before, and there's no reason this one is different.
Was/now pricing rules in Australia: what the ACCC actually tests
Australian Consumer Law doesn't give you a safe-harbour number of days the way the UK's guidance does. The test is whether the comparison is misleading. In practice that means the higher price has to be a price you genuinely charged, recently, for a meaningful stretch, and for a meaningful volume of sales — not a price you set for a fortnight in March so you'd have something to strike through in November.
Three patterns that get merchants in trouble:
- A product launched at a "was" price it never sold a unit at.
- Permanent sale. If the item has been $129 with a $179 strikethrough for nine months, $129 is the price. The $179 is a claim you can't support.
- RRP used as compare-at without saying so. If the number is a supplier's recommended retail price and you have never charged it, calling it "was" is a different claim from calling it "RRP".
The same scrutiny the ACCC applies to sustainability and provenance claims — and Australian shoppers do ask for both — applies to price claims. The difference now is that a machine-readable field makes the history of your pricing far easier for anyone to reconstruct. Keep the receipts: a date-stamped export of your price changes costs nothing and settles arguments.
Discount display for Click Frenzy: compare-at, automatic discount, or code
Click Frenzy's whole proposition is a fixed window with visible markdowns, so the discount has to be legible before the cart. That narrows the choice.
Compare-at price. Shows on collection pages, product pages, search results and now the agentic feed. Best for discoverability. Worst for reporting, because nothing in Shopify analytics flags the order as discounted — you'll be reconstructing sale performance from price history.
Automatic discount. Clean reporting, applies at checkout, stacks poorly with Afterpay messaging because the four-instalment figure your theme displays is usually calculated off the product price, not the discounted one. Shoppers notice when $129 shows "4 payments of $32.25" and then checkout says something else.
Discount code. Fine for a mailing list, useless for a sale event where the price has to be obvious to a crawler.
For a 48-hour event we normally run compare-at for display plus a matching order tag via Flow, so the finance side can still pull the numbers afterwards.
The arithmetic, because the strikethrough isn't the expensive part
Take a $129 item at a $179 compare-at. That's a 27.9% discount, which reads well on a tile.
At $179: GST is $179 ÷ 11 = $16.27, leaving $162.73 ex-GST. Subtract COGS of $48, an average Australia Post parcel cost of $11.80 blended across metro and WA/regional, and Afterpay at roughly 6% plus 30c = $11.04. Contribution: $91.89.
At $129: GST $11.73, leaving $117.27. Same $48 COGS, same $11.80 freight, Afterpay $8.04. Contribution: $49.43.
A 27.9% price cut removed 46% of the contribution. You need 1.86 orders at the sale price to match one at full price — before you count the extra WA deliveries, the higher return rate that discount cohorts reliably bring, and whatever you paid Meta to get them there. With Australia's population, you cannot volume your way out of that the way a US merchant can. This is why the compare-at number deserves a conversation with whoever owns margin, not a quick pass by whoever owns the theme.
Setting sale prices across markets in Shopify
If you sell into New Zealand, Singapore or the US alongside Australia, compare-at behaves in a way that catches people out. Market-level pricing applies an adjustment to the base price, and the compare-at moves with it. A 15% uplift on a $179 anchor gives you $205.85, which no merchandiser would ever choose. Rounding rules help; they don't fix the fact that your anchor price in NZD was never a price anyone paid in New Zealand.
Where the discount matters, set explicit per-market prices rather than relying on percentage adjustment, and set the compare-at explicitly too. It's more work. It's also the only version that survives a question about whether the "was" price was real in that market.
Two more things for cross-border: Australian GST applies to low-value imported goods for registered overseas sellers, so if your prices display GST-inclusive in Australia and exclusive elsewhere, your compare-at has to follow the same convention or your discount percentage silently shifts by 10%. And a market that shows a different currency but an unchanged compare-at will produce discount depths you never approved.
Does compare at price affect Google Shopping?
Yes, directly. Shopify's Google channel maps the fields so that when a compare-at exists and exceeds the selling price, the higher figure goes through as the regular price and the lower one as the sale price. That's what generates the strikethrough annotation in Shopping results.
Google has its own conditions for showing that annotation, broadly that the regular price must have been the real, charged price for a sustained period of recent history. Check the current Merchant Center policy before you build a plan around it, because the specifics have moved more than once. The practical upshot: an anchor you invented for Click Frenzy may get the annotation suppressed, and your feed and your agentic data will then disagree with each other. Both read from the same field, so the fix is upstream, in the admin.
Bulk editing compare at price in Shopify without wrecking anything
Four workable methods, roughly in order of how much damage they can do:
- Admin bulk editor. Filter products, select, Edit, add the Compare at price column. Fine for a few hundred variants. Tedious past that, and the page gets slow.
- CSV import. Export, edit the Variant Compare At Price column, re-import. Fast and dangerous: any column you leave in the file will be written back. Strip everything except Handle, Option values, Variant SKU and the price columns. We get the column set wrong on the first pass more often than we'd like, which is why the first import always goes to a duplicate test product.
- Shopify Flow. Scheduled triggers can set compare-at at the start of a sale and clear it at the end. This is the only method that reliably handles the clearing step, and clearing is the step that gets forgotten.
- A bulk pricing app. Worth it if you run frequent, overlapping, collection-level markdowns. Check how it stores the original price before the sale starts, not after.
Whatever you use, export your price and compare-at columns to a dated file before you touch anything. That file is your rollback and, incidentally, your evidence of pricing history.
Your pre-Click-Frenzy checklist
- Audit every variant with a compare-at set today. Anything that has been on sale for more than a few weeks is a claim you can't defend — either drop the anchor or reset the price.
- Confirm the discount is applied consistently at variant level, so size M and size L don't tell different stories to an agent reading the feed.
- Check Afterpay and Zip instalment messaging renders off the discounted price, not the compare-at.
- Set an end date and a method for clearing the field. Put it in a calendar with a name against it.
- Re-sync the Google feed after the price change and spot-check three products in Merchant Center diagnostics.
- Decide on freight before the discount, not after. A $129 order going to regional WA with free shipping is a different product from the same order going to Richmond. Sendle and Australia Post both let you model this; most merchants don't until January.
What about EOFY and the summer run?
The Australian calendar gives you two heavy discount periods that sit oddly against global retail: a June EOFY push and a Christmas that runs into a January clearance in 35-degree heat. That's a long stretch of the year where compare-at prices are live. If you're running markdowns in June, resetting in July, then going again in November, the gap between sales has to be long enough and the full price real enough that each anchor holds up. Four discount windows a year is manageable. Nine is a permanent sale with extra steps.
If you'd rather someone else do the audit, our free store audit covers pricing fields, feed mapping and the agentic data Shopify now publishes on your behalf. We work with Australian brands from Bengaluru on AEST hours; the Australia page explains how that works in practice. And if the underlying problem is that your product data is thin — short descriptions, missing attributes, no structured specs — that's worth fixing before the sale, because agents read all of it. Our content and SEO work starts there.
Pull the export. Count how many variants have a compare-at older than 60 days. That number will tell you how much work the next three weeks hold.