WooCommerce Min Max Step Control stamps min, max and step values onto each product as postmeta (typically _wpbo_minimum, _wpbo_maximum and _wpbo_step). The values drive checkout validation per product, but cross-catalog questions like "which categories still let single-unit orders through?" stay invisible behind individual product edit screens.

SleekView reads wp_posts joined with the Min Max Step Control meta keys and renders the catalog as a queryable rules audit table. Filter to products without a minimum to find coverage gaps. Sort by category to plan wholesale rollouts. Filter to rules where _wpbo_minimum exceeds _wpbo_maximum to surface configuration errors in one query. The same dataset the chart view aggregates becomes a row-level surface for merchandising and ops.

The plugin keeps owning the checkout-side enforcement of the rules. The table view owns the audit surface, so the rule meta Min Max Step Control already writes stops hiding inside the product editor and becomes something merchandising can actually filter and reconcile.

Min Max Step Control protects margin on bulk catalogs by enforcing checkout rules per product, but the rule values live as postmeta scattered across thousands of products with no native cross-catalog surface. A partial rollout, a conflict (minimum above maximum) or a step value that does not divide the minimum can sit there for months and only show up when an off-spec order reaches fulfilment. SleekView reads wp_posts joined with the rule meta and renders the catalog as a queryable audit table.

Filters stack so the wholesale coverage audit, the conflict triage and the per-category rollout become saved views rather than spreadsheet exports. The plugin keeps owning checkout enforcement, while merchandising gets the per-row surface the rule data always deserved.