How the alert reaches the shopper

An alert is not sent down one pipe. Every destination you have set up gets it, and it counts as delivered as soon as one of them takes it. That matters more than it sounds: a signed-in shopper is reachable one way and a guest another, so insisting that every route succeed would fail half your waiting list every time.

The routes

• Customer tag - a signed-in shopper's customer record is tagged, so a Shopify Flow, Shopify Email or Klaviyo automation can trigger on it. Guests have no customer record, so this one cannot serve them.
• Webhook - the full event is POSTed to your endpoint, guests included. This is how you send the email from your own tool, with your own template.
• Email from us - we write to the shopper directly. On by default.

The email we send

It goes out under your store's name, with your address as the reply-to, so the shopper sees a sender they recognise and a reply reaches you rather than us. It carries the product, the exact size, the image and a link straight to that variant. It says plainly that they joined the waiting list for that item and that this is the only email that will be sent about it.

Turn it off if one of your own automations already covers restocks - otherwise a shopper could hear about the same item twice. Leave it on if you are not sure: most people who ask to be notified are not signed in, so without a webhook or this, they would never hear that the item came back.

Your monthly email allowance

Each plan includes a number of emails we will send on your behalf per billing cycle - 500 on Free, 1,000 on Basic, 2,000 on Starter and 10,000 on Pro. It resets with your billing cycle, and the figure is shown on your plan card and on the Connections page next to the toggle.

This is a safety limit, not something to budget around. These alerts are requested one at a time, by real people, about one item each - a store that reaches the cap has usually hit a problem rather than outgrown the plan. Your own destinations are not counted at all and have no limit: a webhook firing into your own sender is free, however many times it fires.

Addresses we stop writing to

If an address hard-bounces - the mailbox does not exist - or someone marks a message as spam, we stop sending to that address. This is not optional bookkeeping: continuing to mail a dead address is how a sender's reputation collapses, and that reputation is shared with every other store using the app. A temporary problem, like a full mailbox, is not treated as dead.

Consent

A back-in-stock alert is transactional. The shopper asked for it, about one item, and it is sent whether or not they tick anything else. Marketing is a separate, unticked question on the same form - off unless you switch it on - and only a ticked box adds them to your marketing tools.