WooCommerce 10.9 ships on Tuesday, June 23, 2026, and the headline feature is one that store owners have been patching around with third-party plugins for almost a decade. The 10.9 beta went live on June 9, and the release notes from the WooCommerce developer blog confirm that transactional email logging is finally moving into core. That means the next time a customer emails you insisting they never received the order confirmation, the refund, or the shipping notice, you will be able to open one screen, see exactly what WooCommerce tried to send, and know whether the email actually left your server or quietly died in PHP's mail() function. The release also includes a stack of checkout performance work and a long-overdue polish pass on the Woo admin screens, but the email log is the part that will pay for the update on its own.
Why the email log is the only one that matters
If you have ever run a WooCommerce store, you know the exact conversation. A customer writes in furious, swearing the order confirmation never arrived. You check the order, the order is paid, the order is fulfilled, the customer is on the right email address, and you have no way to prove whether the message actually went out. Until 10.9, your only options were to install a separate logging plugin like WP Mail Logging or SMTP Email Log, or to dig into the raw wp_posts table where the older action scheduler used to leave scraps of email data. Most small stores do neither, which is why the "did my email send?" support ticket has been one of the unsolvable mysteries of running WooCommerce for years.
The new feature lives in WooCommerce under Status and then Logs, which is the same place the plugin already exposes PHP and REST API logs. Each email attempt will show up there with the recipient, the subject, the template used, the send outcome, and the local failure reason when the send fails. If your store is using a third-party SMTP service like Postmark, SendGrid, Mailgun, or Amazon SES, those services already log their side of the conversation, but the new core log closes the loop on WooCommerce's own behavior. You will be able to tell, in one screen, whether WooCommerce even tried to send the email in the first place, which is the gap that has cost small store owners hundreds of refund re-sends every year. The deeper dive from Automattic on June 3, titled Keeping track of commerce emails, walks through the storage model and confirms the log persists locally, so it does not depend on a hosted service to be useful.
The checkout performance work is the part you will feel without noticing
The email log is the easy thing to write about because it solves an obvious support problem. The harder and arguably more important work in 10.9 is a set of changes to the Store API that fix a database bloat problem that has been slowly strangling large WooCommerce stores. Before 10.9, every time a shopper opened checkout and started filling in their details, WooCommerce wrote a draft order row to the database, and a shopper who bounced before completing checkout left that draft order behind. A busy store on a slow Tuesday could collect hundreds of those abandoned draft rows, all of which had to be queried, counted, and excluded from real reports forever after. The new release defers draft order creation until much closer to the actual place-order moment, which the release notes describe as reducing "orphaned checkout draft rows for shoppers who never complete an order." That is a polite way of saying your wp_posts table is going to be a lot smaller.
The performance PRs do not stop at checkout. The release also reworks product filter SQL, reduces the number of queries on shop and admin product pages, and trims a handful of lookups that ran on every order save. None of these are features you will see in the changelog UI, and none of them will ring a bell when you log in on Wednesday morning, but they are the kind of work that turns a store that takes eight seconds to load the orders screen into one that takes three. For a small store on shared hosting, that difference is the line between keeping a customer and losing one. Automattic called the period that produced these changes "Radical Speed Month," and 10.9 is the public version of what came out of it.
A smaller note: the admin finally gets some love
The third bucket of changes in 10.9 is admin UI polish, which is the part of the release most likely to be overlooked and most likely to make your daily store management feel less annoying. The Woo admin header gets fresh alignment with the WordPress design system, the modal styles get unified across screens, and the smaller-screen dashboard gets a few targeted fixes that should make the store admin usable on a phone for the first time in years. The task list reminder bar that used to live on most admin pages is gone, with the setup guidance moving into the Woo dashboard and the activity panel where it actually belongs. None of this is going to change your conversion rate. All of it will save you ten seconds a day, which compounds to a real chunk of time over a year.
What to actually do this week
If you run a single WooCommerce store, the action is straightforward. On Tuesday, June 23, update to 10.9 the same way you would any other minor release, and spend five minutes in the new Status and then Logs screen to confirm it is working. Place a test order, watch the order confirmation email show up in the log, and bookmark that screen so your support team knows where to look the next time a customer claims they never got a receipt. If you have been using WP Mail Logging or a similar third-party email log plugin, do not delete it on day one. Let both logs run side by side for a week, confirm the core log captures everything the old plugin did, and then retire the third-party tool.
If you manage more than one store, update a staging copy first and run a real checkout flow, because any change to the Store API order creation flow is the kind of thing that occasionally breaks a custom payment gateway or a bespoke checkout extension that hooks into draft orders. Most stores will not be affected, but the ones that do get hit will lose sales until they notice. The bigger move is to start building a habit of looking at the new log screen every Monday. That single five-minute check is going to surface failing emails, misrouted receipts, and template bugs long before they turn into angry customer emails, and on a small store, that is the difference between a quiet week and a refund week.