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.
Individual HTML example · Urgency
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.
This is an original fictional comparison. It depicts no real company and is not a legal finding or safe harbour.
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.
42 people viewing now. The number is fixed and unrelated to current viewers.. Book before demand rises. Claim basis, collapsed
Current availability. The page uses verifiable inventory rather than invented audience pressure.. Rooms available for these dates. Claim basis, expanded: The relevant population, period, inventory or offer state is presented with the message.. View the source and period for “Rooms available for these dates”
Why the first version can mislead: The message applies immediate pressure at the pricing decision. The cue “Book before demand rises” should correspond to a defined operating state and a real consequence. The example instead states: “The number is fixed and unrelated to current viewers.” The unsupported demand cue can create pressure to book before comparing alternatives.
What a fairer design does: Use a clearly defined live metric only when supported, including the relevant listing and measurement window.
Show annotated differences (2)
Potentially problematic version
- Claim basis, collapsedIn “Fabricated live-viewer count”, this element shows how high-demand claim can shape the decision.
Neutral alternative
- View the source and period for “Rooms available for these dates”In “Fabricated live-viewer count”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- Which timestamped inventory, reservation, demand or offer event substantiates “Book before demand rises”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “The claim refers to demand, viewers, purchases or bookings rather than remaining stock”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “Remaining-stock claim”?
Complete pattern context
How this example relates to High-demand claim
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. 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
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.
Countdown timer
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.
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