Referral disclosure: Some hosting links in this article are referral links. WP Gazette may receive a commission or hosting credit if you make a qualifying purchase.
WooCommerce 10.9.4 shipped today, 7 July 2026. It is a dot release, the kind that arrives quietly and matters mostly to people who maintain stores for a living. The bigger news is the calendar: the WooCommerce 11.0 beta is due on 13 July, and the final release has moved from 28 July to 4 August. If you run stores, that is the date to pin to the wall.
We track the release cycle through the official releases page and the changelog. Nothing in 10.9.4 changes the shape of the platform. It is a maintenance cut, and maintenance cuts are where regressions get patched before a minor version lands. Test it on staging, then ship it. There is no reason to sit on a dot release while a minor is in flight.
WooCommerce 10.9.4: what a dot release is for
Dot releases exist to keep the current branch stable while the next one is built. Woo does not publish a headline feature list for them, and merchants should not expect one. What matters is that 10.9.4 is the version your store should be on today if you are not already testing 11.0.
Two practical checks before you update:
- Run the update on a staging clone first, with your payment gateways and any checkout customisations active.
- Watch the order emails and the checkout flow, not just the admin screens. Dot releases rarely break the admin; they occasionally touch the edges of checkout.
If you use a host that handles Woo updates for you, confirm which version you are on. Managed platforms sometimes lag a day or two behind a dot release. That is usually fine. It is not fine if you are chasing a specific fix from the changelog.
The 11.0 timeline, and why it moved
The original plan had 11.0 landing on 28 July 2026. It now lands on 4 August. The beta still arrives on 13 July. A one-week slip on a minor release is not a crisis; it is the release cycle doing its job. Woo would rather move the date than ship a minor with known issues in the backlog.
Here is the timeline to keep visible:
| Date | Milestone |
|---|---|
| 7 July 2026 | WooCommerce 10.9.4 shipped |
| 13 July 2026 | WooCommerce 11.0 beta |
| 28 July 2026 | Original 11.0 release date (superseded) |
| 4 August 2026 | WooCommerce 11.0 final release |
Plugin and theme developers should treat 13 July as the real deadline. If your extension touches checkout, orders or analytics, the beta is your test window. Three weeks between beta and final is tight but workable. It is not enough time to start from scratch.
What Woo says 11.0 is about
Woo Artistic Director Beau Lebens has written about the 11.0 focus, and it is deliberately unglamorous: foundations and GitHub backlog cleanup. That means the team is spending a cycle on the plumbing rather than on new storefront features. For merchants, the payoff is a platform that is easier to maintain. For developers, it means fewer stale issues and a clearer signal about what Woo will and will not fix.
Two items sit alongside the cleanup:
- Analytics accuracy and resilience. Woo is treating analytics as infrastructure, not a dashboard. If your reports have drifted, this is the cycle where that gets attention.
- Guest-order claiming. Customers who checked out as guests will be able to claim previous orders. That is a real change to how accounts and order history work, and it is the item most likely to touch custom code.
The guest-order work is the one to watch. Any plugin that filters order queries, alters the account page or hooks into customer lookup needs testing against it. If you maintain a store with a membership or loyalty extension, put the 13 July beta on your calendar now.
What to do this week
Update to WooCommerce 10.9.4 on staging, then production. Confirm your host is not holding you back. Then spend an hour on the 11.0 beta plan: identify which extensions touch checkout, orders and analytics, and decide who tests them.
If you sell on Woo and you have not looked at your analytics in a while, do it before 4 August. The accuracy work in 11.0 may change numbers you have been reporting to your board. Better to know now than to explain a shift later.
For stores that need faster checkout and cleaner reporting, the stack around Woo matters as much as Woo itself. We recommend WP Rocket for caching that does not fight the cart, and Cloudways if you want a host that lets you tune the PHP and database layer under Woo. Both are the kind of infrastructure that makes a dot release boring, which is the point.
FAQ
Is WooCommerce 10.9.4 a security release?
Woo has not framed it that way. Treat it as a maintenance dot release and check the changelog for the specific fixes that apply to your store.
Should I wait for 11.0 before updating?
No. Ship 10.9.4 now, then test 11.0 on staging from 13 July. Waiting leaves you on an older branch with no upside.
Why did WooCommerce 11.0 move to 4 August?
Woo moved the date from 28 July to 4 August. The stated focus is foundations and backlog cleanup, and the extra week gives the team room to finish that work without rushing the release.
We conclude: 10.9.4 is the update you ship today, and 4 August is the date you plan around. The beta on 13 July is the one that will tell you whether your extensions are ready.