Free tools Windows power users keep installed
One-click scans. No signup required.
WooCommerce gives you a built-in way to preview an email on desktop or mobile and send a test message to an address you control. Because that preview uses dummy data, a reliable pre-launch check also needs a sample or real order, the actual mail clients your customers use, and WooCommerce logs to distinguish a template problem from a delivery problem.
Preview a WooCommerce email in the dashboard
- In WordPress, open WooCommerce > Settings > Emails.
- Select the notification you want to inspect, such as a new-order, processing-order, completed-order, refund, or customer-invoice email.
- In the email’s preview area, switch between the desktop and mobile views. Check spacing, headings, logo treatment, buttons, tables, and whether long text wraps.
- Choose Send a test email, enter an address you control, and send the message.
- Open the delivered message in the desktop and mobile mail clients that matter to your audience. The dashboard preview shows rendering; it does not prove that a message was accepted, delivered, or placed in the inbox.
Understand what the core preview can—and cannot—show
WooCommerce’s core Email Preview feature renders templates with dummy data rather than records from your store database. It is useful for checking layout and standard wording, but it cannot prove that a particular customer’s name, product, tax, shipping method, refund, or extension field will look correct.
| Method | Data shown | Best use | Order or subscription ID needed? | Delivery diagnostics |
|---|---|---|---|---|
| Core dashboard preview | Dummy data | Quick desktop and mobile layout check for WooCommerce email types | No | No |
| Send a test email | The rendered test version sent to an address you enter | Inspect the received HTML, links, images, headers, and inbox placement | No | No |
| Email customizer with a sample order | Sample-order data selected by the customizer | Dynamic content, shortcodes, branded design, and one-click test sending | Usually no; select the available sample order | No |
| Email Previewer for WooCommerce | A specific order or subscription | Order-specific and subscription-specific rendering | Yes, enter a valid Order ID or Subscription ID | No |
| Controlled test order plus logs | Data produced by an actual order state | End-to-end trigger, generation, sending, and troubleshooting | The test order supplies the ID | Yes, through WooCommerce email logs |
Test dynamic order content with realistic data
Use a sample order in an email customizer
If your design relies on customer names, products, quantities, taxes, shipping, refunds, or extension fields, use an email customizer that supports a sample order. The official customizer workflow includes a Sample order to show selector, shortcode support, live preview, and one-click test sending. Verify that each dynamic token resolves to a sensible value rather than remaining blank or displaying raw shortcode text.
Render one real order or subscription by ID
For a specific transaction, install an order-aware preview extension such as Email Previewer for WooCommerce. Under WooCommerce > Settings > Emails, use the notification’s Preview Email column, enter a valid Order ID or Subscription ID, and click Preview. This is the most direct way to inspect a refund, renewal, subscription, or unusual product combination without guessing what dummy data represents.
#1 Best Overall
Create a controlled test order
Use staging whenever possible. If you must test on production, label the order clearly, use a controlled payment method, and avoid real customer data. WooCommerce notes that test orders can trigger order emails and appear in analytics; an extension may have its own test behavior, so check those settings before creating one. Trigger the exact status change that should send the notification rather than assuming that opening a preview will exercise the trigger.
What to verify before launch
Rendering on real clients
- Compare the dashboard’s desktop and mobile views.
- Open the received message in Gmail, Outlook, Apple Mail, and at least one representative mobile client.
- Check table widths, line wrapping, button appearance, dark-mode effects where relevant, image loading, and whether any content is clipped.
- Keep the complete email under WooCommerce’s recommended 100KB total size.
Email clients implement HTML and CSS differently, so a dashboard preview cannot substitute for received-message testing.
Content and calculations
- Subject line, preheader, heading, logo, sender name, reply-to address, and footer.
- Product names, variations, quantities, prices, coupons, taxes, shipping, totals, billing and shipping addresses.
- Refund amounts, downloadable files, account links, payment instructions, and any fields added by an extension.
- Links, buttons, unsubscribe or preference links where applicable, and image URLs.
Formats and size
If your configuration sends HTML, plain text, or multipart output, inspect every format that recipients can receive. WooCommerce’s email settings documentation warns that plain-text fields may be truncated when product names or variations are long. Confirm that the plain-text version remains understandable and that the HTML version does not exceed the 100KB guidance.
Receipt and inbox placement
- Confirm the test message actually arrives at the address you entered.
- Check the sender and reply-to headers, not only the display name.
- Look in spam and promotions folders as well as the primary inbox.
- Open every important link and verify that images load from secure, reachable URLs.
- Check that the message is not clipped by the mail client.
A repeatable pre-launch procedure
- Save the email’s subject, heading, content, recipient, and enabled status.
- Run the built-in desktop and mobile preview.
- Send a test to an address you control and inspect it on the target desktop and mobile clients.
- For dynamic fields, select a sample order or preview a known Order ID or Subscription ID.
- Create a labeled staging or production test order that reaches the notification’s real trigger state.
- Check the resulting HTML, plain-text or multipart output, links, images, totals, addresses, and extension fields.
- Review WooCommerce email logs and confirm that the event was generated and sent.
- Correct the template, customizer, extension, or mail-delivery configuration, then repeat the failed test rather than relying on the old message.
Why a WooCommerce test email did not arrive
The notification is disabled or has the wrong recipient
Return to WooCommerce > Settings > Emails, open the notification, and confirm it is enabled. Check the recipient field and any role-based or extension-specific recipient settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The event was never triggered
A preview is not an order event. Reproduce the workflow with Send a test email or a controlled test order that reaches the required status. For subscriptions, use a subscription-aware test rather than an ordinary order.
WooCommerce generated an error or never attempted delivery
Open the WooCommerce email logs and determine whether the message was sent, failed, or never attempted. That distinction tells you whether to fix the template or investigate the mail-delivery layer.
The message was delivered but is hard to find or read
Search spam, promotions, quarantine, and other filtered folders. Compare the received message with the admin preview, then inspect sender headers, links, images, HTML size, and mobile rendering.
A customizer or extension changed the output
Temporarily isolate customizer and email-delivery extensions, retest the same notification, and add them back one at a time. If only an extension email fails, confirm that the extension integrates with WooCommerce’s preview system and supplies realistic placeholder values.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Notes for developers and extension authors
An extension that adds an email type should integrate with WooCommerce’s preview system, provide realistic placeholder values, register every style and content setting that changes rendering, and test more than one email type across responsive layouts. WooCommerce 9.8’s April 9, 2025 release announcement also highlighted modernized designs and preview support as extension-development concerns. A successful core preview does not establish that an extension’s custom fields, subscription states, or renewal events work correctly.
Choose the right testing method
- Only checking spacing or branding? Use the core desktop/mobile preview.
- Checking the actual received message? Use Send a test email and inspect multiple clients.
- Checking customer, product, tax, or shipping fields? Use a sample-order customizer.
- Checking one refund, renewal, or unusual order? Preview by Order ID or Subscription ID.
- Checking whether a status change sends mail? Use a controlled test order and review logs.
The Bottom Line
Use WooCommerce’s built-in preview for quick layout checks, but do not launch until a controlled sample or real order has been rendered, the received message has been opened on representative clients, and the email logs show the expected send.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
