It depends on the configuration. By default SleekView caches the matched-product set with a configurable cache duration so resolution doesn't run on every page load. For live conditional rules, set the cache low or trigger resolution on the wapl save hook.

Yes. Build a Line card filtered to one label slug and group by date_resolved. The line shows expansion or contraction of coverage as products move in and out of the rule's match set.

Yes. Dynamic stock-state labels are stored as wapl posts the same way static ones are. They appear in the same Bar and the same coverage count, with the caveat that their match set changes faster, so set a shorter cache duration.

No. The labeled-flag column on the line item is a boolean, so a product wearing two labels still contributes once to the labeled side of the donut. For per-label revenue contribution, switch to a Bar grouped by label_slug.

Yes. Category and taxonomy conditions are stored on the label post the same way other conditions are. Filter the dashboard by category and the cards reflect coverage and sales inside that category only.

Coupons describe how the discount was applied. Labels describe how the product was presented on the storefront. They overlap (a Sale label often accompanies a coupon) but a label can also be active without any coupon code attached to the order.

Only if those blocks also write a wapl-compatible label or product-meta key the dashboard knows to read. For custom label systems, point the dataset at the right meta key and the same charts work.

Yes. SleekView gates each view by capability so a custom role can see the dashboard without seeing the rest of WP Admin. The label-merchandising sub-team typically only needs read access to this one dashboard.