Waitlists & back-in-stock

Captures 'notify me' demand by size and variant, shows it against incoming stock, and releases restocks in waves — one-tap checkout for the people who asked first, one honest question for the ones who didn't buy.

01 · Problem

The restock sold slowly
to everyone except the people who asked for it.

The spreadsheet

'Notify me' goes nowhere

The demand signal exists — sizes, variants, contacts — and it dies in an export nobody opens. Restock day arrives and the waitlist finds out from Instagram, or never.

The blast

Everyone at once, stock for some

One back-in-stock email to the whole list sells out the M in an hour, leaves the XL untouched, and teaches two hundred disappointed people to stop clicking 'notify me'.

The blind buy

Reorders guessed, not counted

The next purchase order is sized on gut feeling while the exact demand — 84 asks for black, size M — sits uncounted in the spreadsheet.

Two hundred people raised their hands. The restock never called on them.

02 · Solution

Demand counted before stock lands. Released in waves — buyers first.

Ongoing · Capture
SignalShopify
Every 'notify me' captured by size and variant
Memory
  • 84 asks: black, size M — counted by variant, not vibes
  • Contact and consent — SMS or email, chosen at signup
  • Sell-out on day 12 — demand kept arriving after stock ran out
Clarwiz· Shopify

Captures each 'notify me' with its variant, channel and timestamp — a demand ledger, not a list.

Clarwiz· Run record

Keeps counting after the sell-out — the demand curve keeps shaping the reorder.

Restock −7 · The count
SignalCockpit
PO time: demand and incoming stock, side by side
Memory
  • Incoming: 30 units M — against 84 waiting
  • Wave plan drafted: three waves, first-asked first, 24-hour holds
Clarwiz· Cockpit

Shows the gap: 84 asks, 30 units — sized before the PO, not after the sell-through.

You· One tap

Approve the wave plan — who gets the first release, and how long each wave holds.

Restock day · Wave 1
SignalSMS
First wave: thirty asked-first customers, one-tap checkout, held units
Memory
  • Wave 1 sent 9:00 AM — thirty people, private link, 24-hour hold
  • 18 of 30 sold in 40 min — full price, no discount
Clarwiz· SMS

Texts the first thirty: it's back in your size — your link holds one unit for 24 hours.

Clarwiz· Stripe

One-tap checkout on the held unit — no cart, no re-search, no code.

Clarwiz· Run record

Wave 2 releases the unclaimed holds automatically at hour 24 — nothing sits reserved for a no-show.

Day 3 · Close the loop
SignalCockpit
Sold through — and the non-buyers answer why
Memory
  • 27 of 30 sold — by wave two, all at full price
  • Non-buyer reasons logged: price (4), bought elsewhere (2)
Clarwiz· Email

Asks the non-buyers one honest question — the answers land in the demand ledger.

Outcome· Run record

Restock sold in three days, not three weeks — and the next PO is sized on counted demand.

Every ask, wave and sale above is logged — demand in, releases out, counted to the unit.
03 · What changed

Same restock. Sold to the waitlist first.

MomentBefore ClarwizOn Clarwiz
The 'notify me'An export nobody opens.A demand ledger by size and variant.
Restock dayOne blast, instant sell-out, 200 disappointed.Waves — asked-first, held units, 24 hours each.
The checkoutSearch the site again, hope.One tap on a held unit. No code, no cart.
The reorderSized on gut feeling.Sized on 84 counted asks, before the PO.
Non-buyersSilent, forever.Asked once — the reasons shape the next drop.
04 · Outcome
40min
for wave 1 to sell 18 of 30 units — full price, first-asked first.
90%
of the restock sold inside three days, against three weeks the drop before.
0
discounts spent. The waitlist wanted the product, not a coupon.
Numbers from one pilot, counted to the unit. Your log will differ — that's why it's a log.
05 · FAQs
Where does the 'notify me' button live?
On your product page, exactly where it is today — Clarwiz takes over what happens after the click: variant, channel and consent captured, and the follow-through actually happening. No new widget for customers to learn.
Why waves instead of telling everyone at once?
Because a blast rewards whoever's fastest, sells out one size in an hour and disappoints everyone else. Waves reward whoever asked first, hold real units behind each link, and give you a lever — wave size, hold time — instead of a stampede.
What if wave 1 doesn't buy?
Holds expire on their own — at hour 24 the unclaimed units roll to wave 2 without anyone touching a spreadsheet. Non-buyers get one honest question, and the answer is logged against the demand ledger.
Does this work for preorders and drops too?
Same engine: capture demand by variant before anything exists, show it against planned stock, release in waves. A drop is just a restock where the count starts at zero.
What do we need to integrate before a demo?
Nothing. The demo replays your last sell-out read-only — who asked, and what a wave release would have sold. Going live connects your store and payments — Shopify, Stripe and about 3,000 others.

See this run on your own data.
Thirty minutes, nothing connected.

We take this process, connect nothing, and show you the run end to end on your real conversations and orders. When you're ready, go live at the autonomy level you choose.

30 minutes · One process · SOC 1 · SOC 2 · ISO 27001 · PCI DSS · GDPR