Min Max Quantities Pro stores its rules in standard WooCommerce postmeta keys: minimum_allowed_quantity, maximum_allowed_quantity, and group_of_quantity on each product, plus equivalent variation-level keys. Store-wide rules live in wp_options under the plugin's own option keys. The plugin's settings screen lets the merchant set defaults and override per product, but never lists the whole catalogue with each product's rule status.

SleekView reads the rule postmeta across every product and variation, plus the option-level defaults, and exposes minimum, maximum, group-of, and cart-level rules as first-class columns. Products without any constraint, products whose minimum exceeds available stock, and variations whose rules conflict with their parent become obvious in saved views rather than one-off audits.

Inline edits route through WooCommerce CRUD so the plugin's hooks fire and any caches it maintains stay correct. Bulk updates to minimum or group-of quantity across a category or tag use the same path, which is the operation merchandising teams most often need to perform during promotions.

Min Max Quantities Pro is the plugin that prevents a customer from buying 1 of a thing meant to be sold in packs of 12, or 500 of a thing only available in dozens, which is a small UX detail in a small catalogue and a major operational lever in a large one. The default admin lets a merchant set rules per product, but it never lists the whole catalogue with each product's rule status, which means products without a max sneak in, variation rules drift from their parents, and promotional packs go live without a group-of value. The data is all there in minimum_allowed_quantity, maximum_allowed_quantity, and group_of_quantity postmeta, plus the store-wide options.

SleekView reads them, joins parent and variation context, and exposes the whole catalogue as a sortable, filterable, editable table. Merchandising can finally find every product missing a max. Catalog ops can finally bulk-update group-of values before a campaign.

Support can finally look up the exact rule that triggered a checkout error. The plugin still owns the rule engine; SleekView turns the catalogue into a working surface.