Lorixen.
EN

Moving to the WooCommerce checkout block: a safe sequence

Short answer: WooCommerce shops started since version 8.3 (November 2023) already use the Cart and Checkout blocks by default. Older shops often still run the classic shortcode checkout. Switching is worth doing, but in order: audit your payment gateway and extensions for block support, rebuild any custom checkout fields the block way, switch on a staging copy, test real orders, then switch live at a quiet time. Both blocks can be turned back into the classic shortcode with one transform, so you always have a way back.

The checkout is the one page where a small mistake costs money immediately. That's why many established UK shops have postponed this change for years, even as WooCommerce has made the blocks the standard. The good news is that the switch itself is a few clicks. The work is in what surrounds it. Here is a sequence that keeps the risk low.

Week 0: Find out what you're running

Open your Checkout page in the editor. If you see a "Classic Shortcode" placeholder or the [woocommerce_checkout] shortcode, you're on the classic checkout. If you see the Checkout block with inner blocks for contact details, addresses and payment, you've already switched, perhaps without knowing.

WooCommerce's documentation states that for stores started after version 8.3 in November 2023, the Cart and Checkout blocks are the default, with no setup needed. Shops older than that usually kept their shortcode pages.

Write down:

  • your payment gateways (card processor, PayPal, buy-now-pay-later, any bank transfer option);
  • every extension that touches the cart or checkout: delivery date pickers, gift messages, upsells, address lookup, VAT number fields, local pickup tools, subscription plugins;
  • any custom code your developer added to checkout hooks.

Week 1: Check compatibility, one extension at a time

According to WooCommerce, most extensions sold on WooCommerce.com are compatible with the blocks, and you should check each extension's changelog and product description for Cart and Checkout block support, contacting the developer if it's unclear. After installation, WooCommerce shows a warning in the editor when an active extension has declared itself incompatible.

The payment gateway deserves the most attention. The Checkout block documentation explains that the payment methods available depend on your active gateways and whether they support the block, and that the editor's Payment Options panel marks integrations identified as incompatible. A gateway that doesn't support the block may simply not appear to shoppers.

For each item on your list, record one of three outcomes: supports blocks, has a block-compatible update available, or doesn't support blocks (yet). A single "no" on a must-have extension is a reason to wait or find a replacement, not to switch anyway.

Week 2: Rebuild custom fields the block way

Many classic checkouts carry extra fields added with PHP hooks: "How did you hear about us?", a delivery note, a company registration field. Those hooks don't carry over to the block checkout automatically.

WooCommerce's developer docs describe an Additional Checkout Fields approach for the block checkout. Fields can be registered in one of three places:

  • Contact information: saved to the shopper's account and editable in their account details.
  • Address: saved to both the customer and the order; a field registered here appears in both shipping and billing addresses.
  • Order information: saved to the order only, suited to things like a gift message, and placed by default as the last step, though it can be moved in the editor.

Ask your developer to re-register each custom field in the right location and to check where the values now end up in order emails and admin screens. If a plugin provided the fields, check whether it has a block-compatible version.

Week 3: Switch on staging and test like a customer

Make a staging copy of the shop with the same theme, plugins and gateway set to test mode. Then switch: replace the shortcode on the Cart and Checkout pages with the blocks (or use the upgrade prompt if your version shows one). Change both pages together; the documentation notes that the cart and checkout work as a pair, and reverting one means reverting both.

Test at least:

  1. a guest order and a logged-in order;
  2. each payment method, including a declined card;
  3. a coupon, a free-shipping threshold and a local pickup option if you offer one;
  4. each custom field, then check the order email and the order screen;
  5. a small phone, a large phone and a desktop browser;
  6. the order confirmation page and any analytics or ad conversion tracking that fires there.

Check your Store Notices block too. Both templates use it to show messages such as "added to cart", so make sure those appear where shoppers will notice them.

Week 4: Go live, watch, keep the way back open

Pick a quiet trading window, not the start of a sale. Switch the live pages, place one real low-value order yourself, and refund it. Keep an eye on order volume, abandoned checkouts and support emails over the next few days.

If something breaks, WooCommerce documents the way back: select the Cart or Checkout block, use the Transform button in the block toolbar, choose "Classic Shortcode", and save. When an incompatible extension has declared itself, the settings sidebar even offers a one-click switch to the classic checkout.

Common snags during the switch

  • Gateway missing at checkout: the gateway plugin doesn't support the block yet, or needs an update.
  • Custom field gone: it was added with classic hooks and hasn't been re-registered.
  • Theme styling looks off: the block checkout uses its own layout; adjust in the editor or block theme styles rather than with old CSS overrides.
  • Upsell or cross-sell widget vanished: the plugin injects into classic templates; look for a block version.

FAQ

Is the checkout block faster or better for conversions?

WooCommerce describes the blocks as a low-friction checkout designed around conversion. We'd judge it on your own numbers after the switch rather than assume any particular improvement.

Can I keep the classic cart and use the checkout block?

The documentation treats the two as a pair and recommends reverting both together, so plan to move both.

What if my essential plugin isn't compatible?

Stay on the classic checkout for now, ask the plugin's developer about block support, or look for an alternative that supports it. There's no need to rush.

Do I need a block theme?

No. On a classic theme you edit the Cart and Checkout pages; on a block theme you edit their templates in the Site Editor.

If you'd rather not run the compatibility audit alone, send us your list of payment and checkout plugins and we'll map out what needs to change before the switch.

Sources

WhatsAppLet’s talk