New buyers skip your upsells, and nothing shows an error
On a client’s membership, about 1 in 9 new buyers went straight from paying to the thank-you page. No error, no complaint, and nobody charged twice. Just offers that never appeared.
The members site was sending a different password back to the main site about 12 seconds after checkout, which logged the buyer out in the middle of the offers. Syncing the Customer role in WP Fusion, plus a one-hour safety net, stopped it. Then re-test every access automation, because a fix like this changes what they see.

How the two sites hand a buyer over
The client sells on one WordPress site and teaches on another: a main site with the checkout, and a separate members site with the courses and the community. Here is what happens in the first minute after someone pays.
- 1
The buyer pays on the main site
WooCommerce creates their account and logs them in. FunnelKit runs the checkout and then shows the one-click offers: extras the buyer can add without typing their card again.
- 2
WP Fusion tells FluentCRM
WP Fusion keeps WordPress accounts and the contact list in step. It adds the product’s tags to the buyer’s contact in FluentCRM. A tag is a label on a contact.
- 3
A tag starts an automation
In FluentCRM, an automation is a list of steps. Here: create the buyer’s account on the members site, wait, then send the login email.
- 4
The members site reads the tags
It also runs WP Fusion, connected to the same contact list, and uses the tags to decide which courses and spaces the buyer can open. WP Fusion keeps one password for both sites.
All of this happens while the buyer is still clicking through the offers. Almost every problem in this guide comes from that overlap.
Why new buyers skipped the offers
It only happened to buyers who weren’t contacts yet. This is the chain we found:
- The main site creates the account and logs the buyer in
- A few seconds later, the members site creates its own account for them, with its own password
- About 12 seconds after checkout, that password is copied back to the main site
- Changing a password in WordPress logs that person out
- The next one-click offer refuses a logged-out visitor, so the buyer lands on the thank-you page
In FunnelKit’s log, those refused clicks show as “403”, which means “not allowed”. Returning buyers were fine, because their password was already on their contact.
What we changed
Sync the Customer role
WP Fusion can be told to sync only some user roles. On this site the list left out Customer, the role WooCommerce gives a new buyer. So a new customer’s password never reached the contact, and the members site made up its own. With Customer added, both sites agree on the password from the first second.
A safety net for the first hour
We added a small must-use plugin (a file WordPress always loads) to the main site. For the first hour after a signup or an order, it ignores a different password coming back from the CRM. A late sync can no longer log a buyer out halfway through the offers.
How we know it worked. Eight test orders across four funnels showed every offer. Refused upsell clicks in FunnelKit’s log stopped the day after the change, and a real buyer then accepted and paid for an offer.
What the fix broke, and why you re-test everything
One product’s login automation only created the members account when the contact had no password yet. Before the fix, a new customer never had one at that point, so the step always ran. After the fix, every new customer already had a password, so the automation skipped creating the account. One buyer sat on a waiting screen for about 18 minutes until someone added their tag by hand.
We removed the “password is empty” check. The automation now always creates the account first, then waits, then sends the login email.
We also tried checking an “account created” tag instead, and dropped it. That tag was added at purchase, about 11 seconds before the members account existed, so it couldn’t mean “the account exists”.
The lesson: an automation that asks “does this contact have a password?” depends on the order things happen in. Change that order and the answer flips. After any change to what WP Fusion syncs, test every product’s access automation, not only the one you were fixing.
Buyers who had unsubscribed got no access
By default, a FluentCRM automation doesn’t run for a contact whose status is “unsubscribed”. So a buyer who had once left the mailing list paid, and then nothing happened: no members account, no login email.
The fix is one box in the automation’s settings: “Run the automation actions even if the contact status is not subscribed”. Tick it on the automations that give access. Leave it off on marketing automations.
One thing the box doesn’t do: it won’t go back and run the automation for contacts who were held back before you ticked it. We found older contacts still waiting as “pending” in access automations that had never run for them. Look for those and deal with them on their own.
Login emails that arrived up to 15 minutes late
FunnelKit can add accepted upsells to the buyer’s first order. To do that, it keeps the first order in a temporary status, “Primary Order Accepted”, until the buyer has finished with the offers, or for 15 minutes if they leave the page open.
WP Fusion added the product’s tags only once the order left that status. So the tags, the automation and the login email all waited. On a typical day, more than 9 in 10 first orders sat in that status.
The client’s main funnel was switched so that each accepted upsell becomes its own order. The first order then completes straight away, and WP Fusion acts about 10 seconds after payment. In the three days after the change, not one order on that funnel waited. Their smaller funnels were still on the old setting when we wrote this.
WP Fusion also has an option to act when an order reaches “Primary Order Accepted”. We haven’t tested it, so treat it as something to try on a copy of your site, not a fix we can vouch for.
Two of the login automations still start with a one-minute wait on purpose, so the account exists before the login is sent. Their email takes 2 to 3.5 minutes. That’s by design, not a fault.
Check your own site
None of these showed an error. Run through the list on a copy of your site, with a test order as a brand-new buyer.
- Which user roles does WP Fusion sync? Is Customer in the list?
- Does anything change a buyer’s password in the first minute after checkout?
- Does every access automation still create the account when the contact already has a password?
- Is “run even if not subscribed” ticked on the automations that give access, and only on those?
- Do your funnels add accepted upsells to the first order? If so, what waits for that order to complete?
- When you count upsells, are you counting the ones added to the first order too?
The times in this guide come from our own test orders on the client’s live sites in November 2026.
Questions owners ask
Was anyone charged twice, or charged for an offer they didn’t see?
No. The buyers who skipped the offers paid for their first order and nothing else. The cost was the offers they never saw, which is why nobody noticed for a while.
I only have one site. Can this still happen to me?
The cause we found needs something to change the buyer’s password in the minute after checkout. Here it was a second site sending its own password back. On one site, check whether any plugin sets or resets a password after signup. If nothing does, this cause doesn’t apply to you.
Will the “not subscribed” box send marketing emails to people who unsubscribed?
The box lets every step in that automation run for that contact. So tick it only on the automations that give access and send login details, and keep marketing emails out of those automations.
How can I tell if my new buyers are skipping offers?
Look in FunnelKit’s log for upsell clicks that were refused, and compare new buyers with returning ones. Don’t judge it by your upsell rate alone: if accepted upsells are added to the first order, a simple count of upsell orders misses them.
Should I stop adding upsells to the first order?
If anything waits for the first order to complete, such as tags, access or a login email, it’s worth a look. Giving each accepted upsell its own order ended the wait on our client’s site. WP Fusion also has an option to act on the “Primary Order Accepted” status, which we haven’t tested.
