AffiliateWP Allow Own Referrals

AffiliateWP Allow Own Referrals changes one specific AffiliateWP rule: affiliates can receive commission when they buy through their own referral link or use their own coupon code. It is aimed at programmes that want affiliates to benefit from their own promotions rather than treating every self-referred purchase as invalid.

Changing self-referrals

AffiliateWP blocks self-referrals by default. This add-on lifts that restriction and applies the change to both of the routes named in the vendor description: referral links and coupon codes. That gives programme owners a clear way to support affiliates who purchase products while actively promoting them.

The appeal is straightforward. An affiliate can place an order through their own tracked link or code and still earn the associated commission. For programmes where affiliates buy products to use, demonstrate, or promote, that keeps the purchase inside the normal commission model instead of treating it as an automatic exception.

What it handles

The feature set is focused rather than broad. The vendor lists support for the payment gateways and commission structures supported by AffiliateWP, so the add-on is designed to work within the existing AffiliateWP setup rather than introducing a separate payment or commission system.

• Allows commission on an affiliate’s own purchases.
• Works with referral links and coupon codes.
• Uses a simple toggle to enable or disable the behaviour.
• Supports AffiliateWP-supported payment gateways.
• Supports AffiliateWP-supported commission structures.

That narrow scope is useful for administrators who want one policy change without adding another layer of affiliate management. The vendor also positions it as requiring no coding knowledge, which suits site owners who prefer a setting-based change.

A small control surface

The toggle is the main control described for the add-on. It allows the policy to be enabled or disabled without disrupting the broader AffiliateWP workflow. This makes the decision easy to reverse when a campaign, product line, or affiliate arrangement no longer calls for self-referrals.

There is also a practical distinction between the two supported tracking methods. A programme that distributes coupon codes can apply the same self-referral policy to code-based purchases as it does to link-based purchases, rather than requiring affiliates to use one particular tracking route.

Where it falls short

The first trade-off is financial: allowing self-referrals increases the number of purchases that qualify for commission. That can raise programme costs and reduce the distinction between an affiliate sale and an affiliate’s own order, so the setting deserves a clear policy before it is enabled.

The second limitation is control depth. The supplied feature list describes a single enable-or-disable toggle, not rules for selected affiliates, products, order types, or commission rates. Programmes that need exceptions at that level will find the decision broader than they want. The add-on also depends on AffiliateWP for its supported gateways and commission structures, so it is not a replacement for that system.

Who it suits

This is a focused fit for AffiliateWP administrators who deliberately want affiliates to earn on their own purchases. It makes sense for programmes where personal buying is part of promotion and where a single setting is enough to define the policy. It is less suited to programmes that regard every self-purchase as a cost to exclude or need detailed eligibility rules for different affiliates and products.