What if the item never comes back?

Tell the customers who asked, once, with the closest alternative. Silence leaves them waiting and mistrustful; an honest message with a good substitute often converts. Clear the requests so they do not fire on a different variant later.

How do we calculate days of cover?

Units on hand divided by the average daily units sold over a recent window — two to four weeks for fast movers, longer for slow ones — adjusted for known promotions. Simple and automatic beats precise and manual.

Should back-in-stock requests get a discount?

No — the customer already wants the item, and they convert on the notification alone. Keep incentives for flows where intent has faded. The one exception is a customer who waited a very long time, where a small thank-you is fair.

← Blog·D2C & e-commerce

Back-in-stock and low-stock automation: turning stockouts into demand signals

A stockout is a lost sale unless the customer can ask to be told. The back-in-stock flow, the low-stock alerts to the buying team, and the reporting that shows what to reorder and what to promote.

26 Nov 2025 · 2 min read · by HeiSyn

Out of stock is where e-commerce demand goes to die quietly. The customer lands, sees the greyed-out button, and leaves; nobody records that a sale was wanted. A back-in-stock flow captures the intent, the low-stock alert prevents the next stockout, and together they turn inventory from a guess into something the customers help forecast.

Capture the intent

On every out-of-stock variant, a one-tap 'notify me' that collects email or WhatsApp with consent. Store the request against the variant. The count of requests per variant is a demand signal the buying team never had.

Notify the moment it lands

When inventory for the variant goes above zero — from the store's inventory event, not a nightly check — send the notification in the order the requests came in, with a direct link and, if stock is limited, a note that it is. Stop when stock runs out again and queue the rest. Conversion on these messages is among the highest of any flow.

Alert the buyers before the stockout

Days of cover per variant, calculated from recent sales velocity, with an alert when it drops under the supplier lead time. Include the back-in-stock request count so the buyer sees demand that is not yet in the sales figures. Slack or email, weekly for the whole catalogue and immediately for fast movers.

Feed the reporting

Lost-sale estimate per stockout from request counts and conversion rates; reorder recommendations ranked by that estimate; which promotions to run for overstocked variants. Inventory decisions become a report, not an argument.

Questions people ask next

What if the item never comes back?: Tell the customers who asked, once, with the closest alternative. Silence leaves them waiting and mistrustful; an honest message with a good substitute often converts. Clear the requests so they do not fire on a different variant later.
How do we calculate days of cover?: Units on hand divided by the average daily units sold over a recent window — two to four weeks for fast movers, longer for slow ones — adjusted for known promotions. Simple and automatic beats precise and manual.
Should back-in-stock requests get a discount?: No — the customer already wants the item, and they convert on the notification alone. Keep incentives for flows where intent has faded. The one exception is a customer who waited a very long time, where a small thank-you is fair.

inventorye-commercedemand

Want this built for your team?

A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.

blog/inventory-and-back-in-stock-automation