No. SleekView Feedback reads directly from the Stitch Labs custom table or the WooCommerce product post type the connector touches. You point it at the source, pick the columns for votes, status, channel, and title, and the board renders. No ETL job, no sync, no duplicated rows of data.

Yes for public boards via cookies, but most ops teams keep this one behind login. SleekView ships with both modes, so you can decide whether warehouse staff sign in with a WordPress user or whether merchants drop in anonymously via a shared link. The same view handles both with a toggle.

Each visitor gets a cookie scoped vote token per item. Logged in WordPress users are tracked by user ID. The plugin also exposes a per IP rate limit so one workstation cannot spam the triage queue, which keeps internal voting honest without slowing down the people who actually do the work.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one channel, one warehouse, one error type, or any combination of meta fields Stitch Labs already stores. Different boards on different ops pages can use different filters.

Drift is just a category value on the row. You can write it into a meta key Stitch Labs already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original sync record, so the engineer who wrote the mapping can see the flag without ever leaving WordPress.

They write back to the source column, which means Stitch Labs reconciliation jobs and any of your own queries can sort future syncs, retries, and audits by that score. Several ops teams use the score to gate which mappings get engineering time first, which makes the board operational and not vanity.

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 ops board on any internal template without touching the page editor.

The view paginates server side and only loads the rows it needs for the current page. Indexed columns stay fast even on long sync tables. For really big catalogues, scoping the board by channel or warehouse keeps both the query and the audience focused, so the page feels snappy even at full scale.