The design asked for a countdown. The offer had no end date.
Why I refused to ship a countdown timer and a scarcity counter on four European storefronts — and how to build urgency that binds to a fact.
The redesign comp for a home & living brand I look after had two urgency devices on it. A countdown to the end of the sale, ticking away under the hero. And a line on the product tile saying only forty were left.
I built everything else on that page across four European storefronts. I did not build those two.
The date had already been and gone
Before wiring the timer up, I went looking for what it should count down to. The promotion end date sitting in the market configuration was three weeks in the past — the tail of a retired campaign window nobody had cleared out. The current strike price has no end date at all. The config file's own comment says so, in plain language, written by someone who knew.
So the honest description of the requested feature is: a clock counting down to a moment that will never arrive, on an offer that will still be there tomorrow. That isn't persuasion with a bit of pressure on it. It's a false factual claim with an animation.
The stock counter was the same shape of problem. Forty was a number somebody typed into a design file to show the component working. There is no reading anywhere in the business that produces forty. To ship it I'd have had to either hardcode it — a lie — or bind it to live inventory, which is real work nobody had scoped.
This is the exact pattern regulators went looking for
I'm not a lawyer and this isn't legal advice, but you don't need to be one to see where this sits. The EU's Omnibus Directive (2019/2161) exists precisely because the digital versions of old misleading-price tricks got easier to run and harder to spot, and it gave member states the power to fine widespread cross-border infringements up to 4% of turnover in the market concerned.
Fake countdowns are a named, catalogued pattern, not a grey area. The deceptive patterns library has a whole category for fake urgency, and its worked example is an app whose default setting was literally "run the campaign all over again" — the timer resets itself when it hits zero. The Princeton study of eleven thousand shopping sites catalogued countdown timers and limited-time messages as a distinct category years ago. Enforcement has followed: the same library lists a retailer fined over fake slashed prices, perpetual discounts and fake countdown timers together, as one bundle.
Urgency you couldn't defend in a letter to a regulator is urgency you can't defend to a returning customer either. They find out the same way — they come back.
The answer isn't "never use urgency"
A real deadline is genuinely useful information, and withholding it doesn't make you honest, it makes you unhelpful. The fix is to bind the device to a fact rather than to a wish.
So the shop pages shipped with a dedicated key for the strike-offer end date, defaulting to empty. The promo bar renders a countdown only when that key holds a real future date, and removes itself when the date passes. Nobody can turn it on by accident, and nobody can leave it running past its own expiry, which is the failure mode that gets you caught. The scarcity counter is specified the same way — it renders only against live stock, or not at all. The end date now sits as one open question with the client instead of as a quiet liability in production.
That cost me an afternoon of argument and saved the only sales tool that matters here. If your sale ends every week and never ends, customers stop reading "sale ends" as information. You've spent the credibility you'd need on the one day you have a genuine deadline. It's the same reason invented testimonials are a liability rather than a shortcut.
Somebody has to ask whether the date exists
The comp was good. The designer did their job — countdowns are a legitimate component and it belongs in the kit. The gap opens between design and implementation, where a placeholder quietly becomes a claim because everyone assumed the number came from somewhere.
In this category the stakes are higher than they look, because a sofa or an adjustable bed is a considered purchase. People take weeks over it, return several times, and compare across sites. A timer that says four hours to a customer on week three of a decision doesn't create urgency. It creates suspicion, right at the point where the checkout is already leaking. And cross-border sellers carry this in every market they're in at once — the same way everyone budgets for the VAT and forgets the compliance layer underneath it.
The countdown will ship. It's built, tested, and waiting. It just needs a date that's true.
Sources & further reading
External: Directive (EU) 2019/2161 — the Omnibus Directive, EUR-Lex · Fake urgency, Deceptive Patterns · Dark Patterns at Scale (Mathur et al., 2019)
Related posts: Fake testimonials are a liability · People spend weeks choosing a sofa · The biggest leak in your mobile checkout · Everyone budgets for the VAT