Yes. SleekView reads FKCart settings, cart event meta, and any request post type straight from the standard WordPress tables, so the integration works with the current release as well as older versions that keep the same schema. No proprietary endpoint is required and no cart data ever leaves your site.

The count writes back to a meta key on the request row in wp_postmeta. SleekView debounces clicks per session and per IP so a single shopper cannot inflate the total. If you already use a different upvote meta from another plugin, you can point SleekView at that column without migrating data.

The default board is read and upvote only, which keeps abuse low and moderation light. If you want shopper submissions, pair the board with a Gravity Forms entry, a custom post type, or the FKCart feedback drawer. SleekView picks up new rows as soon as they hit the database.

Status comes from any column you point at, so a workflow meta key like cart_request_status drives the pills. Your team updates the status inside the WordPress admin or a custom admin column, and SleekView reflects the change on the public board within the next cache window.

No. SleekView pages results server side and caches the rendered card list per filter, so a board with tens of thousands of requests loads as quickly as a board with a hundred. Upvotes use a lightweight admin-ajax endpoint that does not bootstrap a full template render on each click.

Yes. SleekView respects post status, so draft and private requests stay hidden. You can also add a private meta flag and exclude it in the data source filter, which is handy for fraud or refund notes that you route through a private resolution flow with the shopper involved.

Canny and FeatureBase are solid hosted boards, but they live outside WordPress and require copying cart context across systems, paying per seat, and stitching SSO. SleekView Feedback uses the data already inside WordPress, ships as a one time license, and renders inside your existing theme with your own brand on top.

Yes. SleekView reads the post language meta that WPML and Polylang already write, so a board on the English page only surfaces English requests. You can also expose a language category chip if you want one board where shoppers filter across languages from the same surface.