A back-in-stock alert records who wants a notification. A conditional stock request records what exact variant and quantity the shopper needs, whether substitutes or preorders are acceptable, how long the request remains valid, and what happens after inventory returns.
- Alerts are useful for simple notification; requests support decisions.
- Exact variant and quantity prevent misleading demand totals.
- Substitution tolerance can recover demand before a full restock.
- Inventory must be revalidated before checkout.
When a stock alert is enough
If the only goal is to tell a shopper that a single variant is available again, a conventional stock alert is a good, low-friction tool. It should still collect permission clearly and avoid sending messages after the shopper opts out.
What structured stock demand adds
Merchandising and purchasing teams need more than subscriber count. Exact quantity, substitute tolerance, acceptable preorder timing, request expiry, and shopper commitment make the signal more useful for allocation and replenishment decisions.
The request can remain waiting for a deterministic inventory event. When the exact condition is met, the merchant can notify the shopper or review a private offer without creating a public promotion.
Avoid overselling during a restock
A notification is not a reservation unless the merchant explicitly creates and communicates one. Every checkout path should check live sellable inventory, safety stock, quantity, market, and offer expiry. If those checks fail, show a safe next action instead of a broken checkout.
Frequently asked questions
Can a customer request more than one unit?
Yes, when the form captures quantity explicitly. The merchant should compare that quantity with live inventory and any safety-stock rule before accepting.
Is a back-in-stock request a reservation?
No, not by default. Reservation terms must be explicit and time-bounded; otherwise inventory is rechecked when the shopper opens checkout.