Yes. SleekView reads the standard WPCafe tables that ship with both editions, including reservations, menu items, and any extra columns Pro add-ons add. Detection happens at the schema level, so new fields appear in the picker without any code update from us.

Upvotes write to a meta key on the underlying reservation or review row, so the same number drives admin reports and the board. SleekView throttles clicks per session and per IP, and you can chain reCAPTCHA on the upvote endpoint if your site already loads it elsewhere on the menu pages.

The default board is read and upvote only, which keeps the abuse surface small. For new submissions, pair the board with the WPCafe post-meal email, a Gravity Forms entry, or any custom post type, and the new rows appear on the board as soon as they hit the database.

Status comes from any column you map, so a workflow meta key like review_status drives the pill. Your team updates the value inside the WPCafe reservation screen or a custom admin column, and the board reflects the change on the next SleekView cache refresh.

Yes. SleekView pages results server side and caches the card list per filter, so a board with tens of thousands of rows loads as quickly as one with a hundred. Upvote clicks use a lightweight admin-ajax endpoint that skips the full template render cycle.

Yes. Add a private meta flag on any row you do not want public, then exclude that flag in the SleekView data source filter. The card stays in the admin queue for your team to handle while the public board only shows reviews that pass the privacy filter you set.

Canny and FeatureBase work fine on their own, but they live outside WordPress and require copying WPCafe data across systems. SleekView Feedback uses the rows already in your WPCafe tables, ships as a one-time license, and renders inside your theme so the board matches your brand without extra integration work.

Yes. SleekView reads the language meta WPML and Polylang already write, so an English menu page only surfaces English reviews. You can also expose a language chip if you want one board where diners switch across languages without leaving the page.