SleekView reads filter rules data directly from the WordPress database, so any edition that writes its rules and meta to the standard tables works. Both the free build and any premium release of WooCommerce Product Filter expose the same schema, which means the kanban renders the same way regardless of which version is installed on the store.

Yes. A drop writes the new filter_status back to the same row the storefront reads on the next page render, so a filter moved into the active lane shows up on the linked category landing page within seconds. The plugin's own caching layer flushes the affected URLs so shoppers see the new rule immediately.

Yes. SleekView views are configuration only, so you can build one board filtered to women's apparel rules and another to home goods filters from the same Product Filter table. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the merchandising team.

SleekView reads distinct status values on every load, so a new state shows up automatically as its own lane at the right edge of the board. You can rename, recolor, or reorder lanes from the view config without touching the Product Filter settings, and any rules already in the new state stay live.

Yes. Drag-and-drop drops are gated by the same capability checks that protect the WooCommerce settings screen. Merchandising leads can move rules into active, while staff with restricted roles see read-only cards on the active lane until their permissions are raised by an admin on the WordPress side.

Yes. Each card opens a side panel that pulls the target shop page, every linked taxonomy and attribute, the active and scheduled windows, and the last-edited user. A merchandiser can audit a rule end to end from the panel without jumping to the Product Filter settings screen in a separate browser tab.

Yes. Every drop records the user, the previous filter state, the new state, the affected rule, the linked category, and the timestamp into the SleekView change log. A merchandising lead can export the log as CSV at any time, which is much faster than reading raw filter revisions in the WordPress database.

No. SleekView lazy-loads cards per lane and paginates each column server-side, so the initial render only fetches the rows currently on screen. Stores with tens of thousands of filter rules still see a board that opens in under a second, and drag-and-drop updates use single-row writes that stay fast at any catalog size.