✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WC Vendors

SleekView reads WC Vendors applications and commission records directly, groups them by status, and lets staff drag cards between Pending, Approved, Rejected, Due, and Paid columns so every move runs through WC Vendors's standard status update hooks.

♾️ Lifetime License available

SleekView Kanban board for WC Vendors

Why WC Vendors needs a board view

WC Vendors stores vendor applications and commissions in custom tables that sit alongside WooCommerce. Vendors live as users with the vendor role plus a pending or approved flag managed through the WC Vendors approvals screen. Commissions are stored in the pv_commission table with a status field that takes due, paid, and reversed. The default admin offers one screen for vendor approvals and another for commissions, which forces marketplace operators to bounce between them constantly.

SleekView Kanban reads each of these sources directly. Point the board at vendor applications and the Pending column is the approval queue. Approved applicants land in Approved, rejected ones land in Rejected, and the seller dashboard activates immediately on approval. Point the board at commissions and finance works Due left to right, drags each commission row into Paid as the payout clears, and the underlying pv_commission row updates with full hook coverage.

Dragging a commission from Due to Paid calls the same WC Vendors commission update API the admin uses. Vendor notifications fire, commission reports recalculate, and any add-on listening for the commission status change reacts normally. Vendor approvals call the same WC Vendors approval helper, which writes the user meta, fires the welcome email, and unlocks the seller dashboard so the new vendor can start adding products on their next login.

Workflow

Connect WC Vendors and pick the right marketplace board

1

Connect the WC Vendors source

SleekView reads from the WC Vendors approvals table and the pv_commission table. Add filters for date range, vendor, payout method, or amount so each board scopes to today's queue instead of every record across the marketplace's full history.
2

Pick the WC Vendors status column

Vendor applications group by approval status, which maps to Pending, Approved, and Rejected. Commissions group by the pv_commission status field, which maps to Due, Paid, and Reversed. Each board renders one column per native WC Vendors state.
3

Choose what each marketplace card shows

Map fields onto the card front. Vendor cards show shop name, payout method, signup date, and product count. Commission cards show vendor, order ID, commission amount, payout method, and the date the commission was earned, so finance acts without opening detail.
4

Enable drag-and-drop status updates

Turn on writeback and dragging a card calls the matching WC Vendors API: the vendor approval helper or the commission status update. Notifications, payout calls, vendor balance updates, and any commission report hook fire exactly as they would after a manual admin click.

Sample board

Sample WC Vendors commissions board

Native WC Vendors commission statuses with realistic vendor names, payout methods, and amounts showing how finance would work a weekly batch from due into paid in one sitting.
Due
34
Cedar Goods commission on order #2014
PayPal, $128.40 due
Atelier Maja batch from last week
Bank, $612.50 due
BeanBros Coffee commission earned
PayPal, $94.20 due
Paid
212
Lumi Studio paid via PayPal batch
PayPal, $480.00 paid
GraniteWorks bank transfer cleared
Bank, $1,240.00 paid
FernFox monthly invoice paid
Stripe, $820.00 paid
Reversed
6
Tinker Tools order refunded, reversed
PayPal, $48.00 reversed
Maple Lane chargeback recorded
Bank, $312.00 reversed
ShoreLine order cancelled by customer
PayPal, $76.00 reversed
Pending vendor
11
Driftwood Crafts application waiting
Signed up 2 days ago
OakMoss Studio tax form pending
Signed up last week
Halo Print Shop manual review
Signed up yesterday

Comparison

Default WC Vendors admin vs SleekView Kanban

Default WC Vendors admin

  • Separate admin screens for vendor approvals and commission records
  • Bulk approvals or commission updates require checkbox selection and dropdowns
  • No visual sense of how many commissions are still due across the marketplace
  • Reviewing vendor profile, payout method, and earnings requires opening each record
  • Filtering by status reloads each WC Vendors admin screen instead of showing queues

SleekView Kanban

  • Reads from WC Vendors approvals and pv_commission tables directly
  • Drag a card to fire the matching WC Vendors approval or commission status update hook
  • Cards show vendor, payout method, amount, order ID, and earned date for context
  • Two boards from one configuration: vendor approvals and the commission queue
  • Capability checks honor manage_woocommerce and WC Vendors admin capabilities

Features

What SleekView Kanban gives you for WC Vendors

Vendor approval queue

Pending applications cluster in their own column with shop name, payout method, and signup date visible. Approvals call the WC Vendors approval helper, which writes the user meta flag, fires the vendor welcome email, and activates the seller dashboard on next login automatically.

Commission payout batch

Finance works the Due column, drags approved commission rows into Paid as the payout batch clears at the bank or through PayPal Payouts, and the pv_commission table updates with full hook coverage. Vendor notifications fire and commission reports recalculate immediately.

Reversed commission tracking

Refunded orders move their associated commission rows into Reversed automatically when WC Vendors processes the refund. Finance reviews the Reversed column to confirm the vendor balance was adjusted, with the original order ID and reason visible on every card.

Audience

Where a WC Vendors kanban changes marketplace operations

Vendor onboarding triage

Operations works the Pending vendor column daily, dragging genuine applications into Approved and rejecting spam into Rejected. The seller dashboard activates the moment a card lands in Approved, and the welcome email goes out automatically.

Weekly commission payout

Finance opens the commissions board every Friday, reviews Due rows against the bank export, and drags each batch into Paid as the payment processes. Reversed commissions for refunded orders show in their own column for a clean audit trail.

Refund and reversal reconciliation

The Reversed column collects every commission tied to a refunded order. Finance reviews each card against the original order, confirms the vendor balance update, and adds a note for the vendor support team to relay the adjustment to the seller.

The bigger picture

Why WC Vendors needs a board view

Marketplace operations break down at the seam between vendor sign-up, fulfillment, and finance, and WC Vendors is no exception. The default admin gives vendor approvals their own screen and commissions their own screen, which works fine when the marketplace has a handful of vendors but turns into constant tab-switching once volume picks up. Vendor applications go uninspected for days because nobody happens to open that screen.

Commission payouts get processed at the bank, but the underlying pv_commission rows stay marked Due because the staff member who pressed Send forgot to come back and update the marketplace. Refunded orders generate reversed commissions that pile up invisibly. A board per source fixes the shape of the work.

Vendor approvals are a column you actively drain. The Due commission column is a queue with a clear start and a clear finish, and dragging through it both processes the work and updates the database in the same step. Reversed commissions get their own column for review instead of disappearing into a filter dropdown.

The data stays in WC Vendors. The interface finally maps onto the real-life operations of a marketplace team.

Questions

Common questions about SleekView Kanban for WC Vendors

Yes. The board reads from the same database tables that WC Vendors free uses for approvals and commissions, and any additional Pro features like product approval queues, vendor verification, or payouts are available as additional configurable sources or card fields. The setup is identical across both editions.

 

Yes. Dragging a card from Pending to Approved calls the WC Vendors approval helper, which writes the approval meta on the user, fires the vendor welcome email, and the seller dashboard becomes available on the vendor's next login. The transition runs through the same code path as the admin approval.

 

Yes. Saved boards support filters per vendor, per payout method, per date range, or per order. Finance teams typically run separate boards for PayPal batches and bank transfers, while vendor support can pull a board scoped to a single seller during a payout inquiry.

 

Yes. The commission amount on each card reflects the rate WC Vendors stored when the order was created, including per-product or per-vendor overrides. Status changes fire the same hooks that WC Vendors's internal commission rate logic uses, so reports and exports stay consistent.

 

Filters apply at the query level. A typical board scopes to this week's due commissions, this month's paid batches, or a single payout method. Rendered card counts stay manageable even on busy marketplaces, and older commission history remains queryable through dedicated archive boards.

 

Yes. WC Vendors Pro adds a product approval workflow where vendor-submitted products start as Pending. This is available as an additional board source. The configuration mirrors the vendor approval board, with cards showing product title, vendor, price, and submission date for triage.

 

Yes. Every drag runs through current_user_can with the appropriate WC Vendors capability check, which is typically manage_woocommerce for vendor operations. Unauthorized users can drag for personal sorting only, the underlying status does not change, and the card snaps back with a toast.

 

Yes. Every drag writes a note onto the underlying record. Vendor approvals get a note on the vendor user, commission status updates get a note on the pv_commission row, and refund-driven reversals link back to the original order. Each note captures staff name, source, destination, and timestamp.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView