Checkout · 7 min read · Jul 7, 2026
Checkout Blocks Can Break More Than the Checkout Layout
A practical review for WooCommerce stores moving from classic checkout to block checkout without losing VAT, company, phone, or tracking data.
Moving to WooCommerce checkout blocks is not only a design change. Older snippets and plugins may depend on classic checkout hooks, and those hooks do not always behave the same way inside the block-based checkout flow.
The risky fields are usually business-critical
The fields that break are often the fields a store notices too late: VAT number, company name, delivery notes, custom phone requirements, invoice details, or internal order metadata.
A checkout can still take payment while silently losing information the business needs for fulfilment, accounting, or B2B compliance.
Do not test checkout only as a shopper
A visual checkout test is not enough. The store should test whether required fields appear, whether values save to the order, whether emails include the expected data, and whether payment and tracking events still fire.
The right question is not “can I place an order?” The right question is “does the order contain every piece of information the business relies on?”
A safer migration pattern
Before switching the live checkout, scan for classic-hook customizations and list fields that must survive the migration. After switching, run a test order for each major customer type: consumer, company, VAT customer, local pickup, and shipped order.
Checkout Blocks Guard focuses on that risk review. Tracking Health Guard is the natural follow-up for analytics and advertising events after checkout changes.