Why subscribers haven't been notified yet

If subscribers are sitting in Waiting even though you've restocked, work through these checks in order. They cover nearly every case we see.

1. The restock didn't reach the campaign's threshold

Each campaign has a restock threshold: notifications only send when available inventory reaches at least that many units.

Threshold 1 (the default) — any restock triggers notifications.
Threshold 5 — restocking 1–4 units triggers nothing, and subscribers stay in Waiting until stock reaches 5 or more.

A raised threshold is the most common reason for "I restocked multiple times and nothing sent." Check the threshold on the campaign that owns the waiting subscribers — not the campaign you expected to own them (see How campaigns choose where signups go).

2. The campaign is paused

Pausing a campaign is a hold, not a delete: it keeps collecting nothing new and sends nothing, but existing subscribers stay saved. They'll be notified on the first restock after you reactivate the campaign — pausing never loses your waitlist.

3. Batch settings are pacing the sends

If the campaign has a batch size and delay, notifications go out in waves — e.g. batch size 1 with a 2-minute delay sends one email every 2 minutes. A long waitlist with small batches takes a while by design; the Activity tab shows each batch as it goes out.

4. The subscriber is on a different campaign than you expect

Subscriptions belong to whichever campaign matched the product at signup time. If a subscriber isn't in this campaign's list, check your other campaigns (including the Default Campaign) — a higher-priority campaign targeting All products collects everything.

A note on duplicate signups

A shopper can only be waiting once per product variant. Re-entering the same email shows "you're already on the list" instead of creating a second entry — they'll still be notified exactly once when it restocks.