No. SleekView Feedback reads directly from whatever bridge log table or synced CPT the connector uses. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL, no sync, no duplicated data. Anything the bridge writes shows up on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so merchant staff can upvote incidents without juggling a WordPress account on a shared workstation. You can also require login if you want the board restricted to verified merchants, and the same view handles both modes with a single toggle.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep an internal integration board honest without forcing a separate signup wall in front of merchants on a shared screen.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one shop, one combination reference, or any combination of bridge dimensions the connector already tracks. Different boards on different pages can use different filters per merchant or per team.

Combination Bug is just a category value on the row. You can write it into a meta key the synced product CPT already understands or a dedicated column on the bridge log. Either way it shows up in the WordPress admin alongside the original sync event, so the engineer can act without leaving WordPress.

They write back to the source column on the WordPress side, which means your queries and the synced product CPT can sort by that score. Several integration teams use the score to decide which PrestaShop combinations to remap next, which makes the board operational and not just a vanity dashboard.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any merchant portal, internal ops, or roadmap template without touching the editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns on the bridge log table stay fast even at high volume. For really big catalogs, scoping the board by shop or product type keeps both the query and the audience focused on each board.