Your conversion rate has been flat for two quarters. Traffic is fine, the product is fine, and nothing obvious has broken. Meanwhile the countdown on your product pages has been running continuously since March, resetting every time somebody loads the page.
Those two facts are related, and the relationship is almost impossible to see in a dashboard. Fake urgency ecommerce tactics do not fail loudly. They fail on one segment at a time, starting with the segment you can least afford to lose.
Why does the damage stay hidden?
Because the people it works on and the people it damages are different, and your headline number blends them.
A first-time visitor has no way to know that your timer resets. To them, the deadline is information, and it behaves exactly as intended. So the conversion rate on new traffic holds up.
A returning visitor sees the same offer with a fresh countdown. They now know one specific thing about your store: the numbers on it are decorative. That knowledge does not stay contained to the timer. It generalises to the sale price, the delivery estimate, and the stock count.
- New-visitor conversion stays flat, so the blended number reassures you.
- Returning-visitor conversion drifts down slowly enough that no single week looks wrong.
- The gap widens over months, and by the time it moves the aggregate you have been training your best customers for a long time.
Repeat customers are the cheapest revenue any store has. You have already paid to acquire them. A mechanic that specifically degrades trust with that group is expensive in a way that is genuinely difficult to attribute after the fact.
What actually counts as fake?
Not urgency. The false version of it. The distinction is precise and it is worth being exact, because a lot of legitimate mechanics get lumped in.
| Mechanic | Fake? | Why |
|---|---|---|
| Timer that resets on page load | Yes | The deadline does not exist |
| Same sale relaunched weekly under a new name | Yes | The offer never actually ends |
| Timer that hits zero and the price does not change | Yes | The claim was not kept |
| Stock counter decrementing on views | Yes | A false statement about your warehouse |
| Daily dispatch cutoff | No | True, and it genuinely resets each day |
| Recurring weekly sale that really ends each week | No | The price reverts, so the claim holds |
| Pre-order window with a production deadline | No | The constraint is physical |
The pattern: a recurring deadline is fine if the thing it describes actually recurs. A dispatch cutoff resets every day because the warehouse closes every day. A timer resets on page load because nothing happened at all.
Is it actually illegal now?
In the UK, yes, and the wording is worth reading rather than paraphrasing.
Under Schedule 20 of the DMCC Act 2024 it is a banned practice to falsely state that a product will only be available for a limited time, or that it will only be available on particular terms for a limited time, in order to elicit an immediate decision and deprive consumers of sufficient opportunity or time to make an informed choice.
Three things follow from that:
- Urgency is not banned. Falsity is. You can run as many real deadlines as you have.
- Intent is part of it. The provision names eliciting an immediate decision, which is exactly what a timer is for. So the mechanic is squarely in scope when the claim is untrue.
- Recurrence is not the test. Running the same promotion again is fine. Running it continuously while claiming it ends is not.
Even outside the UK this is the right standard, because enforcement is the smaller risk. The larger one is a customer base that has quietly stopped believing you.
How did this get installed in the first place?
Rarely as a decision. Almost always as a default.
Most timer apps make a rolling countdown the easy option and a fixed deadline the configured one. Somebody sets up a sale, accepts the defaults, and ships. Nobody chose to mislead anyone. The app chose, and the merchant did not notice because the storefront looks correct from a desk where you already know when the sale ends.
The same is true of stock counters. Very few merchants deliberately fabricate inventory. They install an app whose default behaviour is to invent a number, tick it down on views, and reset it for the next visitor.
What else does it quietly cost?
Three things beyond the conversion drift, and none of them show up where you would look for them.
Support load. Fake deadlines generate a specific kind of message: the customer who missed the sale and wants the price honoured, or who noticed it came back and wants to know why they were rushed. Each one is a person who was paying attention, which is to say a person worth keeping.
Review sentiment. Pressure selling produces buyer's remorse, and remorse arrives a week later attached to a one-star review that mentions the tactic by name. That review then does the damage permanently, to every shopper who reads it, long after the campaign ended.
Internal calibration. This one is subtle and matters most. A store that runs a permanent sale loses the ability to tell whether discounting works, because there is no baseline left to compare against. Everything is always on offer, so nothing can be measured. Merchants in this position often cannot say what full price even means on their own store any more.
That last cost compounds with the others. You cannot diagnose a conversion problem while every product is permanently discounted, because the obvious lever has already been pulled and held down.
How do you fix it without losing the mechanic?
You almost certainly have real deadlines you are not using. Swap, do not delete.
- Audit what is currently running. Every timer, every stock badge, every "selling fast" label. Write down what each one claims.
- For each, name what happens at zero. If the answer is "nothing", that mechanic is false and comes down today.
- List the deadlines you genuinely have. Dispatch cutoff, delivery-by dates for named occasions, real sale end dates, pre-order windows, discontinued lines.
- Replace the biggest offender first, usually the product page timer, with a real deadline from that list.
- Verify the price actually changes at zero. If it does not, you have moved the problem rather than fixed it.
- Reduce the footprint. Whatever survives should be on the products it genuinely applies to, not the whole catalogue.
- Put an end date in your own calendar, because the most common way a real deadline becomes a fake one is that nobody turned it off.
Step three is where most of the value is. The dispatch cutoff in particular is true, resets honestly, repeats forever, and helps the shopper plan rather than pressuring them.
How long does trust take to come back?
Longer than it took to lose, and there is no clean way to measure the recovery.
The practical approach is to stop watching the timer and start watching the segment. Track returning-visitor conversion separately from new, monthly rather than weekly, and expect the line to move slowly. You are not undoing a campaign. You are undoing a belief.
Two supporting signals worth adding: refund and cancellation rate, because pressure selling produces buyer's remorse that lands a week later, and any support message that mentions a deadline. A handful of "the timer said I had two hours" tickets tells you the mechanic is being noticed for the wrong reason.
The same slow-rebuild dynamic applies to reviews on your product pages, and for the same reason. Both are claims a customer can check, both are cheap to lose, and both are rebuilt one honest interaction at a time.
Where does Edge Timer fit?
Edge Timer is ours and it is new, so there is no review history to point at, which is worth weighing.
It is built around the assumption that the deadline is real. Timers take a specific date and time rather than a rolling window, the timezone is resolved server-side so a shopper abroad sees the correct remaining time, and at zero the timer removes itself instead of freezing above an unchanged price.
None of that stops anyone running a dishonest deadline. Software cannot. What it does is remove the excuse that the default made you do it, because the default here is a real date, and the fake version is the one you would have to go out of your way to build.
Questions people ask next
How would I know if fake urgency is hurting me?
Split conversion rate by new versus returning visitor and watch the gap over months rather than weeks. Fake urgency holds up on first-timers, so the blended number looks stable while returning-visitor conversion drifts down. By the time the aggregate moves, you have been training your best customers to discount you for a long time.
Is an evergreen countdown timer illegal?
In the UK, falsely stating that a product is only available for a limited time in order to elicit an immediate decision is a banned practice under Schedule 20 of the DMCC Act 2024. An evergreen timer on an offer that never ends is the case the guidance describes. The test is whether the claim is true.
SourceWhat if my competitors all run fake timers?
Then the tactic is already discounted by shoppers in your category, and you get the reputational cost without the conversion benefit. Being the store whose deadlines are real is worth more in a market where nobody else's are, because it is the one claim a customer can check for themselves.
Can I fix this without removing urgency entirely?
Yes, and you probably should not remove it. Almost every store has real deadlines it does not display: a dispatch cutoff, a delivery-by date, a genuine sale end. Swapping an invented deadline for one of those keeps the mechanic and removes the liability.
Anurag Chandra
Founder, Edgecoms
Anurag runs Edgecoms, a studio of Shopify apps. He spends most of his week inside merchant stores working out why a number is lower than it should be.
Connect on LinkedInRead this on your assistant
Opens with a summary request for this page already written.