No. SleekView Feedback reads directly from whatever CPT or table Lemon Squeezy mirrors on your site. 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 Lemon Squeezy writes shows up on the next page load.

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

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID, and license holders can be tracked by their activation key. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public roadmaps honest.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one product, one variant, or one license tier. Different boards on different pages can use different filters, so each product can have its own public roadmap if you want.

Refund is just a category value on the row. You can write it into a meta key the Lemon Squeezy synced order already understands or a dedicated column on a log table. Either way it shows up in the WordPress admin alongside the original order, so finance can resolve the dispute without leaving WordPress.

They write back to the source column on the WordPress side, which means your queries and the synced product CPT can sort by that score. Several teams use the score to decide which variants to push back to Lemon Squeezy in the next sync, 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 product, account, or roadmap 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 license table stay fast even at high volume. For really big catalogs, scoping the board by product or tier keeps both the query and the audience focused, so the page feels snappy even on launch day.