✨ 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 Back in Stock: subscriber lists as tables

Read back-in-stock subscribers from the plugin's custom table (commonly wp_wc_bis_subscribers) or post type, joined to the product post type. See demand per SKU, scrub stale entries, and trigger notifications in bulk.

♾️ Lifetime License available

SleekView table view for WooCommerce Back in Stock

Restock subscriber data, finally a real list

Back-in-stock plugins record an email address against a product variation, sometimes with stock thresholds and notification preferences. The data typically lives in a custom table like wp_wc_bis_subscribers (or the plugin's equivalent) or as a custom post type tied to product IDs by postmeta. The default admin tends to show subscriptions in a simple list per product, with limited filters and no easy way to surface demand across the catalogue.

SleekView reads the subscriber table directly and joins to the product post type (and product_variation where the plugin records variation IDs). A merchandiser's daily view becomes: products with the most active subscribers, sorted by signup count, with current stock level and last notification date visible inline. A support agent can search by email and see every product a customer is waiting on; an operations lead can scrub subscriptions older than 90 days that no longer make sense to retain.

Inline edits route through the plugin's CRUD APIs where exposed, so any hooks for notification triggers, customer email opt-outs, or GDPR cleanups still fire. Bulk-delete stale entries with confidence that subscriber records are removed correctly across all related tables, including notification log meta and any third-party CRM sync.

Workflow

How SleekView reads your back-in-stock data

1

Pick the subscriber source

Custom table (commonly wp_wc_bis_subscribers) or the plugin's custom post type, whichever the installed plugin writes to. SleekView detects both and exposes the right columns.
2

Compose subscriber columns

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

Save merchandising and support views

Name views like "Demand by SKU", "Stale subscribers 90d+", "Per-customer history" and gate by capability so merchandising, support, and marketing each get their own.
4

Notify, delete, export inline

Bulk-flip status to notified, delete stale entries with plugin hooks honoured, export filtered subscriber lists to CSV. Writes route through the plugin's CRUD layer so notification triggers fire.

Sample columns

A typical back-in-stock subscriber list view

Joins the plugin's subscriber table or post type with the product and product_variation post types for readable rows.
Source: wp_wc_bis_subscribers (or wp_posts post_type=bis_subscription) + wp_postmeta + wp_posts (product, product_variation)
Subscriber Product Variation Current stock Signed up Status
alex@studio.co Linen Apron Stone, M 0 Apr 12 Waiting
ria@design.io Walnut Stool Default 2 Apr 18 Notified
tom@hello.dev Brass Lamp Brushed 0 Apr 22 Waiting
mia@brew.coop Ceramic Mug Cream 0 Mar 02 Stale (60d+)

Comparison

Default WooCommerce Back in Stock admin vs SleekView

Default Back in Stock admin

  • Subscriber list is usually scoped per product, no global catalogue view
  • Variation-level subscribers don't always show variation names inline
  • Current stock level is not joined into the subscriber list
  • Stale subscriptions accumulate with no easy cleanup workflow
  • Per-customer cross-product subscription history is hard to inspect

SleekView

  • Cross-catalogue subscriber view sortable by product demand
  • Variation names joined from the product_variation post type
  • Current stock level surfaced inline next to subscriber count
  • Inline-delete stale entries with notification hooks honoured
  • Per-customer cross-product subscription history in one filtered view

Features

What SleekView gives you for WooCommerce Back in Stock

Demand-per-SKU table

Aggregate the subscriber table grouped by product and variation. Sort by signup count to surface the highest-demand out-of-stock SKUs for the next purchase order.

Notification trigger inline

When a SKU is back in stock, flip its subscribers from waiting to notified inline. Notification dispatch routes through the plugin's CRUD layer so customer emails, opt-out logic, and CRM sync all fire.

Stale-subscriber cleanup

Filter to subscriptions older than 90 days that have never been notified, bulk-delete with the plugin's hooks honoured. Keeps the subscriber table lean and GDPR-tidy.

Audience

Who uses SleekView for WooCommerce Back in Stock

Merchandising and purchasing

Demand-per-SKU view sorted by subscriber count. Combines waiting customers with current stock level to inform purchase orders, no spreadsheet exports.

Marketing

Per-customer subscription history view, useful for re-engagement campaigns and for understanding which categories drive restock interest. Filter by category to slice intent.

Support

During chat, search by email to see every product a customer is waiting on. Helps support recommend alternatives or update notification preferences mid-conversation.

The bigger picture

Why restock-demand visibility informs better buying

Back-in-stock subscriptions are a leading indicator of demand that most stores leave on the table. The data is collected diligently by the plugin, an email per shopper per out-of-stock product, but it stays trapped in the plugin's admin scoped per product. A merchandiser deciding what to reorder for the next purchase wave should be looking at "top 50 out-of-stock SKUs by subscriber count" first, then cross-referencing with margin and supplier lead time.

Without that view, the decision falls back on instinct or last quarter's sales report, neither of which captures unmet demand. A retention marketer should be looking at categories with high restock interest to know where to invest in pre-launch teasers. A support agent should be able to answer "what is this customer waiting on" in five seconds, not by clicking through three screens.

SleekView turns the subscriber table into the workspace each team needs without inventing new tracking. Same data, much more useful shape, dramatically better stocking decisions.

Questions

Common questions about SleekView for WooCommerce Back in Stock

SleekView reads from whichever surface the plugin writes to, custom table (commonly wp_wc_bis_subscribers or similar) or a custom post type. The column picker reflects the actual fields present in your data, so the same SleekView config adapts to the plugin's schema without manual mapping.

 

Yes. The join to the product and product_variation post types brings _stock postmeta in as a column. Useful for spotting subscribers waiting on items that have already restocked but were missed by automated triggers.

 

Yes. Status writes route through the plugin's CRUD layer where exposed, so notification emails, opt-out logic, and any third-party CRM or marketing-tool sync hooks fire as expected. SleekView does not bypass plugin logic on bulk operations.

 

Inline-delete from SleekView routes through the plugin's delete path, which typically also removes related notification log meta. A per-customer view shows all subscriptions for a given email so a single screen handles a data-erasure request end to end.

 

Yes. Filtered views export to CSV. Many merchants export per-category subscriber lists for retention campaigns in their email tool, then push results back as tags on the customer record.

 

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

 

Yes. The signup timestamp column is filterable by date range. Common saved views: "New subscribers last 7 days", "Stale subscribers, 90+ days waiting", "Subscribers waiting on items that restocked in the last 24 hours".

 

Yes. Queries hit indexed columns (subscriber id, product id, signup date) on the plugin's table. Aggregate columns (per-product subscriber count) are heavier; keep them off triage views and on summary dashboards to keep query plans efficient.

 

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