- Who this is for
- Store operators with recurring out-of-stock demand and a dependable inventory source.
- What you will leave with
- A request-to-availability map, controlled recipient cases and a stop-and-recovery checklist.
- Scope of this guide
- An editorial pilot with proposed acceptance cases. Use controlled records, record actual results, and check your current account before expanding.
On this page · 12 sections
01 / Choose one unavailable variant
Select a real product variant whose demand the team wants to understand. Record its identifiers, selling location and present availability rule. Start with a restock request rather than simultaneously enabling preorder, wishlist and urgency modules. The first test should answer one clear question: can a shopper request useful information about this particular item and receive an accurate next step?
02 / Write the public request promise
Draft the widget explanation, selected channel, expected alert and any separate optional marketing choice. Make clear what requesting an alert does and does not reserve. Keep the product and variant recognizable throughout the route. Review the promise with the person who handles stock questions so the store does not describe a guarantee that its operating process cannot honor.
03 / Inspect the published installation
Use the current platform and theme documentation to test the actual product page on a phone and with a keyboard. Include a long option label, missing contact information and a variant that remains available. Check that the request button appears in the intended state and that the customer can understand the difference between requesting information and placing an order.
04 / Prepare controlled request records
Create a fresh interested shopper, an existing request, a duplicate request and a shopper interested in two variants. Use controlled contact details. Record expected request and alert counts before testing. Preserve identifiers and timestamps so an operator can distinguish a repeat request from an unintended replay or a separate product interest.
05 / Define the authoritative stock event
Write which quantity and location make the variant eligible to be described as available. Distinguish expected supply, reserved stock and actual sellable units. Include a stock correction and a planned receipt that has not arrived. The alert should follow an accepted availability rule rather than any convenient number change in an upstream tool.
06 / Run one controlled availability change
Use the documented test approach for the account and observe the request, eligibility decision and planned message. Keep any real sending or stock change under the merchant's chosen test boundary. Record the actual event source and destination. A successful save in inventory settings is not yet evidence that the correct request became eligible for one appropriate notification.
07 / Inspect the complete alert
Review sender identity, product and variant wording, current availability statement, link and next action. Use the selected channel's actual presentation. Follow the destination on a phone and check that the shopper can recognize the requested item. Keep the alert's message aligned with the current product page rather than assuming every stored link remains correct after a catalog change.
08 / Test limited stock and renewed interest
Include a case where stock sells out again before the shopper acts and another where the same person wants a later alert. Inspect the documented behavior under the chosen settings. Keep a restock alert separate from a reservation or accepted purchase. The operator should know how to explain the result without overstating the number of units or the customer's priority.
09 / Prove changes and withdrawal
Use the supported way to stop or change a controlled request while an alert is outstanding. Check future eligibility and connected audiences. Include an ordinary contact update afterwards. The request history should preserve what the shopper actually chose, so a repair or import does not quietly turn one item-specific alert into continuing promotional contact.
10 / Assign discontinued items and failures
Retire a product or deliberately break a controlled destination. Record who handles waiting requests, failed deliveries and customer replies. Check whether the responsible person sees the variant and original promise. Keep a procedure for unavailable supply rather than leaving shoppers indefinitely attached to an item the team no longer expects to offer.
11 / Reconcile results and message costs
Count unique relevant requests, eligible alerts, observed deliveries, return visits where measured and accepted orders as separate outcomes. Verify current app allowances and channel-related charges. Add stock review and customer support time. Waitlist volume is useful evidence of interest, but it should not be treated as a committed purchase quantity or guaranteed revenue.
12 / Decide whether to retain the route
Compare the controlled normal, duplicate, stopped, sold-out-again and discontinued-item cases with the existing store process. Keep the owner, actual settings and recovery evidence in the worksheet. Retain the tool when the product promise remains accurate, request choices persist and the team can maintain the workflow without creating an unowned message queue.
A restock alert should preserve the requested variant, contact choice and current availability, while leaving the customer free to decide.
Official sources
Notify Me!: product overviewNotify Me!: modules and Shopify setupPostscript: SMS marketingPostscript: subscriber opt-out handlingSource material supports product descriptions; workflow criteria and pilot suggestions are our editorial analysis. Check the current documentation and your account settings before implementation.