Recover stockout sales by capturing the exact variant, quantity, acceptable substitutes, timing, preorder or reservation preference, and request expiry. Use that evidence for replenishment and allocation, notify only with consent, and recheck sellable inventory before checkout. Do not treat alert subscriptions as guaranteed orders.
- Stockout demand must be variant- and quantity-specific.
- Substitution tolerance can clear demand before exact replenishment.
- A notification is not a reservation unless terms explicitly say so.
- Safety stock and live inventory must be checked at conversion.
Diagnose the revenue constraint before choosing a tactic
Combine product views during unavailable periods, exact variant attempts, alert or request data, substitute behavior, cancellation reasons, and replenishment lead times. Avoid multiplying subscribers by list price and calling it lost revenue. Some shoppers no longer need the item, wanted multiple units, or would accept another variant.
Treat profitable sales as a system: qualified traffic multiplied by conversion, order value, repeat behavior, and contribution margin. A tactic that raises one number while damaging another is not durable growth. Segment the evidence by product, variant, device, market, new versus returning customer, and purchase stage before deciding what to change.
A practical merchant playbook
Offer useful alternatives immediately, then capture a structured request when the exact need remains unresolved. Route high-value or time-sensitive demand for review, group compatible requests for purchasing insight, and notify only when the relevant condition is actually satisfied. Define whether any inventory is reserved and for how long.
- Capture exact variant, quantity, timing, substitutions, and expiry.
- Show approved alternatives without misrepresenting compatibility.
- Separate notification, preorder, reservation, and private-offer terms.
- Respect safety stock, markets, locations, and concurrent demand.
- Reconcile paid orders and expired requests with the original signal.
Where BuyWhen fits—and where it does not
BuyWhen adds the decision context missing from a basic stock alert and can keep requests waiting for deterministic inventory evidence. Merchants see demand clusters while each customer's consent, requested quantity, and expiry remain distinct.
BuyWhen is most relevant when a shopper has purchase intent but one explicit condition is unresolved: price, stock or variant, delivery date, product question, bundle, or custom quote. It does not replace acquisition, storefront quality, checkout, customer service, or a sound product. Use it as the structured demand and decision layer between those systems.
Measure the change without overstating the result
Report unavailable product views, request rate, exact units requested, substitute acceptance, restock notification, checkout, paid order, time to fulfillment, expiration, and cancellations. Use conversion probabilities rather than assuming every requested unit becomes a sale.
Record the full path from eligible shopper to request, qualification, merchant decision, offer, checkout, paid order, refund, and cancellation. Report potential demand, attributed paid sales, net sales, and experimentally estimated lift as separate measures. Document the window and exclusions so a useful signal never becomes an unsupported revenue claim.
Frequently asked questions
Is an out-of-stock request a preorder?
No. A preorder includes explicit commercial and fulfillment terms. A request or notification can simply record interest until the merchant decides what is feasible.
Should I hide sold-out Shopify products?
It depends on restock likelihood, search value, substitutes, and customer experience. A clear unavailable state with alternatives or a useful request path can preserve demand without misleading shoppers.
Can requested units guide replenishment?
Yes as one input, adjusted for duplication, expiry, confidence, lead time, substitution, existing forecasts, and the fact that a request is not a guaranteed purchase.
Sources and further reading
Product guidance is grounded in BuyWhen's documented behavior. The broader commerce and search principles in this guide also reference these primary sources: