SleekView Kanban for ATUM Inventory Management
ATUM Inventory Management writes stock quantity, status, supplier, and reorder point into wp_atum_product_data. SleekView Kanban groups those rows by stock_status so purchasing sees In Stock, Low Stock, Out of Stock, and Backorder as columns, and a drag updates the row directly.
♾️ Lifetime License available
Inventory triage on a board, not Stock Central rows
ATUM Inventory Management is the most installed purchasing plugin in WooCommerce. Every SKU lands in wp_atum_product_data with stock_quantity, stock_status, supplier_id, and out_stock_threshold wired up. Stock Central renders that table as a list, which works for cell editing but treats the morning purchasing standup as a scroll exercise: how many SKUs are low, which suppliers own the low rows, and which SKUs crossed the reorder threshold overnight are all answerable from the table only after a manual scan.
SleekView Kanban reads the same wp_atum_product_data rows and groups them by stock_status. The natural status column is right there, with canonical values In Stock, Low Stock, Out of Stock, and Backorder. Each card shows the SKU, the product title joined from wp_posts, the supplier name joined from the ATUM supplier post type, the stock quantity, and the reorder threshold. The purchasing lead reads the day in column counts: 47 Low, 12 Out, 3 Backorder, and the rest healthy.
Drag a card from Out of Stock to In Stock and SleekView writes stock_status = 'instock' back to wp_atum_product_data alongside the standard WooCommerce _stock_status postmeta sync so the storefront and Stock Central agree. The ATUM reorder logic, low-stock email triggers, and supplier purchase orders keep running because the underlying row is the same one Stock Central edits.
Workflow
From Stock Central rows to a purchasing board
Point SleekView at wp_atum_product_data
Pick stock_status as the status column
Choose what shows on each card
Enable drag-and-drop with stock sync
Sample board
Sample ATUM purchasing board
Comparison
Default ATUM Stock Central vs SleekView Kanban
Default ATUM Stock Central
- Stock Central renders inventory as a flat row table with no kanban grouping
- No column split by stock_status to read In Stock, Low, Out, Backorder counts at a glance
- Reorder-threshold breaches are surfaced only via the low-stock email after the fact
- Supplier-level low-stock pressure requires a manual Stock Central filter and a scroll
- Status changes are dropdown saves per row, with no drag interaction across statuses
SleekView Kanban
-
One card per row in
wp_atum_product_data, joined to product title and supplier -
Group by
stock_statuswith canonical In Stock, Low Stock, Out of Stock, Backorder columns -
Drag a card across columns and SleekView writes the new
stock_statusback to ATUM and WooCommerce - Card front shows SKU, supplier, current quantity over reorder threshold at a glance
-
Reorder badge highlights SKUs that crossed
out_stock_thresholdovernight
Features
What SleekView Kanban gives you for ATUM Inventory Management
stock_status is the natural status column
ATUM already canonicalizes stock state into four values: instock, lowstock, outofstock, onbackorder. SleekView Kanban consumes that directly and renders a column per value, so the board configures with one click and zero data transformation work.
Drag writes back to ATUM and WooCommerce
Dropping a card on the In Stock column writes stock_status to wp_atum_product_data and syncs WooCommerce _stock_status postmeta. The storefront, the cart, the low-stock email trigger, and the ATUM purchase-order workflow all stay aligned automatically.
Reorder-threshold badge surfaces the urgent work
ATUM stores out_stock_threshold per SKU. SleekView highlights cards whose quantity has crossed the threshold with a small badge, so the Low Stock column sorts visually by purchasing urgency before any explicit ordering is done.
Audience
Three ways purchasing teams use the ATUM kanban view
Morning purchasing standup
Open the board, read the day in column counts, drag any SKUs that landed in Out of Stock into Backorder where appropriate, and assign supplier follow-ups directly from the card menu before the standup ends.
Supplier-scoped boards
Filter the board to one supplier_id and the kanban becomes that supplier's exposure snapshot. The Low Stock column is the next purchase order's draft list, the Out of Stock column is the escalation list for the supplier call.
Threshold rebalancing
The reorder-threshold badge surfaces SKUs whose thresholds are out of sync with actual sell-through. Drag them into a saved 'Review threshold' view and the purchasing lead has the rebalancing queue for the week, with no spreadsheet detour.
The bigger picture
Why purchasing teams need a board, not a row table
Stock Central is a great editing surface but a poor read surface for the question purchasing actually asks: where is the day's exposure right now. The list answer means scanning thousands of rows, the kanban answer is four columns with counts on top. Forty-seven Low Stock and twelve Out of Stock is a reading every team member can take in at a glance.
Supplier-level exposure becomes a one-click filter that turns the board into a supplier-specific snapshot ready for the call. The reorder-threshold badge replaces the spreadsheet step where someone exports Stock Central, sorts by quantity over threshold, and hands a list to the buyer. The drag interaction matches how purchasing actually changes stock state: a SKU arrives, a card moves to In Stock, the row updates, the storefront agrees.
ATUM's reorder logic, low-stock email triggers, supplier purchase orders, and Stock Central editing all keep running because the kanban is a read and write layer over the same wp_atum_product_data the rest of the plugin uses. Stock Central stays where it shines, the board takes over where it does not.
Questions
Common questions about SleekView Kanban for ATUM Inventory Management
No. Stock Central remains the editing surface for cell-level changes like supplier reassignment, cost adjustments, and bulk attribute edits. The kanban view is the read-and-react surface for stock-status transitions across the day. Both views read and write the same wp_atum_product_data rows, so anything edited on either surface shows up on the other immediately.
SleekView updates the stock_status column on the wp_atum_product_data row for that product ID and syncs the WooCommerce _stock_status postmeta on the corresponding wp_postmeta row. WordPress fires the standard woocommerce_product_set_stock_status hook so plugins listening for status changes (the storefront cache, the low-stock email, the purchase-order workflow) react automatically.
Yes. wp_atum_product_data carries rows for both simple products and individual variations, and SleekView renders one card per row. The card front shows SKU and product title, with the parent product title shown for variation rows so the buyer can read 'Wool Blanket Queen Charcoal' on a variation card and know which parent it belongs to.
ATUM stores out_stock_threshold per SKU on wp_atum_product_data. SleekView compares stock_quantity to out_stock_threshold on every row at render time and shows a small badge when quantity is at or below the threshold. The badge is just a visual cue, no data is written until a moderator drags the card.
Yes. SleekView's column filters apply to the kanban view, so you can scope by supplier_id, by location_id, by product category, or by any other column in wp_atum_product_data or the joined tables. A supplier-scoped board becomes a supplier-specific exposure snapshot ready for the daily call.
It can. The low-stock email in ATUM listens for stock_status transitions into outofstock or lowstock, and SleekView fires the standard WordPress and WooCommerce hooks on every drop. If the destination column corresponds to one of those statuses, the email trigger runs the same way it would after a Stock Central edit.
Yes. SleekView reads and writes wp_atum_product_data directly, so concurrent drops by different buyers each issue their own update against the row they hold. A card that was just moved by another buyer appears in its new column on the next refresh, with the optional realtime indicator showing where teammates are working.
The board reflects it on next refresh. SleekView reads the live wp_atum_product_data table on every page load, so changes from Stock Central edits, ATUM purchase-order receipts, WooCommerce orders depleting stock, or any other code path land on the board the same way as a drag interaction. The card moves to the column matching the new stock_status.
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