Back-in-stock alerts on WhatsApp: the honest version

There is no back-in-stock trigger, because no stock-level event reaches the automation builder. Shopify delivers seven events — order placed, payment success, payment failed, order shipped, order delivered, order cancelled and abandoned cart — and none of them fires when inventory changes.

We are stating that plainly because it is routinely sold as automatic. What works instead is a two-step process: a flow captures who wants the item, and you send the alert as a broadcast when it lands. That is more manual than the promise, and it still recovers sales you are currently losing.

What the flow can do

Sending the alert when stock arrives

1. Open your waitlist sheet and filter to the item that has landed.
2. Go to Broadcasts → New campaign and choose the Google Sheet as the audience source.
3. Select an approved marketing template — a restock alert is promotional, so it cannot be utility.
4. Send, then clear those rows so nobody is told twice.

The audience side is covered in broadcasting from a Google Sheet, and the sheet mechanics in using a Google Sheet as your automation's database.

The constraints on the alert itself

Constraint	Consequence
It is a marketing template	Charged per recipient, every time
US numbers cannot receive marketing templates	US waitlists cannot be alerted this way
Per-user marketing limits apply	Some sends may not deliver
Requires marketing opt-in	Asking to be notified is good evidence of consent

The US restriction is documented in Meta's per-user marketing template limits, alongside the fact that these limits do not apply in the EEA, the UK, Japan or South Korea. Read what's left for US stores if that is your market.

Make the capture flow catch real messages

Customers do not write "please add me to your back-in-stock waitlist". They write "sold out?", "when will you have it", "any more of these", "available?". Build the keyword list from your own inbox rather than from imagination, and include transliterated phrasings if your customers use them — keyword triggers that actually match covers the technique.

Two things worth doing while you have their attention

1. Offer an alternative now. A customer who wants the sold-out blue one may take the green one today. One extra question converts a waitlist entry into an order.
2. Give a rough timeline if you have one. "Back in about two weeks" reduces the follow-up messages asking when.

Both are free, because the customer messaged you first and the conversation window is open.

What would have to change for this to be automatic

A stock-level event would have to reach the builder — either from Shopify, which does not currently send one to us, or pushed by your own system. That second route exists today: if your inventory software can post an event when stock lands, the External Event trigger can start a flow from it.

That is a developer task, not a no-code one, and for most stores the sheet and a broadcast is the better trade. But it is a real option, and it is the honest answer to "can this be automated?" — yes, if you build the missing half.

What the waitlist is worth even without automation

It is easy to read the manual step as a reason not to bother. That would be a mistake, because the capture half is where most of the value sits.

Without the flow	With it
"Sorry, sold out" and the customer leaves	Their name, number and the exact item are recorded
You guess what to reorder	You have a demand signal per product and size
Restock announced to everybody	Announced to people who asked, so it converts
No opt-in evidence	A customer who explicitly asked to be told

That second row is quietly the most valuable. A waitlist sheet is a purchasing document as much as a marketing one — it tells you which size sells out first and how many people wanted it, which is information most small stores simply do not collect.

Turn the "no" into a sale today

The customer is in a live conversation and the window is open, so everything you send now is free text at no cost. Two questions worth adding before the flow ends:

1. Offer the nearest alternative. Someone who wants the sold-out blue may take the green today. This converts a share of waitlist entries into orders immediately, which no restock broadcast can.
2. Give a rough timeline if you have one. "Back in about two weeks" prevents the follow-up messages asking when, and sets an expectation you can meet.

Sending the restock message well

When stock lands, the audience is the sheet, and the message is a marketing template — so the constraints from earlier apply: charged per recipient, subject to per-user limits, and undeliverable to US numbers.

Three things make it land better:

• Send it promptly. A waitlist message three weeks after restock reaches people who have bought elsewhere.
• Name the item. "The item you asked about" is weaker than "the {{1}} you wanted", and you stored exactly that.
• Clear the rows after sending, so nobody is told twice and your next restock does not re-message people who already bought.

The audience mechanics are in broadcasting from a Google Sheet, and the consent position — a customer who asked to be told is unusually clear evidence — in opt-in rules.

Catching the question in the first place

None of this runs unless the keyword condition matches, and customers do not write "please add me to your back-in-stock waitlist". They write short, and often not in English.

A starting list: out of stock, sold out, back in stock, restock, available, availability, when will you have, any more, notify me, let me know. Then add the phrasings from your own inbox, including transliterated ones — keyword triggers that actually match explains why one spelling catches a fraction of the people who meant it.

If the flow shows zero runs in its activity view, this is the cause. It is never the sheet.

A simpler version with no sheet at all

If connecting Google feels like too much for a first attempt, there is a cut-down version that still captures the demand: ask which item they want, save it to a contact field, and tag the contact "waitlist". You then send the restock message to that tag as a broadcast audience rather than to a sheet.

It is less useful for purchasing — you cannot easily count how many people wanted each size — but it takes minutes and it keeps the customer. You can always add the sheet later. Contact fields are covered in saving customer answers to contact fields, and remember the field has to exist under Settings → Contact Attributes first or the save silently does nothing.

Why we will not call this automatic

Competitors advertise back-in-stock alerts as a switch you turn on, and it is worth being explicit about why this article does not. Nothing in the automation builder observes your inventory. There is no trigger that fires when a count changes, so no flow can react to one.

The honest framing is that this is a two-step process with one manual step: automated capture, manual send. That manual step takes a few minutes per restock and it is the reason the whole thing works at all — a merchant who knows they will have to send it also remembers to clear the rows afterwards, which is what stops customers being told twice.

If a vendor tells you their version is fully automatic, the useful question is which event they are listening to. Either they have built the inventory integration themselves, or they mean the same capture-and-broadcast pattern described here.

None of which makes the flow less worth building. A waitlist you actually collect is better than an automation you do not have, and the capture half is where the customer is saved — the send is a few minutes of your time once the stock lands.

For scale, a waitlist of 40 people on one sold-out size is about 2 minutes of filtering and sending, against 40 customers who would otherwise have bought elsewhere. That ratio is why the manual step is not the objection it first appears to be.

Build the capture half today; the send takes minutes when the stock lands.

Capture today; send when it lands.

What the restock message will cost you

The capture half is free — the customer messaged you, so it runs inside an open 24-hour window, and service conversations have been free and unlimited since 1 November 2024 under Meta's pricing documentation.

The send is where the cost sits, and it is worth planning for. A restock alert is promotional, so it is a marketing template: charged on every delivered message, subject to Meta's adaptive per-user marketing limits — for which Meta publishes no numeric threshold — and undeliverable to US phone numbers entirely. Those limits do not apply in the EEA, the UK, Japan or South Korea.

Two consequences for how you run the waitlist. Send promptly, because a list that ages converts worse and you pay the same either way. And clear the rows after sending, so the next restock does not re-message people who already bought — every duplicate is both a charge and a small withdrawal from the goodwill that keeps your quality rating green.