Every WooCommerce store sends the same nine emails, in the same grey box, with the same borrowed logo at the top. They are the messages customers are most certain to open, and in most shops they are the only part of the brand nobody has looked at since launch.
Which emails WooCommerce sends and what each one is for
Nine templates ship with the plugin, and they split into two groups that deserve very different treatment.
Three go to the shop: a new order notification, a cancelled order notice and a failed order notice. Their job is speed of comprehension, not design. Whoever reads them is usually standing up, on a phone, trying to establish whether something needs doing in the next ten minutes, and anything that delays that answer is a cost.
Six go to the customer: the order on hold, processing, completed, refunded, the invoice or payment request, and the new account email. These are the brand ones. The completed email in particular gets opened by almost everybody, often more than once, because it is the receipt people go back to when they want the tracking link.
The new account email is the one worth checking today, since in a default install it tells a human being that their account has been created and then says almost nothing else useful.
What to change first
Start with the processing and completed emails, because between them they account for most of the opens in the whole store.
What they need is not decoration. They need the thing the customer came for to be visible without scrolling, which usually means the tracking information, the delivery estimate and what to do if something is wrong. Everything else can sit below that, including the logo.
The failed order email deserves a second look as well, though for a different reason. In a default install it is sent to the shop and not to the customer, which means a person whose payment failed receives nothing at all and quietly assumes the order went through. That single gap produces more support tickets than any styling decision ever will. There is a walkthrough of the related case in our guide to pending payment notifications.
Replacing a template rather than editing it
There are two ways to change these emails and they age very differently. Overriding the template file in a theme works, and it keeps working until WooCommerce changes the template, at which point the store is silently running a version that is several releases behind. Most shops discover this during an update.
The alternative is to turn the default off and send your own on the same event. The message then lives outside the theme, survives both plugin and theme updates, and can do things the template cannot, such as waiting, checking what was ordered, or going to a different address depending on the country. Our guide to custom emails in WooCommerce covers the switch.
Replacing a default means catching the same order status change and sending your own message instead. ShopMagic has an event for every WooCommerce status, so a replaced email keeps the original trigger while living outside the theme.
Summary
WooCommerce ships nine email templates that fall into two groups. Three are internal, covering new, cancelled and failed orders, and they are read quickly by somebody deciding whether to act, so clarity beats design. Six go to the customer, covering on hold, processing, completed, refunded, invoice and new account, and these are the brand-carrying ones. The completed email is opened most often, because it is the receipt customers return to for the tracking link.
Processing and completed are worth changing first, and what they need is the useful content above the fold, meaning tracking, a delivery estimate and what to do when something is wrong, with the logo below it. The failed order email needs attention for a different reason: by default it goes to the shop and not to the customer, so somebody whose payment failed hears nothing and assumes the order went through, which generates more support work than any styling choice. On method, overriding the template in a theme works until WooCommerce changes that template and the store is left running an outdated copy. Turning the default off and sending your own on the same event survives updates and can also wait, check the order and vary by country.
Frequently asked questions
These three come up when a store takes over its transactional email.
Will turning off a default email break anything?
Not in itself, as long as something replaces it. The risk is turning one off and forgetting to build the replacement, which is worth checking with a test order.
Can the same email go to the customer and the shop?
It can, though it rarely should. The two readers want different things, and an email written for both usually serves neither.
Do custom order emails affect deliverability?
The content does not, but the sending address does. Keep the from address on a domain that is properly authenticated, whichever system builds the message.
