SleekView Kanban for Stock Manager for WooCommerce
Stock Manager for WooCommerce reads and writes the same wp_postmeta WooCommerce uses for _stock_status, _stock, _regular_price, and _sale_price. SleekView Kanban groups those rows by _stock_status so merchandising drags simple products and variations between In Stock, Out of Stock, and Backorder.
♾️ Lifetime License available
Drag products between stock states instead of editing a row at a time
Stock Manager for WooCommerce is a focused inventory editor that reads and writes the WooCommerce postmeta WooCommerce itself uses: _stock_status, _stock, _regular_price, _sale_price, _sku. The plugin's dashboard renders a paginated table where each row carries one product or variation and a few inline editors. That works well for cell edits, but for the question merchandising asks first thing in the morning, how does the catalog split by stock status, the table is a thousand-row scroll exercise.
SleekView Kanban reads the same postmeta rows and groups them by _stock_status. WooCommerce canonicalizes stock status to three values, instock, outofstock, onbackorder, and the board renders one column per value. Each card shows the SKU joined from _sku, the product title joined from wp_posts, the stock quantity from _stock, and the active price (sale if set, otherwise regular). A fourth column for Low Stock surfaces SKUs whose _stock is at or below the WooCommerce notification threshold.
Drag a card from Out of Stock to In Stock and SleekView updates the _stock_status postmeta row directly. WooCommerce's storefront cache, the cart's add-to-cart eligibility check, the catalog-visibility filter for out-of-stock products, and the low-stock email trigger all keep working because SleekView only reads and writes the same postmeta the Stock Manager and WooCommerce core both already use.
Workflow
From a paginated table to a drag-and-drop board
Point SleekView at WooCommerce postmeta
Pick _stock_status as the status column
Choose what shows on each card
Enable drag-and-drop with WooCommerce sync
Sample board
Sample stock-status board for a WooCommerce catalog
Comparison
Default Stock Manager dashboard vs SleekView Kanban
Default Stock Manager dashboard
- Stock Manager renders inventory as a paginated row table with inline cell editors only
- No column split by _stock_status to see In Stock, Out of Stock, Backorder counts together
- Low-stock SKUs only surface through the standard WooCommerce notification email
- Changing stock status requires opening a dropdown and clicking save per row
- No drag interaction between stock states, no visual column counts per state
SleekView Kanban
-
One card per
productandproduct_variationpost, joined to its WooCommerce postmeta -
Group by
_stock_statuswith canonical In Stock, Out of Stock, Backorder columns -
Virtual Low Stock column driven by
_stockat or below_low_stock_amount -
Drag a card and SleekView updates
_stock_status, firing the WooCommerce stock-status hook -
Card menu opens the full row for inline editing of
_stock,_regular_price, and_sale_price
Features
What SleekView Kanban gives you for Stock Manager for WooCommerce
Drag updates the same postmeta WooCommerce uses
Dropping a card on the In Stock column writes _stock_status to wp_postmeta, the same row Stock Manager edits and WooCommerce core reads. The storefront, the cart, the catalog visibility filter, and the low-stock email all read the same value as before.
Low Stock virtual column
WooCommerce already tracks _low_stock_amount per product. SleekView adds a virtual Low Stock column that shows any SKU whose _stock is at or below its threshold, so the urgent restocking work is one column to the left of Out of Stock and easy to drain into purchase orders.
Variations and simple products in the same view
SleekView renders one card per row in wp_posts filtered to product or product_variation. Variation cards show the parent title plus the variation attributes so a buyer can tell 'Wool Blanket Queen Charcoal' from 'Wool Blanket King Cream' at a glance without opening either row.
Audience
Three ways merchandising uses the stock-status board
Morning low-stock triage
Read the Low Stock column count, sort by sell-through, and the top of the column is the day's reorder list. Drag SKUs to Out of Stock when the supplier confirms zero availability, or to In Stock once the receiving team logs the new shipment.
Sale planning
Filter the board to products with a _sale_price set and read the column split. A sale that drives heavy traffic into Out of Stock products is a markdown that needs replenishment; the board surfaces the pressure as soon as it builds.
Cross-team coordination
Open the board on the warehouse screen during fulfillment shifts. As cycle counts complete, drag SKUs between columns to reflect the current truth, and the storefront, the cart, and the merchandising dashboard all see the same answer.
The bigger picture
Why merchandising needs a board on top of WooCommerce postmeta
WooCommerce stores stock status as a meta value with three canonical values, and that schema is already a kanban waiting to be drawn. Stock Manager makes the rows editable but does not redraw the catalog as a board, which is the read surface merchandising actually needs. The kanban view turns a paginated table into four columns with counts on top, and the question 'how much of the catalog is healthy right now' answers in one glance instead of a pagination scroll.
The Low Stock virtual column adds the urgent restocking queue without inventing a new field, it just compares _stock to _low_stock_amount and highlights what is already in the WooCommerce data model. Drag-and-drop replaces the dropdown plus save click that every status change demands today, and the savings compound across a busy week. Stock Manager's editing flow, the WooCommerce storefront, the cart's add-to-cart logic, the catalog visibility filter, and the low-stock email trigger all keep working without changes because the kanban writes the exact same _stock_status postmeta row that Stock Manager itself does.
The table is for editing, the board is for reading and reacting, and both surfaces share a single source of truth.
Questions
Common questions about SleekView Kanban for Stock Manager for WooCommerce
No. Stock Manager stays the editing surface for cell-level changes like bulk price updates, SKU corrections, and inline quantity edits. The kanban is the read-and-react surface for stock-status transitions. Both surfaces read and write the same WooCommerce postmeta, so changes on either show up on the other immediately.
 SleekView updates the _stock_status meta value on the wp_postmeta row for that product ID. WooCommerce fires woocommerce_product_set_stock_status, the storefront cache invalidates the product, the catalog visibility filter re-evaluates, and the low-stock email trigger runs if the new value crosses the threshold. Nothing else is rewritten.
 Yes. The Low Stock column is a SleekView virtual grouping that compares _stock to _low_stock_amount. Toggle it off in the kanban settings and the board falls back to the three canonical WooCommerce stock-status values: In Stock, Out of Stock, Backorder.
 Yes. SleekView reads wp_posts filtered to post_type product and product_variation, so simple products and individual variations all appear as cards. Variation cards show the parent product title plus the variation attributes so a single board can mix both row types without confusion.
 Yes. SleekView's column filters apply to the kanban, so you can scope by product_cat, by product_tag, by attribute, by sale-price-set, by stock-quantity range, or any other column promoted from the WooCommerce data model. A category-scoped board becomes that category's stock-status snapshot.
 It can. WooCommerce listens for stock-status transitions into outofstock and runs the low-stock notification logic. SleekView fires the same woocommerce_product_set_stock_status hook on every drop, so the notification runs the same way it would after a Stock Manager edit or a store order depleting inventory.
 The board reflects the change on the next refresh. SleekView reads wp_postmeta live on every page load, so a Stock Manager edit, a store order, or any other code path that touches _stock_status lands on the kanban the same way as a drag interaction.
 Yes. Each drop issues its own postmeta update against the row it holds. A card moved by another buyer appears in its new column on the next refresh, and the optional realtime indicator highlights where teammates are working so a single SKU does not get dragged twice in a tight window.
 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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout