The block-based product editor beta is being removed from WooCommerce core in version 11.0, currently scheduled for Tuesday, July 28, 2026, and no product data is being migrated or lost. Stores fall back to the classic product editor. WooCommerce 10.9, due June 23, starts the deprecation window with in-product notices.
That is the short version of the advisory the WooCommerce developer blog published. The editor has sat behind a feature flag for a while, and development on it stopped in November 2024. This is cleanup of a surface that was already dead, and you do not have to react overnight. I think the removal is the right call, and the rest of this post is the checks I would run before July 28.
Why the removal is the right call
Core should have shed this code earlier. Three reasons.
First, development ended in November 2024, per the earlier advisory the post links to. Since then the package, the block-editor product pages, the toggle, the routes, and the tests have all shipped in core with no future. The 11.0 work is framed as reducing the maintenance cost of exactly that, and I believe it. Experimental code that has stopped moving is the worst kind to keep, because it still has to be checked against every WordPress release and it teaches nobody anything new.
Second, the data layer was never part of the beta. Products are still posts, post meta, and the same CRUD objects they have always been. The advisory is explicit that no migration is needed. That contains the blast radius: anything you built on the product data layer keeps working, and only code tied to the editing surface has to change. If the beta had also redesigned how product data is stored, this would be a much longer post.
Third, the whole thing was labeled experimental from day one. The flag is product-block-editor-v1, the extension points were prefixed __experimental, and the scaffold package for building blocks against it was only ever a convenience. Extensions that shipped against those APIs were betting that a beta behind a flag would become the default. It was a fair bet, since that is roughly how the post editor went, but it was still a bet.
The merchant side of this loses something real, and I don’t want to wave that off. The comments under the advisory are mostly store owners pointing out that the classic product screen is dated, particularly the description box, and they are right. A reply from the WooCommerce team in those comments argues that products and orders carry complexity posts do not, such as variations, inventory, pricing, tax, and extension data. True as far as it goes. The replacement is currently a proof of concept, so store owners get the old UI for a while longer. It is still the right call technically, but that is thin consolation if you edit products all day.
What to check before July 28
Store owners first. If the beta is enabled on your site, WooCommerce 10.9 will show a notice inside the editor with a one-click switch back to the classic editor. Use it, then edit a product end to end, variations and inventory included, before you update to 11.0. If you never see the notice after moving to 10.9, the flag was never on and there is nothing to do.
To check the flag without hunting through screens, run this from the site root. The beta lives under the product-block-editor-v1 key in the features option, which is the same thing you see under WooCommerce, Settings, Advanced, Features. The greps are for developers auditing extensions and themes.
wp option get woocommerce_features_enabled --format=json
grep -rn "product-block-editor-v1" wp-content/plugins/ wp-content/themes/
grep -rn "@woocommerce/product-editor" wp-content/plugins/ wp-content/themes/Extension developers should grep for the three strings the advisory names: @woocommerce/product-editor, product-block-editor-v1, and __experimental. The third will return noise, because half of WooCommerce’s newer JavaScript APIs carry that prefix, so treat the hits as a review list rather than a fix list. The @woocommerce/create-product-editor-block scaffold package is deprecated too, so any build tooling around it should go. The 11.0 removal takes out the package, the block-editor product pages, the feature toggle, the related routes, and menu entries. Code that depends on any of that should not expect it to exist after the update.
10.9 also adds deprecation warnings on the public entry points, so run your integration with WP_DEBUG on after updating and read what it prints. The work is tracked in the open: issue 65318 for the 10.9 notices and issue 65319 for the removal. The advisory asks maintainers who are stuck to comment on the relevant issue with the extension point they use. Do that in June rather than in the last week of July.
If you maintain a plugin that touches the product screen and you are not sure which grep hit is a real dependency, that is the kind of audit I do for stores and agencies. Send me the integration and I will tell you what survives 11.0 and what has to change.
What comes after the product editor beta
The direction Woo names is DataViews and DataForms, the newer WordPress admin interface work, and there is a proof of concept in Reimagining catalog management that rebuilds the All Products screen with hierarchical variation rows, quick edit, and bulk edit. It looks like a better foundation than the beta, because it composes with WordPress instead of forking the block editor into a product-shaped one. I would still treat it the way I treated this beta: read it, test it, build nothing commercial on it until it ships without a flag. A proof of concept with no ship date carries the same class of risk as a beta behind a flag. It is just younger.
For work clients pay for now, the stable surfaces have not moved: product CRUD, meta, the REST API, and the hooks that editor has always had. Classic does not mean abandoned either, since the classic editor is still getting hotfixes in WordPress itself.
On a client site this week I would flip the flag off on staging once 10.9 lands, have whoever edits products daily do a full pass, and grep the custom code for the package name. If all three come back clean, the 11.0 update in late July is routine.
