United Kingdom · CAP Code 3.7 · availability
Limited stock and “only X left” claims on UK landing pages — CAP 3.7 literacy
Product detail pages, cart drawers and checkout modules often show “Only 2 left”, “Selling fast”, or dynamic stock bars tied to SKU quantity. Shoppers frequently read those cues as literal warehouse facts. Under CAP Code 3.7, availability and scarcity wording is usually treated as an objective claim that needs substantiation before publish. This guide helps UK marketers inventory limited-stock copy for a claim register — not ASA clearance and not legal advice.
Why scarcity modules are claims, not pure UX
Published CAP and ASA materials on substantiation expect marketers to hold evidence before an ad makes factual implications. A red “Low stock” pill next to a variant selector implies the business knows current quantity. That is different from subjective puff such as “customer favourite”, which still needs care but sits on a different risk column in your register.
Inventory every placement separately:
- PDP hero and variant-level counters.
- Collection pages aggregating many SKUs — “limited availability” without naming which SKU.
- Email capture modals reusing the same counter logic.
- App WebViews mirroring the mobile site — breakpoints often hide or restate the claim.
Common limited-stock patterns
| On the page | Likely consumer takeaway | Register note |
|---|---|---|
| “Only 4 left in stock” | Exact units available now | SKU, warehouse, refresh interval, oversell rules |
| “Almost gone” / “Selling fast” | Imminent sell-out | Define metric: sales velocity vs absolute stock |
| Progress bar “82% claimed” | Measured allocation depleting | Denominator and time window |
| “Limited edition — when it’s gone, it’s gone” | Finite production run | Manufacturing batch evidence, not just marketing label |
| Store pickup “2 at your local shop” | Branch-level quantity | POS sync lag, reservations, online basket holds |
Pair with urgency timers — countdown timer advertising — and clearance modules — clearance sale claims. A timer plus a fake low-stock counter compounds consumer takeaway.
CAP 3.7 literacy — material information
Rule 3.7 requires objective claims to be substantiated. Scarcity copy also interacts with rule 3.9 (material information): if the counter applies only to one colour but the hero shows another, the shopper may be misled about availability of the pictured item. Log variant scope in the evidence column.
Marketplace and dropship models add complexity. If fulfilment is split between your warehouse and a supplier API, the register should state which system feeds the counter and what happens on API timeout — CiteBefore flags wording; it does not audit your ERP.
Dynamic counters vs static copy
JavaScript-driven inventory
Engineering may treat the widget as “real time”. Marketing still owns the claim consumers see when the script fails open and shows a default “Only 1 left”. Screenshot staging with ad blockers off and on; log failure states in the register.
Manual merchandising
Merchandisers sometimes paste “Limited stock” during a campaign without tying to quantity. That is still an objective scarcity implication unless clearly labelled as generic promotional language — and generic scarcity is itself risky under published ASA case themes on urgency.
Pre-publish inventory habit
- List each URL and SKU where a counter appears.
- Record the consumer-facing string exactly — including aria-labels.
- Attach stock evidence or mark gap in the register — agency template.
- Run a free scan on staging — free scan.
Marketplace, bundles and multi-SKU pages
Collection pages that say “Selling fast across our range” without SKU-level substantiation can imply range-wide scarcity when only one variant is low. Bundle offers — see bundle pricing claims — may inherit a parent product’s counter while components differ. Log whether the counter binds to the master SKU, each variant, or the bundle ID in your OMS.
Third-party marketplace fulfilment adds another column: if the ad promises “Only 2 left” but stock sits with a partner warehouse, the register should name which inventory feed powers the widget and what shoppers see when the partner reports zero.
After publish: change control
Merchandising teams sometimes raise counters during campaigns without updating the register. Treat counter threshold changes like copy changes — re-scan before major paid media bursts. Compare historical screenshots in your claim register to before-and-after URL discipline when disputes arise internally.
What CiteBefore does not do
- Not warehouse auditing — we do not reconcile pick faces to your WMS.
- Not ASA clearance — we inventory and suggest evidence columns.
- Not legal advice on Consumer Rights Act fit with availability claims.
Questions
Are “only 3 left” banners objective claims under CAP 3.7?
Consumers often read low-stock counters as factual statements about warehouse quantity. Treat them as objective availability claims needing substantiation, not decorative urgency.
What evidence belongs in the claim register?
Stock system export, SKU-level quantity, refresh frequency, and whether the counter applies to the variant shown. Log exclusions such as marketplace fulfilment.
Does CiteBefore clear limited-stock copy?
No. CiteBefore inventories claims on live URLs and flags evidence gaps. The ASA decides complaints.
More guides: /guides/. Green badges: eco certification badge claims.