WooCommerce Min/Max Quantities stores its rules as standard product meta: _wc_min_max_qty_minimum_allowed_quantity, _wc_min_max_qty_maximum_allowed_quantity, _wc_min_max_qty_group_of_quantity plus order-level option keys. The plugin's admin lets a merchandiser open one product, set values and save. What it does not offer is a rollup: which products have rules, which have only a min, which have a group-of step, which categories are uncovered.

SleekView reads wp_postmeta joined with wp_posts and the category taxonomy and renders Product, SKU, Min qty, Max qty, Group-of and Category as sortable, filterable columns. Filter to products with a min but no max for inventory reviews. Sort by category to spot wholesale SKUs that should have a higher minimum. Group by rule type to count coverage across the catalogue.

The plugin keeps owning the rule engine and the cart-side enforcement. The table view owns the audit surface, so the per-product meta merchandising teams already wrote stops hiding inside individual edit screens and becomes a catalogue-wide query they can actually open on Monday morning.

Min/max quantity rules are quiet operational levers: one meta key on one product can lift average order value, protect stock or unlock a wholesale tier. The plugin's admin handles per-product editing well and reporting not at all, so merchandisers end up with thousands of rules scattered across product screens and no way to audit them as a set. SleekView reads the same wp_postmeta the plugin already writes and renders min, max, group-of, category and price as columns.

Filters stack so coverage gaps, wholesale minimums and stepped SKUs become one-click views rather than catalogue crawls. The plugin keeps owning the rule engine; merchandising gets the per-row surface the dataset always deserved.