WCFM Marketplace layers vendor management on top of WooCommerce with its own structures. Vendors live as WordPress users with the wcfm_vendor role plus rows in wcfm_marketplace_vendor. Sub orders are shop_order_vendor posts tied back to a vendor via vendor_id. Withdrawal requests live in wcfm_marketplace_orders with status values of requested, approved, and cancelled. The default WCFM admin builds a separate screen for each, which forces operations to switch tabs constantly during a busy day.

SleekView Kanban reads each of these directly. Point the board at vendors and approvals run from a Pending column. Point it at sub orders and you get a per-vendor fulfillment queue grouped by WooCommerce status. Point it at withdrawals and finance works Requested left to right, dragging each request into Approved as the payout clears. Cards can show shop name, payout method, requested amount, customer, order total, and the date each record was created.

Dragging a withdrawal request from Requested to Approved calls the same WCFM API the admin uses, which updates the row, deducts the vendor balance, and fires WCFM's notification system so the vendor's dashboard reflects the change immediately. Vendor approvals activate the seller dashboard. Sub order status changes fire the standard woocommerce_order_status_changed hook so any WooCommerce integration listening for status updates reacts normally.

WCFM Marketplace shares the same fundamental challenge any multivendor platform faces: it stitches together three separate businesses behind one storefront. There is the vendor signup funnel, the fulfillment operation that runs per vendor, and the finance department that processes payout batches every week. The default WCFM admin offers a screen per concern, and each screen is a list.

That fits a marketplace with a dozen vendors. It stops fitting the moment vendor counts and order volumes scale up, because the operations team starts switching tabs constantly and losing track of which queue they were working. Vendor applications go cold for a week before anyone notices.

Payout batches get processed at the bank but never marked Approved in WCFM, so vendor balances drift. A single vendor's sub orders cluster in Processing because nobody happened to look at that vendor's queue today. A board per source fixes the shape of the work.

Vendor approvals become a single column to drain. Withdrawals become a single column to clear weekly. Sub orders become a vendor-scoped board the support team pulls up per ticket.

The data stays in WCFM exactly where it belongs.