Email Verification

In this guide

Explore the steps and reference sections below.

Start reading

On this page

Require newly registered users to verify their email address before signing in. With Pro, you can instead review accounts manually, enforce verification at logged-in checkout, and manage pending users.

Before you start

• Enable Email Verification in Swift Commerce → Customers → Email Verification.
• Confirm that WordPress registration or WooCommerce My Account registration is enabled for the form you intend to protect.
• Send a test registration using an address you control. Your site must be able to deliver WordPress email for link verification to work.

Settings: choose registration forms

Turn on WordPress Registration for the default WordPress registration form and/or WooCommerce My Account for WooCommerce account registration. Save Changes after selecting your surfaces.

If Swift Commerce Registration Form is enabled on the same form, Registration Form controls fields lets that feature supply its field order and custom fields. Turn it off to use Email Verification’s default password setup fields. New users create a password during registration, so their account is ready after verification or approval.

Role exemptions

Expand Role exemptions to exempt selected existing WordPress/WooCommerce roles. This checks the role assigned after registration; it does not assign a role. WordPress commonly assigns Subscriber and WooCommerce commonly assigns Customer. Exempting either may let public registrations bypass verification, so leave them unchecked if those accounts must verify.

Verification Email

Open the Verification Email tab to edit the message and shared email design, preview desktop and mobile, and send a test. Keep the {{verification_link}} placeholder in the email so recipients can complete verification. The subject and message can also use {{user_name}}, {{user_email}}, {{site_name}}, {{site_url}}, and {{expiry_time}} where appropriate. Save editor changes and test delivery before inviting customers.

Advanced (Pro)

Verification mode

Choose Email Verification to send a self-service verification link, or Admin Approval to hold new accounts until a site administrator approves them. In approval mode, review the pending, approved, administrator-notification, and rejected-account email templates in the email editor.

Checkout enforcement

Enable Logged-in Checkout to require tracked, unverified users to complete verification before placing an order. This setting applies to classic WooCommerce checkout and Checkout Blocks. It is separate from choosing which registration forms to protect.

Links, resends, and retention

• Verification Link Expiry: 1, 3, 6, 12, 24, 48, or 72 hours. Expired links require a new verification message.
• Administrative Resend Limit: unlimited, 3, 5, or 10 resends. This limits resends from the administrative workflow.
• Auto-delete Unverified Users: Never, 24/48/72 hours, or 7/14/30 days. Deletion removes the WordPress account; use this only after choosing a retention period appropriate for your store.
• Redirect After Verification: an optional same-site URL. Leave it empty to send users to the account login page.

Pending Users (Pro)

Use Pending Users to search and review accounts awaiting verification or approval. In link mode, you can resend a verification email or mark a user verified. In the current Registration & Access workflow, review each registration to approve or reject it. Rejection retains the account with access restricted; it does not delete the WordPress user. Reopen for review returns a rejected account to pending approval without granting access. See the linked current guide for the updated review controls.

If the list fails to load, use its Retry action. Do not infer that an empty list means there are no pending users when the dashboard reports an error.

Check the customer experience

• Register a test account on each protected form. Confirm the password field appears, the correct email arrives, and the account cannot sign in before verification or approval.
• Follow the link—or approve the user in Pending Users—and confirm sign-in succeeds. If checkout enforcement is on, also test a logged-in unverified account at your active checkout type.
• Verify that any exempt roles and the Registration Form field-source setting behave as intended.

Free and Pro

Free: registration-form verification, the verification email, and role exemptions. Pro: manual approval, logged-in checkout enforcement, link/resend/retention controls, redirect after verification, and the Pending Users management workflow.