WordPress 7.0 Release Candidate 1 has landed, and if you are running a WooCommerce store, this is not a release you can afford to treat like a routine update and forget about. This is the most significant WordPress core release in years, and it has already had its timeline shifted once. Understanding what changed, why it changed, and what that means for your store is the kind of planning that separates businesses that update smoothly from those that spend a weekend firefighting a broken checkout.
RC1 alone contains more than 134 updates and fixes since Beta 5. That volume of change in a single release candidate is significant. It signals that the testing cycle has been active, that issues have been found and addressed, and that the codebase going into the final release is materially different from what entered beta. For WooCommerce store owners, that scale of change demands attention.
Why the Delay Matters More Than the Date
The original release date for WordPress 7.0 was April 9, 2026. On March 31, 2026, the core team announced it would not ship on that date. The decision was made in the Making WordPress Slack workspace by Matt Mullenweg and the release squad. The updated target is now May 20, 2026, with additional release candidates added to allow more time for testing.
The reason matters. This was not a cosmetic delay or a resourcing issue. The Real-Time Collaboration database architecture needed more time to get right, with the core team acknowledging on March 31st that the release cycle needed to be extended, and a follow-up post published on April 2nd explaining the practical implications. Database architecture decisions in a platform running millions of sites are not minor. Getting them wrong creates problems that are difficult to reverse and expensive to resolve. The team made the right call by delaying, but it also tells you something about the complexity of what is being shipped.
Real-Time Collaboration is a headline feature of WordPress 7.0 — the ability for multiple users to edit content simultaneously. For WooCommerce stores with more than one person managing products, content, or orders, this eventually has genuine operational relevance. But at launch, the priority is stability, not feature adoption.
What WooCommerce Store Owners Should Do Before May 20th
WooCommerce has more than 7 million active installs. Automattic, the company behind WooCommerce, maintains it actively, which means WooCommerce itself is expected to ship a compatible version at or near the WordPress 7.0 launch. That is reassuring, but it is not the whole picture. Your store is not just WooCommerce. It is WooCommerce plus your payment gateway plugin, your shipping extensions, your product customiser, your reviews plugin, your page builder, and however many other tools sit between a customer landing on your site and completing a purchase.
Plugins that modify Posts, Pages, or Media list views carry the highest compatibility risk in WordPress 7.0 due to changes in DataViews — the underlying system WordPress uses to render these screens. Niche or unmaintained plugins carry the highest risk overall. If you are running extensions that have not been updated in several months, or that come from developers who are slow to respond to major releases, those are the ones to audit now — before May 20th, not after.
The practical steps I would recommend to any WooCommerce store owner ahead of this release are straightforward:
- Set up a staging environment that mirrors your live site exactly — same plugins, same theme, same configuration
- Audit every active plugin and check when it was last updated and whether its developer has communicated WordPress 7.0 compatibility
- Disable auto-updates for WordPress core on your live site if you have not already done so — a release of this scale should never be applied automatically
- Apply WordPress 7.0 to staging first and run through your full purchase journey, from product page to order confirmation
- Test your admin screens, particularly any that involve product lists, order lists, or media management, given the DataViews changes
- Only update your live site once you have confirmed everything functions correctly in staging
None of this is alarmist. WooCommerce is well-maintained, the core team has taken the time to get the architecture right, and the extended testing cycle means RC1 and subsequent candidates are absorbing real-world issues before the final release ships. The message here is informed readiness. You have a window between now and May 20th to do this properly. Use it.
If you would rather have someone manage this process for you — setting up staging, auditing your plugin stack, and handling the upgrade on your behalf — get in touch with me at The WordPress Guy. This is exactly the kind of work I do for WooCommerce store owners who would rather focus on running their business than worrying about what a core update might break.
