Restock request to an accurate alert and an owned reply
Use this playbook when shoppers ask to hear about unavailable products. The goal is a specific request preserved through stock review, an appropriate alert and a response when the customer needs help. You can run it with a small manual queue before purchasing a dedicated application.
Establish the promise and roles
The storefront owner defines the request wording and the exact product or variant. Operations confirms usable availability. A messaging owner releases the alert under the relevant preferences and channel requirements. A service owner accepts replies and exceptions. One person may hold several roles, but each decision must still be explicit.
For an illustrative size-and-color request, record the exact variant and channel. Do not turn it into a broad newsletter subscription without the appropriate separate collection process. Tell the shopper whether the alert is an availability notice or a reservation; those are different promises.
Keep a request and release record
| Field | What to record |
|---|---|
| Request reference | Stable identifier, collection source and received time |
| Product identity | Internal SKU, storefront variant and destination page |
| Requested communication | Purpose, channel and current preference evidence |
| Stock review | Usable unreserved quantity, source and verification time |
| Release decision | Authorized batch, wording, reviewer and send reference |
| Customer outcome | Purchase, remaining request, changed preference or reply |
| Owner and next update | Accepting person, backup and next review time |
Keep sensitive customer data in the approved system rather than copying it into a public planning document. The record is a coordination reference, not a reason to collect unnecessary information.
Review stock before releasing messages
For an illustrative ten-unit restock and a waitlist of 80 people, choose a transparent release rule. An alert to all 80 is not a reservation. Account for damaged units, already committed stock and variant mapping before authorizing the message.
Inspect timing constraints. Klaviyo's SMS restock guidance notes subscription prerequisites and quiet-hours delays. Notify Me!'s documentation explains request-based modules and the Shopify app embed. Those are configuration inputs to verify, not proof that stock remains available whenever a person reads the alert. Klaviyo guidance and Notify Me! scope.
Handle exceptions without competing alerts
If stock is corrected before release, pause the affected batch and record the reason. If it sells out after release, give replies an owner who can explain the next realistic option. If a shopper changes channel preferences, reconcile the applicable pending communication before another import or retry.
Define which application owns each alert. If both a marketing platform and a specialized widget are connected, test for duplicate notifications. A failed or repeated stock event should enter a review queue rather than automatically generate another customer promise.
Run the acceptance rehearsal
Use staff-controlled requests for two variants, leaving one unavailable. Replenish a small quantity, reverse one unit and test a changed preference. Check mobile request submission, the destination link and the actual reply route.
After a Shopify theme change, verify the published widget again; Notify Me!'s embed guide describes per-theme activation. Ask another person to reconstruct the request and release decision from the record.
Review outcomes and select tools
Count unmatched variants, alerts sent after stock ceased to be usable, repeated messages and unowned replies. Review the causes before optimizing message volume. Compare Notify Me! and Klaviyo only after the workflow is defined. If availability data is the main failure, begin with inventory ownership rather than buying another notification channel.
Research basis: official information reviewed November 2, 2026, with original editorial analysis. Trial scenarios are proposed checks, not hands-on results. Confirm current plans and availability before purchase.