No. Variation stock lives in wp_postmeta on the product_variation post type by default in WooCommerce. SleekView reads it directly. If you also use an inventory or stock-manager plugin, its custom keys (warehouse-id, supplier-id) are surfaced alongside the core stock keys.

Yes. SleekView writes through WooCommerce's variation CRUD where supported, so woocommerce_product_set_stock, low-stock and out-of-stock email triggers, and any third-party stock listener fire per row. Bulk operations iterate through CRUD so side effects are identical to manual edits.

Yes. The parent product is joined via post_parent, exposing parent title, status, categories, and tags as columns. A variation stock row can include variation-specific stock and parent-context tags side by side.

Yes. _backorders (no, notify, yes) is a filterable column, so views like "Out of stock but backorder allowed" or "Out of stock with no backorder" are saved filters. Useful for support teams during stockouts.

Yes. _low_stock_amount is exposed as a column, and views can filter to _stock below _low_stock_amount at the row level. The trigger for the low-stock email aligns with the same condition.

Yes. subscription_variation from WooCommerce Subscriptions follows the same post-type structure as product_variation. Stock keys (_stock, _stock_status) are surfaceable as columns alongside subscription-specific meta.

Queries hit indexed columns on wp_posts and the indexed meta_key + post_id path on wp_postmeta. Attribute-term filters use wp_term_relationships indexes. Pagination is keyset where possible so large catalogs stay responsive.

Yes, indirectly. Any inventory plugin that logs movements on the woocommerce_product_set_stock hook captures inline-edit changes from SleekView as if they came from the default editor. Movement logs aren't bypassed.