Products and variations from wp_posts joined to the WooCommerce stock postmeta keys (_stock, _stock_status, _backorders, _low_stock_amount). SleekView reads only what WooCommerce and Bulk Stock Management already store.

Yes. Group a Pie or Bar card by _stock_status and the dashboard shows the share of instock, outofstock and onbackorder products. A donut variant gives proportional reading, a bar gives absolute counts.

Yes. Filter to products under their low-stock threshold and group a Bar card by product_cat. The chart ranks categories by gap size, which is the lens merchandising uses to plan restock orders.

No. Bulk Stock Management still owns the editing surface and the bulk grid. SleekView Charts adds the reporting dashboard on top of the same postmeta values. Use one for fixes, the other for awareness.

Yes. SleekView writes through the WooCommerce product CRUD layer where supported, so woocommerce_product_set_stock and similar hooks fire on stock changes. Bulk operations iterate through CRUD so side effects match manual edits.

Yes. Any filtered product set behind a chart card exports as CSV with the stock columns the Table view would show. Suppliers and warehouse partners use this for purchase orders and restock plans.

Yes. Variation-level stock is exposed as a chartable dataset alongside parent products, so a Pie of stock status can split by simple product, variable product and individual variation.

Products and variations remain post types under HPOS, so SleekView reads them the same way. Orders move to wc_orders, stock stays in postmeta, chart config is unaffected by the schema switch.