AffiliateWP plugin review and common issues

SliceWP uses cookie-based referral tracking. Common tracking failures: (1) the affiliate URL is not using the correct format — verify the referral parameter (?swp_ref=AFFILIATEID) is appended to the destination URL; (2) the customer cleared cookies or uses a private browser that blocks cookies; (3) a purchase completed before the cookie was set (direct checkout bypassing the referral page); (4) a WooCommerce order placed with a cached page that does not trigger SliceWP’s referral hook; (5) verify the SliceWP integration with WooCommerce is enabled in SliceWP → Settings → Integrations.

A white screen or 500 error on the affiliate registration page usually indicates a PHP error. Steps: (1) enable WP_DEBUG in wp-config.php temporarily to see the specific error message; (2) check if another plugin conflicts with SliceWP’s registration page handling — deactivate other plugins to test; (3) verify the Affiliate Area page in SliceWP → Settings → Pages is set to an existing published page with the [slicewp_affiliate_registration] or [slicewp_affiliate_area] shortcode; (4) check PHP version compatibility — SliceWP requires PHP 7.0+.

SliceWP uses Stripe Connect for affiliate payouts. Each affiliate must connect their Stripe account to receive payments. Steps: (1) ensure SliceWP’s Stripe Connect is configured in Settings → Payments → Stripe with your Stripe API keys; (2) affiliates must go to their dashboard and connect their Stripe account via the Connect Stripe button; (3) affiliates without a connected Stripe account cannot receive Stripe payouts — they must connect before you can pay them; (4) verify your Stripe account has the Transfer API capability enabled for making payouts to connected accounts.

Custom per-affiliate commission rates require the Custom Commissions add-on (paid). After installing the add-on, go to SliceWP → Affiliates → [affiliate] → Edit and configure a custom commission rate for that affiliate (overriding the global rate). This allows premium affiliates (high-volume or exclusive partners) to earn a higher percentage than standard affiliates. Without the add-on, all affiliates earn the global commission rate configured in SliceWP → Settings → Commissions.

Affiliate coupon tracking in SliceWP requires the Affiliate Coupons add-on. Once activated, go to SliceWP → Affiliates → [affiliate] and assign or create a WooCommerce coupon for that affiliate. When customers use the affiliate’s coupon code at checkout, the referral is attributed to that affiliate regardless of whether a referral URL was used. This is the preferred tracking method for social media influencers who promote discount codes.

SliceWP is better for small businesses that prioritize simplicity and a polished affiliate experience over maximum configurability. Its clean interface, one-click payouts, and visually impressive affiliate dashboard make it ideal for businesses launching their first affiliate program. AffiliateWP provides more integrations (supporting more WordPress plugins beyond WooCommerce and EDD), more advanced commission structures out of the box, and a larger community. For businesses already in the AffiliateWP ecosystem or needing membership plugin integrations, AffiliateWP is the more complete solution.

SliceWP’s core plugin supports standard single-level affiliate commissions. Multi-level or tiered commission structures (where an affiliate earns commission on referrals made by affiliates they recruited) are not natively supported in SliceWP. AffiliateWP offers an MLM add-on for multi-tier commission structures. For businesses needing genuine multi-level commission structures, AffiliateWP’s more extensive add-on ecosystem is the better choice.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.