Solid Affiliate stores every referral in the wp_solid_affiliate_referrals table. Each row carries an affiliate_id linking to the affiliate, a reference column linking to the related order, an amount in the store currency, a status column with values pending, unpaid, paid, and rejected, plus timestamps for created_at and updated_at. Solid Affiliate's referrals screen shows everything in a flat table, which is fine for a small program but blind to the live approval workflow a growing program needs.

SleekView Kanban reads the same wp_solid_affiliate_referrals rows directly. Pick status as the group column and every referral becomes a card slotted under Pending, Unpaid, Paid, or Rejected. Card fronts show the affiliate name from wp_users, the related order reference, the referral amount in store currency, the date created, and the commission rate, so the affiliate manager sees every referral's context without opening the detail screen for any single referral row.

Dragging a card between columns calls the Solid Affiliate helper for updating referral status, which writes back to wp_solid_affiliate_referrals.status and fires the matching status change hook. 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 Solid Affiliate admin screen via the program manager.

Affiliate programs running Solid Affiliate often handle hundreds of referrals 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 referrals list treats them all the same, which means the program manager runs queries to find anything beyond the most basic filter and finance keeps a spreadsheet of which referrals are approved versus pending. The disconnect between the program data and the finance workflow shows up in the worst places.

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

A kanban view that reads and writes the same wp_solid_affiliate_referrals 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.