Black FridayCyber Monday 2026
13Days
14Hrs
18Mins
39Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WooCommerce

WooCommerce Checkout Block vs Classic Checkout: Which One Should You Use?

Your checkout is the page that earns the money. Compare the WooCommerce checkout block and the classic shortcode, see what decides the choice, and test a switch safely.

wpallsolution Updated 8 min read

WooCommerce checkout block vs classic is a choice that sounds technical and quietly decides how many customers finish paying. Both versions can take an order. The difference is how they are built, what they support, and what happens when one of your plugins does not understand the one you picked. This guide explains the two in plain language, shows what should decide your choice, and gives you a safe way to test a switch before customers see it.

Quick answer

WooCommerce documents that stores started after version 8.3 (November 2023) use the Cart and Checkout blocks by default, and that you can switch to the classic checkout by transforming the block into a Classic Shortcode block. The right choice depends on your payment gateways and extensions: if a gateway does not support the block checkout, it may not appear as a payment option at all. If everything you use supports the block, the block is the current default. If something important does not, switching to classic, or replacing that extension, may be better. Test either way on staging with a test payment.

How this guide was prepared: the facts follow the WooCommerce documentation listed under Sources, read on October 21, 2026. We did not benchmark the speed or conversion of either checkout, so we make no such claims. We also did not test your gateways or extensions. Statements marked as our advice are practical suggestions, not quotes.

Before you change anything

  • Use a staging copy and a test payment mode. WooCommerce recommends testing payments on a staging site. See WooCommerce checkout not working for safe testing.
  • Back up the site. See Is your WordPress backup really safe?
  • List your gateways and checkout-related extensions (payments, shipping, fields, subscriptions, discounts).
  • Switch the Cart and Checkout together. WooCommerce says the two blocks work together, so when you revert, revert both.

WooCommerce checkout block vs classic: the decision tree

WooCommerce checkout block vs classic flowchart: five questions covering the default, payment gateways, incompatible extensions, custom code and checkout problems
Five questions help you pick the checkout that your store can really support.
  1. Is it a new store on a recent WooCommerce version? Then the block is the default, so start there (Step 1).
  2. Do all your payment gateways support the block? If not, one may not appear at checkout (Step 3).
  3. Does the block editor warn about an incompatible extension? Ask the developer or switch to classic (Step 4).
  4. Do you rely on custom code for the classic checkout? Test on staging first (Step 5).
  5. Is checkout failing right now? Compare both on staging (Step 6).

Symptoms and likely causes

What you seeLikely causeStart with
A payment method is missing at checkoutThe gateway does not support the checkout blockStep 3
“No payment methods” warning on checkoutOnly incompatible gateways are activeStep 3
Editor shows a warning about an extensionAn extension declared itself incompatibleStep 4
A custom field or code snippet stopped workingIt was written for the classic checkoutStep 5
Local pickup option does not showBlock local pickup is not enabled or configuredStep 2
Cart and checkout behave differentlyOne is a block and the other is classicStep 6

6 steps to choose between the WooCommerce checkout block and classic

Step 1: Know which one you have today

Open the Checkout page in the editor. If you see the Checkout block with Checkout Fields and Checkout Totals inside it, you are on the block. If you see a “Classic Shortcode” placeholder, you are on the classic checkout. WooCommerce says the page must also be designated under WooCommerce → Settings → Advanced, so check that the page you edit is the one WooCommerce uses. The documentation adds that stores started after WooCommerce 8.3 use the blocks by default, and that you can still upgrade an older store to the blocks or go back.

Step 2: Understand what the block offers

The Checkout block collects contact, delivery and payment information in one flow. According to the documentation, it has inner blocks you can reposition or rename, settings for address fields (such as showing the company or phone fields and whether they are required), an Express Checkout block that appears only when a supporting gateway is active, a Delivery block that can offer shipping or local pickup, and a Terms and Conditions block with an optional required checkbox. Local pickup in the Delivery block needs the block version of Local Pickup to be enabled and configured under WooCommerce → Settings → Shipping → Local Pickup. In the block editor you also get options such as form step numbers and dark-mode inputs.

Step 3: Check every payment gateway

This is the step that decides most stores. WooCommerce explains that the payment methods available in the block checkout depend on your active gateways and whether they support the block. In the editor, the Payment Options list shows active integrations and marks those identified as incompatible. If a gateway is not compatible, it may not appear as a payment option on the checkout page, and if only incompatible gateways are active, there are no payment methods and a warning is shown. Check your gateway’s documentation for block support, and test a real flow in the gateway’s test mode.

Step 4: Check your other extensions

WooCommerce says compatibility for extensions on WooCommerce.com is shown in the Compatibility section of each product page. If an extension has declared itself incompatible, the Checkout block’s settings sidebar shows a warning and a button to switch to the classic checkout in one click. Incompatible extensions can make parts of the checkout unavailable. For third-party plugins, WooCommerce suggests contacting the developer. Our advice: if the extension is important and its developer has no block support plan, weigh staying on classic against replacing it.

Step 5: Think about custom code and design changes

Custom fields, code snippets and theme overrides that were written for the classic checkout may not carry over to the block, because the block is built differently. This is general practice rather than a WooCommerce quote, so test it: list your customizations and check each one on a staging copy in both versions. If you are not sure what your site relies on, our WooCommerce checkout service can audit it, and a slow page is a separate problem covered in why WooCommerce checkout is slow.

Step 6: Switch on staging, then test like a customer

WooCommerce documents the switch to classic: edit the Cart or Checkout page (Appearance → Editor → Pages for a block theme, or Pages → All Pages for a classic theme), open the List View, select the block, use the Transform button in the block toolbar, choose Classic Shortcode, and save. Do this for both Cart and Checkout. To go back, you add the block again following the same documentation. After each change, run a full test order: guest and logged in, with a coupon, with each shipping method and each payment method, on phone and desktop, and check the emails. Only then repeat on the live site, at a quiet time. If anything fails, see WooCommerce checkout not working.

Version and hosting differences

  • The default behaviour described here applies to stores started after WooCommerce 8.3. Older stores may still be on the classic shortcode.
  • Block themes and classic themes differ in where the template is edited.
  • Gateways, subscriptions and shipping extensions each have their own block support status and timetable.
  • Caching and security rules affect both versions, so keep Cart, Checkout and My Account out of the cache. See WooCommerce cart empty after adding products.

How to verify the fix

  • Every payment method you expect appears at checkout, on both desktop and mobile.
  • A test order completes, the order appears in WooCommerce → Orders and the emails arrive.
  • Shipping, coupons and taxes still calculate correctly.
  • Both Cart and Checkout are the same type (both block or both classic).

How to prevent it from happening again

Frequently asked questions

Is the block checkout the default?

WooCommerce documents it as the default experience for stores started after version 8.3 (November 2023). Older stores can be upgraded.

Can I switch back to classic?

Yes. The block toolbar has a Transform option to a Classic Shortcode block, and you should switch Cart and Checkout together.

Why is my payment method missing?

The gateway may not support the checkout block. Check the Payment Options list in the editor and the gateway’s documentation.

Which one is faster?

We have not measured it and will not guess. Test your own store with a tool like PageSpeed Insights and compare.

Related guide: WooCommerce HPOS: What High-Performance Order Storage Is and How to Enable It Safely

What to do next

List your gateways and extensions, check each for block support and test both versions on staging. If your WooCommerce checkout is failing, or you are unsure what your store relies on, wpallsolution offers a WooCommerce checkout service and independent plugin support. We cannot promise results without seeing your setup.

Sources and official documentation

Last reviewed: October 21, 2026. WooCommerce is a trademark of its owner. wpallsolution is not affiliated with or endorsed by WooCommerce or Automattic.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us