AffiliateWP Force Pending Referrals

Updates for one year, unlimited sites, auto updates, and regular updates.

$3.99

Version 1.2.0 report outdated
Updated on November 11, 2026
Auto Updates Yes
License GPLv2+

Access all items listed on our website. All new releases are also included as long as the plan is active.

Force Pending Referrals puts a deliberate checkpoint in front of every new affiliate referral. Once the add-on is active, AffiliateWP records each new referral as Pending rather than approving it automatically. Nothing counts toward an affiliate’s earnings until an administrator reviews the referral and accepts it. The aim is accuracy: you can keep out referrals that look questionable and catch mistaken ones before they are treated as final.

How referrals are held for review

Activating the add-on sets every new referral to Pending automatically, so there is no configuration to complete. Pending referrals are visible only to site administrators, and they appear in one place: the Referrals screen under AffiliateWP. Each referral offers four actions. You can accept it, reject it, edit it, or delete it. Accepting is what allows a referral to count toward earnings and statistics. Rejecting it removes its effect from earnings and reports, and affiliates never see a rejected referral.

What Pending means in AffiliateWP

AffiliateWP gives every referral one of four statuses. Pending means the referral exists but has not been confirmed. Unpaid means it has been confirmed and is waiting for a payout. Rejected means it has been turned down and will not be paid. Paid means the affiliate has already received payment for it. Pending referrals are left out of earnings totals and conversion figures, and they stay hidden from the affiliate’s dashboard until they are confirmed.

Under the standard flow, a referral usually leaves Pending once the linked order or sign-up is complete. This add-on changes that rhythm by holding every referral until an administrator decides. In practical terms, the approval step becomes a human decision rather than an automatic one, and that is the whole point of the add-on.

Reviewing referrals one by one

Because approval is manual, a consistent routine helps. Open the Referrals screen and work through the pending entries. Check the order or sign-up behind each referral, then decide. Accept a referral that matches a genuine sale. Reject one that looks like a mistake or an unsupported attribution. Use Edit when a referral was captured correctly but its details need a fix, and use Delete only when a referral should never have been recorded in the first place. The documentation does not explain the difference between rejecting and deleting, so agree on a rule with your team before you begin.

Keep a short internal log of your decisions. Over time, that record helps you spot patterns, such as a particular source of questionable referrals or a recurring mistake in how sales are attributed. A log also makes it easier to answer an affiliate who asks why a referral is still pending.

A weekly review routine

  • Set a fixed time each week to clear the Pending queue, so referrals never sit for long.
  • Compare each pending referral with the order or sign-up that produced it before making a decision.
  • Record every accept and reject decision in your internal log.
  • Let affiliates know when their referrals have been confirmed, using your own messages, because the documentation does not describe automatic notifications.
  • Recheck any referral that was edited, to confirm that the corrected details are the ones you intended.

Setting a review policy

Write down the checks that a referral must pass before you accept it. Your policy might ask whether the order exists and matches the referral, whether the affiliate is eligible under your program rules, and whether the sale looks like a genuine customer purchase. Keep the list short enough that reviewers can apply it quickly. When two reviewers would reach different answers on the same referral, refine the wording until the outcome is consistent.

What affiliates see while referrals are pending

Affiliates do not see pending referrals in their dashboards, so their totals will look lower than the number of sales they generated until an administrator accepts the referrals. Set that expectation at the start of your program. A short note in your affiliate onboarding material, explaining that referrals are confirmed by hand before they count, prevents confusion and reduces support questions later.

Reporting and payouts

Pending referrals are kept out of reports, so the reporting view changes as the review queue is cleared. The documentation does not explain how payouts are calculated or made, so check your payout process on a staging copy with a few test referrals. That way you can see exactly which referrals move into your payout run.

Requirements and installation

Force Pending Referrals cannot run unless AffiliateWP is already installed and active. The add-on’s directory page lists AffiliateWP 2.6 or newer, WordPress 5.2 or newer, and PHP 7.4 or newer as requirements. Installation follows the usual pattern for WordPress plugins: place the plugin folder in wp-content/plugins, or search for the plugin name under Plugins, then Add New, and activate it once it is installed. No settings need to be configured after activation.

Things the documentation does not address

Some questions are left open, so it is worth checking them on a staging site first. The documentation does not say whether referrals created before activation are affected by the new pending rule. It does not say whether a rejected referral can be restored later. It does not explain the practical difference between rejecting and deleting a referral, and it does not say whether affiliates are notified when a decision is made. Test each of these before relying on the add-on for a live program.

Version notes

The add-on’s history includes one fix for a specific payment situation. Version 1.1.1 corrected a case in which a referral was not switched to pending after a payment failed at first and then went through. Version 1.1.0 added checks that enforce the minimum versions of AffiliateWP, WordPress, and PHP. The current release, 1.2.0, raised the WordPress minimum to 5.2.

Who should use it

Force Pending Referrals suits programs that prefer manual control over every commission. A new affiliate program, where you do not yet know how partners will promote the store, benefits from a review step while trust is still being built. The add-on also suits businesses that want to check each attribution before a sale is credited to an affiliate. Because approval is always manual, it works best when someone on your team can review referrals promptly.

It also pairs well with the Allow Own Referrals add-on. If you choose to let affiliates earn on their own purchases, holding those referrals in Pending gives you a chance to check each one before it counts.

Preparing the review team

Only site administrators can see pending referrals, so anyone who reviews the queue needs an administrator account. Decide who that will be before you activate the add-on, and make sure at least two people can cover for each other when one is away. A shared expectation about response times helps too, because a referral that sits unreviewed keeps its earnings out of the affiliate’s totals. Delays of that kind are easy to spot on the Referrals screen if you check it on a fixed schedule.

Scaling the workload

Approval cannot be automated with this add-on, so the review effort grows in step with the number of referrals your program generates. A small program may clear its queue in a few minutes a day, while a larger one may need a dedicated routine. Plan for growth early by deciding how many referrals one reviewer can handle in a session, and by checking the queue more often when a campaign launches. If the queue starts to lag, affiliates may ask why their totals have not moved, so the backlog will surface as support questions.

Common mistakes to avoid

  • Do not assume a missing commission is lost; first check the Referrals screen for a pending entry.
  • Do not reject a referral only because it looks unusual; check the order behind it first.
  • Do not ignore referrals that were already in progress when you switched the add-on on, because the documentation does not say how older referrals are handled.
  • Do not assume Delete and Reject do the same thing, because the documentation does not explain the difference.
  • Do not rely on affiliates to flag problems, since they cannot see pending referrals.

Explaining the rule to affiliates

Affiliates will ask how their referrals are confirmed, so write a short explanation they can read in full. Say that every new referral is held until it is reviewed, that held referrals do not appear in their totals, and that the review checks each referral against your program rules. Put the explanation in your affiliate terms and in the onboarding email, so it is available before the first question arrives.

Compatibility note

The plugin’s directory page flags that it has not been tested with the three most recent major WordPress releases. Treat that as a reason to test on a staging copy before any WordPress upgrade, and check the Referrals screen afterwards to confirm that new referrals still arrive in the Pending state.