WooCommerce: "An Account Is Already Registered With Your Email Address"

If customers hit "An account is already registered with your email address. Please log in." and can't get past checkout, WooCommerce is refusing the order because that email belongs to a user and your store won't take orders from guests. Here's how to confirm that and unblock it.

Last updated: 16 Jul 2026 · ~6 min read

What this message actually means

WooCommerce checks the billing email at checkout against your WordPress user list. If it finds a match and the shopper isn't logged in, it has two options: let them buy as a guest, or stop them. Guest checkout switched off removes the first option, so it stops them.

The customer reads it as "you already have an account" — which is often news to them, because WooCommerce may have created one silently on a previous order. From your side it's usually invisible: no failed order, no error log, just a checkout that quietly doesn't convert.

The most common causes (most likely first)

1. Guest checkout is switched offWooCommerce → Settings → Accounts & Privacy → "Allow customers to place orders without an account" is unticked. Tell: the message appears the instant a returning customer types their email, on every browser, every device. The overwhelmingly likely cause.
2. They really do have an account and don't know it"Allow customers to create an account when placing an order" is on, so their first order made them a user. They have never set a password. Tell: the email exists under Users in wp-admin with a registration date matching an old order.
3. An orphaned WordPress user holds the emailA newsletter import, a contact-form plugin, a membership import or an abandoned registration created a user they never asked for. Tell: the user exists under Users but has no orders against it at all.
4. They are logged in, but checkout doesn't know itA cached checkout page or a lost session makes WooCommerce treat a logged-in customer as a guest — then block them on their own email. Tell: it only happens to logged-out-looking sessions, and a hard refresh or incognito window changes the behaviour.
5. A membership or force-login plugin is requiring accountsGuest checkout is ticked on, but a memberships, wholesale or "force login" plugin still demands a user. Tell: the setting is correct and the message persists, but stops when that plugin is deactivated.

Where to look first

• Open WooCommerce → Settings → Accounts & Privacy. Is "Allow customers to place orders without an account" unticked? Tick it, save, and retest — that's cause 1 and it's the fix for most stores.
• Check Users in wp-admin for the customer's email. Does it exist? Then the message is technically true — the question is only whether they should have to log in (cause 2 or 3).
• Does that user have any orders? No orders at all means it's an orphaned user from an import or a form plugin (cause 3), not a real customer account.
• Also check "Allow customers to log into an existing account during checkout" in the same screen. With that off and guest checkout off, a returning customer is stuck with no way through at all.
• Setting already correct and it still blocks? Deactivate memberships/force-login plugins one at a time (cause 5), or test in an incognito window to rule out a cached session (cause 4).

How to know you fixed it

Frequently asked