The AffiliateWP integration for WooCommerce records each qualifying order as a referral in affiliate_wp_referrals, linked back to affiliate_wp_affiliates and to the originating wc_orders row via the order ID column. The default AffiliateWP admin lists referrals on one screen and affiliates on another, with no joined view that shows the underlying order total, customer, or status.

SleekView reads all three tables and joins them, so a referral-ops view shows referral ID, affiliate name, order total, order status, commission, and approval state in one row. Filter to referrals stuck in pending for more than 14 days and see which affiliates and which order statuses are blocking them. Switch to a view rooted in affiliate_wp_affiliates for an affiliate-roster table with total commissions, unpaid balance, and last referral date.

Inline status updates write through AffiliateWP's CRUD so the affwp_set_referral_status action and the linked payout-balance recalculation still fire. Bulk-approve thirty pending referrals after a chargeback window closes, instead of clicking into each one.

Affiliate programs work when payouts are accurate, predictable, and timely. AffiliateWP's referral table records the commission, the affiliate, and the originating order, but the default admin keeps each of those screens separate. To decide whether to approve a batch of pending referrals, a payout manager needs to know the underlying order's status (was it refunded?), the affiliate's prior dispute history, and the cumulative unpaid balance.

Doing that one referral at a time turns a 15-minute payout cycle into a half-day spreadsheet job. SleekView reads affiliate_wp_referrals and joins wc_orders and affiliate_wp_affiliates on the fly, so the joined context lives on one row. Payout managers bulk-approve clean rows and bulk-reject refunded ones in two filters instead of three exports.

Affiliate managers see who's converting and who's dormant from the roster view. Fraud and risk teams catch refund-after-payout patterns by filtering on the joined order status. The data is already relational.

SleekView just surfaces the relation.