Scarcity Tell

A countdown timer that resets isn't urgent. It's lying, and your browser remembers what it said last time.

Date: 2026-10-19 Form factor: Browser extension (Manifest V3) Browser surface: content script, toolbar popup, chrome.storage.local Status: Prototype

What it is

Scarcity Tell reads Shopify product pages for the three claims that show up again and again in dark-pattern research: a countdown timer, a "only N left" stock line, and a "people are viewing this" social-proof number. It saves what each one said and compares it against what the same claim said the last time you were on that page. A timer that should have ticked down but shows more time than before, or a stock count that hasn't moved in three days despite "almost sold out" — that's what gets flagged, on the page, with the old and new numbers side by side.

Why it has to be an extension

A site has no reason to tell you its countdown reset, and it has every reason to hope you didn't notice. The only way to catch it is to keep a memory the site doesn't control: a local record of what the page claimed last time, tied to your browser rather than to any account on the retailer's side. That's chrome.storage.local, read and written by a content script on every visit, which is not something a page you're looking at can do to itself.

Who it serves

Online shoppers who've started to suspect the "4 left in stock" banner is decorative. Fake urgency is specifically named in the EU's planned Digital Fairness Act, Australia's ACCC fined Emma Sleep roughly $15 million AUD this year for a countdown timer that reset before each sale actually ended, and a Princeton crawl of 11,000 shopping sites found countdown timers on 361 of them and low-stock messages on 581 — this isn't a rare trick, it's a standard fixture people have stopped trusting but can't easily prove wrong without a tool that remembers what they saw.

Why it could be profitable

Free: unlimited scanning, on-page flags, and a running history capped at 20 tracked claims. Pro ($3/month or a $20 one-time unlock): no cap on tracked claims, plus an exportable evidence log — timestamped before/after readings a shopper could attach to a chargeback dispute or a complaint to a consumer-protection body. That export and any cross-device sync would need a real backend, which this prototype doesn't build; it's noted as roadmap, not shipped. The harder question is whether "prove the timer lied" is worth paying for versus just not buying from that store again — I think the chargeback-evidence angle is the stronger of the two, but it's unproven outside this one prototype. A secondary, more speculative lane: licensing the anonymized, aggregated flag data to researchers or regulators tracking how common these patterns are at scale, which is close to what the Princeton study already does manually.

How to load it in Chrome

1. Open chrome://extensions and turn on Developer mode.
2. Click Load unpacked and select this folder's extension/ directory.
3. Visit any product page on a myshopify.com storefront. Scarcity Tell reads the page once it settles, and flags appear inline the first time it sees a claim repeat with a contradiction — which means the first visit to any given page just records a baseline.

How to try the demo

1. Open index.html in any modern browser — it works straight from file://, no local server needed.
2. Click the Scarcity Tell button in the mock toolbar to open the popup over the mock product page.

The mock page simulates a second visit to a running-shoe listing: the countdown now shows more time remaining than it did an hour ago, the stock line still says "2 left" after three days, and the viewer count has swung from 4 to 51 between loads. The popup and the on-page flags both reflect that comparison. On the real extension, content.js does this scan and the storage comparison live, on whatever page you're on; here, script.js recreates that one comparison from sample-data.json since there's no live page to read.

Permissions, and why each one

What's in this prototype

• A content script that scans Shopify storefront pages for countdown timers, low-stock claims, and viewer-count claims, using text-pattern matching rather than per-theme selectors.
• Per-claim history in chrome.storage.local, keyed by page and claim type, with flags raised on timer resets, static stock counts, and volatile viewer claims.
• Inline on-page badges on the flagged elements, plus a popup showing the current page's flags and a scrollable log of everything caught recently across other pages.
• A free-tier cap at 20 tracked claims, with an upgrade note in the popup.
• A demo harness pre-seeded with 20 tracked claims and a 13-entry flag history across eight mock storefronts, so the popup has a real log to show beyond the one live page.

Roadmap

• Match custom Shopify domains (not just myshopify.com) by detecting the storefront's own Shopify.shop global instead of relying on the URL.
• Add WooCommerce and BigCommerce pattern sets once the Shopify version has real usage to learn from.
• Build the evidence-export and sync backend the paid tier depends on.
• Let a flagged claim link straight to the FTC or ACCC complaint form pre-filled with the before/after reading.
• Track price alongside the countdown, since a few sites pair a resetting timer with a price that quietly ticks back up once it "ends."

Sources

• EU Digital Fairness Act Targets Dark Patterns — the European Commission's planned 2026 legislation names fake countdown timers and "only 2 left in stock" claims as examples of the dark patterns it would cover.
• Emma Sleep fined $15m for fake countdown timers and phantom discounts — Australia's ACCC action over a timer that reset itself before each sale period actually ended.
• Dark Patterns at Scale: Findings from a Crawl of 11K Shopping Websites — the Princeton study behind the 361-site countdown-timer and 581-site low-stock-message figures.