Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

WooCommerce · Explainer

WooCommerce Checkout Block vs Classic Checkout

Short answer

The Checkout block is the default for new WooCommerce stores since version 8.3, released in November 2023, and it is the version WooCommerce recommends. The classic [woocommerce_checkout] shortcode still works and is the better choice when a payment gateway or extension you need has no block support. You can switch between the two from the page editor at any time.

Key takeaways

  • The Cart and Checkout blocks became the default for new WooCommerce stores with version 8.3 in November 2023.
  • The classic [woocommerce_cart] and [woocommerce_checkout] shortcodes still work, and WooCommerce still documents them.
  • A payment gateway that lacks block support will not appear on the Checkout block, so check compatibility first.
  • You can switch back with the Transform menu by choosing Classic Shortcode, and you should revert both pages together.
  • The My Account page has no block version, so [woocommerce_my_account] stays in place even on block-based stores.

What is the difference between the Checkout block and the classic checkout?

The Checkout block is a block-based checkout that you edit in the Site Editor, while the classic checkout is the [woocommerce_checkout] shortcode on a plain page.

Both collect the same order details: billing and shipping addresses, a payment method, and an order review. The block version renders its fields as separate inner blocks that you can move or restyle in the editor.

The shortcode version renders one fixed form through PHP templates, so changes need code or a plugin.

WooCommerce made the blocks the default for new stores with version 8.3, released 14 November 2023, according to the WooCommerce developer FAQ. Stores created before that release kept the version they already used. The shortcodes still work, and WooCommerce has not removed them as of November 2026.

What do the Cart and Checkout blocks actually do?

The Cart block shows the items, quantities, prices, and totals on the cart page, and the Checkout block collects the details needed to place an order.

The Cart block combines several smaller blocks to show products, order totals, shipping, and checkout options on one page. Shoppers can change quantities, apply a coupon, and review the total before they move on.

The Checkout block is the main container for the checkout template, and it holds the contact, shipping, billing, payment, and order review steps.

Both pages also use the Store Notices block, which shows messages such as a confirmation when an item is added to the cart. The Mini Cart block gives a quick view of cart contents from other pages, and it opens as a drawer.

You can edit the cart and checkout templates in the Site Editor when your theme is a block theme, as explained in the WordPress template guide.

The blocks work with no setup on a new store. WooCommerce says no customization is required for the block cart and checkout to function.

That means a new store can take orders before any design work. The checkout is ready the moment the pages exist.

What are the classic cart and checkout shortcodes?

The classic cart and checkout are shortcodes, which are small bracketed tags that tell WordPress to print a full page of store content.

[woocommerce_cart] prints the cart page, with cart contents, a coupon field, and basic order totals. [woocommerce_checkout] prints the full checkout form, with billing and shipping fields, payment methods, and the order review.

WooCommerce adds these pages for you during setup, so you only need to type the shortcodes if a page was deleted or rebuilt.

Two more page shortcodes exist: [woocommerce_my_account] shows the account area, and [woocommerce_order_tracking] shows a form that looks up an order by number and email.

There is still no block version of the My Account area, so that page keeps its shortcode even on block-based stores. That fact comes from the WooCommerce page shortcodes doc.

The shortcodes take no settings of their own. Each one prints a full page based on your settings under WooCommerce, then Settings, then Advanced, then Page setup. That is why a shortcode page looks plain in the editor: the real form only appears on the live page.

How do blocks and shortcodes compare side by side?

Blocks give you visual control in the editor, while shortcodes give you wider extension support through the classic PHP hook system.

FeatureCart and Checkout blocksClassic shortcodes
Default for new storesYes, since WooCommerce 8.3 in November 2023No, but still supported
EditingVisual, in the Site EditorFixed form, changes need code
Custom fields and hooksNeeds block integration workClassic PHP hooks work
Payment gatewaysOnly gateways with block support appearAll installed gateways appear
My Account pageNo block version exists[woocommerce_my_account] still used
SwitchingTransform button or block inserterPaste the shortcode on the page

The table shows the trade-off in one line: blocks are easier to shape, and shortcodes fit more extensions. WooCommerce recommends the blocks, but its own docs note that the shortcode versions can have better compatibility with extensions. That is the point to check before you switch a live store.

Which extensions and payment gateways work with the blocks?

An extension works with the blocks only if its developer has added block support and declared it, so you must check each one before you switch.

WooCommerce can warn you in the editor when an active extension has declared itself incompatible with the blocks. The warning names the extension and offers a button to switch to the classic checkout.

If you dismissed a warning earlier, it may not appear again, so check the extension docs too. Extensions that add custom checkout fields through classic hooks usually need extra integration work to support the blocks.

Payment gateways need their own block integration, separate from general extension support. If none of your active gateways supports the Checkout block, the checkout page shows no payment methods at all.

In that case the editor shows a notice in the Payment Options section. Open Configure Payment Options to review your methods, or switch back to the classic checkout.

The core plugin is free and lists more than 100 payment gateways on its WordPress.org plugin page, but each gateway still needs block support of its own.

Before you install an extension, check its changelog and product description for notes on Cart and Checkout block support. If it is still unclear, contact the extension developer, as WooCommerce advises in its customizing guide.

How do you switch from shortcodes to blocks?

To switch, delete the Shortcode block from the Cart or Checkout page and add the Cart or Checkout block in its place.

  1. Open the Cart page in the editor.
  2. Select the Shortcode block and delete it.
  3. Use the block inserter to add the Cart block.
  4. Review the page and save your changes.
  5. Repeat the same steps for the Checkout page.

Switch both pages together, because the cart and checkout blocks work as a pair. Before you switch a live store, place a test order with each payment method you offer.

Confirm that every custom field still appears. If your checkout breaks, see our guide on fixing a checkout that is not working.

Back up your site before the change, and update WooCommerce first if you are behind. Our guide to updating WooCommerce safely walks through the backup and staging steps. As of November 2026, the current release is WooCommerce 11.3.1, dated 19 November 2026 on WordPress.org.

How do you switch back to the classic shortcode checkout?

To switch back, select the Cart or Checkout block, open the Transform menu in the block toolbar, and choose Classic Shortcode.

  1. For a block theme, go to Appearance, then Editor, then Pages, and open Cart or Checkout.
  2. For a classic theme, go to Pages, then All Pages, and edit the Cart or Checkout page.
  3. Open List View and select the Cart or Checkout block.
  4. Click Transform, the leftmost button in the block toolbar.
  5. Choose Classic Shortcode, then save the page.

The block turns into a Classic Shortcode placeholder, and the page works as it did before. WooCommerce advises reverting both pages, since the cart and checkout blocks work together.

If the cart empties after you add a product, the fix is often separate from the block choice, as covered in our guide to fixing an empty cart.

Which one should you choose for your store?

Choose the blocks for a new store with few custom fields, and keep the shortcodes if a gateway or extension you need lacks block support.

A new store has nothing to migrate, so the blocks are the simple choice. They are the default since WooCommerce 8.3, and new block-only features will land there first.

If your checkout uses custom fields, a delivery date picker, or a local gateway that has not added block support, stay on the shortcodes until that extension is updated.

Stores that sell subscriptions or bookings should check those extensions first, because a missing field or gateway at checkout costs orders at once. If you are weighing WooCommerce as a whole, read is WooCommerce worth it before you commit to a setup.

The choice is not final: you can switch in either direction from the editor, so test on staging and keep the version that passes a full test order.

What myths about the blocks and shortcodes should you ignore?

The most common myth is that the shortcodes are gone, but they still work and WooCommerce still documents them as of November 2026.

  • “Shortcodes are removed” — they are not. WooCommerce still lists all four page shortcodes in its docs.
  • “Blocks work with every plugin” — they do not. Each extension must add block support and declare it.
  • “Switching is one-way” — it is not. The Transform menu switches back in a few clicks.
  • “The blocks are only a new look” — they are not. They use a different system, so classic hooks and custom fields do not carry over on their own.

A second myth is that the blocks are always better for sales. WooCommerce describes them as built for conversion, but no public number in its docs promises a set sales lift.

Judge them by a test order on your own store, not by a claim. If the add-to-cart button itself fails, the cause is usually separate, as our guide to fixing the add-to-cart button explains.

What mistakes should you avoid?

The biggest mistake is switching a live checkout without testing every payment method and custom field first.

  • Switching only the checkout and leaving the cart on blocks, or the reverse.
  • Ignoring the incompatible-extension warning in the editor.
  • Placing the Cart or Checkout block straight into a template file instead of the page content.
  • Forgetting that [woocommerce_my_account] has no block version, so the account page keeps its shortcode.
  • Changing the checkout on a live store instead of staging first.

High-performance order storage changes how orders are stored, not how checkout renders, so it does not settle the block question. If you want that background, read what HPOS is in WooCommerce. Test on staging, switch both pages together, and keep the shortcode version ready as a fallback.

Frequently asked questions

Do I have to switch my old store to the Checkout block?

No. Stores created before WooCommerce 8.3 keep the checkout they already use, even after updating. You can switch to the blocks when your extensions support them, or stay on the shortcodes for as long as they meet your needs.

Will my payment gateway work with the Checkout block?

Only if the gateway has added block support. WooCommerce checks the gateways registered on the server against those registered for the block checkout, and a gateway that is missing from the block list will not show up. Check the gateway docs or ask its developer before you switch.

Can I use the blocks with a classic theme?

Yes. With a classic theme you edit the Cart and Checkout pages from Pages, then All Pages, instead of the Site Editor. The blocks work the same way, and you switch back through the same Transform menu on the block toolbar.

What happens if an extension is incompatible with the blocks?

WooCommerce can show a warning in the editor that names the extension and offers a switch to the classic checkout. The missing feature simply will not appear, and in the worst case a payment method may vanish from checkout, so test before you switch a live store.

Is the Checkout block free?

Yes. The Cart and Checkout blocks ship with the free WooCommerce plugin, and there is no extra charge to use them. Paid extensions or gateways you add on top may have their own prices, but the blocks themselves cost nothing.

Sources

  1. Customizing the Cart and Checkout Pages WooCommerce
  2. Page Shortcodes WooCommerce
  3. FAQ: Cart and Checkout Blocks by Default WooCommerce Developer Blog
  4. WooCommerce WordPress.org
  5. Introduction to Templates WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test