E-commerce 31 Mar 2026 6 min read

Block checkout or classic checkout in WooCommerce – which should your store use?

New stores should use the block checkout. If your store has checkout customisations or payment and shipping plugins without block support, plan the switch as a small project.

Kristoffer Pihlfelt

Developer and founder, Pihlfelt & Vänner

If you are starting a new store, or your store has few checkout customisations, choose the block checkout. It has been the default in new WooCommerce stores since late 2023, and it is where WooCommerce is focusing its development. If your store already has checkout customisations, or payment and shipping plugins that do not support the block checkout, stay on the classic checkout until you have gone through every part. Switching is not hard, but it should be handled as a small project with testing, not by flipping a setting on an ordinary Tuesday.

What separates the two checkouts for a store owner

To the customer, the two checkouts look fairly similar: address, shipping, payment, button. The difference lies in how they are built and how they are changed.

  • The block checkout is built in the normal WordPress editor, using blocks. Order, headings and some fields can be changed without a developer, and it has built-in support for express payments such as Apple Pay and Google Pay at the top of the checkout if your payment provider offers them.
  • The classic checkout is the one that has existed since WooCommerce began. It is changed with code or extensions, and almost every extension ever written for WooCommerce works with it.

The key point is that the technology underneath is completely different. An extension or customisation built for one checkout does not automatically work in the other. That is why choosing a checkout is first and foremost a compatibility question, not a design question.

Compatibility with payment and shipping plugins

Start with the extensions that handle money and deliveries. Go through them one at a time:

  • Payments: cards, Klarna, Swish (the Swedish mobile payment app), invoice and any instalment options. Does the extension's page say it supports cart and checkout blocks?
  • Shipping: especially extensions where the customer chooses a pickup point or delivery time. These are often the last to get full support.
  • Other checkout features: fields for company registration numbers, gift cards, discount rules, terms checkboxes and newsletter sign-up.
  • Tracking: tools that measure purchases and checkout steps for analytics and advertising. If they break, you will not notice in the checkout, only in the reports weeks later.

WooCommerce itself shows a warning in the editor when an active extension does not support the block checkout. That warning is a good start but not the whole story, because custom code in your theme does not show up there.

Customisations you already have

Over the years many stores have collected small additions in the checkout: an extra field, a note about delivery times, a rule that hides a payment method for certain products. In the classic checkout these are often a few lines of code in the theme. When you switch, none of it comes along by itself.

That is because customisations are done differently in the two checkouts. A custom field in the block checkout is registered in a way that lets WooCommerce handle display and saving, while the same field in the classic checkout is built and saved in an entirely different way. For you as a decision-maker the point is simple: every customisation needs to be redone, and that takes time.

Cost and risk of switching

The cost depends almost entirely on how much has been customised. A store with standard extensions that all support the block checkout can switch in a day, testing included. A store with several custom checkout rules, an older shipping plugin and custom-built tracking may need a few weeks of work, because each part has to be rebuilt or replaced.

The risks are concrete:

  • A payment method disappears from the checkout and nobody notices until sales drop.
  • Shipping prices or pickup points behave differently than before.
  • A field is shown to the customer but the value never reaches the order, the order email or the export to shipping and accounting.
  • Conversion tracking stops working and advertising data becomes wrong.

What makes the switch manageable is that you can go back. The classic checkout is still available in WooCommerce, and switching back takes minutes if something unexpected happens.

How to make the decision

Ask four questions:

  1. Do all our payment and shipping plugins explicitly support the block checkout?
  2. What customisations do we have in the checkout today, and who knows where they are?
  3. What do we concretely gain, such as express payments or easier changes without a developer?
  4. Is there a quiet period in the coming months when the switch can be made?

If the answers are yes, few, something concrete and yes, it is time. If an important extension lacks support, there is no reason to rush. Wait, or replace that extension first as a separate step.

How to test before you switch

Make the switch in a copy of the store, not the live one. Then test as a customer and as the person who handles the order:

  • Place a real order with every payment method, ideally a small amount that you refund.
  • Try every shipping option and a few postcodes, on both desktop and mobile.
  • Check that custom fields appear on the order, in the order email and in what is sent to shipping and accounting.
  • Confirm that the purchase is recorded in your analytics and advertising tools.

Then make the switch in the live store on a low-traffic day and watch the first orders closely.

Our recommendation

New stores should use the block checkout. Existing stores should plan for it, but switch only once payment and shipping plugins support it and the customisations have been mapped. It is a decision that can be made calmly, but not one to postpone for years. If you want help reviewing your checkout and making the switch, that kind of work fits naturally into a WordPress and WooCommerce maintenance agreement, or as part of our WooCommerce development.

Share: