Urgency · European Union
High-demand claim
The label “High-demand claim” describes this recurring design mechanism: a claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. It is a design and research taxonomy, not a standalone legal conclusion. Depending on the complete journey and likely effect, current EU consumer or sector rules may require separate assessment. No published Digital Fairness Act proposal currently creates a pattern-specific prohibition or duty under this label.
- Family
- Urgency
- Also known as
- Journey stages
Definition
What is this pattern?
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.
How it works
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. A demand message suggests competition from other buyers without a current, relevant measure connecting that activity to the user’s available offer.
Warning signs
- The claim refers to demand, viewers, purchases or bookings rather than remaining stock.
- It is temporally framed and connected to a transaction.
- Truth and representativeness require provenance or controlled replay.
Potential harms
- The unsupported demand cue can create pressure to book before comparing alternatives.
- Historical popularity is framed as immediate demand and may rush a decision.
Learn by comparison
What does this look like?
These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.
Illustrative example 1 · Travel search result
A fictional travel site displays “42 people are viewing this” from a fixed script that runs for every result and visitor.
Potential consumer harm: The unsupported demand cue can create pressure to book before comparing alternatives.
Illustrative example 2 · Event ticket page
A fictional seller says “Selling fast today” using sales from the launch week three months earlier.
Potential consumer harm: Historical popularity is framed as immediate demand and may rush a decision.
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)
- Claim basis, collapsedIn “Fabricated live-viewer count”, this element shows how high-demand claim can shape the decision.
- 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”?
Old booking spike presented as current demand
A fictional seller says “Selling fast today” using sales from the launch week three months earlier.
Selling fast today. The supporting sales period ended three months ago.. Tickets moving quickly. Claim basis, collapsed
Ticket availability. Remaining allocation and refresh time are shown without a stale demand claim.. 312 tickets at 14:05. Claim basis, expanded: The relevant population, period, inventory or offer state is presented with the message.. View the source and period for “312 tickets at 14:05”
Why the first version can mislead: The message applies immediate pressure at the pricing decision. The cue “Tickets moving quickly” should correspond to a defined operating state and a real consequence. The example instead states: “The supporting sales period ended three months ago.” Historical popularity is framed as immediate demand and may rush a decision.
What a fairer design does: State the actual period behind a demand claim or remove the claim when it is no longer current.
Show annotated differences (2)
- Claim basis, collapsedIn “Old booking spike presented as current demand”, this element shows how high-demand claim can shape the decision.
- View the source and period for “312 tickets at 14:05”In “Old booking spike presented as current demand”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- Which timestamped inventory, reservation, demand or offer event substantiates “Tickets moving quickly”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “It is temporally framed and connected to a transaction”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “static aggregate popularity claim”?
What is a fairer alternative?
Base demand messages on current auditable data and state the metric and period without exaggeration.
Legal and information status
Legal position at a glance
A claim of unusually high current demand is used to accelerate a decision without a clear or supportable basis. A demand message suggests competition from other buyers without a current, relevant measure connecting that activity to the user’s available offer. Risk increases where the mechanism changes a material consumer choice, hides a consequence or makes a genuine alternative harder to use. The taxonomy label remains a review prompt and does not establish an infringement.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support identification and comparison of this recurring interface mechanism. They do not determine that a particular interface is unlawful.
UCPD Articles 5 to 9, where applicable
Possible risk indicator
Depending on the trader, audience, overall presentation, material information and likely transactional effect, the facts may require a separate assessment under the applicable UCPD provisions.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Current lawCurrent law
The UX label “High-demand claim” is not a standalone EU offence. Depending on the trader, audience, complete presentation, omitted information and likely transactional effect, the observed facts may require a separate assessment under the applicable UCPD provisions or another instrument within scope.
Under considerationUnder consideration
The Commission is preparing a Digital Fairness Act initiative, but the call for evidence does not select a final rule for high-demand claim or establish that this taxonomy term will appear in a proposal.
Editorial analysisEditorial analysis
The pattern definition, variants and examples on this page use the cited research taxonomy sources to support recognition and comparison. That analytical classification is not a legal conclusion about an individual interface.
UnknownUnknown
No published DFA proposal currently establishes a definition, covered actor, legal threshold, duty, remedy, transition rule or application date for high-demand claim. Those details remain unknown pending primary legislative text.
Context matters
Context and boundary cases
- The claim refers to demand, viewers, purchases or bookings rather than remaining stock.
- It is temporally framed and connected to a transaction.
- Truth and representativeness require provenance or controlled replay.
- Exclude or qualify the label where remaining-stock claim.
- Exclude or qualify the label where static aggregate popularity claim.
- Exclude or qualify the label where auditable live demand metric with clear definition.
When a similar design can serve a legitimate purpose
- A similar design should not be classified this way where remaining-stock claim.
- A similar design should not be classified this way where static aggregate popularity claim.
- A similar design should not be classified this way where auditable live demand metric with clear definition.
Operational review
What teams should review
- Teams
- 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”?
- Which timestamped inventory, reservation, demand or offer event substantiates “Tickets moving quickly”, and what changes when its limit is reached?
- Record the claim, timestamp, data source and post-claim state; which evidence supports “It is temporally framed and connected to a transaction”?
- What happens when the stated limit is reached, and could the observed message be the legitimate case “static aggregate popularity claim”?
- Which complete journey evidence supports or contradicts the high-demand claim classification?
Evidence to retain
- Versioned captures of the Pricing states before, during and after the relevant decision
- Configuration, content and event records supporting the observed high-demand claim mechanism
- Responsive, keyboard and assistive-technology review of every material option and consequence
- Timestamped operational data supporting every urgency, demand or social-proof message
Legal map and implementation tools
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
- Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573
- Commission work programme 2026: Europe's Independence MomentEuropean Commission · Primary · checked 2026-09-14 · COM(2025) 870 final; CELEX 52025DC0870; Annex I item 30