No. SleekView Feedback reads directly from MVX vendor users, the commission table, the withdrawal CPT, or any custom feedback CPT you set up. 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.

Vendors already have a WordPress user, so they can upvote directly when logged in. Public visitors get cookie scoped anonymous voting on the board if you allow it. You can also require login if you want the board restricted to verified vendors only, and the same view handles both modes with one toggle.

Each visitor gets a cookie scoped vote token per item. Logged in vendors are tracked by user ID, which means duplicate votes from the same vendor are blocked. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep marketplace boards honest.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one vendor category, one commission tier, or any combination of MVX dimensions the plugin already stores. Different boards on different pages can use different filters per vendor segment.

Commission Bug is just a category value on the row. You can write it into a meta key the MVX commission row already understands or a dedicated column on a log table. Either way it shows up in the WordPress admin alongside the original commission, so finance can act without leaving WordPress.

They write back to the source column, which means your queries and the MVX admin can sort by that score. Several marketplaces use the score to gate which commission bugs get fixed first and which dashboard ideas earn engineering time, 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 inside the MVX vendor dashboard template without touching the page editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns on the commission table stay fast even at high volume. For really busy marketplaces, scoping the board by vendor segment or commission state keeps both the query and the audience focused at peak.