WooCommerce email templates: edit, test and deliver

Edit WooCommerce email templates around the actual order event and required fields, then verify the customer message, attachments and failed delivery.

Edit WooCommerce email templates by choosing the order event first, keeping its live order fields and testing the message in a customer inbox. Use the built-in settings for routine wording and branding. Choose a visual customiser when you need more control over the layout or supported extension fields.

A transactional email explains something that happened to an order or account. Its subject and payment wording must agree with that event. A newsletter or campaign builder has a different job and does not replace these notifications.

Choose the event and editing method

Choose the notification that corresponds to the fact you need to communicate. New order is a merchant alert. Processing order is the customer notification after payment. Completed order follows the Completed status, which usually means the order has shipped. A refund needs the refund notification and its actual amounts.

Start in WooCommerce > Settings > Emails. Open Manage for the relevant notification and inspect its recipient behaviour before changing its text. WooCommerce’s email settings documentation explains the individual controls.

Match the editor to the change

MethodSuitable changeEntitlement and upkeep
Built-in WooCommerce settingsSender identity, shared branding and each notification’s subject or additional contentIncluded in core. Available appearance controls depend on the installed version and Email improvements setting.
YayMail FreeVisual editing of supported default WooCommerce emailsFree edition. Keep the order elements and confirm that your specific notification appears in its editor.
YayMail ProDynamic blocks and supported third-party fieldsPaid edition. Third-party extensions’ own email templates can require a separate add-on.
WooCommerce Block Email EditorEditing a block-based transactional template on a store using that systemDocumented as alpha. Treat it as a separate template system and test compatibility on an isolated store.

YayMail is a visual editor for WooCommerce transactional emails. Its Free and Pro editions both edit email content and design. The vendor’s comparison distinguishes Pro support for third-party variables from separate add-ons for third-party email templates. Buying Pro does not establish that every extension’s email is covered.

Use core settings when the existing order table already supplies the required facts. Choose YayMail for a layout change that those settings cannot make. This guide’s main procedure uses core settings, with a separate YayMail route where layout control is needed.

  1. Record the installed WooCommerce version, active email editor and any template overrides. Prepare an isolated store with test inboxes and fictional orders. Keep live customer sending and fulfilment disconnected.
  2. Save the current design before editing. For core settings, record the existing values. For YayMail, export the templates through its supported settings.
  3. Edit one notification. Save it and check its content before applying shared design changes to the other messages.

Build the message from order facts

Build each message around the saved order’s item lines and payment state. Keep dynamic fields dynamic so the next customer receives their own purchase details.

For this fictional example, Cedar Linen sells two Navy cotton napkins at $22 each, plus $11 standard delivery. Assume those amounts include a configured 10% tax, giving a $55 total with $5 tax. The business name, product and amounts below are illustrative.

Use this wording for the paid Processing order notification, with the order table supplying the changing values.

We’ve received payment for order 1042.

Cotton napkin, Navy, quantity 2: $44. Standard delivery: $11. Total paid: $55, including $5 tax.

Delivery is to the shipping address shown in your order details. We’ll email you when your order is dispatched.

For help, reply to this email and quote order 1042. Cedar Linen support: support@cedar-linen.example.

Only promise a dispatch email if your store sends it when dispatch is recorded. The order confirmation email guide explains the customer information that belongs in a confirmation.

Changed status after dispatch

For the Completed order notification, use dispatch wording only when your team sets Completed after dispatch. Keep the actual shipping address and order summary in the message.

Order 1042 has been dispatched by standard delivery.

Cotton napkin, Navy, quantity 2: $44. Delivery: $11. Your order total is $55, including $5 tax.

For delivery questions, reply to this email and quote order 1042. Cedar Linen support: support@cedar-linen.example.

A tracking link belongs here only if the fulfilment system supplies one for this shipment. A status change alone does not create a carrier tracking number.

Partial-refund exception

Suppose the customer returns one napkin after delivery. Refund that item for $22, including $2 tax, and leave the original shipping charge unchanged in this example.

We’ve issued a partial refund of $22 for one Navy cotton napkin from order 1042. The refund includes $2 tax.

Your original order was $55, including standard delivery. We’ve refunded $22 and retained $33. The delivery charge is unchanged.

For help with this refund, reply to this email and quote order 1042. Cedar Linen support: support@cedar-linen.example.

Use “issued” only after the refund method has processed the refund. WooCommerce’s refund instructions distinguish automatic refunds from manual records that need a separate return of funds. A partial refund does not automatically change the whole order to Refunded.

Add post-purchase content safely

  1. In the core notification’s Manage screen, use Additional content for a short instruction, such as how to contact the store. Use the supported {order_number} variable where you need the order reference.
  2. Keep the generated order table and addresses. Static text must not replace the customer’s changing totals or imply that every order has paid.
  3. If using YayMail, select the notification and a fictional order in its builder. Preserve the Order Items element and the address elements your message needs. Add explanatory text beside them, using the editor’s supported variables.
  4. Save and send a test message. Then trigger the real event on the isolated store to test the notification itself.

A design editor changes an existing message. YayMail’s documentation says it does not create new custom emails by itself. A separate post-purchase event needs an automation or extension that actually generates that notification, with an editor integration for its template.

Check template and extension compatibility

Check the template system that sends the message, not just the editor you last opened. A PHP template override, a visual customiser and a block email template have different owners.

  1. Inspect WooCommerce > Status for outdated template overrides. Record the active theme and checkout type. A field collected by a checkout extension needs to be saved on the order before an email editor can display it.
  2. If the store uses core settings, inspect its Email improvements setting. The separate Block Email Editor is documented as alpha under Advanced > Features. Its blocks are not interchangeable with YayMail elements or ordinary webpage blocks.
  3. For YayMail, compare the installed edition and extension against its supported integrations. Its WooCommerce documentation explains the order selector, dynamic elements and template controls. Check the actual received message for each extension-owned field.
  4. Test a product with a variation and any required purchase-specific options. If a colour or instruction is missing, compare the saved order with the email. Fix collection or saving when the order lacks the value. Fix the template mapping when the order has it.

For an invoice attachment, identify the extension that generates the document and the event that attaches it. Check that its attachment survives your selected editor and arrives on the intended notification. Open the received PDF and compare its order number, currency and tax totals with the order. An email customiser’s PDF capability does not establish invoice numbering or tax-document correctness.

Export custom templates before updating YayMail. After a WooCommerce update, review outdated PHP overrides and any offered block-template update. Recheck your edited notification with the same fictional order, including its refund version. Preserve the order elements when merging a design change.

Verify delivery and correction

Verify an isolated order event all the way to its intended inbox. A preview checks appearance. A test-send checks a sending path. Neither proves that a particular order transition sends the right customer message once.

  1. Create a fictional order using the payment gateway’s test mode and a test mailbox you control. Record the order number and expected notification. Confirm that the stored billing email is that mailbox.
  2. Complete the intended event once. For a paid confirmation, use a successful test payment and inspect the saved payment state. For a refund, perform the test refund through the supported refund workflow.
  3. Compare the received message with the order. Check the variation, quantities and total. Inspect the recipient and reply address, then test the order link while signed out and signed in as the relevant test customer.
  4. Open any attachment and compare its values too. Read the received email on a phone and a desktop, including with images blocked. The order details and contact route must remain usable.

Find the failed stage

What you observeDiagnostic checkCorrection and retest
Preview looks right, but no order email appearsConfirm the intended order transition occurred and the notification is enabledCorrect that condition and trigger one new isolated event.
A queued job has not runIf an extension schedules the message, inspect its scheduled action and errorRepair the scheduler or reported extension fault, then run one controlled retry.
WooCommerce records FailedInspect the mail error and sending-service configurationCorrect the connection or sender fault, then send one test message before repeating the event.
WooCommerce records Sent, but the inbox is emptyCheck the sending provider’s delivery result and recipient filteringFix the recorded rejection or authentication fault. Confirm receipt in the test inbox.
The customer receives duplicatesCompare send times with order notes, scheduled jobs and enabled automationsRemove the overlapping trigger on the isolated store. Repeat one event and count the received messages.

Where available in your installed version, open WooCommerce > Status > Logs and filter transactional-emails. Sent records a successful handoff to the mail system, not inbox delivery. Disabled and Skipped identify different causes. WooCommerce’s email troubleshooting procedure explains the outcomes and log-level settings.

If the mail provider rejects the sender, correct its authenticated sending configuration. Keep the store’s From address on its own domain and use a monitored reply inbox. Changing the subject line cannot fix a rejected sender.

Before resending a correction, confirm whether the first message already arrived. Send the corrected message to the intended test recipient and verify its facts again. The finished template must deliver the right event and order details once, with a working route for the customer’s reply.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup