WooCommerce Product Vendors turns a single store into a multi-vendor marketplace, with vendors stored as wc_product_vendors_vendor taxonomy terms and orders flagged with vendor meta so each line item knows which vendor it belongs to. Orders still live in the standard WooCommerce orders table with post_status values like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded. The admin list mixes every vendor's orders into one screen, so the marketplace owner has no way to see per-vendor pipeline at a glance.

SleekView Kanban reads the same orders through the WooCommerce REST endpoints, pulls the vendor taxonomy and commission meta with each row, and turns the status column into the natural grouping axis. Each card shows the customer name, the order total, the vendor name, and the commission split. Columns mirror your WooCommerce statuses, so the marketplace owner sees the full pipeline while a per-vendor board gives each vendor exactly the view they need.

Drag a card from Processing to Completed and SleekView writes through the WooCommerce REST endpoints. Vendor meta is preserved, commission calculations run as they always do, and refund drags trigger the standard WooCommerce refund flow. Custom vendor statuses your marketplace uses appear as their own columns automatically, and per-vendor boards let each vendor work their own queue without seeing other vendors' orders.

A multi-vendor marketplace running on WooCommerce Product Vendors is really many small stores stitched into one storefront, each with its own pipeline, its own fulfilment cadence, and its own commission terms. The default WooCommerce admin throws all of that into one giant order list sorted by ID, with the vendor attribution hidden in line-item meta and the commission split on the order edit screen. Marketplace owners cannot tell at a glance which vendor is behind on shipping, which vendor cleared their queue today, or where the bottlenecks are.

Vendors themselves either get full admin access (overkill) or a slimmed-down dashboard that loses context. The board view fixes both problems with one pattern. The marketplace owner gets an aggregate board with vendor on every card.

Each vendor gets a board filtered to their own orders, with the same status axis and the same drag-to-update workflow. Writes go through the WooCommerce REST endpoints so commission calculations behave, refunds flow normally, and every vendor's fulfilment is visible on the same operational surface.