The classic WooCommerce checkout based on the [woocommerce_checkout] shortcode is now in maintenance-only mode – it gets security fixes only, no new features. The future is the block checkout, but before you switch, check your payment gateways, customisations and conversion tracking, because those are what most often break during migration. You do not have to do it overnight, but it is worth planning before a missing feature blocks your store.
Below I explain, without jargon, what changes, what can genuinely stop working, and how to migrate safely.
What actually changes
For a while now, WooCommerce has been moving the cart and checkout from the old shortcode-based pages to new blocks (the Cart Block and the Checkout Block). Version 10.6, from March 2026, added further improvements that accelerate the move away from the classic solution.
In practice this means three things:
- the classic checkout is maintained but not developed – it gets security fixes, but no new features,
- new integrations target the blocks – some new capabilities appear only in the block checkout,
- new stores start on blocks already – that is the default direction.
In other words, this is not an outage, just a slow closing of the old path. The longer you wait, the greater the risk of being stuck on an unsupported solution.
Why this may concern you
If you have a simple, standard store, migration can be almost painless. The trouble starts where something has been customised. And there are plenty of stores like that.
The reason is technical: the classic checkout relied on PHP hooks (for example woocommerce_checkout_fields or woocommerce_after_order_notes) that the block checkout no longer supports the same way. Some actions and filters will work, some will not. If your store depends on them, they have to be moved to the new way of extending the checkout.
What can break during migration
Here is a list worth checking before you switch the checkout live:
- extra form fields (tax ID, notes, consents, delivery fields) based on old hooks,
- payment gateways – most major ones already support blocks, but older or niche solutions may not,
- plugins that edit the checkout (field editors, surcharges, conditional logic) – they need a block-compatible version,
- conversion tracking – events like “add to cart”, pixels and GA4 goals can stop counting after the cart changes, which hits your campaign data directly,
- custom styles and layout of the checkout, if they were built for the old HTML.
None of these points is a death sentence – but each has to be checked, not assumed to “just carry over”.
What you gain with blocks
Migration is not only an obligation. The block checkout has real advantages:
- it is faster and lighter, which matters especially on mobile,
- it works better on mobile, where most purchases are completed today,
- it receives new features and integrations the classic one will never see,
- fewer abandoned carts thanks to a smoother checkout.
For a store that genuinely sells, those differences translate into money.
How to migrate safely
The order that protects you from surprises:
- Back up the whole store – a starting point you can always return to.
- Audit customisations, plugins and gateways – list what modifies the checkout today and whether it has a block-compatible version.
- Test on a copy (staging) – switch the checkout to blocks on a copy, not on the live store.
- Check fields and validation – whether all the needed fields are there, work and save correctly.
- Test payments and the whole purchase path – from cart to order confirmation, across different payment methods.
- Verify tracking – whether events, pixels and goals still count.
- Deploy to production – only once the copy works flawlessly.
When you can still stay on the classic checkout
If your checkout is heavily customised, works, and you do not need new integrations – you can still wait. But treat it as postponing, not a solution. Since the classic checkout will not be developed, migration is coming sooner or later. Better to plan it calmly than in a rush when something stops working.
Summary
The block checkout is the direction WooCommerce has already taken, while the classic one is merely maintained. For simple stores migration can be easy; for customised ones it requires checking gateways, fields, plugins and conversion tracking. The key is a backup and a test on a copy before anything reaches the live store.
If you have a WooCommerce store with customisations and do not want to risk something breaking during migration – get in touch. I will run an audit, test the checkout on a copy and carry out the migration so that neither sales nor conversion tracking suffer.
FAQ
Do I have to move to the WooCommerce block checkout?
Not overnight, but it is the direction WooCommerce is going. The classic shortcode checkout is now in maintenance-only mode (security fixes only, no new features), and new integrations target the block checkout exclusively. It is worth planning the migration before a missing feature blocks you.
What can break when migrating to Checkout Blocks?
Most often customisations based on old PHP hooks (e.g. extra fields, form tweaks), some payment gateways, plugins that edit the checkout, and tracking of events like add-to-cart. That is why migration is done after an audit and on a test copy, not straight on the live store.
Is the block checkout better?
Usually yes: it is faster, works better on mobile, and receives new features and integrations the classic one no longer will. That translates into fewer abandoned carts. The condition is moving over what you have configured today correctly.
Will I lose data or orders during migration?
No, the migration concerns how the cart and checkout are displayed, not the products or orders themselves. The risk lies in customisations and integrations, which is why a backup and a test on a copy before going live are essential.
