Making Sure Your Store's Order Emails Actually Send Print

The problem

Your store takes an order, and the confirmation email never arrives. Or it arrives in the customer's spam folder. Or your own new-order notification never reaches you, so you miss sales. This is one of the most common frustrations with any online store, on ThirtyBees, WooCommerce, or anything else, and the cause is almost always the same underlying thing.

Why it happens

By default, store platforms send email using the server's basic built-in mail function, often called PHP mail. It works, in the narrow sense that the message leaves the server. The problem is what happens next: mail sent this way frequently fails the authentication checks that Gmail, Outlook, and every other modern mail provider now apply, so it gets marked as spam or quietly discarded.

The mail is technically being sent. It is simply not being trusted, and untrusted mail does not reach inboxes. Your store looks like it is working, while your customers wonder why they heard nothing.

The fix: send through proper SMTP

The solution is to stop using basic PHP mail and send your store's email through a proper authenticated SMTP connection instead, the same trustworthy method a real mail program uses. Sent this way, your order emails carry the authentication that lets them pass the checks and land in inboxes rather than spam.

• On ThirtyBees, we install a PHP mailer module and configure it to send through a proper SMTP service, which is part of how we set up a store correctly.
• On WooCommerce, we recommend exactly the same approach, an SMTP plugin configured to authenticate properly rather than relying on the built-in function.

Either way, the store sends its mail through a real mailbox with real authentication, and deliverability stops being a mystery.

The other half: authenticate your domain

SMTP gets your store's mail sent properly. Making sure it is trusted also depends on your domain being set up to vouch for it, through the SPF, DKIM, and DMARC records covered in our article on why email lands in spam. A store sending through authenticated SMTP from a domain with proper email records is mail that arrives. Miss either half and you are back to the spam folder.

What you can do, and where we help

This is self-doable. The SMTP plugins and modules exist, and a confident store owner can install and configure them by following the documentation. What trips people up is the configuration detail, the right ports and settings, a working mailbox to send through, and the domain records lining up behind it, which our email settings and ports quick reference lays out.

Where we come in is certainty. If we install and configure your store, correct email sending is part of the job, done and tested, so the first order confirmation is not the first time you discover whether it works. If your store is already live and its emails are misbehaving, open a support ticket and we will sort the sending out for you.

Good to know

Test this deliberately before you open, and test it properly: place a real order and confirm the email arrives in a normal inbox, a Gmail or Outlook account, not just your own domain's mailbox, and check it is in the inbox rather than spam. Order emails are not a nicety, they are how customers know their money reached you and how you know to fulfil the order. A store whose confirmations land reliably looks professional, and one whose emails vanish loses trust on the very first transaction, which is the worst possible moment to lose it.