Send through Google Workspace

Grade school

If your work email is from Google, your store can send its emails from that same email account. It’s simple, but there’s a daily limit on how many it can send.

High school

Good for smaller stores that already use Google Workspace. Your storefront’s emails go out from a real Google mailbox, so they also appear in that mailbox’s Sent folder.

Google sets daily sending limits per mailbox. If your store sends a lot, a dedicated sending service such as SendGrid or Brevo is a better fit.

College

The Google mailer sends through the Gmail API with OAuth, not a stored password. It’s in the free WP Mail SMTP plugin; only the “One-Click Setup” shortcut needs Pro. Trade-offs: per-user sending limits, sent copies in the mailbox, and the From address must be that mailbox or an alias you’ve set up in Gmail.

Postgraduate

Using a user mailbox as a transactional transport couples storefront delivery to one account’s lifecycle, quotas and security policy. It’s acceptable at low volume; at scale, a dedicated provider separates transactional reputation from staff mail and removes mailbox quotas from the critical path.

Developer

Transport: Gmail API via OAuth 2.0 authorization-code flow; the plugin stores a refresh token. Google’s per-user sending limits apply (see Gmail sending limits in Google Workspace). Mailer ID: gmail.

Grade school

You make a special “permission slip” in Google that lets your website send email from your account. You never give your password to the website.

High school

1. Sign in to the Google Cloud Console with your Workspace account and create a project for your storefront.
2. Enable the Gmail API for that project.
3. Set up the OAuth consent screen following the WP Mail SMTP guide’s steps for Workspace.
4. Create an OAuth client ID of type Web application, with the authorized redirect URI that WP Mail SMTP shows you.
5. Copy the Client ID and Client Secret straight into WP Mail SMTP. Don’t send them to anyone.

College

The Cloud project owns the OAuth client; the Client Secret identifies your site to Google, and your authorization later grants it permission to send as your mailbox. Keep the project in your organization’s Google account so access survives staff changes, and restrict who can administer it.

Postgraduate

OAuth separates authentication of the application (client credentials) from delegated authority (the user’s consent), and lets you revoke the site’s access without changing any password. Treat the Client Secret like any credential, and prefer a service mailbox such as orders@ over a person’s mailbox as the consenting account.

Developer

Application type: Web application. Redirect URI: the value shown in WP Mail SMTP (the manual guide lists https://connect.wpmailsmtp.com/google/). Scope requested by the plugin: Gmail send. Source: WP Mail SMTP Google mailer.

Grade school

Paste the two codes into your website, press the button to let it send, and send yourself a test.

High school

1. In WP Mail SMTP → Settings, choose the Google / Gmail mailer and paste the Client ID and Client Secret.
2. Save, then click Allow plugin to send emails using your Google account and approve it while signed in as the sending mailbox.
3. Set From Email to that mailbox (or a Gmail alias you’ve already set up) and set your From Name.
4. Send Tools → Email Test to yourself.

College

Google only sends as the authorized mailbox or its configured aliases. To use several aliases across your site, the plugin guide says to leave Force From Email unchecked. Set Reply-To in WooCommerce so replies go to a monitored address.

Postgraduate

The consenting user becomes the effective sender of record. If that user leaves or their account is suspended, storefront email stops. Plan for this by consenting with a service mailbox and documenting who can re-authorize.

Developer

Re-authorization is needed if the refresh token is revoked (for example after an admin reset or security change). Monitor the plugin’s debug events for invalid_grant.

Grade school

Your domain needs Google’s notes, which you probably added when you set up Google email. Make sure the signature (DKIM) is turned on.

High school

Your SPF record should include Google (include:_spf.google.com) — usually done when Workspace was set up. Turn on DKIM in the Google Admin console and add the record it gives you. Keep your DMARC record.

College

Mail sent through the Gmail API leaves from Google’s servers with your domain as the envelope sender, so SPF passes via Google’s include and DKIM passes once you’ve enabled Workspace DKIM signing. That aligns with your From domain for DMARC. No extra sending-service records are needed.

Postgraduate

Because this path reuses your organization’s primary mail infrastructure, storefront traffic shares its reputation with staff mail. Monitor DMARC aggregate reports for alignment and volume after enabling it.

Developer

SPF: v=spf1 include:_spf.google.com ~all merged into your single record. DKIM: Admin console → Apps → Google Workspace → Gmail → Authenticate email; publish the google._domainkey TXT it generates, then start authentication.