A restock request records that a customer asked to be notified when a product or variant becomes available. Review the item, contact, request type, status, and date in Restock Requests.
Understand the status
Pending requests are waiting. Queued notifications are waiting to be sent. Notified means the sending provider accepted the message; it does not mean the customer read it. Failed means sending could not be completed. Suppressed means a setting or eligibility rule prevented sending. Expired, Converted, and Cancelled are separate outcomes.
Capture and expiry settings
Disabling Notify Me stops new requests without deleting existing demand. The expiry setting applies when a request is created or renewed. Expired requests are no longer eligible for a notification. In Restock Settings, edit capture, automatic sending and expiry controls, then choose Save. Only edited settings are saved. Discard restores saved values, and leaving with a changed draft asks for confirmation. Staff need permission to manage inventory to save these settings.
Automatic and manual notifications
Automatic notifications wait until the requested item is available to buy. Notify subscribers follows the same availability rules. A variant request waits for that variant; a whole-product request can be fulfilled when any variant returns. Only stock at active locations that fulfill online orders counts.
Staff need permission to view customer details to see the contact. Check the restock template, sender, and sending allowance before notifying customers. Repeating a queued request does not send another message. Review Failed or Suppressed requests and fix their cause before asking the customer to subscribe again.