Back-in-stock notifications via SMS and email: a waitlist journey for OOS products

A back-in-stock notification journey means: when a shopper joins a waitlist for an out-of-stock SKU, you SMS/email them the moment inventory returns — with a direct product link — so the sale does not walk to a competitor.

What is a back-in-stock notification?

It is a waitlist journey. The shopper taps “notify me” on an OOS PDP (or equivalent), you store identity + SKU/variant, and when a restock event fires you send a short message with the exact product link.

In Iranian WooCommerce, plugins like Pars Stock Notifier, FarazSMS restock flows, Melipayamak guides, and store SMS add-ons sell exactly this Digikala-familiar pattern. The ChatGPT ask is usually: “How do I auto-SMS customers when a product is back in stock?”

Why Iranian stores need it

OOS on bestsellers is normal in fashion, electronics, beauty, and even online grocery. Shoppers leave unless you promise to notify them — and then actually do.

Three concrete benefits:

1. High intent — waitlist signups are hotter than cold browsers;
2. Fewer tickets — less “when is it back?” if you announce it yourself;
3. Smarter inventory signal — a long waitlist is a buying/supply signal, not only a marketing trick.

Consent and transactional vs promotional boundaries

“The item you asked for is back” is close to transactional. Add a heavy discount or a blast of unrelated SKUs and cautious teams treat it as promotional.

Practical rules:

• Keep the first alert on stock + product link;
• Treat discount codes as optional and separate;
• Respect quiet hours / advertising-line rules (promo sends overnight are often restricted in Iran);
• Require explicit marketing consent for follow-on blasts.

Use the transactional-vs-promotional guide for channel nuance; this post focuses on the stock journey.

Designing the “notify me” form

1. Make it obvious on OOS PDPs, not buried;
2. Prefer mobile if SMS is your main channel; collect email too when you can;
3. Clear consent checkbox if you treat the message as promo;
4. Store exact variant (size/color);
5. Confirm signup so the user does not think it vanished.

Common failure: a generic newsletter form with no SKU binding — then you restock and send a vague broadcast.

Timing after inventory returns

If you update stock manually once a day, send in allowed daytime hours — overnight promo lines risk blocks.

Sample SMS and email

SMS:

“[Brand] [short product] is back. Buy: [link] STOP11”

Email: image, variant name, buy button, limited-stock line only if true.

Avoid:

• Category links instead of the PDP;
• Three SMS in one hour;
• Ten unrelated products in the first alert;
• Nudging after stock dies again without updating state.

Step-by-step implementation checklist

1. Waitlist event — stock_alert_requested with user + product_id + variant;
2. Restock event — product_back_in_stock or store status change;
3. Queue/segment — waiters for that SKU who have not purchased yet;
4. Journey — restock trigger → SMS → email (order by your stronger channel);
5. Exits — order_completed on that SKU, opt-out, or OOS again;
6. Cap — at most one secondary reminder;
7. Test — real Kavenegar/Nikaline Persian preview;
8. Two-week report — delivery, CTR, purchase in 24–48h, STOP rate.

Common mistakes

1. Storewide blast instead of that SKU;
2. Multi-day delay after restock;
3. Forgetting variant (size/color);
4. Messaging after they already ordered the same item;
5. No clear opt-out path;
6. Mixing restock alerts into Black Friday blasts without segmentation.

How to build it in Leadara (truthfully)

Leadara provides events, segments, and journeys; SMS goes through your Kavenegar or Nikaline:

1. Wire waitlist + restock events from the store/webhook into profiles;
2. Build a restock-triggered journey filtered to “no order for this SKU yet”;
3. Fill SMS/Email steps with the exact variant PDP link;
4. Exit on purchase or opt-out;
5. Honor quiet hours for promotional framing;
6. Dashboard AI Chat is for internal copy drafts only — not a customer-facing bot;
7. Live Chat handles human “when is it back?” while still OOS;
8. Popups can host the waitlist form; gamification does not replace the alert.

If SMS consent logging is weak, fix that before scaling the waitlist.

Real Iranian store scenarios

Fashion and footwear

Size 40 black is OOS; the shopper waitlists that exact variant. When only size 42 returns, do not message “your size is back.” Keep variant precision. If several sizes return together, tell each person only their size.

Beauty and health

Expiry and authenticity matter. The alert only needs the same SKU link — no medical claims or fake “last units” pressure. If a flash campaign runs in parallel, keep the waitlist segment out of the public blast so nobody gets two conflicting messages.

Electronics

Limited stock and price swings are common. Speed beats discount. If price moved a lot since signup, say so in the email; checkout shock kills trust.

Fast-moving consumables

Sometimes “OOS” means today’s supply slot is full, not a catalog delist. Match copy to operations; do not promise hourly ETAs if the warehouse updates once a day.

Prioritizing a long waitlist

1. Simple FIFO — earlier signups get notified first;
2. VIP / repeat buyers — only with a transparent loyalty policy that does not insult everyone else;
3. Wave splits — 100 waiting and 20 units means notify 20, then the next wave on the next restock;
4. Honest support — human live chat can say “you’re in the queue”; do not invent a promise bot.

Helpful metrics: notified/signed-up and purchased/notified in wave one. If wave one always buys and others never see stock, raise supply or manage expectations in the UI.

FAQ

Is a back-in-stock alert transactional or promotional?

Stock + requested SKU link is close to transactional; heavy codes and unrelated offers usually make it promotional.

SMS or email?

SMS for speed; email for detail. A short combo works best.

What if only two units returned?

Send fast and be honest about limits; do not promise everyone a unit.

How many reminders?

One at restock; at most one 24–48h later if they did not buy.

Can non-buyers join the waitlist?

Yes — that is the point. Capture identity and consent cleanly.

Does it collide with abandoned cart?

If they cart after the alert, cart recovery wins; do not double-message.

Can we use this for preorders?

Similar idea, but be clear about release dates; do not blur real stock with preorder promises.

How do we measure ROI?

Compare 24–48h purchases after the alert to SMS cost — usually one of the highest-intent automations.

Wrap-up and next step

This week: turn on waitlist CTAs on OOS PDPs, connect restock events to a journey, write one short same-SKU SMS, lock purchase exits, and measure time-to-send. “We’ll tell you” only has credit when you actually send in minutes.

Related reading

• Transactional vs promotional email and SMS: the operator’s guide
• SMS marketing opt-in for Iranian online stores: from the form to a compliant send
• Abandoned cart recovery playbook for Iranian online stores: SMS + email