WooCommerce’s long-telegraphed move to make its block-based checkout and storefront architecture the only supported path forward is finally landing with force. The platform’s 9.0 release, which began rolling out to self-hosted WordPress sites in late June 2026, officially deprecates the classic shortcode checkout — meaning merchants still running [woocommerce_checkout] on legacy themes are now operating on unsupported infrastructure. For the estimated 3.2 million active WooCommerce stores worldwide, the pressure to migrate is no longer theoretical.
Agency operators and mid-market DTC founders are scrambling to understand what the transition actually costs — in developer hours, plugin compatibility losses, and conversion rate exposure during switchover. The answers aren’t comfortable.
What Exactly Changed in WooCommerce 9.0?
The 9.0 release formally moves the block-based checkout — introduced as an experimental feature in WooCommerce Blocks 2.6 back in 2021 — to the default and only actively maintained checkout path. Classic shortcode-based checkout will continue to function for existing installs but will no longer receive feature updates, security patches beyond critical CVEs, or compatibility support for new extensions entering the WooCommerce marketplace after August 1, 2026.
The change also affects the Storefront theme and its child themes. Merchants running Storefront versions below 4.5 will see deprecation warnings inside wp-admin beginning July 15, with Automattic pushing hard nudges toward the new default theme, Twenty Twenty-Six Commerce, a block-native theme co-developed with the Gutenberg team.
- Block Checkout: Now the only path for new WooCommerce marketplace extension compatibility post-August 2026
- Classic Shortcode Checkout: Maintenance-only; no new features, no new extension support
- Storefront Theme <4.5: Deprecation warnings active from July 15; full end-of-support December 31, 2026
- PHP Minimum: Raised to 8.2, forcing server environment upgrades for merchants on managed hosting plans below that threshold
- WooCommerce Subscriptions and Memberships: Block checkout compatibility required for version parity with new WooCommerce Payments features
Which Plugins Are Breaking — and Which Vendors Are Ready?
The migration pain is concentrated in the plugin layer. WooCommerce’s extension marketplace lists over 800 plugins, but agency leaders estimate that fewer than 40% have published confirmed block checkout compatibility as of early July 2026.
Among the high-profile casualties: several customization plugins that hook into the classic checkout’s woocommerce_checkout_fields filter — a mechanism that doesn’t carry over cleanly to the block architecture. Checkout field editors from vendors like Checkout Field Editor Pro (ThemeHigh) and some builds of WooCommerce Checkout Add-Ons (SkyVerge/GoDaddy) have required patch releases merchants must manually apply.
Stripe’s WooCommerce plugin (now maintained under the Stripe-branded extension, separate from the legacy WooGateway fork) shipped block checkout support in version 8.4.1 in May. PayPal’s official extension reached block compatibility in June. But smaller regional payment gateways — particularly those used by European and Southeast Asian merchants — remain inconsistently supported.
“We audited 60 client stores last month. Seventeen of them had at least one revenue-critical plugin that wasn’t block-checkout compatible. That’s not a fringe problem — that’s a quarter of a significant agency portfolio sitting on a ticking clock.” — Carla Mendes, Head of Commerce Engineering, Blend Commerce (London)
Blend Commerce, a WooCommerce-specialist agency with roughly $40M in client GMV under management, has begun charging a flat £1,200 migration audit fee before touching any 9.0 upgrade project, Mendes confirmed. She says the audit alone is surfacing compatibility gaps that would have caused checkout failures post-upgrade in about 30% of cases.
What Is the Real Cost of Migrating to Block Checkout?
Developer cost estimates are all over the map, which itself tells a story. Simple stores with fewer than 10 plugins and a modern theme — say, a brand running Astra or Kadence with WooCommerce Payments as the sole gateway — can migrate in under eight hours of billable work. Complex builds are a different matter.
A mid-market apparel brand running WooCommerce on WP Engine with a custom child theme, 23 active plugins, a third-party loyalty integration (in this case, Yotpo Loyalty), and a custom one-page checkout built on CartFlows is looking at 60 to 80 hours of migration and QA work, according to estimates from three agencies contacted for this article. At agency rates of $150–$220/hour, that’s $9,000 to $17,600 before conversion rate risk is priced in.
“The block checkout performs well out of the box — we’ve seen 4% to 7% checkout completion rate improvements on stores with clean migrations. But a messy migration with JavaScript conflicts and broken field validation? That can crater conversion by 10 points while you’re debugging it live.” — Ryan Osei, Founder, Storetasker-certified developer and WooCommerce core contributor
Osei, who has completed 14 WooCommerce 9.0 migrations since the release candidate dropped in May, recommends staging environment testing for a minimum of two weeks before any production cutover — advice that’s obvious in theory but routinely skipped by merchants trying to move fast.
Is This Accelerating Migration to Shopify?
The honest answer: for some merchants, yes. WooCommerce 9.0 is functioning as a forcing function that’s landing at the same time Shopify has made platform migration structurally easier and cheaper than it was even 18 months ago.
Shopify’s Store Importer app — updated in March 2026 to handle WooCommerce product metafields, customer records, and order history with significantly higher fidelity than earlier versions — is being actively marketed to WooCommerce operators by Shopify’s partner channel. Several Shopify Plus Partners contacted for this article confirmed they’ve seen inbound migration inquiries from WooCommerce merchants spike since WooCommerce 9.0’s release candidate went public in May.
LittleData, the analytics connector used by thousands of WooCommerce and Shopify stores, has started offering a migration readiness assessment as an upsell — a sign that vendors adjacent to the WooCommerce ecosystem see platform switching as a near-term revenue opportunity.
- Shopify’s Store Importer now handles WooCommerce product metafields, order history up to 5 years, and customer tags
- Shopify Plus migration credits of up to $10,000 are available for qualifying WooCommerce merchants above $1M GMV
- Several WooCommerce-to-Shopify migration agencies (including Velstar and Swanky Agency) report inquiry volume up 35–40% YoY through Q2 2026
- BigCommerce has launched a parallel WooCommerce migration program offering six months of platform fees waived for stores migrating before September 30
Not every WooCommerce merchant is a Shopify candidate, and agency leaders are quick to say so. Merchants with highly customized checkout logic, complex B2B pricing rules, or deep WordPress content integrations often face higher total cost of ownership on Shopify than they’d expect when licensing fees, app subscriptions, and Shopify Payments transaction fees are properly modeled.
“We’ve converted maybe 12% of our WooCommerce migration inquiries into actual Shopify projects. The rest, when you model it out honestly, either stay on WooCommerce after the upgrade or go to BigCommerce if they want a SaaS exit. Shopify isn’t always the answer, especially once you get above 50,000 SKUs.” — Carla Mendes, Blend Commerce
How Should Merchants Prioritize the WooCommerce 9.0 Upgrade?
For merchants committed to staying on WooCommerce, the sequencing of the migration matters as much as the migration itself. Agencies recommend a four-phase approach:
- Phase 1 — Audit: Inventory every active plugin against the WooCommerce 9.0 compatibility matrix (available at woo.com/document/woocommerce-90-compatibility). Flag payment gateways, checkout field editors, and loyalty/rewards plugins as highest risk.
- Phase 2 — Hosting environment: Confirm PHP 8.2 support with your host. WP Engine, Kinsta, and Pressable all support 8.2 with one-click PHP version switching. Shared hosting environments on older cPanel stacks may require plan upgrades.
- Phase 3 — Staging migration: Run the full 9.0 upgrade on a staging clone. Execute end-to-end checkout tests with real payment gateway credentials in sandbox mode. Test mobile checkout on iOS Safari specifically — the block editor’s field rendering has known quirks on older WebKit builds.
- Phase 4 — Production cutover: Schedule for lowest-traffic window. Have rollback plan documented. Monitor checkout abandonment rate in real time for the first 48 hours post-launch using Hotjar or Microsoft Clarity session recordings.
What Does This Mean for the WooCommerce Ecosystem Long-Term?
Automattic’s push is strategically coherent even if operationally disruptive. The block editor architecture gives WooCommerce a modern, composable foundation that closes some of the developer experience gap with Shopify’s theme and checkout extensibility model. Long-term, it also positions WooCommerce to compete more credibly in the headless and composable commerce conversation — block-based components are easier to surface via the WordPress REST API and compatible with React-based frontends.
But the short-term cost is real ecosystem friction. Extension developers who haven’t shipped block compatibility updates are already losing marketplace placement — WooCommerce.com began deprioritizing non-compatible extensions in search results as of July 1. That’s an existential pressure point for smaller plugin vendors whose entire revenue model depends on marketplace discoverability.
Iconic, a WooCommerce extension developer behind popular plugins including WooThumbs and Flux Checkout, has publicly committed to full 9.0 block compatibility across its entire catalog by July 31. Its Flux Checkout plugin — a single-page checkout replacement that competes directly with CartFlows — is one of the most-watched compatibility cases in the ecosystem, given how many merchants use it as a conversion optimization layer on top of default WooCommerce checkout.
For Shopify and BigCommerce, WooCommerce 9.0’s migration disruption is an acquisition window. Both platforms are resourced to capitalize on it. Whether the merchants who leave WooCommerce during this cycle represent a meaningful GMV transfer or just the long tail of lower-complexity stores remains the open question heading into Q4 2026 planning season.
