How to let existing WordPress users purchase additional subscriptions

WordPress subscription forms can fail when they treat every purchase as a new account registration. In this case, customers with existing accounts received the error “That email is already registered.” when they tried to buy another subscription or an individual copy. The fix allowed existing users to complete additional purchases, added mailing-address fields for physical fulfillment, and preserved legacy PayPal renewals based on each subscriber’s original billing date.

Issue background

A WordPress publication site offered recurring subscriptions, gift subscriptions, and individual physical copies. After launch, several problems appeared on the subscription page:

• The forms did not collect a mailing address for physical products.
• Customers with existing WordPress accounts could not complete another purchase.
• The checkout returned the message “That email is already registered.”
• There was uncertainty about how existing PayPal subscriptions would renew after the website relaunch.

The site needed to support customers who might hold more than one subscription, including a personal subscription and a gift subscription under the same account.

Diagnosis

The duplicate-email error showed that the purchase workflow was attempting to create a new WordPress user every time the form was submitted.

That approach worked for a first-time customer but failed when the submitted email already belonged to an account. The purchase and registration steps were too tightly coupled.

The correct business rule was that one account could own multiple subscriptions. A new purchase should therefore attach to the authenticated or existing customer rather than attempt to replace the account or create another user with the same email address.

The missing mailing-address fields were a separate form-configuration issue. Because the subscriptions and individual copies involved physical delivery, the forms needed to collect the information required for fulfillment.

The legacy subscriptions were managed through PayPal rather than through the rebuilt website. As long as those subscriptions remained active in the customer’s PayPal account, renewals would continue on the anniversary of the original registration date rather than receiving an extra year because of the relaunch.

Resolution steps

1. Map the available purchase paths. Identify first-time subscriptions, renewals, additional subscriptions, gift subscriptions, and individual-copy purchases.
2. Reproduce the duplicate-email error. Sign in with an existing account and attempt a new purchase using the same email address.
3. Separate registration from purchasing. Create a WordPress account only when the email does not already belong to a user.
4. Attach purchases to existing users. When the submitted email matches an account, use that customer record instead of rejecting the transaction or attempting another registration.
5. Allow multiple subscriptions per account. Store each purchase as its own subscription or order so a personal subscription does not conflict with a gift subscription.
6. Avoid replacing an active subscription automatically. Only upgrade, cancel, or replace an existing subscription when that behavior is explicitly selected and supported by the business rules.
7. Add mailing-address fields. Collect the recipient name, street address, city, region, postal code, and country wherever a physical product will be shipped.
8. Handle gift addresses separately. When the purchaser and recipient differ, store the recipient’s mailing address independently from the account billing details.
9. Validate required fulfillment data. Prevent submission when a physical order is missing the address information needed for delivery.
10. Test both new and existing customers. Complete controlled purchases using a new email address and an email already registered in WordPress.
11. Test multiple purchases on one account. Confirm that an existing customer can hold a personal subscription, a gift subscription, or an individual-copy order without conflicts.
12. Verify the PayPal handoff. Confirm that successful purchases reach the correct PayPal account and that the website records the expected transaction details.
13. Document legacy renewal ownership. Existing PayPal subscriptions should continue according to the recurring-payment schedules stored in PayPal.
14. Deploy through staging first. Review the revised forms and account logic in a non-production environment before applying them to the live site.

A duplicate-email message is often a sign that a checkout flow is treating account creation as mandatory. Existing customers should usually be authenticated or matched to their current account before a new subscription record is created.

Final outcome

The subscription forms were updated with mailing-address fields for physical fulfillment. Existing WordPress users could then purchase additional subscriptions or individual copies without encountering the duplicate-email error.

The workflow also supported multiple subscriptions under one account, which prevented gift subscriptions from replacing a customer’s personal subscription.

The legacy recurring subscriptions remained under PayPal’s control. Customers with active subscriptions from the previous site would continue to be billed on the anniversary of their original sign-up date.

The key lesson is that customer accounts and subscription records should be treated as separate entities. One account may need to own several active purchases, and the checkout should recognize an existing user instead of attempting to register the same email again.

For help fixing WordPress subscription forms, integrating PayPal renewals, or supporting multiple purchases under one customer account, contact Freshy.