What does a discount mean when the price it is measured against was never charged? As of November 12, 2026, Australia's consumer regulator has opened its third Black Friday sweep, and the list of practices it will examine reads like an inventory of ordinary e-commerce: storewide banners that exclude a large part of the catalogue, countdown timers that outlive the sale they announce, scarcity messages generated by a marketing plugin, and strikethrough prices the product was rarely or never sold at. None of these tactics is new. What is new is that websites, emails and social media are being reviewed in the same exercise, and that six retailers have already paid penalties after earlier sweeps.
What the sweep actually checks
The four categories the regulator names map neatly onto the four places where promotion data usually goes missing. A sitewide claim fails when the exclusion list lives in a legal footnote rather than in the banner logic. A countdown timer fails when nobody owns the end date after the campaign is extended. Scarcity messaging fails when the stock threshold is a plugin default. A strikethrough price fails when the historical price was never recorded with a date attached.
Read together, they describe a single operational gap: promotions are designed by marketing, priced by category teams and audited by nobody. The regulator is not asking retailers to stop discounting. It is asking them to be able to prove, on request, that the saving shown on the page corresponds to a price the product was actually offered at, for a reasonable period, before the sale.
Reference prices need a paper trail
The most exposed number in any campaign is the one with a line through it. A discount is only as honest as the price it is compared to, and that comparison has a date requirement attached in most jurisdictions. A European Commission check of 314 online shops found that 30% displayed discounts measured against the wrong prior price, which suggests the failure is systemic rather than occasional. The practical remedy is a daily price log per SKU, kept from at least a month before the campaign, with the timestamp retained so a category manager can answer a query without reconstructing history from memory.
Urgency is a data field, not a design choice
Countdown timers and low-stock labels feel like interface details, but they are claims about supply and time. When they are generated automatically by a third-party tool, responsibility does not move to the tool. A timer should read its end date from the campaign record, and a scarcity label should read from an inventory threshold someone has agreed to defend. If neither has an owner, the safest option is to switch the element off rather than to add a disclaimer underneath it.
The thirty-day rule is spreading
Europe already requires the before price to be the lowest price charged in at least the previous thirty days, and the European Court of Justice has ruled that the percentage must be calculated from that figure as well. The effect on campaign design is significant: an early-November promotion becomes the reference price for the Black Friday discount that follows, so a brand that starts discounting three weeks early quietly shrinks the saving it can advertise later.
For markets without an explicit thirty-day rule, the same discipline still pays. Regulators increasingly ask for the evidence behind a claim, and a daily price record answers that question in any jurisdiction. It also improves internal decisions, because category teams can see how deep a discount really was rather than how deep it was designed to look. Price monitoring, in this sense, is less about catching competitors and more about being able to explain your own shelf.
| Claim on the page | Evidence required | Typical failure |
|---|---|---|
| Up to 50% off | Share of catalogue actually at 50% | Headline carried by a handful of SKUs |
| Was 199, now 129 | Dated record of the 199 price | Reference price never charged |
| Ends tonight | Campaign end date in the system | Timer extended without an owner |
Three rows, three different owners: merchandising, pricing and campaign operations. Most enforcement cases start with a customer complaint about one of them and end with a request for records that no single team holds. Assigning the record to a named role is cheaper than any legal response.
Where price monitoring earns its keep
Monitoring is usually sold as competitive intelligence: track rival prices, spot gaps, react faster. The compliance use case is more valuable and easier to justify. If a retailer captures its own product pages daily, it can prove what it charged, when, and for how long, and it can see the moment a promotion drifts from the plan. That record also settles the internal argument about whether a discount was real.
The same data supports a second decision that rarely gets attention: how long a promotion should run. A campaign that starts early and deepens gradually compresses the reference price for everything after it, so the calendar itself becomes a pricing decision. Teams that model this in advance avoid advertising a discount that is smaller than the one customers saw three weeks earlier.
FAQ
What exactly is a misleading reference price?
A reference price is the higher figure a discount is measured against. It becomes misleading when the product was rarely or never sold at that price, so the saving exists only on the page rather than in the price history.
Does the thirty-day rule apply outside Europe?
The rule itself is European. Elsewhere the test is usually whether the retailer can show the price it actually charged, with dates, when asked. A daily log satisfies that test in most markets.
How should a brand monitor its own promotions?
Capture product page prices daily from before the campaign, keep the timestamps, and compare the advertised discount against that record. Most problems are record-keeping problems rather than pricing decisions.
Are countdown timers a compliance risk on their own?
Only when they are inaccurate. A timer that keeps running past the stated end date, or restarts for the same visitor, turns a design detail into a claim about urgency that cannot be defended.
