Only from the feedback source you point it at. SleekView does not call the AliExpress API. The plugin renders a board of votable items on top of whatever WordPress table you map. If you want to enrich a card with live AliExpress data, add a meta field and hydrate it server-side from your existing API key.

Yes. SleekView ships with a built-in submit form that writes a new row to whichever post type or table you configured. The form pre-fills the category based on the dashboard tab where it lives, so submissions land tagged correctly without requiring a manual category edit by an editor later.

Tag those rows as Bug in your category column and SleekView renders them with the rose color pill. Staff change the status to Investigating, then Shipped once the carrier integration is patched. Store owners see the resolution in the same card thread without chasing up a separate ticket each time.

No. SleekView paginates server-side and caches the rendered board per filter combination. On stores with 10k+ rows the initial page loads under 300ms because only the visible page hydrates. Category filters use indexed queries on the meta keys you mapped at setup time.

Yes. SleekView honors WordPress capabilities and the WooCommerce customer role system. Pass a role attribute to the shortcode and the board filters cards to that tier. Premium owners see priority requests, free-tier owners see general asks, staff see everything plus internal status filters.

SleekView surfaces a similar-cards suggestion as the owner types in the submit form. If a duplicate slips through, staff merge two cards in the admin and the vote counts add up. The merged card keeps the earlier date, so the chronological audit trail stays intact across the partner network history.

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

Yes. Map an additional meta key to the card subtitle slot and SleekView renders it on every card. If you track supplier IDs or variation counts in a meta field, surface them on the card to give dropshippers context on why the team prioritized one fulfillment fix over another in the current sprint.