Yes. The Frontend Manager piece runs on the vendor-facing side — vendors edit products, view orders, and manage their store from there. SleekView reads the marketplace tables on the admin side, which is where operators manage cross-vendor data. The two are complementary: Frontend Manager handles vendor-side workflows, SleekView handles admin-side ops. They don't overlap or interfere.

Yes. Status edits write through the WCFM API so notifications fire (vendor gets emailed), balance updates run (their available balance recalculates), and audit hooks fire (the action gets logged). Bulk approval selects multiple rows and processes them in sequence — useful for monthly payout cycles where you have many requests to handle at once. The result is the same as approving them one-by-one in the WCFM admin, just faster.

Membership data is stored in postmeta on the vendor user account. Surface tier as a column and segment vendors by plan — useful for growth reviews comparing performance across tiers, or for tier-specific outreach. A view scoped to 'tier=premium' gives marketing the high-value vendor list; the inverse spots vendors stuck on a free or starter tier who might be candidates for an upgrade conversation.

Yes. If you use vendor staff (sub-accounts under a primary vendor with restricted permissions), those records become a related table or column. Filter views by primary vendor or by individual staff member, useful for tracking which staff manage which orders or for auditing staff-level access during a security review. The staff feature is a Pro module, and SleekView surfaces it when present.

Yes. Any view exports to CSV with the columns and filters you've configured — withdrawals, refunds, commissions, vendor performance — for accounting reconciliation against payment processor reports. Useful for monthly bookkeeping where you need to match WCFM withdrawal records against Stripe transfers or bank ACH disbursements. The CSV is one click from the table header.

Currency is stored per order. Build per-currency views for separate operations workflows where finance reviews in different base currencies, or aggregate by converted amount where currency conversion is recorded by your currency module. Useful for international marketplaces where the marketplace operates in one base currency but vendors transact in their local currency, and reconciliation needs both perspectives visible.

Commission rules — flat, percentage, tiered, per-product — apply at order time and write the resulting commission amount to wcfm_marketplace_orders. SleekView reads the resolved amount, so you see the actual commission per order regardless of which rule applied. For rule-level analysis (which rule is generating the most commission, which is being applied least), build a separate view scoped to the rules table.

Yes. Refund and dispute records have timestamps and statuses. Build a per-vendor dispute count column over a rolling window — vendors with rising dispute counts surface for quality review before the marketplace's reputation takes a hit. Combine with order count for a ratio view, since absolute dispute counts on high-volume vendors can be normal while the same count on a low-volume vendor signals a real quality issue.