WooCommerce has announced that the block-based product editor beta will be removed from core with the release of WooCommerce 11.0, scheduled for July 28, 2026. Ahead of its removal, WooCommerce 10.9 (scheduled for June 23, 2026) will introduce deprecation notices and warnings for store owners and extension developers.
Following this change, the classic editor will become the sole product editing experience available in WooCommerce core.
Introduction of the block-based product editor beta and later rethinking
The editor was first introduced in WooCommerce 7.8 through a feature flag. At the time, WooCommerce said that “customer expectations are constantly evolving” and that users increasingly demand “an effortless and intuitive experience,” prompting them to “embark on a journey to redefine the product creation experience.”
Describing its vision for the project back then, WooCommerce said, “Our goal is to empower users with a new experience that makes them feel in control, helping them seamlessly navigate between the two sides of the spectrum: from creating a basic product to a product requiring multiple options and additional customization. It should feel like a superpower.”
By late 2024, WooCommerce had already begun rethinking the strategy for the Product Editor. Announcing plans for a new Product Editor Experience, v3, the team said it had identified that “the newer WordPress Data Forms and Data Views projects are a better fit for our use case” after experimenting with earlier Core APIs and gathering feedback from contributors. Since then, development has been stopped on the current beta.
Luigi Teschio (Technical Lead at Automattic), replying to Fernando Tellado, iterated, “ This wasn’t a sudden pivot: in Nov 2024 we shared that new development on the current Product Editor beta was paused while we moved toward a more WordPress-native direction based on DataForms/DataViews..,”
Veronica Fasulo and Luigi Teschio already shared a new experimental work based on that approach, which remagines the catalog management.
In WooCommerce 10.1, the editor was officially deprecated. At the time, WooCommerce removed the feature toggle from the admin interface for most users and indicated that the feature would be “sunset and removed from the codebase in the near future.” The documentation page also highlights this.
We reached out to the WooCommerce team for comment, and here’s what they shared:
With the Product Editor beta, the team explored creating an experience based on the WordPress core APIs available at that time — gaining valuable feedback on what was and wasn’t working well.
Since then, WordPress introduced new APIs — specifically Data Forms and Data Views — that aligned closely with what the Woo team needed. As these matured, we saw an opportunity to build on them as a foundation, and began contributing directly to WordPress Core alongside Core contributors to help shape these components to meet WooCommerce’s needs.
That upstream work, rather than building a separate framework from scratch, is now the path forward. These are the same components powering content management and settings screens across WordPress — and we’re working to ensure they’re extensible enough for any plugin to build on the same foundation.
Deprecation and removal timeline
The upcoming WooCommerce 10.9 release will serve as a transition period ahead of the editor’s removal in version 11.0. Store owners using the beta editor will see notices informing them of the change and providing a one-click option to return to the classic editor, while extensions that rely on related public entry points will begin generating deprecation warnings to help developers identify affected code. WooCommerce also highlighted that no editor code is being removed in 10.9.
WooCommerce outlined the components that will be removed in 11.0 release, “ That removal includes the @woocommerce/product-editor package, the block-editor product pages in WooCommerce Admin, the feature toggle, related routes, menu entries, tests, and other code that only supported the beta editor.”
Once the change takes effect, the classic editor will become the sole product editing interface available in WooCommerce core. WooCommerce added that the underlying product data layer will remain unchanged, allowing existing products to continue being edited without any data migration.
While most stores will only need to switch back to the classic editor if the product editor beta remains enabled, WooCommerce said extension developers should review code that integrates with the beta editor and also review any integrations built specifically for the beta editor.
The company also noted that it has deprecated the @woocommerce/create-product-editor-block package, which was designed to help developers build extensions for the product editor.
WooCommerce said developers working with product data integrations can continue using supported product APIs and extension points that are independent of the beta editor, “ For product data integrations, continue using the supported WooCommerce product APIs and extension points that are not tied to the beta editor. This change is about retiring an experimental admin editing surface, not changing how WooCommerce stores product data.”
For extensions that were built with beta editor-specific custom behavior, WooCommerce suggested reviewing whether that behavior is still necessary in the classic editor flow, adding that, “ In many cases, beta-editor-specific integration code can be removed rather than replaced.”
WooCommerce also confirmed it does not plan to bring back the beta editor in its existing form. They also noted that they continue to explore future product management approaches built on DataViews and DataForms.