It works with default WooCommerce product reviews directly. SleekView reads wp_comments filtered by the review comment type, surfaces ratings, and writes helpful counts back if you map them to the vote column.

Whatever column you mapped as the vote source. If you point SleekView at the rating helpful count, upvotes increment that column. If you point it at a custom meta key on a feedback CPT, upvotes write to that meta. SleekView never creates a parallel vote database, so the data stays consistent with the rest of your store admin.

Both flows work. SleekView ships with a built-in submit form that writes to whichever post type or table you configured as the source. If you already use Fluent Forms or Gravity Forms for feedback collection, you can keep that flow and let SleekView render the board on top of those submissions without changing the intake.

Canny and FeatureBase are external SaaS tools with their own login, their own database, and their own monthly bill. SleekView lives inside WordPress, reads from your existing tables, and ships as a one-time-purchase plugin. The board sits on your domain, respects your existing shopper accounts, and stays inside your data.

No. SleekView paginates server-side and caches the rendered board per filter combination. On stores with 50k+ comment rows the initial page load is under 300ms because only the visible page worth of cards gets hydrated. Filtering and sorting use indexed queries on the columns you map.

Yes. SleekView honors WordPress capabilities and WooCommerce customer roles. Pass a role attribute to the shortcode and the board filters cards to that audience. Wholesale buyers can see B2B-only requests, retail buyers see the public board, staff see everything plus internal status filters.

Both modes are supported. Logged-in mode prevents duplicate votes per account and surfaces vote-by-name in the admin. Guest mode rate-limits by IP and cookie, which is the right default for stores that want broad participation without forcing account creation just to upvote a feature request.

Nothing destructive. SleekView only reads the data, it does not migrate or rewrite reviews. You can run the SleekView board on a dedicated feedback page while keeping the default review section on product pages. Most stores use both, with the board acting as a roadmap layer above the per-product reviews.