It depends on the build. Plugins like Advanced Coupons or Discount Rules for WooCommerce use a custom table (e.g. wc_conditional_discount_rules or similar). Others serialise rules into a wp_options row. SleekView reads either, mapping condition objects to columns where they're scalar and to expandable child views where they're nested.

Yes if the plugin records application on the order. WooCommerce typically writes applied-rule data to wc_orders_meta under a plugin-specific meta key. SleekView aggregates that into a Last Fired or Times Applied column on the rule row. If a plugin doesn't record application, the column is unavailable but everything else still works.

Yes. Nested condition groups expand as a child view on each rule row so the structure is readable. Scalar conditions (min cart total, applicable role) become columns. Bulk-editing a top-level threshold across many rules is straightforward; deep-nested structural edits are still better done one rule at a time.

Yes. Status changes, discount-value edits, and threshold updates route through the plugin's CRUD method where supported. The plugin's updated_rule action (or equivalent) fires so cache invalidation, analytics events, and any third-party integrations run as expected.

Yes. The applicable-roles condition exposes as a multi-value column. Filter to rules that apply to customer, wholesale, or any custom role, and confirm at a glance that each segment has appropriate coverage.

Native WooCommerce coupons live in wp_posts with post_type=shop_coupon and their own postmeta. Some conditional-discount plugins extend coupons rather than implementing a separate rules table. SleekView has a dedicated coupon view for that schema and a discount-rules view for the table-based schema; both unioned if you want a unified discounts dashboard.

Yes. Filter to a tagged set (e.g. all spring-sale rules), bulk-update Start Date and End Date, and save. Each row writes through the plugin's update method so scheduling logic kicks in correctly. Useful for porting a successful Q1 calendar to Q2 with date shifts.

No. SleekView reads admin-side from the rules table and the orders table. It doesn't sit in the cart resolution path or modify checkout queries. The plugin's own resolution logic runs unchanged at runtime.