Notify Me!: make a restock request a promise you can keep
Notify Me! is relevant when shoppers encounter unavailable products and the store needs a useful next step. A request for a particular size or color is specific customer intent. The operating challenge is to preserve that intent, alert the right people when usable stock exists and respond when supply or delivery plans change.
Separate the modules and promises
Notify Me!'s current documentation describes Back in Stock, PreOrder, Wishlist and Low Stock modules. They share a Shopify theme app embed but can be enabled independently. The product also advertises availability for BigCommerce; inspect the platform-specific version rather than assuming identical behavior. How Notify Me! works and official FAQ.
A back-in-stock request asks for a notification. A preorder creates an order and a fulfillment obligation. A wishlist records an interest, while a low-stock notice makes a claim about availability. Evaluate them separately; installing one application does not establish a reason to enable every sales feature.
Tie the request to the actual variant
| Case | Intended decision | Check before sending |
|---|---|---|
| One size returns | Notify people waiting for that size | Variant and destination page agree |
| Small quantity arrives | Define who can be alerted and when | Unreserved stock supports the planned batch |
| Stock receipt is reversed | Pause misleading availability messages | An owner can inspect scheduled work |
| Customer requests cancellation | Stop the relevant request or order path | Request cancellation and refund are distinct |
| Shopper changes contact preference | Use only the appropriate channel | Current channel eligibility is recorded |
For an illustrative restock of ten units and a waitlist of 80 people, sending 80 alerts is not a reservation policy. Decide whether the store uses a fair ordering window, phased messages or another clearly explained rule. Do not imply a customer has secured an item simply because an alert was sent.
Treat theme changes as a deployment
The app-embed instructions explain that the embed needs activation in the Shopify theme and must be activated again after switching themes. A module can be configured inside the app while its storefront widget is missing. Add a live-theme check to your launch checklist. App embed setup.
Use a test product to check desktop and mobile, each intended variant, an untranslated label and a product excluded from the offer. Keep evidence of which theme and settings were reviewed. Test after publishing a new theme rather than assuming that a previous successful setup still applies.
Keep channel permission and purpose visible
The documentation includes email, SMS, push and WhatsApp for back-in-stock messaging, with country-dependent costs for SMS and WhatsApp. A product availability request should not silently become a general newsletter subscription. Record the requested product, requested channel, collection wording and preference changes. For legal requirements in your market, review the applicable rules and qualified advice separately; this article describes the operating records to maintain, not a universal legal determination.
Choose a monitored reply route. If a shopper replies that the item has already sold out, support should be able to find the request and explain the next realistic option. The restock-to-notification playbook follows the request through stock review, message release and human response.
Evaluate the economics of usable notifications
Quote requests, notifications, preorder volume, wishlist usage and messaging charges as distinct units where relevant. Do not price the system using only the number of installed widgets. Include peak arrivals, destination countries, repeated requests and the labor required to resolve inaccurate stock or delayed preorders.
When to use an alternative
Compare Notify Me! with Klaviyo's back-in-stock workflow if you already operate a broader marketing platform. Katana or another inventory process may be the more important first improvement when your availability data is unreliable. Keep a manual request process for low volume if one person can maintain it accurately and the customer-facing promise is clear.
Give preorders their own acceptance record
A preorder is not merely a longer waitlist. Record what was paid or authorized, the promised fulfillment conditions, how changes are communicated and the person who can handle a cancellation or delay. Confirm the relevant platform, payment and app behavior before treating every advertised payment arrangement as available to the store.
For an illustrative product expected next month, keep the supplier or production estimate distinct from the customer-facing commitment. If the dependency changes, identify affected orders and the message that needs review. A changed inventory date should not leave customers relying on an obsolete promise.
Rehearse a customer who requests an edit before receipt, another who wants to stop waiting and an item that becomes available only in part. Inspect the actual order and payment states, not just the widget. Preserve each authorized decision and customer update.
If you only need an availability notice, keep preorder disabled until the business can maintain this additional obligation. The value of a multi-module application is the ability to select appropriate scope, not a reason to enable every module on installation.
Research basis: official information reviewed November 2, 2026, with original editorial analysis. Suggested trials are not hands-on findings. Original publication dates are retained; plan scope and eligibility require confirmation.