Skip to content
Restoc

Alert channels

One alert, four channels

Every alert starts as an email — the channel every shop sends — and the optional channels stand beside it, never instead of it. Each optional channel stands below with the exact message it sends, rendered from the real template on example data, and with the conditions it sends under, stated the way the app states them to the shop itself.

Email

The alert itself — the channel every shop sends.

The moment a product is back, the app emails everyone who asked, automatically, in controlled waves, so a long list never lands on the store all at once.

It goes out from the shop's own sending domain once the shop connects it: the app checks the DKIM and DMARC records before the first send, and until then the alerts go out from the app's sending address with the shop's name on them.

It speaks the shop's language: the sign-up block and the alert emails follow it automatically, across 24 languages.

The shopper's consent is the signup itself — the address they leave on the sold-out product. Nothing else is asked of them.

The email is the shop's own message: its subject, its opening words and its button can be reworded in Settings, so what stands here is the alert in its frame, not a fixed text.

The back-in-stock alert email in a mail client
The alert email, sent automatically when stock returns.

SMS

A text message beside the email, for the shoppers who ask for one.

With the channel on and its conditions standing, the sign-up form gains a phone field with its own consent box, separate from the email subscription: a shopper who ticks it and leaves a number is texted when their item comes back, in addition to the email.

Every text carries the words to stop it — reply STOP — and stopping the texts stops nothing else.

Texts are sent per piece, under the channel's own daily cap; when the cap is reached, the day's remaining alerts go out by email only — nothing is queued or retried.

  • Off until the shop turns it on in Settings: while it is off, no texts are sent.
  • Part of the paid plan: while the shop is not on it, the switch is recorded and no texts are sent.
  • The provider is the app's — nothing to connect on the shop's side: until it is connected, no texts are sent either.

Preview — the message your shoppers receive, rendered from the real template with example data (the shop, the product and the link are fictitious):

Example product is back in stock at Example Shop: https://example.com/products/example-product Reply STOP to stop these texts.

WhatsApp

The same alert as a WhatsApp message, on a consent of its own.

The phone field gains a second consent box, for WhatsApp alone: one number serves both phone channels, and a shopper can take texts, WhatsApp messages, both, or neither — each channel's consent is the shopper's own fact.

WhatsApp does not let a business open a conversation with free text: every alert goes out as one message template, approved in advance, filled with the shop's name, the product and its link. Approving that template is part of connecting the app's WhatsApp account — there is nothing to write on the shop's side.

Every message ends with the words to stop it — reply STOP — which stops this channel's messages only.

Messages are sent per piece, under the channel's own daily cap; when the cap is reached, the day's remaining alerts go out by email only — nothing is queued or retried.

  • Off until the shop turns it on in Settings: while it is off, no messages are sent.
  • Part of the paid plan: while the shop is not on it, the switch is recorded and no messages are sent.
  • The provider is the app's — nothing to connect on the shop's side: until it is connected, no messages are sent either.

Preview — the message your shoppers receive, rendered from the real template with example data (the shop, the product and the link are fictitious):

Example product is back in stock at Example Shop: https://example.com/products/example-product Reply STOP to stop these WhatsApp messages.

Web push

The same alert as a notification in the shopper's own browser.

The form gains its own web-push consent box, separate from the email subscription and from both phone consents; the shopper's browser itself then asks for notification permission, and only a browser that grants it and hands back a subscription is ever notified.

Support varies by browser and device: a browser that refuses, or cannot do this, simply collects no push consent — the email signup is untouched.

Notifications are counted per piece, under the channel's own daily cap; when the cap is reached, the day's remaining alerts go out by email only — nothing is queued or retried.

  • Off until the shop turns it on in Settings: while it is off, no notifications are sent.
  • Part of the paid plan: while the shop is not on it, the switch is recorded and no notifications are sent.
  • The provider is the app's — nothing to connect on the shop's side: until it is connected, no notifications are sent either.

Preview — the notification your shoppers receive, rendered from the real template with example data (the shop, the product and the link are fictitious):

Back in stock: Example product Good news — Example product is back in stock at Example Shop.

Be ready for the next restock.

Install the app, add the block, and the next sold-out product starts building its list today.

Get the app on ShopifyBack to the home page