No. SleekView Feedback reads directly from whatever log table or 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 job, no sync, no duplicated data. Anything the connector writes shows up on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so floor staff can upvote incidents without juggling a WordPress account on a shared terminal. You can also require login if you want the board restricted to verified ops staff, 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 ops board honest without forcing a separate signup wall in front of pickers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to Amazon, eBay, Etsy, or any combination of channels the connector already tracks. Different boards on different internal pages can use different filters per team.

Channel Issue is just a category value on the row. You can write it into a meta key the connector log already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original sync event, so the engineer who maintains the channel can act on the flag without leaving WordPress.

They write back to the source column on the WordPress side, which means your queries and the connector log can sort by that score. Several ops teams use the score to decide which channel bugs to escalate to engineering first, 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 internal ops, warehouse, or merchant 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 log table stay fast even at high volume. For really busy operators, scoping the board by channel or warehouse keeps both the query and the audience focused, so the page feels snappy even at peak.