In partnership with

Hi, {{first_name|friend}}. 👋

Welcome to Issue #196 of Loop WP!

Last week was the final part in our series as we compared and contrasted Beau’s answers with Matt Mullenweg’s and a dash of my thoughts sprinkled in, too.

This week is about the block and classic checkouts in WooCommerce. The results may surprise you.

Let’s go! 👇

Vibe code with your voice

Vibe code by voice. Wispr Flow lets you dictate prompts, PRDs, bug reproductions, and code review notes directly in Cursor, Warp, or your editor of choice. Speak instructions and Flow will auto-tag file names, preserve variable names and inline identifiers, and format lists and steps for immediate pasting into GitHub, Jira, or Docs. That means less retyping, fewer copy and paste errors, and faster triage. Use voice to dictate prompts and directions inside Cursor or Warp and get developer-ready text with file name recognition and variable recognition built in. For deeper context and examples, see our Vibe Coding article on wisprflow.ai. Try Wispr Flow for engineers.

It Started With A Poll

Last week, Rodolfo Melogli (Business Bloomer & Checkout Summit) asked in a Twitter (X) poll: “Do you use the new block, or are you still on legacy/classic/shortcode?”

Based on 64 votes:

  • Block checkout 32.8%

  • Classic checkout 67.2%

The Block checkout adoption surprised me (even though it’s the default for new stores).

It seemed too high 🤔.

Then Maarten Belmans (Studio Wombat) took things a step further. 👇

10,000 Websites

Maarten was able to analyse a subset of 10,000 of his customers. The custom script checked for two things:

  • Is the website still built on WooCommerce?

  • Does the site use the Cart/Checkout blocks?

The Results

  • 5% moved to Shopify.

  • 87% of sites are on Classic layouts.

  • 13% of sites are on Block layouts.

💡 To me, this is a good data set to work with and large enough to show that the block adoption rate for the cart/checkout is much lower than that in Rodolfo’s poll.

🚨 Interestingly, Maerten also provided additional data taking into consideration the adoption rate since the block checkout/cart became the default, in which case 13% > 18%.

The scraper couldn't determine the layout of 3k sites for various reasons:

  • 404 errors due to misconfiguration,

  • 403 errors due to maintenance mode, password protection, etc.

(Maarten did say he could catch more sites, but would need to look into the errors more closely for ways to do that.)

Maarten’s Thoughts

I asked Maarten, “Did you have a hypothesis or assumptions before the research, and were they reinforced?” He answered as follows:

a) “I thought more sites would have moved to Shopify, so that's good news. Bad news: about 5k sites didn't exist anymore (404 on home page), so there's still plenty of sites that are no longer running Woo.

b) I expected less sites using the block layout, tbh.”

I am also surprised more sites have not moved to Shopify, but sadly, not surprised by the number of sites that no longer exist (eCommerce is not easy).

Why Do Most People Still Use Classic?

Like Maarten, I expected fewer sites to be using blocks for the checkout/cart, but James Kemp (Core Product Manager for WooCommerce) noted these numbers align with what Woo is seeing.

🤔 So, based on James’ comment and Maarten’s data, if 87% of WooCommerce users don’t use the block cart/checkout, why is that?

The truth is, there are many reasons:

  • “If it’s not broken, don’t fix it” A lot of store owners (especially those without a Dev) won’t want to switch if everything is working now (switching a checkout is a big deal).

  • Feature parity or lack thereof. Many things were possible with the classic checkout that are not possible in the new block checkout.

  • James Kemp said the “biggest issue I'm seeing for adoption is many plugins aren't compatible with the blocks checkout, so Classic is the only option.“

  • Ian Misner (General Manager Kestrel) added further to James’s comment that “it's not possible to 'catch up'. It's [block checkout/cart] not extensible ‘by design’” and draws attention to Woo’s Extensibility Principles.

💡 I echo both James and Ian’s comments, based on first-hand experience building an Address Autocomplete plugin. I documented the comparative ease of building for the classic checkout compared to the block checkout (which I eventually got working with some help).

However, a quick Google search shows stories over the years, and still now, with plugin compatibility issues using the block cart/checkout.

Increased Conversions

💡 The classic checkout is not perfect, and there are lots of plugins and themes which exist to improve the classic checkout experience and increase conversions, whether that be:

  • A single-page, clean checkout

  • A stepped checkout process

However, James Kemp argues: “We do see a 27% increase in checkout conversions when using the block checkout vs classic!”

I asked James more about this number:

  • Any thoughts on why that is for the increased conversions?

  • And is that in comparison to the Classic Checkout with no modifications?

James said:

“I expect because it’s a more controlled experience.

It’s compared against data from stores using classic vs blocks, so not like for like.”

💡 I agree, the block checkout/cart is much cleaner and better than the default classic cart without any modifications, and it’s fast too, so it’s understandable that the conversion rate is considerably higher.

Best of Both Worlds

I am still not a massive fan of the block editor, though the likes of Brian Coords and Mike McAlister show what’s possible, and there are solutions that would allow the best of both worlds.

ThemeSwitcher would allow you to have a block them for your site and a classic cart/checkout experience, if you wanted to investigate that option.

Final Thoughts

💡James Kemp feels that, over time, as it [block checkout/cart] becomes more extensible, we should see greater adoption, and while that’s a logical presumption, I think the adoption of the block editor and FSE as a whole will have a determining impact.

What are your thoughts, {{first_name|friend}}?

  • Have you switched to the block checkout/cart?

  • Do you have plans to switch anytime soon?

  • When (if) will the point come when we are all forced to switch?

Reply and let me know.

That’s it for this week. 👋

Privacy-first email. Built for real protection.

End-to-end encrypted, ad-free, and open-source. Proton Mail protects your inbox with zero data tracking.

Sponsorship Opportunities

🚨 The Google Doc contains all the details if you’re interested in sponsoring the Loop WP Newsletter.

Classifieds

Get access to WooCommerce tutorials, a private community powered by humans, and exclusive learning content with the Business Bloomer membership.

How fast is your website, and what’s slowing it down? Find out with the free DebugBear website speed test.

Leave single-server hosting in 2015. Choose autoscaling Managed WordPress Hosting built for traffic surges, complex sites & demanding PHP workloads - without missing a beat.

Kinsta, a reliable hosting partner for your WordPress sites. Everything you need: edge caching, CDN, WAF, 24/7 support, free migrations and much more.

Weekly WordPress News & Tips

This week's excellent and insightful WordPress News & Tips:

  • Personal Negotiation - Automattic, Mullenweg Asks Court to Keep Details of WordPress.org Hosting Negotiations Private. (The Repository)

  • ACP Optimisation - A Technical Guide To Prepare For Google’s UCP. (Search Engine Journal)

  • WooCommerce 10.6 - What’s coming for developers. (Woo Dev Blog)

  • AI Search - 14 GEO Conferences to Attend in 2026. (ahrefs)

  • Credits Program - How WordPress Is Reaching the Next Generation of Contributors. (The WP Minute)

  • Press Release - The WP Community Collective Expands Board of Directors. (The WPCC)

  • Accessibility Education - Support WP Accessibility Day at WordCamp Europe. (WP Accessibility Day)

  • Intervention - WordPress 7.0 Beta 1 Ships After Delay as Project Leadership Realigns Release Around AI and Milestone Story. (The Repository)

  • wp-devdocs-mcp - A tool that stops AI coding assistants from hallucinating WordPress hook names. (Marcel Schmitz)

  • Homepage Schema - There are two types that I gravitate towards and recommend (especially for eCommerce stores). (Brodie Clark)

  • Code Mode - Give agents an entire API in 1,000 tokens. (Cloudflare)

  • WP:26 - Discover where WordPress is heading in 2026. (Human Made)

  • The Wrong Starting Place - Stop trying to rank for keywords. (Jono Alderson)

If you have a question about this email or WordPress, please reply, and I will respond as soon as possible.

👋 Until next time,

Keep Reading