No. SleekView Feedback reads directly from the SureCart order post type, the abandoned cart table, and any meta SureCart already stores. You point it at the source, pick the columns for votes, status, gateway, and title, and the board renders. No ETL job, no sync, no duplicated data.

Yes. SleekView ships with anonymous voting backed by cookies, so shoppers can vote on a public status board without an account. You can also restrict voting to logged in customers if you want the score to reflect verified buyers, and the same view supports both modes from one toggle.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID, so even if they switch devices they only count once per issue. The plugin also exposes a per IP rate limit so a single network cannot brigade the board with synthetic votes from one shopper.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one gateway like Stripe, one country, one currency, or any combination of meta fields SureCart Checkout already stores. Different boards on different pages can use different filters.

Bug is just a category value on the row. You can write it into a SureCart meta key or a dedicated column. Either way it shows up in the WordPress admin alongside the original order record, so the developer who maintains the checkout can see the flag and reproduce it without leaving WordPress.

They write back to the source column, which means SureCart and any of your own engineering queries can sort the backlog by score. Several stores use the score to gate which checkout fixes ship next, which makes the board operational instead of a vanity status page that nobody on the team actually checks.

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 checkout status board inside your existing layout without changing the editor.

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