WP Affiliate Manager (from Tips and Tricks HQ) tracks affiliates, referral transactions, paid payouts and click counts in its own tables (wp_affiliates_tbl, wp_affiliates_transactions_tbl, wp_affiliates_payouts_tbl, wp_affiliates_visits_tbl and related). The default admin shows a list per table with a few static summary stats up top: total affiliates, total commissions, paid and unpaid amounts. It does the basics well and stops short of letting you combine those into one filterable cohort with partner, status, amount and payout date together on one screen.

SleekView reads those tables together and joins transactions with affiliates and payouts so each row pulls from the right columns. A referrals view exposes txn_id, affiliate name, amount, status and txn_date in one row, sortable by any column and filterable in combinations the default admin doesn't surface. A payout queue view filters to unpaid transactions, sums the amount column for the next cycle and lets a payout admin bulk-flip them to paid after the actual transfer.

Inline status edits route through WP Affiliate Manager's CRUD layer where supported, so referral-paid and referral-rejected hooks keep firing for downstream notification emails and integrations like the WooCommerce and PayPal add-ons.

WP Affiliate Manager already records the full picture: who referred whom, which transactions paid, who got the commission and which ones got rejected. The default admin shows that picture as separate row lists with a few static summary stats up top, which is fine for spot checks and unhelpful for almost every cross-cutting question a program owner asks. A table that joins transactions with affiliates and payouts turns three screens into one workspace, where filters combine status, partner and date in a single click and bulk-mark-paid happens in one pass instead of one referral at a time.

Same WP Affiliate Manager tables, same status flags, completely different operational posture. The table renders the data the plugin already maintains as a queryable, editable surface, which is the difference between checking three admin screens and running the program from one.