Distinguish unavailable stock, notice requests and alternatives
Attach a stock notice to the exact unavailable selection and state what the request does. Keep an alternative-product choice distinct from notification permission. Receipt, later stock and any reservation are separate states; the design must not imply a confirmed restock date or held item without a real supporting mechanism.
Worked example — illustrative data.
| State | Fictional message | Next action |
|---|---|---|
| One finish unavailable | Brass is unavailable; black remains available | Choose another finish or request a notice |
| All variants unavailable | No current purchasing option | View relevant alternatives |
| Notice requested | Request recorded if actually received | Explain how notices work under approved terms |
| No stock date confirmed | Restock date unknown | Avoid invented countdowns or promises |
Decide what the notification is tied to: a specific SKU, a finish or the whole product. Ask only for the information needed to send it and explain the intended use before submission. Keep marketing permission separate from the requested stock notice according to the approved data-handling approach. Include duplicate requests, failed submission and withdrawal in the design. Verify any automation in a sandbox with synthetic stock changes.
Tie each notice to the selection the shopper requested
In the fictional lamp flow, record whether the request concerns brass only or any finish. Rehearse a synthetic stock change for another finish and confirm it does not produce a misleading notice. Check repeated requests, an unavailable submission and withdrawal through the supported process. Keep notice receipt separate from inventory reservation.
A restock notice does not guarantee sufficient inventory
A restock can be too small to fulfil every interested buyer. Unless the business has a real reservation mechanism, the notice must not imply that an item is held or guaranteed.
Publish the flow when selection identity, receipt and notification scope are clear. Use an honest unavailable state if the team has not yet implemented the notice process.
Can I promise a restock date in the acknowledgement?
Use only an approved date supported by the inventory or supplier record, with any relevant uncertainty. If the date is unknown, say so. A notification request is not an order or a promise that stock will be available when the message arrives.
Continue with Guides for stores, software teams and local businesses, eCommerce website design and development and What to do with discontinued product pages.