No. SleekView Feedback reads directly from whatever table or post type Spocket writes to. You point it at the source, pick the columns for votes, status, supplier, and title, and the board renders. No ETL job, no sync, no duplicated data. Anything Spocket imports shows up on the next page load of the board.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote SKUs without an account. You can also require login if you want the board restricted to customers or members only, and the same view handles both modes with a single toggle on the block settings.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a per IP rate limit so a single household or office cannot spam the board, which is enough to keep public storefront voting honest without forcing a signup wall in front of shoppers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one supplier, one country of origin, one shipping speed bracket, or any combination of meta fields Spocket already stores. Different boards on different pages can use different filters.

Shipping issue is just a category value on the row. You can write it into a meta key Spocket already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original product, so the store manager who imported the SKU can see the flag without ever leaving WooCommerce.

They write back to the source column, which means Spocket sync jobs and any of your own queries can sort future imports, restocks, and bulk pushes by that score. Several stores use the score to gate which suppliers get more catalogue space, 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 storefront board on any 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 stay fast even on long product tables. For really big catalogues, scoping the board by category or supplier keeps both the query and the audience focused, so the page feels snappy even at scale.