WooCommerce Product Vendors Pro models vendors as a taxonomy (wcpv_vendors) attached to products, and writes per-line-item commission rows to its own wcpv_commissions table (column names vary by version, the underlying shape is order-id, product-id, vendor-id, commission-amount, status). The default vendor admin shows a list of vendors and per-vendor reports, but joining vendor to product to order to commission in one screen is exactly what the default UI does not do.

SleekView reads wcpv_commissions as a first-class source and joins to wc_orders (HPOS) by order id, to the product post type by product id, and to the wcpv_vendors taxonomy by term id. The result is a single table showing vendor name, product, order, commission amount, and commission status, sortable and filterable across all of them.

Inline edits to commission status (pending, paid, voided) write through the plugin's data layer where supported, so payout state stays consistent with the rest of the plugin. Bulk-mark a payout batch as paid in one pass after a Stripe Connect or wire transfer cycle, with a clean audit trail attached to each row.

A WooCommerce multi-vendor marketplace is a relational system by definition. Vendors live in a taxonomy, products belong to vendors and to categories, orders contain line items from multiple vendors, and commissions are computed per line item. The default Product Vendors Pro admin gives you per-vendor reports and a vendor list, but no cross-vendor commissions table, no payout queue filtered by date, and no per-vendor revenue ranking.

Finance teams running a monthly payout cycle end up exporting CSVs, matching them in a spreadsheet, and updating commission status one vendor at a time. Vendor managers fielding "why is my commission lower this month" questions cannot answer without custom SQL. SleekView joins the same four tables once: commissions, vendors, products, orders.

The result is a marketplace operations workspace inside WP Admin: payout queues, per-vendor revenue, commission-status edits, all sourced from the database your plugin already maintains.