SliceWP stores every commission in the wp_slicewp_commissions table. Each row carries an affiliate_id linking to the affiliate user, a reference_id linking to the related order, an amount value, a currency, a status column with values pending, unpaid, paid, and rejected, plus timestamps for date_created and date_modified. The plugin's commissions screen shows everything as a sortable table, which is fine for a small affiliate program but blind to the live approval workflow a growing program really needs.

SleekView Kanban reads the same wp_slicewp_commissions rows you would query with slicewp_get_commissions. Pick status as the group column and every commission becomes a card slotted under Pending, Unpaid, Paid, or Rejected. Card fronts show the affiliate name from wp_users, the related order reference, the commission amount in the store currency, the date created, and the commission rate, so the affiliate manager sees every commission's context without leaving the board.

Dragging a card between columns calls the SliceWP helper for updating commission status, which writes back to wp_slicewp_commissions.status and fires the slicewp_update_commission_status action. The affiliate's running totals on their profile recompute, payout calculations refresh, and any extension listening for status changes reacts, exactly as it would after a manual update from the SliceWP commissions admin screen by a manager.

Affiliate programs running SliceWP often handle hundreds of commissions every month. Some are clean conversions that should be approved as soon as the refund window closes. Some are flagged for review because the order was unusually high value or came from a new affiliate.

Some are reversed by refunds and need to be marked rejected before the next payout batch runs. The default commissions list treats them all the same, which means the program manager runs SQL queries to find anything beyond the most basic filter and finance keeps a spreadsheet of which commissions are approved versus pending. The disconnect between the program data and the finance workflow shows up in the worst places.

A pending commission sits unreviewed for weeks because nobody noticed it. A rejected commission stays in Pending and accidentally gets included in the payout batch. A high-value affiliate complains about a missing payout because three of their commissions are stuck in Pending.

A kanban view that reads and writes the same wp_slicewp_commissions rows the affiliate dashboard reads keeps the program manager and the books honest. Every drag is a real status change, every column count reflects the real approval pipeline, and the cards themselves carry enough context for a new program manager to handle approvals on day one of the job.