No. Frontend Submissions still owns vendor onboarding, the submission forms, and the payout workflow. SleekView Charts adds a flexible reading layer on edd_commission posts, the fes-vendor users, and the linked EDD orders so the team sees unpaid totals, status mix, top vendors, and signups on one screen.

Frontend Submissions writes the vendor user_id into _edd_commission_info on every commission and assigns the fes-vendor role to the user. SleekView reads both signals to attribute sales and commissions to the right vendor across the marketplace.

Yes. The _edd_commission_status meta carries unpaid, paid, or revoked on every edd_commission post. SleekView Charts plots a donut of the status mix and a Number card for the unpaid total ready for the next vendor pay run.

Yes. Join edd_order_items to the linked download and use the download author (which Frontend Submissions sets to the vendor user_id) to sum total per vendor. The resulting horizontal bar shows which vendors are actually driving the marketplace.

Yes. The fes-vendor role lives on standard users with user_registered as the signup date. SleekView Charts plots an area chart of new vendor signups per day, useful for measuring marketing and partner acquisition campaigns over time.

Yes. Saved chart views support role-based and user-based scoping, so a vendor can view a dashboard of their own commissions and sales while partner managers see the full marketplace. The same chart respects the role rules on the frontend embed.

Yes. Any saved chart view can be embedded on a frontend page with role-based access, so vendors and partners read their own commission and sales numbers without WordPress admin access. Embeds respect the same role rules as admin.

Cards aggregate against the existing post type and edd_orders indexes on post_status, post_date, customer_id, and date_created, so dashboards stay quick even on marketplaces with thousands of vendors and tens of thousands of commissions in history.