No. WCFM's reports stay where vendor managers expect them. SleekView Charts is the dashboard layer for cross-table and role-scoped views, like top-vendor leaderboard plus withdrawal donut plus commission trend on one screen with one filter.

Primarily wcfm_marketplace_orders for commissions and per-vendor performance. Joins to wp_users for vendor identity, wcfm_marketplace_withdraw_request for payout charts, and wcfm_marketplace_refund_request for refund ratios.

Yes. The Frontend Manager piece runs on the vendor-facing side; SleekView reads the marketplace tables on the admin side. The two are complementary and don't overlap. Vendors keep their dashboard, marketplace operators get the admin-side dashboard.

Yes. Membership data lives in postmeta on the vendor user account. Promote tier to a column and add a donut card showing the marketplace's vendor distribution across tiers. Useful for growth reviews and tier-upgrade outreach.

Currency is stored per order. Build per-currency dashboards for separate workflows, or aggregate by converted amount where currency conversion is recorded by your currency module. International marketplaces typically save one dashboard per major currency plus a global converted-amount view.

Yes, if you use the vendor staff module. Staff records become a related table or column. Filter dashboards by primary vendor or by individual staff, useful for staff-level performance audits or security reviews where access patterns need a visual check.

Yes. Each card's underlying dataset exports as CSV with the columns and filters configured. Useful for monthly bookkeeping where you need to match WCFM commission and withdrawal records against payment-processor reports for reconciliation.

All chart work happens inside wp-admin with server-side pagination and aggregation against the indexed WCFM columns. Storefront pages, vendor frontend, and checkout are untouched. Dashboards typically render in under a second even on marketplaces with hundreds of vendors and high order volume.