Back in stock waitlists

See where back-in-stock signups send emails and product choices

A waitlist form can save a visitor email plus the exact product they wanted before any order exists. Some plugins keep that waitlist on your WordPress site and send the restock email from there. Others send the email and product interest to an outside notification service when that signup is configured. Abandoned-cart plugins capture a checkout email after a cart is started. Newsletter plugins cover subscriber forms. This table describes the setups below; your settings can change what is saved.

Based on plugin documentation, not tests of your site. Your settings can change what is saved. This is not legal advice or a compliance rating.

Scan your site for third-party requests

This scan checks requests made by a visitor’s browser. It cannot inspect saved waitlists or verify transfers made by your server or email provider.

How we group waitlist plugins

We compare where the named plugins store a waitlist email and the product a visitor asked to be told about. A plugin that saves that waitlist on your WordPress site is different from a plugin that sends it to an outside notification service when signup is configured. Abandoned-cart plugins capture a checkout email after a cart is started. Newsletter plugins cover subscriber forms. Consent timing and vendor data retention have not been tested.

Waitlist on your site vs waitlist sent outside when signup is configured

Waitlist stored on your site

Some plugins save the email and product in WordPress, then send restock emails from the site. The visitor browser talks to your site to save those fields. A restock email still means the address and product left the site by email. We list an outside host only when the plugin source names a visitor request to that host.

Waitlist sent outside when signup is configured

A waitlist can be sent to an outside notification service when back-in-stock signup is configured. Onsite script and product events do not prove a waitlist submission. Those hosts are not the added signup path. That send can happen in the visitor browser or from the server after the store saves the fields. We list an outside host only when the plugin source names a visitor request to that host. If the source uses a server API instead of a visitor host, the table says receiving domains are not verified.

Before consent

Consent timing is not tested here. The Before consent column is not a scan finding.

Back in stock plugins

No paid placement. Waitlist stored on your site first, then waitlist sent outside when signup is configured, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented outside hostsHow long data is keptBefore consentLinksSource
Back In Stock Notifier for WooCommerce

This row covers Back In Stock Notifier for WooCommerce on out-of-stock products. The visitor form posts the email and product to your site. The plugin saves each subscriber as a WordPress post and sends confirmation and restock emails through WooCommerce. Optional add-ons can sync that waitlist to an outside service. Consent timing is not tested here.

Waitlist stored on your siteNo outside notification-service host documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Notifima

This row covers Notifima on out-of-stock products. The visitor form sends the email and product to your site REST route. The plugin saves that waitlist in a WordPress table and sends confirmation and restock emails through WooCommerce. Consent timing is not tested here.

Waitlist stored on your siteNo outside notification-service host documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Waitlist Woocommerce

This row covers Waitlist Woocommerce on out-of-stock products. The visitor form posts the email and product to your site. The plugin saves that waitlist in a WordPress table and sends restock emails from the site. Consent timing is not tested here.

Waitlist stored on your siteNo outside notification-service host documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
YITH WooCommerce Waitlist

This row covers YITH WooCommerce Waitlist on out-of-stock products. The visitor form posts the email to your site. The plugin saves waitlist emails on the product in WordPress and sends restock emails from the site. Consent timing is not tested here.

Waitlist stored on your siteNo outside notification-service host documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Klaviyo with back-in-stock signup

This row covers Klaviyo with back-in-stock signup. The plugin loads klaviyo.js from static.klaviyo.com and records Viewed Product events at a.klaviyo.com. Those onsite script and product events do not prove a waitlist submission. Their hosts are not the added signup path. Email and product are sent to Klaviyo when signup is configured. Official custom setup is linked in this row. Abandoned-cart checkout capture is a different page. Consent timing is not tested here.

Email and product sent to Klaviyo when signup is configuredstatic.klaviyo.com, a.klaviyo.comNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named waitlist setups. It does not show what loads on your site. Where no outside notification-service host is documented, that applies only to the setup described. Other page requests are not covered. A server request that sends a waitlist to a notification service is not the same as a visitor browser request. Onsite script and product events do not prove a waitlist submission. A restock email from your site still means the address left by email. Abandoned-cart checkout capture and newsletter plugins are outside this table. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long vendor logs are kept. The site scan linked below checks requests made by a visitor’s browser. It cannot inspect saved waitlists or verify transfers made by your server or email provider.

Documentation snapshot: Oct 7, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-back-in-stock-privacy