WordPress 7.0 is coming, and if you run a WooCommerce store, it deserves your attention now — not when the update notification appears in your dashboard. The original final release date was April 9, 2026, but on March 31, 2026 the WordPress core team announced the release would not ship on that date, extending the cycle to get the Real-Time Collaboration database architecture right. The updated schedule sets May 20, 2026 as the new release date, with two additional release candidates added to allow more time for testing the performance enhancements supporting Real-Time Collaboration. That delay is a signal worth reading carefully. When a release team needs extra time on the architecture, it tells you something about the scale of what is changing underneath.
WordPress 7.0 has been described as the biggest core release in eight years. That is not marketing language. The changes running through this release are structural, and for WooCommerce store owners, the practical consequence is that some of what is currently installed and working on your site may not continue working without an update from the plugin’s developer. The question is not whether WordPress 7.0 will cause problems in general — it is whether it will cause problems on your specific site, with your specific combination of plugins, extensions, and theme.
What Is Actually Changing, and Where the Risk Sits
WordPress 7.0 introduces DataViews API changes, classic meta box conflicts with collaborative editing, Block API v3 alignment, and PHP version requirement changes. Each of these carries the potential to disrupt plugins and themes that have not been updated to account for them. For a WooCommerce store, that translates directly into checkout add-ons, product display extensions, order management tools, and any customisation that touches the admin interface.
The good news on WooCommerce itself is straightforward. Actively maintained plugins, including WooCommerce, will likely ship compatible versions at or near launch. WooCommerce operates on a predictable release cycle of roughly every five weeks, and WooCommerce 10.7.0 was released on April 14, 2026, meaning further updates are already in progress before May 20 arrives. The core platform is unlikely to be your problem.
The risk sits elsewhere. Niche or unmaintained plugins are identified as the highest risk category. Think about every extension you have installed: payment gateway add-ons, subscription tools, checkout customisers, review plugins, shipping calculators, CRM integrations. Many of these were built by smaller developers who may not have published a compatibility update, or may not do so before May 20. Plugins that modify Posts, Pages, or Media list views carry the highest compatibility risk due to the DataViews changes in WordPress 7.0. If any of your installed plugins touch those areas of the admin — and a surprising number do — they need to be audited before you upgrade.
What to Do Before May 20
The delay to May 20 is not a reason to relax. It is a window to prepare. Here is what I recommend to any WooCommerce store owner right now:
- Set up a staging environment that mirrors your live store. This means the same plugins, the same theme, the same version of WooCommerce, and as close to the same data as practically possible. This is where you test WordPress 7.0 before it ever touches your trading site.
- Audit every installed plugin and theme for compatibility. Go through your plugin list one by one. Check the plugin’s changelog, its WordPress.org page, and its developer’s communications. If a plugin has not been updated in twelve months or more, treat it as high risk. If it modifies list views in the admin, treat it as high risk regardless of when it was last updated.
- Identify which plugins are genuinely active and which have been forgotten. Many stores accumulate plugins that were installed for a reason that no longer applies. A WordPress 7.0 audit is a good opportunity to remove them. Fewer installed plugins means fewer compatibility variables to manage.
- Check your PHP version. WordPress 7.0 changes the PHP requirements. If your hosting environment is running an older PHP version, that needs addressing before you upgrade WordPress, not after.
- Do not apply the update to your live store until compatibility is confirmed on staging. This is non-negotiable. Running a WooCommerce store means your website is a trading asset. An untested major update applied directly to a live site is an avoidable risk to your revenue.
The delay from April 9 to May 20 gives you an additional six weeks compared to the original timeline. That is enough time to work through this preparation methodically if you start now. It is not enough time if you wait until the release lands and then discover that a checkout extension your customers depend on is broken.
If you would rather have this handled properly — staging environment set up, plugins audited, compatibility confirmed, and the upgrade applied safely — that is exactly what I do at The WordPress Guy. Get in touch and I will tell you what is involved for your specific site.
