1. The screens looked different on every theme. The default WooCommerce "My Account" form takes its styling from the theme, so on one site it looked fine and on the next it was a mess of misaligned inputs.
2. The user list filled up with fake accounts. WooCommerce creates the account the moment someone submits the form. Bots love that.

I kept fixing these one site at a time. In the end I turned the fix into a plugin: Logvia. It was approved on WordPress.org this week.

What Logvia does

• A login and sign-up popup. Shoppers log in or register without leaving the product or cart page. It also works as a full page at /auth/, and can slide in from the side instead of opening in the centre.
• Email verification before the account exists. New customers get a six-digit code by email. The WordPress user is created only after they type it in.
• Google sign-in, built in. One button, with no extra plugin and no SDK.
• A drag and drop registration form builder. 15 field types, including phone with country code, country and state, dropdowns and dates. Each answer can be saved to the user profile, WooCommerce billing fields or a custom meta key.
• Bot protection. Cloudflare Turnstile or Google reCAPTCHA v2/v3, rate limiting and password rules.
• Theme-independent design. Its own CSS, scoped so the theme can't break it, with an accent colour, corner radius and layout you choose in the settings.

Three decisions I'm happy with

1. Don't create the user until the email is proven

Most "email verification" plugins create the account first and then flag it as unverified. That still leaves you with thousands of junk rows in wp_users.

Logvia keeps a pending registration instead. While the code is pending it stores only a password hash and the form answers, never the plain password. Codes expire, wrong guesses are limited, and only a correct code turns the pending entry into a real WordPress user. Bots that never read the email never become users.

2. Google sign-in with PKCE and a safe default for staff

The Google flow is the standard OAuth 2.0 authorization-code flow with PKCE and a state value stored in a short-lived cookie. No Google JavaScript SDK is loaded on the page, so there are no extra tracking scripts.

One default I care about: administrators, editors and shop managers cannot log in with Google unless the site owner allows it. If a staff member's Google account is ever compromised, it shouldn't hand someone the dashboard.

3. No jQuery, no build step for the store owner

The front end is plain JavaScript. The popup, the phone field with its searchable country list and the password strength meter all work without jQuery. The CSS is scoped and every interactive state is set explicitly, so theme button:hover styles don't bleed into the popup.

What the WordPress.org review taught me

The plugin team's review was strict and fair. The fixes they asked for are worth knowing if you are about to submit your own plugin:

• Check the nonce at the very start of every handler, before reading any other $_POST data. Each action should have its own nonce.
• Escape late, sanitise early. Every value printed to HTML goes through the right esc_* function at the point it is printed.
• Watch the plugin name. Names that start with a trademark ("WooCommerce …", "Google …") are not allowed. Mine became Logvia – Login and Registration with Google Sign-In for WooCommerce.
• Document every external service in the readme: what is sent, when, and links to the service's terms and privacy policy.
• Don't lock features in the free version. A paid add-on is fine, but whatever is in the free plugin has to work fully.

Running the Plugin Check plugin before submitting saved me at least one review round.

Free and Pro

The free plugin is complete on its own and has no trials or locked buttons. Logvia Pro is a separate add-on for stores that need more: file upload and profile photo fields, manual approval for B2B and wholesale customers, "log in to add to cart", password-less sign-up and extra fields on the My Account and Users screens.

Try it

• Free on WordPress.org: https://wordpress.org/plugins/logvia/
• Docs, changelog and Pro: https://sobirov.dev/en/logvia/

In your dashboard, go to Plugins → Add New, search for "Logvia" and activate it. Most stores are set up after the first three steps of the documentation.

If you run a WooCommerce store, I'd really like to hear what works and what doesn't. Leave a comment here or open a thread on the support forum.

I'm Farrukh Sobirov, a WordPress and Next.js developer from Tashkent. More of my work is at sobirov.dev.