WooCommerce Conditional Shipping and Payments lets a store hide or restrict gateways and shipping methods based on cart conditions: total, category, country, role. The plugin saves the resolved payment_method and the chosen shipping method on the order, while the rule definitions stay in plugin options. Configuration is in one place, outcomes are scattered across order rows, and the question of which rule did what is hidden inside individual orders.

SleekView joins wc_orders with the shipping order_item and the conditional rule meta in options, exposing the gateway, the shipping method, the matched-rule ID and the cart conditions as columns. Filter to orders where a region-restriction rule fired to confirm compliance. Sort by date_created to assemble the daily rule-firing log. Group by matched rule to see which rules are doing the work and which are dead. The data the chart view aggregates becomes a row-level surface for payments, logistics and compliance.

The plugin keeps owning the rule UI and checkout enforcement. The table view owns the audit surface so rule outcomes become something the team can review without clicking order by order.

The conditional layer in a Woo checkout is invisible by design. Customers never see the gateways or methods that were hidden, and the team only sees the methods that survived. That makes rule effectiveness one of the least-measured surfaces in the store despite the rules touching every order.

SleekView reads the chosen gateway, the chosen shipping method and the matched rule and renders them as one queryable row per order. Filters stack into a single query so the per-rule firing list, the regional compliance audit and the gateway-distribution review become one-click views. The plugin keeps owning the rule UI and the checkout enforcement, while the team finally gets the per-row outcomes the rule engine was always producing.