Individual HTML example · Urgency

Sale timer resets on reload

A fictional retailer shows a fifteen-minute sale countdown that returns to fifteen minutes whenever the page reloads and the price never changes at zero.

Countdown timerRetail promotionPricing

This is an original fictional comparison. It depicts no real business and is not a regulator finding, statutory category or legal safe harbour.

Retail promotionPricing

Sale timer resets on reload

A fictional retailer shows a fifteen-minute sale countdown that returns to fifteen minutes whenever the page reloads and the price never changes at zero.

Potentially problematicSale ends in

Sale ends in. The timer restarts and has no effect on price or availability.. Displayed time: 14:59. Expiry consequence, collapsed

Neutral alternativeOffer ends at 18:00 CET

Offer ends at 18:00 CET. The deadline is fixed and the stated discount ends at that time.. Displayed time: 42 minutes remaining. Expiry consequence, expanded: The expiry event and resulting reservation or offer state are shown with the timer.. View the source and period for “42 minutes remaining”

Why the first version can mislead: The message applies immediate pressure at the pricing decision. The cue “14:59” should correspond to a defined operating state and a real consequence. The example instead states: “The timer restarts and has no effect on price or availability.” The timer can manufacture urgency without a corresponding offer deadline.

What a fairer design does: Use a countdown only for a genuine deadline and explain exactly what changes when it reaches zero.

Show annotated differences (4)
Potentially problematic version
  • The timer restarts and has no effect on price or availability.Why this state matters: The message applies immediate pressure at the pricing decision. The cue “14:59” should correspond to a defined operating state and a real consequence. The example instead states: “The timer restarts and has no effect on price or availability.” The timer can manufacture urgency without a corresponding offer deadline.
  • Expiry consequence, collapsedReview prompt: Which timestamped inventory, reservation, demand or offer event substantiates “14:59”, and what changes when its limit is reached?
Neutral alternative
  • The deadline is fixed and the stated discount ends at that time.Fairer design: Use a countdown only for a genuine deadline and explain exactly what changes when it reaches zero.
  • View the source and period for “42 minutes remaining”Review prompt: Record the claim, timestamp, data source and post-claim state; which evidence supports “A decreasing time representation is shown near a choice”?
Review questions (3)
  • Which timestamped inventory, reservation, demand or offer event substantiates “14:59”, and what changes when its limit is reached?
  • Record the claim, timestamp, data source and post-claim state; which evidence supports “A decreasing time representation is shown near a choice”?
  • What happens when the stated limit is reached, and could the observed message be the legitimate case “Purely informational clock”?
Side-by-side retail promotion interface showing “Sale ends in” and the clearer alternative “Offer ends at 18:00 CET”.Provenance: Original hypothetical retail promotion example created for this library; no real business, product or interface is depicted.

Complete practice context

How this example relates to Countdown timer

A visible countdown applies time pressure, particularly where it resets, is personalised without disclosure or has no corresponding consequence at zero. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.

The full guide explains inclusion and exclusion criteria, potential harms, fairer design, evidence questions and separate Australian legal information layers. The example page isolates one scenario so it can be shared and discussed without reproducing the complete library on one page.

Continue comparing

Countdown timer

Reservation timer has no inventory hold

Ticket checkoutCheckout

A fictional ticket seller displays “Seats held for 02:00” although no seats are reserved and the timer simply restarts after zero.

Open this example

High-demand claim

Fabricated live-viewer count

Travel search resultPricing

A fictional travel site displays “42 people are viewing this” from a fixed script that runs for every result and visitor.

Open this example

High-demand claim

Old booking spike presented as current demand

Event ticket pagePricing

A fictional seller says “Selling fast today” using sales from the launch week three months earlier.

Open this example
Sources and provenance for this example

Evidence base

Sources

  1. Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
  2. Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064
  3. Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
  4. Manipulative conduct in the digital economy, pricing claims and competition in essential services among ACCC priorities for year aheadAustralian Competition and Consumer Commission · Primary · checked 2026-08-09
  5. Exposure draft explanatory materials: unfair trading practicesTreasury · Primary · checked 2026-08-09