No. SleekView Feedback reads directly from the WooCommerce order CPT, the Printful log table, and any meta keys the integration writes to. 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.

Yes. SleekView ships with anonymous voting backed by cookies, so designers can upvote print issues on a shared studio workstation without each one signing in. You can also require login if you want the board restricted to verified studio 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 designer board honest without forcing a separate signup wall in front of staff on shared screens.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to t shirt prints, hoodie mockups, EU warehouse delays, or any combination of dimensions Printful already tracks. Different boards on different pages can use different filters per team or per launch.

Mockup Issue is just a category value on the row. You can write it into a meta key the order already understands or a dedicated column on the print file log. Either way it shows up in the WordPress admin alongside the original order, so the designer can act on the flag without leaving WordPress at all.

They write back to the source column on the WordPress side, which means your queries and the synced order screen can sort by that score. Several POD shops use the score to escalate print and mockup bugs to Printful support faster, 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 studio, merchant portal, 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 print log stay fast even at high volume. For really busy stores, scoping the board by product type or warehouse keeps both the query and the audience focused, so the page feels snappy on launch days.