Bundle Add-ons - Back In Stock Notifier for WooCommerce documentation

Restock Reminders follows up with people who were told a product is back but have not bought it yet, while it is still in stock. You can send up to two reminders.

To set it up, open Instock Notifier > Settings > Restock Reminders:

1. Tick First reminder and set First reminder delay in hours after the alert. Twenty four hours suits most stores. Go shorter for fast-moving lines.
2. Write the subject and message. Use {cart_link} rather than the product link, because these people have already decided.
3. To send one final reminder, tick Second reminder. Its delay is measured from the original alert, not from the first reminder, so set it comfortably later.
4. If you want, set Stop below this stock level so reminders stop once only a few units remain. Zero means keep reminding while anything is in stock. This only applies to products with stock management enabled.

Placeholders: {product_name}, {cart_link}, {product_price}, {stock_left} and {subscriber_firstname}.

Each reminder is checked again just before it goes out. It is skipped, and not retried, in any of these cases:

• the subscriber bought
• the subscriber unsubscribed
• the product sold out again or fell to your stock floor

The Reminders column in the subscribers list shows who has received what.

Switch on Track Sales as well. Without it, there is no way to know that a subscriber already bought.

This add-on sends restock alerts by SMS, WhatsApp or both to subscribers who gave a phone number. Its settings are on the SMS and WhatsApp tab.

1. Turn on the phone field on the Visibility Settings tab. Otherwise nobody has a number to message.
2. Paste your Account SID and Auth Token from the Twilio console and save. Then use Send a test message to check them. The test uses the saved credentials and costs one message.
3. Pick your Channels: SMS only, WhatsApp only, or WhatsApp first, SMS if that fails.
4. For SMS, enter an SMS From number in international format. A Messaging Service SID is the better option: when you set one, it is used instead of the From number.
5. For WhatsApp, connect a WhatsApp sender in Twilio. Create a content template for restock alerts and wait for Meta to approve it. Then paste its WhatsApp Content SID. Variables 1 to 3 are filled with the product name, the price and the add to cart link. Enter the WhatsApp From number without the whatsapp: prefix.
6. If you want delivery results, paste the URL shown under Delivery receipts into your Twilio Messaging Service as the Delivery Status Callback. Results then appear in the subscribers list.

Keep the Restock message under 160 characters so it fits in one SMS segment. Signup confirmation texts people when they join a waitlist. It is off by default because it doubles your message spend. Country rules limits sending to the dialling codes you list.

Messages are queued, never sent inline. WhatsApp free text only works inside the twenty four hour service window. Outside it, Meta rejects the message and Twilio still charges for the failed attempt.

This add-on syncs waitlist subscribers into ActiveCampaign as contacts on a list you choose. Each contact is tagged with the product it is waiting for, so you can build automations on those tags.

1. In ActiveCampaign, open Settings and then Developer. Copy the account URL into Account URL, with no trailing slash and no /api/3 on the end. Copy the key into API key and click Save Changes.
2. Click Fetch lists, then pick the Target list.
3. Adjust Tags if you want. Placeholders such as {only_product_name} and {product_id} are filled in per subscriber.
4. Turn on Enable sync. Existing subscribers are backfilled in the background.

Tags that do not exist yet in ActiveCampaign are created automatically. With Mirror unsubscribes on, someone who leaves the waitlist is marked unsubscribed on that list. The contact is not deleted and your other lists are untouched. Catch-up sync retries failed rows every five minutes, up to 25 subscribers per run.

If you get a 403 error when fetching lists, the account URL is almost always the cause.

This add-on syncs waitlist subscribers into a Brevo list, with the product they want stored as contact attributes. It can also have Brevo send the restock alert from one of your transactional templates.

1. Create a v3 API key in Brevo under SMTP and API and then API keys. It starts with xkeysib. Paste it into API key and save.
2. Click Fetch lists and pick the Target list.
3. Turn on Enable sync.

To let Brevo send the alert itself:

1. Build a transactional template in Brevo and note its numeric ID.
2. Enter the ID in Restock template ID.
3. Turn on Send events.
4. Turn on Replace the built-in email. Without it, customers get two emails about the same restock.

In the Brevo template, use the parameters PRODUCT_NAME, PRODUCT_URL, CART_URL, PRODUCT_PRICE, PRODUCT_IMAGE and FIRSTNAME. In Brevo's syntax you reference them as {{ params.PRODUCT_NAME }}. The names must match exactly, in capitals.

This add-on syncs waitlist subscribers into a Constant Contact list. Constant Contact uses OAuth rather than a plain API key, so you register an app and then authorise your store once. After that, tokens are refreshed automatically.

1. Sign in at developer.constantcontact.com and create an app of the "Authorization Code Flow" type.
2. Copy the redirect URI shown in the Connection row into your app's Redirect URI list. It must match exactly, including https.
3. Paste the app's API key (Constant Contact calls it the client ID) and App secret, then save.
4. Click Connect to Constant Contact, approve access, and you are returned to your site.
5. Click Fetch lists, pick a Target list, and turn on Enable sync.

Constant Contact has no tags. The product a person is waiting for is recorded as a note on the contact instead. When someone leaves the waitlist, the contact is removed from the selected list, but the contact record is kept.

This add-on syncs waitlist subscribers into Klaviyo with the product they want as profile properties. It also fires two metric events, Back In Stock Subscribed and Back In Stock Available, which Klaviyo flows can trigger on.

1. In Klaviyo, create a private API key with full access under Settings and then API keys. Paste it into Private API key and save.
2. Click Fetch lists and choose the Target list.
3. Turn on Enable sync and Send events.
4. Click Create templates and flows in Klaviyo. This creates two email templates and two flows. Running it again updates what is already there rather than making duplicates. Open the flows in Klaviyo, check the sender name and address, and send yourself a test.
5. Once the flows work, turn on Let Klaviyo send the email. This stops the WooCommerce restock and subscription emails.

These event properties are available in your templates: event.product_title, event.product_url, event.cart_url, event.product_image and event.product_price.

A metric only exists in Klaviyo after it has been received once. If the setup reports that Klaviyo does not know the metric yet, do this:

1. Subscribe a test address with events on.
2. Run a restock.
3. Run the setup again.

This add-on adds everyone who joins a waitlist to a Mailchimp audience, tagged with the product they are waiting for. You can then build a segment such as "everyone waiting for this product" and mail those people directly.

1. Create an API key in Mailchimp under Account and then Extras and then API keys. Paste it into API key and save. The part after the dash is your data centre and is read automatically.
2. Click Fetch lists to load your audiences and pick the Target list.
3. Adjust Tags if you want. The default writes one general tag plus one tag per product.
4. Turn on Enable sync last. Existing subscribers are backfilled in the background over the next few minutes.

By default, contacts are subscribed straight away. Turn on Mailchimp confirmation if you want Mailchimp to email them a confirmation first. They receive nothing until they click it.

First and last names go into FNAME and LNAME, and PHONE is filled if your audience has that field. Contacts who unsubscribed from or were deleted in Mailchimp cannot be re-added by API. That is Mailchimp policy.

This add-on adds waitlist subscribers to a MailerLite group. The product they are waiting for is stored in custom fields, which you can use for segments and automation triggers.

1. In MailerLite, go to Integrations and then MailerLite API and generate a token with read and write access to subscribers and groups. Paste it into API token and save.
2. Click Fetch lists to load your groups, then choose one as the Target list.
3. Turn on Enable sync. The custom fields are created on your account automatically before the first sync.
4. In MailerLite, build an automation triggered by "joins a group" on that group.

The add-on creates these custom fields: bis_product, bis_product_id, bis_product_sku, bis_product_url and bis_tags. MailerLite holds one contact per email address, so the product fields reflect the most recent waitlist the person joined. bis_tags builds up the full set.

Leave Subscriber status off if you already confirm consent on your site, for example with Double Opt-In. Turning both on asks people to confirm twice.

This add-on syncs waitlist subscribers into Omnisend as tagged contacts. It also fires two custom events, back_in_stock_subscribed and back_in_stock_available, so an Omnisend automation can send the whole alert. Omnisend segments on tags and events rather than lists, so there is no list to choose.

1. Create an API key in Omnisend under Store settings and then Integrations and API and then API keys. Paste it into API key and save.
2. Turn on Enable sync.
3. If you want Omnisend to send the alert, turn on Send events. Then create an automation in Omnisend with a Custom event trigger and pick back_in_stock_available.
4. In the automation, use the event properties productName, productUrl, cartUrl, productImage and productPrice.

Email channel opts contacts into marketing email. Turn it off to add contacts without opting them in. SMS channel also subscribes the phone number to SMS. Only use it if your form makes clear that giving a number means agreeing to texts. A contact who already unsubscribed in Omnisend is never flipped back to subscribed.

If Omnisend sends the alert, turn off the built-in notification under WooCommerce > Settings > Emails so customers do not receive both.

Track Sales links orders back to the restock email that produced them. Every add to cart link in a back in stock email is signed with the subscriber it was sent to. When an order from that link reaches a paid status, the subscriber is marked Purchased and the order and revenue are recorded.

Settings are on the Sales Attribution tab.

1. Make sure your back in stock email uses the {cart_link} placeholder. That is the link this add-on signs. A plain {product_link} is still matched later by email address, but only the signed link gives same-session attribution.
2. Leave Reconcile by email on. It catches customers who got the email, browsed away and came back later without the link.
3. Set the Attribution window in days. It only applies to email matching. Signed links are always attributed.
4. Leave Revenue on to record the line total of the subscribed product against each converted subscriber.

Converted subscribers show a Purchased status, and the Order and Revenue columns are filled in the subscribers list. Orders from a signed link are attributed immediately. Orders matched by email are picked up by a background job that runs every fifteen minutes.

Waitlist Analytics and Restock Reminders both rely on this add-on for conversion and purchase data.

Waitlist Analytics turns the waitlist into reports. Open Instock Notifier > Analytics, choose a Period and click Apply.

At the top are summary cards:

• People waiting now
• Signups in period
• Notified in period
• Converted
• Attributed revenue

Below them:

• Signups and notifications over time: a chart of signups against restock alerts sent.
• Where everyone stands: every waitlist entry by status.
• Unmet demand: products with people waiting, ranked by count, with Waiting, Oldest signup, Stock and Potential value. Start here. It is the closest thing to a purchase order this data can give you.
• Notification performance: Notified, Purchased, Conversion and Revenue per product.

Use Export this table to CSV under a table to download it. The export contains product names and counts, not subscriber addresses.

Figures are cached for fifteen minutes. Click Refresh figures to recompute now. Conversion and revenue need the Track Sales add-on.

The Waitlist Analytics settings tab only controls the default period, the dashboard widget and how many rows each table shows.

Team Alerts posts waitlist signals to a chat channel your team already uses.

1. Create an incoming webhook for the channel:
   • Slack: create an Incoming Webhook.
   • Discord: use Channel settings and then Integrations and then Webhooks.
   • Microsoft Teams: add an Incoming Webhook connector.
2. Paste the URL into Webhook URL and choose the matching Destination: Slack, Discord, Microsoft Teams or Plain JSON webhook. Message formats differ, so this must match.
3. Save, then click Send a test message. The test uses the saved URL and destination.
4. Set the alerts you want. Start with Demand threshold.

The Demand threshold alert fires when a product passes that many waiting subscribers, and again at each multiple of it. Zero turns it off. Restock summaries are batched over a few minutes, so a popular restock produces one message instead of one per subscriber. Daily digest posts yesterday's signups, notifications and top demand. Mention on threshold alerts adds something like <!here> in Slack or @here in Discord.

Alerts carry product names, counts and potential values only. No email addresses or phone numbers are sent. The webhook URL is encrypted at rest and shown masked.

Waitlist Priority decides who hears first when stock is limited, and how many people hear at a time.

Under Notify in this order, choose one of these:

• First come, first served (the default, and the one to keep unless you run a VIP tier)
• Highest lifetime spend first
• Priority customer roles first, then signup order
• Registered customers first, then guests

For role ordering, list role slugs in Priority roles, highest first, for example vip_customer, wholesale.

Turn on Wave release if your restocks are often smaller than your waitlists. Then set these:

• People per unit of stock: how many subscribers to notify per available unit. Three is a sensible start.
• Gap between waves: minutes between waves. Under fifteen minutes there is little point having waves.
• Maximum waves
• Stop at this stock level: hold back a few units, for example for walk-in or wholesale.

Stock is re-read before every wave. Once the product sells out, the remaining waves are cancelled and those subscribers stay on the waitlist for the next restock. Wave sizing needs a stock number. For products without stock management, the add-on paces sending with a fixed wave size instead. Spend ordering computes a score per customer the first time, which takes a moment on a large waitlist.

With Double Opt-In on, joining a waitlist sends a confirmation email first. The entry stays at Awaiting confirmation until the link is clicked. Only then does it become active and count towards your subscriber numbers.

1. On the Double Opt-In tab, tick Require confirmation.
2. Make sure Confirmation message contains {doubleoptin_verify_link}, usually inside a link or button. Without it, nobody can confirm.
3. Edit the on-screen messages for after signing up, a pending confirmation, after confirming, and an expired link.
4. Set Delete unconfirmed entries after in days. Older unconfirmed entries are deleted automatically.

Placeholders: {doubleoptin_verify_link}, {product_name}, {subscriber_name} and {shopname}.

Unconfirmed entries appear under the Awaiting confirmation filter in the subscribers list. You can resend the email there, row by row. With Consent evidence on, the add-on stores the confirmation time, the originating page and a salted hash of the IP address. The raw IP is never kept.

Confirmation only applies to new signups. People already on a waitlist stay active.

The Unsubscribe add-on gives people three ways to leave a waitlist:

• a signed one-click link in your emails
• the mailbox Unsubscribe button in Gmail and Yahoo
• a Subscribed List tab in My Account

1. On the Unsubscribe tab, choose your Unsubscribe page. A page is created for you the first time the add-on is switched on. It must contain the [cwginstocknotifier_unsubscribe] shortcode. The tab shows Ready with a View page link when the page is set up.
2. Add {cwginstock_unsubscribe} to your subscription and back in stock email templates, usually in an "unsubscribe" link at the foot of the message. Use {cwginstock_unsubscribe_all} for a link that removes the person from every waitlist.
3. Leave Mailbox unsubscribe button on. It sends the List-Unsubscribe and List-Unsubscribe-Post headers. Turning it off makes it more likely your notifications land in spam.
4. If you change My Account endpoint, save your permalinks once afterwards so the new URL works.

You can also edit these:

• the confirmation, already-unsubscribed and invalid-link messages
• the My Account tab label and heading, and the link text
• whether the Subscribed List shows thumbnails, hides SKUs, or shows how many people are waiting for each product

With Edit Subscribers on, every row in Instock Notifier > All Subscribers gains an Edit link, and Add New Subscriber appears in the menu. Use it to fix a mistyped address, move someone to a different variation, or add a customer who asked to be notified by phone.

1. Go to Instock Notifier > All Subscribers, hover over a row and click Edit.
2. You can change the email, name, phone, product, quantity or status. The product field searches your catalogue, including variations, so you do not need to know the ID.
3. Setting someone back to Subscribed makes them eligible for the next restock notification.

Edits are silent. No email is sent because of an edit. Only users who can manage WooCommerce can edit subscribers.

On the Editing Subscribers tab, Change history records which fields changed, when and by whom. The latest entries show under the edit form. Leave Duplicates off, because the same address on the same product twice means duplicate notification emails.

The subscribers list also shows columns added by other add-ons, such as Reminders, Confirmed, the sync status for each marketing platform, Order and Revenue.

Never Restock is for products that are gone for good. You map a discontinued product to one or more replacements. When a replacement comes into stock, everyone on the discontinued product's waitlist is emailed about it instead.

1. On the Never Restock tab, tick Enable and save. A Never Restock item appears in the Instock Notifier menu.
2. There, add a rule: pick the discontinued product, then one or more replacements.
3. Write the Email subject and Email message. Be honest that the original is discontinued.
4. Lower Emails per batch if your mail provider rate limits you.

Placeholders:

• {replacement_product}, {replacement_product_link}, {replacement_product_add_to_cart} and {replacement_product_price}
• {product_name} (the original product)
• {subscriber_name} and {shopname}

Rule priority decides what happens when one replacement is named in several rules. Apply every matching rule can mean several emails to the same person.

Stock is checked again before each batch is sent. Each subscriber is told once per replacement and is then marked Notified.

Export CSV downloads your subscriber list as a CSV file.

1. Go to Instock Notifier > All Subscribers.
2. Click Export CSV above the list.
3. Tick the columns you want and, if you like, narrow the export by status, product or date. The file downloads straight away.

The file is UTF-8 with a byte order mark, so Excel shows accented names correctly. Any value starting with =, +, - or @ gets an apostrophe in front so spreadsheets treat it as text. Rows are fetched in batches, so large waitlists do not run out of memory.

On the CSV Export tab you can change two things:

• Category columns: how many category columns the file gets, so every row lines up.
• Delimiter: Comma, Semicolon or Tab. Semicolon suits regional Excel builds where comma is the decimal separator.

Only users who can manage WooCommerce can export. The file can contain personal data, so treat it with care.

Import CSV brings waitlist subscribers in from another platform or a backup. Open Instock Notifier > Import CSV.

1. Prepare a CSV file with a header row. You need an Email column plus either Product ID or Product SKU. Everything else is optional. The screen has a Download a sample file link.
2. Choose the file and click Upload and read columns. The maximum size is 20 MB, so split larger lists into several files.
3. Map each column to a field. Match products by ID if you have it, or by SKU when the data came from another store.
4. Review the preview of the first few rows, then start the import. It runs in chunks with a progress bar, and you can close it and resume.

Rows whose email and product are already on the waitlist are skipped and counted as duplicates. Your Ban Emails block list applies to imports too. Use dates in the format YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. The uploaded file is deleted when the import finishes.

On the CSV Import tab:

• Status for rows with no status column sets the status for rows that have none.
• Run integrations on import is off by default, so imported rows are not pushed to your marketing platform and do not trigger confirmations.
• Leave Unknown products on to skip rows whose product does not exist in your store.

Custom CSS restyles the front-end subscribe form, button and popup without editing theme files. Its settings are on the Subscribe Form Styling tab.

1. Pick the layout first. Use Subscribe Form Design on the Frontend Form tab (and the popup design if you use the pop-up form). This tab then recolours whichever design you chose.
2. Set the sizes and colours you want and save. Leave a field empty to keep your theme's styling.
3. View an out of stock product to check the result. If you use a page cache, purge it once after saving.
4. For anything the fields do not cover, use the Custom CSS box at the bottom. It is output after every other rule, so it always wins. Tags and scripts are stripped on save.

The tab covers these areas:

• form width on desktop and mobile (mobile applies below 768px)
• heading, button, form panel and input styling
• popup backdrop, background, corner radius and maximum width
• popup button, success and error message colours
• the guest notice

Colour fields use Select Color pickers. The mobile width is written as a media query, so it works behind page caching.

Demand Signals shows how many people are already waiting for an out of stock product. It can also tell a new subscriber their place in the queue.

1. On the Demand Signals tab, set Minimum before showing. Below this number, nothing is shown. The add-on's own guidance suggests ten as a reasonable floor.
2. Choose Where to show it:
   • Above the subscribe form, outside the box
   • Inside the form, above the fields
   • Below the subscribe button
   • Inside the form heading bar
   • Only where I place the shortcode
3. Edit the Message. Use {count} for the number.
4. If you want, tick Queue position and edit the Queue position message, using {position}. It is shown straight after someone subscribes.
5. If you want, tick Shop and category pages to show a short badge on product listings, and choose the Appearance.

The Showing right now panel tells you how many products or variations are at or above your minimum. Variations are counted separately from their parent product.

To place the count anywhere else, use the [bis_demand_count] shortcode. Only real counts are shown, and there is no setting to inflate them. When you switch the add-on on, counts are rebuilt from the existing waitlist.

The Polylang add-on records the language each person subscribed in. It treats every translation of a product as one waitlist and sends each notification in the subscriber's own language.

1. Go to Languages > String translations and filter by the group "Back In Stock Notifier". Translate the email subject, heading and body for each language you sell in.
2. Check the translation status table in the add-on's settings. A cross means that language will get the original text.
3. Leave "Treat translations as one waitlist" on, unless each translation of a product really has its own stock.
4. Test by subscribing on a translated product page and then restocking.

You edit the original email text under WooCommerce > Settings > Emails, on the Back In Stock emails. Editing it registers a new string, so check the status table again afterwards. If the strings are not listed yet, open WooCommerce > Settings > Emails once and look again.

A fallback language code covers subscribers with no recorded language, such as imported rows. Leave it empty to use the site default. Do not run this add-on together with the WPML add-on.

The TranslatePress add-on records the language a person was browsing in when they subscribed. It then sends their restock notification in that language.

TranslatePress translates rendered pages, and an email is never rendered as a page. So you write the email text in the add-on's settings instead of the TranslatePress editor.

1. Write the email subject, heading and body for each language in the add-on's fields. There is one set per language configured in TranslatePress.
2. Check the translation status table. A cross means that language will receive the original text, never a blank email.
3. Test by switching the shop to another language, subscribing on an out of stock product, and restocking it.

TranslatePress does not duplicate products, so each product already has one waitlist and no shared waitlist setting is needed. Set a fallback language code for subscribers with no recorded language, for example rows imported from elsewhere.

The Weglot add-on records the language a person was browsing in when they subscribed. It then sends their restock notification in that language.

Weglot translates pages as they are served, and emails never pass through it. Without this add-on, every notification goes out in your original language.

1. Write the email subject, heading and body for each language in the add-on's fields. There is one set per destination language configured in Weglot.
2. Install the WordPress language pack for each language under Settings > General, so the surrounding email template is translated too.
3. Check the translation status table. A cross means that language will receive the original text.
4. Test by switching the shop to another language, subscribing on an out of stock product, and restocking it.

The email text is stored on your site and never sent to Weglot, so it does not use your Weglot word quota. Each product has one waitlist, so no shared waitlist setting is needed. Set a fallback language code for subscribers with no recorded language.

The WPML add-on records the language each person subscribed in. It treats every translation of a product as one waitlist and sends each notification in the subscriber's own language.

1. Go to WPML > String Translation and filter by the domain "Back In Stock Notifier". Translate the email subject, heading and body for each language you sell in.
2. Check the translation status table in the add-on's settings. A cross means that language will receive the original text.
3. Leave "Treat translations as one waitlist" on, unless each translation of a product really has its own stock. Without it, a restock on the original product does not reach people who signed up on a translation.
4. Test by subscribing on a translated product page and then restocking. The email should arrive translated, with a link to the translated product.

The original email text is under WooCommerce > Settings > Emails, on the Back In Stock emails. Editing it creates a new string, so check the status table again afterwards. Set a fallback language code for subscribers with no recorded language. Do not run this add-on together with the Polylang add-on.

Ban Emails keeps junk addresses off your waitlist. Every rule runs before a subscription is stored, so a blocked address never appears in your subscriber list. The settings are on the Blocked Emails tab.

1. Leave Disposable providers on. It uses a list of throwaway mail domains that ships with the add-on and updates with it. Click Show the full list to see it.
2. If you want, tick Role accounts to block shared mailboxes such as info@, admin@ and sales@.
3. If you want, tick Deliverability check to reject domains with no mail server. This catches typos such as gmial.com.
4. Add your own Blocked domains and Blocked addresses, one per line or comma separated. Wildcards work for domains, for example *.example.com.
5. Put genuine customers in Always allow. It is checked first and overrides every other rule.
6. Set the Message shown when blocked. Keep it vague.

With Logging on, blocked attempts are written to the plugin log with the address partly masked. That helps when a customer says they cannot subscribe. Rules apply at signup and to CSV imports. Existing subscribers are left alone.