Explore Notify Me! and check its current features and plans.
Visit Notify Me!- Who this is for
- Store operators investigating one recurring product-interest or opted-in customer-message workflow.
- What you will leave with
- A tested customer promise, eligibility rule and order or message handoff, with exceptions assigned to an operator.
- Scope of this guide
- Documentation-based product information and an editorial evaluation plan. Verify the current plan, account configuration, and connection before implementation.
On this page · 10 sections
A supported store with repeated out-of-stock interest and a reliable stock and customer-follow-up process.
A store with uncertain inventory or delivery promises, or a team treating a restock request as a general marketing subscription.
Choose one module and one customer need
Notify Me! describes back-in-stock, preorder, wishlist and low-stock modules, with Shopify setup documented in its help center. Start with the particular job causing repeat work. A request to hear when a variant returns is different from accepting a paid preorder. Record which module you intend to evaluate and why the existing product page or store process does not already meet that need.
Make the signup promise specific
Choose one product and variant, one supported contact channel and a clear explanation of the alert. Review the public widget, confirmation and destination as a single customer promise. A shopper asking about a sold-out size has not necessarily requested updates about the whole store. Keep any separate promotional choice visible and give the operator enough context to recognize the original request later.
Verify the current storefront installation
Use the current documentation for the store platform, theme and selected module. Test the published product page rather than only an app preview. Include a narrow screen, a long product name, a missing contact value and an unavailable variant. Check the actual placement of the request button and whether a shopper understands the difference between requesting an alert and placing an order.
Map variants and availability
Document the store's product and variant identifiers, relevant location and rule for sellable stock. Include two sizes or colors with different availability. Check which change should qualify as a restock, and distinguish a planned receipt from accepted stock. The notification route should point to the requested item and reflect availability that the fulfillment team can actually support.
Separate a waitlist from a preorder
For a preorder pilot, write the payment or deposit expectation, anticipated timing, change process and customer-support owner before enabling a purchasing route. Verify the account's exact behavior using current materials. Keep waitlist interest and accepted orders as different records. This distinction matters when stock is delayed, because a shopper waiting for an alert and a customer who has paid need different responses.
Try repeated and overlapping requests
Use a controlled shopper who requests the same variant twice and then requests a second variant. Record the intended contact count and notification behavior. Inspect the actual app and store records rather than inferring success from the widget closing. Decide how the team handles changed contact details, a renewed request after an earlier alert and an item that is permanently discontinued.
Check the alert-to-product route
Review the alert's product name, variant, link and explanation using controlled contacts. Follow the destination and inspect the item that can actually be added to the cart. Include a case where another shopper consumes the limited stock first. An alert should provide useful current information without being treated as a reservation or a guarantee of continued availability.
Own preference changes and message charges
Test the supported way to stop or change the selected alert. Check what happens to outstanding work and any connected marketing audience. The provider documents channel-dependent messaging costs, so confirm the channels and billing applicable to your store. A controlled restock test should make the resulting usage explainable rather than generate a surprise batch of messages during a stock correction.
Keep demand reporting interpretable
Separate raw requests, unique interested shoppers, eligible alerts, successful deliveries and accepted orders in the pilot record. A large waitlist can signal interest but does not establish a purchase commitment. Record which variant and time period a number describes. Use the information with inventory planning rather than assuming that every stored contact justifies the same replenishment quantity.
Decide from a bounded restock test
Use the linked checklist with one unavailable variant, a controlled stock update, repeated requests, a changed preference and a product that sells out again. Compare the route with the current store process. Keep an owner for disappointed or confused shoppers. Retain the tool when the request and availability remain aligned, the customer-facing message is accurate and the team can maintain the setup.
A useful restock workflow connects the requested variant and channel to real availability, with the original promise preserved.
Independent editorial guide based on official documentation. We may earn a commission if you sign up or purchase through an affiliate link. Read our affiliate disclosure.
Visit Notify Me!Official sources
Notify Me!: product overviewNotify Me!: modules and Shopify setupSource material supports product descriptions; workflow criteria and pilot suggestions are our editorial analysis. Check the current documentation and your account settings before implementation.