Countdown timer
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.
Individual HTML example · Urgency
Reservation timer has no inventory hold
A fictional ticket seller displays “Seats held for 02:00” although no seats are reserved and the timer simply restarts after zero.
This is an original fictional comparison. It depicts no real company and is not a legal finding or safe harbour.
Reservation timer has no inventory hold
A fictional ticket seller displays “Seats held for 02:00” although no seats are reserved and the timer simply restarts after zero.
Seats held for. No inventory state corresponds to the repeating countdown.. Displayed time: 02:00. Expiry consequence, collapsed
Reservation valid until 14:32. The deadline is tied to the identified seats and releases them at expiry.. 01:42 remaining. Claim basis, expanded: The relevant population, period, inventory or offer state is presented with the message.. View the source and period for “01:42 remaining”
Why the first version can mislead: The message applies immediate pressure at the checkout decision. The cue “02:00” should correspond to a defined operating state and a real consequence. The example instead states: “No inventory state corresponds to the repeating countdown.” A buyer may hurry through payment because the interface represents a protection that does not exist.
What a fairer design does: Connect the timer to a real reservation record and show a stable exit when no hold exists.
Show annotated differences (2)
Potentially problematic version
- Expiry consequence, collapsedIn “Reservation timer has no inventory hold”, this element shows how countdown timer can shape the decision.
Neutral alternative
- View the source and period for “01:42 remaining”In “Reservation timer has no inventory hold”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- Which timestamped inventory, reservation, demand or offer event substantiates “02:00”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “The stated or implied consequence at expiry is material”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “genuine fixed event deadline that produces the represented consequence”?
Complete pattern 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. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
The full guide explains inclusion and exclusion criteria, harms, fair design principles, evidence questions and the relevant EU 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
Related examples
Open this example
High-demand claim
Fabricated live-viewer count
A fictional travel site displays “42 people are viewing this” from a fixed script that runs for every result and visitor.
High-demand claim
Old booking spike presented as current demand
A fictional seller says “Selling fast today” using sales from the launch week three months earlier.
Sources and provenance for this example
Evidence base
Sources
- Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
- Unfair Commercial Practices DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2005/29/EC; CELEX 02005L0029-20220528