Back-in-Stock Alerts: Turn "Sold Out" Into Sales Instead of Lost Customers

A back-in-stock notification lets a shopper tell you they still want a sold-out item, so you can tell them the moment it's available again instead of losing the sale to a competitor. Done right, it's three parts working together: a way to capture interest while the item is out, an automatic text or email the second it's received, and a running count you can use to decide how many to reorder. Most stores only do the first part, and even that badly.

What Is a Back-in-Stock Notification, and Why Should Retailers Care?

A back-in-stock notification is a message sent to a customer, on their request, the moment an out-of-stock item is available to buy again. It matters because a stockout doesn't just cost the sale in front of you — it costs every sale that customer would have made if you'd reached them again before they bought the item somewhere else.

• A shopper who hits "sold out" leaves with no next step, and no reason to come back on their own
• Popular sizes and colors sell out fastest, so your bestsellers are the items most often silently turning customers away
• Every stockout with no waitlist is a guess about demand you'll never get to check later
• Staff answer the same "do you know when this is back" question over and over with no record of who asked

How Do You Build a "Notify Me" Waitlist Without a Dedicated App?

You don't need a specialized back-in-stock plugin to run this well — you need a place to capture the request and a way to reach people once the item lands. The workflow is the same whether the request comes from the sales floor or your online store:

• Capture the request where it happens — at the register when a customer asks, or through your online store if they land on a sold-out product page
• Attach it to that customer's profile, with the specific item and variant (size, color) they want, not just "restock me on anything"
• Group requests by SKU so you can see, at a glance, how many people are waiting on a single item
• Watch the item's inventory status as you receive the purchase order that brings it back in stock
• Send the alert the moment received quantity posts to the ledger — not when the PO is placed, and not "coming soon"
• Clear or archive the request once the customer has been notified, so the same list doesn't get texted twice

The part retailers skip is the SKU-level grouping. If you only keep a general customer note, you can tell a shopper you'll let them know — but you can't see that fourteen people are waiting on the same blue medium jacket, which is the number you actually need for the reorder decision later.

Text or Email: Which Gets the Sale When Stock Lands?

Text wins on speed — most people read a text within minutes, which matters when you're competing with how fast a customer can search for the same item elsewhere. Email wins on detail — it can carry a product photo, price, and a direct link to buy. The practical answer is to use both, with text carrying the short

"it's back" nudge and email as the backup for customers who didn't opt into texting. Either channel needs explicit consent first; back-in-stock texts are a form of marketing message and follow the same consent and timing rules as any other retail SMS campaign.

When Should You Actually Send the Alert?

Send it when the stock is sellable, not when you know it's coming. Two timing mistakes cost more sales than a slow alert ever will: notifying customers when the purchase order is placed (before it's arrived or been counted in), and batching every back-in-stock alert into a single weekly newsletter instead of triggering it item by item. The first sets a customer up to show up to an empty shelf; the second means someone who's been waiting three weeks for a restock hears about it at the same time as everyone else, including people who don't care about that item at all.

How Can Waitlist Size Tell You How Much to Reorder?

A waitlist is a live demand signal that's more accurate than a sales forecast, because it's made of people who already tried to buy and couldn't. If you use reorder points and par levels to decide when to reorder, the waitlist count is the missing input for how much: it's real, confirmed demand sitting on top of whatever your normal sell-through would suggest.

• Start with your normal reorder quantity based on lead-time demand plus safety stock
• Add the number of open waitlist requests for that exact SKU and variant
• Order at least enough to clear the waitlist on day one — arriving to a restock alert and finding the item sold out again is worse than the original stockout
• If the waitlist is unusually large relative to normal sell-through, treat it as a signal the item deserves a bigger standing reorder point going forward, not just a one-time larger order

How Does Retailer OS Support Back-in-Stock Alerts and Reordering?

Retailer OS gives you the pieces this workflow runs on, without asking you to bolt on a separate app for waitlists. Customer profiles and purchase history hold the request against the right customer, and the items appear against real inventory: every sale, receipt, transfer, and adjustment writes to the same per-location inventory ledger, so "back in stock" means the register can actually sell it, not just that a purchase order was placed.

Sending the actual alert — the text or email that tells a waiting customer their item landed — runs on a Messaging plan, which is a paid plan starting at $49.99/month for texting, email marketing, and a shared inbox (Growth is $99.99/month, Pro is $249.99/month). Messaging plans are what power the campaigns and automations you'd use to reach a waitlist segment, including the restock flow covered in our guide to retail email automation.

For the reorder side, reorder points and par levels flag items that have dropped below the level you set, and receiving against a purchase order updates on-hand the moment stock arrives. If you're on an AI plan (from $19.99/month), Retailer OS can also suggest reorder quantities using demand forecasting — a useful second check against the waitlist count, though the final call on how much to buy is still yours. And because the same catalog feeds your storefront's product feed to Google Shopping, keeping the ledger accurate also keeps your ads from showing an item as available when it isn't, or hiding it once it's back.

None of this needs a second system. Every store on Retailer OS is $99.99/month plus $9.99/month per user seat, with point of sale and inventory included; the online store that would host a sold-out product page is a paid add-on at $99.99/month on that same catalog. See how the pieces fit together on the analytics side or the AI plans page before you decide what to turn on.

What Mistakes Turn a Waitlist Into a List Nobody Reads?

• Collecting the request but never tagging it to a specific SKU or variant, so the alert goes out to everyone instead of the people who actually want that item
• Notifying customers when the PO is placed instead of when the item is counted in and sellable
• Letting the same customer get notified twice because the request wasn't cleared after the first alert
• Ignoring waitlist size when deciding how much to reorder, then running out again on day one of the restock
• Texting without consent, or using a channel the customer never opted into