Yes. Free has the core pv_commission table; Pro adds more commission fields (shipping commission, tax handling, more granular status types) and additional metadata. SleekView surfaces whichever columns your install has — when Pro is active, the additional fields appear automatically without configuration. Build a view once and it adapts to the schema you actually have.

Yes. Select rows and update status inline — the standard WC Vendors hooks fire so any payout integrations (Stripe Connect, PayPal Mass Pay, custom processors) run normally. The bulk update is the same operation as a one-by-one status change, just batched. Useful for monthly cycles where you process dozens or hundreds of approvals at once and want a verifiable record of what got paid when.

Same data layer. WC Vendors Marketplace is the rebrand of the Pro version — the schema is unchanged, the table names are unchanged, and SleekView reads the same pv_commission table on either branding. If you migrated from one name to the other, no reconfiguration is needed; existing views keep working with no changes.

Yes. Shipping is stored alongside item commission in the same table on Pro/Marketplace setups. Surface both as separate columns or as a sum. Useful for marketplaces where vendors handle their own shipping and the commission split needs to reflect that — finance can review item commission and shipping commission separately, or roll them up for the vendor statement.

Yes. HPOS (High-Performance Order Storage) moves orders from wp_posts to wc_orders, but commission records still live in pv_commission with order ID references. SleekView's joins use whichever order storage WooCommerce is configured for — legacy or HPOS — and the result is the same. No migration step needed when you flip the HPOS toggle.

Yes. Any view exports to CSV with the columns you've defined — vendor, order, commission amount, status, paid date, etc. Useful for monthly bookkeeping, quarterly reviews, or year-end 1099 preparation where you need a clean record of payouts per vendor. The CSV is one click from the table header and includes the same data visible in the view.

Build a per-vendor commission history view filtered by vendor — each row shows the commission, the parent order, the date, and the status. When a vendor questions a commission amount, the view answers their question in seconds with order-level context. For deeper investigation, the order join lets you see refunds, partial refunds, and reversed commissions tied to the same order.

Yes. Add a calculated column dividing commission by order total — surfaces effective commission rate per order. Useful for spotting orders where a flat-fee structure resulted in unusually high or low effective rates, or where a vendor's commission rule isn't producing the expected percentage. Filtering by effective rate range catches edge cases your commission rules might be missing.