No, it's an additional admin surface that reads the same source data the Stock Manager UI reads (_stock, _stock_status, _backorders in wp_postmeta). The two coexist: keep Stock Manager for merchants who like its workflow and use SleekView for ops teams that want custom column sets and saved filtered views.

Yes. Inline-edit _stock, _stock_status, and any postmeta key in the row. Bulk-update routes through WooCommerce's product CRUD so woocommerce_product_set_stock and stock-status transition hooks fire for every row, identical to manual edits.

Yes. SleekView writes through WooCommerce's CRUD layer where supported, so low-stock and out-of-stock notification emails fire on the same hook (woocommerce_low_stock) regardless of whether the change came from Stock Manager, SleekView, or the product edit screen.

Yes. The product_variation post type is exposed alongside product, with the parent product id and attribute summary available as joinable columns. Variation-level stock (_stock on the variation) and parent-product fields can sit in the same view.

Yes. The agent UI scans wp_postmeta for keys actually in use and lets you pick from a real list. Add a column for any supplier-id, reorder-window, lead-time, or warehouse-zone key your plugins or imports populate.

Queries hit indexed columns (ID, post_type, post_status) on wp_posts and the indexed meta_key + post_id path on wp_postmeta. Pagination is keyset where possible, and heavy aggregate columns (total movement over 30 days, joined from order items) are opt-in per view so default lists stay quick.

Yes. Views are gated by WordPress capability, so warehouse staff get the low-stock-and-reorder view, finance gets the cost-and-value view, and store managers see the full grid. Each role's saved filters and column sets persist between sessions.

Through hooks where supported. SleekView prefers the plugin's CRUD path so all WooCommerce listeners (stock sync extensions, marketplace bridges, ERP integrations) see the same events a manual edit would emit. Direct writes are a fallback only for keys with no CRUD wrapper, and a conflict-detection check prevents stale overwrites.