✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WooCommerce Stock Notifier: notification queues as tables

Read stock-notifier subscribers from the plugin's table (or wp_postmeta against the product), joined to product, product_variation, and current stock. Trigger restock emails in bulk, audit deliveries, and clean up stale subscriptions.

♾️ Lifetime License available

SleekView table view for WooCommerce Stock Notifier

Stock notifier subscribers in one place

WooCommerce Stock Notifier plugins record an email-and-product pair so the system can fire a notification when stock returns. The data typically lives in a custom table (often wp_wc_stock_notifier_subscribers or similar) or as postmeta against the product. The default plugin admin shows a per-product subscriber list with status (subscribed, notified, unsubscribed) but rarely offers cross-product views, queue prioritisation, or aggregated demand metrics.

SleekView reads the subscriber surface directly and joins to product, product_variation, and the live stock field (_stock in wp_postmeta). A merchandiser's view sorts products by subscriber count to spot the highest-demand out-of-stock SKUs; an operations lead's restock view filters to SKUs that are back in stock with active subscribers waiting to be notified; a support agent's view searches by email to see every product a customer is waiting on.

Inline writes route through the plugin's CRUD layer where exposed, so notification dispatch, opt-out logic, and any sync to a third-party CRM or transactional email tool fire as expected. Bulk-status changes ("notify all subscribers for SKU 1234") iterate through the same path so side effects match per-customer manual triggers exactly.

Workflow

How SleekView reads your stock-notifier data

1

Pick the subscriber source

Custom table or postmeta, whichever the plugin writes to. SleekView detects both and exposes matching columns plus joinable product and variation data.
2

Compose demand columns

Add subscriber email, product (joined from product), variation attributes (joined from product_variation), current stock from _stock, signup date, and notification status.
3

Save operations views

Name views like "Restock-day queue", "Top-demand out-of-stock SKUs", "Stale subscriptions" and gate by capability so merchandising, fulfilment, and support each get their own.
4

Notify, clean, export inline

Bulk-flip status, delete stale entries with plugin hooks honoured, export filtered lists. All writes route through the plugin's CRUD layer so dispatch and CRM hooks fire.

Sample columns

A typical Stock Notifier queue view

Joins the plugin's subscriber table or postmeta with product, product_variation, and the _stock postmeta key for live stock visibility.
Source: wp_wc_stock_notifier_subscribers (or wp_postmeta) + wp_posts (product, product_variation)
Subscriber Product Variation Current stock Signed up Status
alex@studio.co Linen Apron Stone, M 0 Apr 14 Subscribed
ria@design.io Walnut Stool Default 3 Apr 16 Notified
tom@hello.dev Brass Lamp Brushed 0 Apr 19 Subscribed
mia@brew.coop Ceramic Mug Cream 0 Feb 14 Stale

Comparison

Default WooCommerce Stock Notifier admin vs SleekView

Default Stock Notifier admin

  • Per-product subscriber lists with no cross-catalogue demand view
  • Current stock is shown on the product screen, not next to subscribers
  • Notification status (subscribed / notified / unsubscribed) is rarely filterable
  • Variation-level subscriptions don't always surface variation names
  • Stale subscriptions accumulate and there is no cleanup workflow

SleekView

  • Cross-catalogue demand view sorted by subscriber count
  • Current stock joined from _stock next to each subscriber row
  • Variation attributes joined from product_variation
  • Bulk-notify with plugin hooks (email dispatch, opt-out) honoured
  • Stale-subscriber cleanup with safe deletion through the plugin's CRUD

Features

What SleekView gives you for WooCommerce Stock Notifier

Per-SKU demand ranking

Aggregate subscribers grouped by product (or variation), sort by count, surface the top out-of-stock SKUs. Pair with margin from wp_postmeta to inform purchase orders.

Bulk restock notifications

When a SKU restocks, filter subscribers for that product, bulk-flip to notified. Dispatch routes through the plugin's CRUD so emails, opt-outs, and CRM sync all fire.

Stale-subscription cleanup

Filter subscriptions older than 90 days with no notification activity, bulk-delete with the plugin's hooks honoured. Keeps the table compact and GDPR-tidy.

Audience

Who uses SleekView for WooCommerce Stock Notifier

Merchandising

Cross-catalogue demand view sorted by subscriber count. Surfaces high-demand out-of-stock SKUs that need to be reordered, with stock and category visible inline.

Fulfilment / ops

Restock-day workflow: filter to SKUs that just came back in stock, bulk-notify subscribers in signup order, watch status flip to notified across the queue.

Support

Per-customer subscription history. Search by email, see every SKU a customer is waiting on, opt them out or move them inline. Resolves "why am I getting these emails" tickets in one screen.

The bigger picture

Why stock-notifier visibility shortens the restock loop

Restock notifications are one of the highest-converting transactional emails an ecommerce store sends. The customer asked to be told, the SKU is now available, the click-through-to-purchase rate is unusually strong. The problem is that the data behind those notifications usually lives in a per-product list that no merchandiser ever opens.

Restock decisions get made on last quarter's sales report rather than on "how many people are waiting for this SKU right now". Notification campaigns get triggered manually per product, missing SKUs that quietly came back in stock through a bulk inventory import. Stale subscribers from six months ago accumulate in the table, slowing queries and inflating bounce rates.

SleekView turns the subscriber table into a real operations workspace: ranked demand by SKU for merchandising, a restock-day queue with current stock visible for fulfilment, per-customer history for support, scheduled cleanup for stale entries. Same plugin, same notifications, materially more leverage from data the store was already collecting.

Questions

Common questions about SleekView for WooCommerce Stock Notifier

Most stock-notifier plugins use a custom table (often wp_wc_stock_notifier_subscribers or similar) keyed on product id and email. Some store subscriptions as postmeta against the product. SleekView detects both, with the column picker reflecting whichever schema is in use.

 

Yes. Writes route through the plugin's CRUD layer where exposed, so notification emails, opt-out logic, and any sync to a third-party CRM or transactional email tool fire as expected. SleekView does not bypass plugin logic on bulk actions.

 

Yes. The join to product brings in _stock from wp_postmeta (or the product's HPOS-equivalent if the plugin uses one). Subscribers waiting on SKUs that have actually restocked stand out, useful for catching automation gaps.

 

Yes. Where the plugin stores variation IDs, the join to product_variation surfaces attributes (size, colour, finish) inline. Aggregate views by variation are essential for stores with deep variant trees.

 

Opt-out status is tracked by the plugin and surfaces as a column. The default views filter to active subscribers; the audit view shows opted-out subscribers so support can confirm a customer's preference history if they ask.

 

If the plugin records dispatch results (last-notified timestamp, delivery status, bounce flag), those keys surface in the column picker. Useful for catching bounced addresses and removing them from future notifications.

 

Yes. The join to product taxonomies (product_cat) makes per-category filters straightforward. Export filtered lists to CSV for retention campaigns or feed into an email tool's category-tagging logic.

 

Indexed columns on the subscriber table (id, product id, email, signup timestamp) get hit directly. Aggregate columns (per-product subscriber count) are heavier and should be reserved for summary views; triage views work directly off the indexed columns to keep query plans fast.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView