Open WooCommerce, go to Orders, and filter the list by status. On most stores I look at there is a long run of entries marked Checkout (draft): abandoned carts, bots, shoppers who got as far as the checkout block and left. Until now, every fresh session that touched checkout through the Store API wrote one of those rows, whether anyone bought anything or not. WooCommerce 10.9 changes that, and of everything in this release, it’s the change with the widest reach.
Where the draft orders were coming from
The Store API used to create a persisted draft order during fresh-session GET and PATCH requests. In 10.9 that creation is deferred until close to place-order time, so a session that never buys never writes an order row at all. The release post on the WooCommerce developer blog also lists the work around it: fewer checkout saves and lookups, better product filter SQL, and lower query volume on shop and admin product pages. None of it is flashy, but on a store with real traffic it shows up in database size and in how the admin order list feels.
Before upgrading, get your own number. On a store with HPOS enabled:
wp db query "SELECT COUNT(*) FROM $(wp db prefix)wc_orders WHERE status = 'wc-checkout-draft';"
On older stores still on the posts table, the same rows live in wp_posts with a post_status of wc-checkout-draft. Run it now and again a few weeks after the update, and you have a before and after.
One caution: if you have custom code that assumed a draft order ID exists early in a session, test it. Some fraud checks and analytics snippets key off that ID, and deferring creation changes when it first exists.
Email logging moves into core
10.9 also ships transactional email logging in core. Email attempts now show up under WooCommerce > Status > Logs with send outcomes and local failure reasons, so the first debugging step is no longer installing a logging plugin. I wrote more about that when the feature landed, so I’ll keep this short. The comments under the release post have one more detail: a store owner on 10.8.1 reported stock notifications going silent. A team member traced it to deferred email handling, pointed to a fix in 10.9 (PR #64820), and suggested turning off Deferred emails under Settings > Advanced > Features until the update arrives. If a client store has quiet email failures today, check that toggle before anything else.
The deprecation that has a deadline
The block-based Product Editor beta is deprecated in 10.9 and removed in 11.0. In 10.9, admins who open it get an in-product notice with a one-click switch back to the classic editor, and extensions that call the related entry points start emitting deprecation warnings. No product data or content is affected; this retires an editing screen and leaves your catalog alone. If you ship extensions or heavy custom admin code, grep for @woocommerce/product-editor imports and any product editor feature flags now, because warnings in 10.9 become broken imports in 11.0. The retirement advisory has the timeline and the full audit list.
The experimental pile
The rest of 10.9 is a large batch of experiments, which the post credits to a “Radical Speed Month” inside Automattic. The one I find interesting is abilities: schema-backed operations for querying and updating products and orders, with permission checks, replacing the earlier MCP abilities that wrapped REST endpoints one to one. The old MCP endpoint stays available as a transition path. There’s a dual API experiment too, where PHP classes generate a matching GraphQL surface. It needs PHP 8.1 or newer, covers products and coupons as a proof of concept, and plugins can use the same utilities. I went through which of those APIs I would pick today separately. Color swatches and variation galleries sit behind toggles under WooCommerce > Settings > Advanced > Features, with galleries off by default. Wishlist, save-for-later, and back-in-stock notifications are at an earlier stage, and back-in-stock is gated by a constant. Test the toggles on staging if a client has asked for swatches, but I wouldn’t build against the rest yet.
How to test before June 23
Install the WooCommerce Beta Tester on a staging copy, switch to the beta channel, and update to 10.9.0-beta.1. What I would test, in order: a full checkout with the real payment gateway, because draft order timing changed and that is where gateway callbacks and confirmation emails live; the email log after a test order; and any admin screens you have styled, since the Woo header and modals got a round of polish. File problems on GitHub rather than in a client Slack.
If you would rather hand the beta pass and the extension audit to someone who does this regularly, that is work I take on. The question I still have is whether headless builds break: they lean on the Store API hardest, and if any of them assumed a draft order exists early in a session, they will hit that change first.