One of the most common frustrations WooCommerce store owners encounter after updating to a recent version of WooCommerce is discovering that their checkout field customizations have stopped working. Custom fields that were carefully configured are missing. Conditional logic is not triggering. Required fields are not validating. The checkout that took hours to set up looks and behaves like the default form again. In most cases, the cause is the same: the store has migrated to the WooCommerce Blocks checkout, and the checkout field editor plugin being used was built exclusively for the classic shortcode-based checkout that WooCommerce is leaving behind.
This is not a minor compatibility inconvenience. WooCommerce Blocks represents the future architecture of the WooCommerce checkout experience. WooCommerce has been actively investing in the block-based checkout since its introduction and has made it the default for new installations. Stores that have not yet migrated will eventually face this transition, and stores that have already migrated need checkout field tools that are genuinely built for the new environment — not patched onto it with workarounds that may break again with the next WooCommerce update.
This guide covers everything you need to know: what WooCommerce Blocks actually is and how it differs architecturally from the classic checkout, why most checkout field editor plugins fail on Blocks, what genuine Blocks compatibility means and how to verify it, and how the NEXU Advanced Checkout Field Editor with full WooCommerce Blocks support handles both checkout environments correctly in 2026.
Whether you are currently on the classic checkout and planning a migration, already on Blocks and experiencing field editor problems, or setting up a new store and choosing tools from scratch, this guide gives you the context to make the right decisions.
What WooCommerce Blocks checkout actually is
To understand why checkout field editor compatibility is such a significant challenge in 2026, you first need to understand what WooCommerce Blocks is and how it differs from the classic checkout that most plugins were built for.
The classic WooCommerce checkout — the one that has powered the vast majority of WooCommerce stores for over a decade — is built using a PHP shortcode:
WooCommerce Blocks checkout works completely differently. Instead of a PHP shortcode, it uses a Gutenberg block — the WooCommerce Checkout block — which renders the checkout form using React.js on the client side. The entire checkout form is a JavaScript application that communicates with the WooCommerce backend via a REST API. There are no PHP template hooks for the checkout form itself. The rendering happens in the browser, not on the server.
Classic checkout: WooCommerce builds the form on your server and sends the completed HTML to the browser. Plugins can modify this form by injecting HTML via PHP hooks before it leaves the server. Blocks checkout: WooCommerce sends a React application to the browser, and the browser builds the form. Plugins cannot inject HTML via PHP hooks into a React application because the HTML does not exist on the server — it is generated on the client. Plugins must instead use WooCommerce’s JavaScript extension APIs to interact with the Blocks checkout.
This architectural shift is fundamental. A checkout field editor that works on the classic checkout by hooking into woocommerce_checkout_fields, woocommerce_checkout_after_customer_details, or similar PHP hooks will have no effect whatsoever on a Blocks checkout. Those hooks do not fire in the Blocks environment. The plugin appears to work (the settings save without errors), but nothing actually renders in the checkout form. This is why store owners often describe the issue as “my custom fields disappeared” after migrating to Blocks — they did not disappear from the plugin, they were never rendered by it in the Blocks environment.
Which stores are on WooCommerce Blocks checkout in 2026
As of 2026, WooCommerce’s Blocks checkout is the default for new WooCommerce installations. Any store that installed WooCommerce in the past couple of years and did not manually switch to the classic checkout shortcode is likely running the Blocks checkout. This represents a significant and growing portion of all active WooCommerce stores.
Almost certainly on Blocks checkout by default. If you set up your store in the last two years without specifically switching to the classic checkout, you are using WooCommerce Blocks. Your checkout field editor needs Blocks compatibility.
Stores that consciously migrated from the classic shortcode to the Blocks checkout. These store owners are most likely to have discovered the field editor compatibility problem first-hand — it is often the migration itself that exposes the issue.
Older stores still running the classic
Check your checkout page in the WordPress block editor. If the checkout is built with a Checkout block, you are on WooCommerce Blocks. If you see the shortcode
Even for stores currently running the classic checkout, the future trajectory is clear. WooCommerce has publicly committed to the Blocks architecture as the long-term direction for the platform. Choosing a checkout field editor that only supports the classic checkout means choosing a tool that will require replacement when the migration to Blocks happens — and in 2026, that migration is something every WooCommerce store owner should be planning for if they have not already undertaken it.
How to check which checkout version your store is using right now
Before getting into plugin compatibility details, it is worth knowing with certainty which checkout version your store is currently running. Here is how to check.
In your WordPress admin, go to Pages and find your Checkout page. Click Edit. If the page content shows a block labeled “Checkout” with a WooCommerce icon and a React-rendered preview of the checkout form, you are using WooCommerce Blocks checkout. If the page content shows a text block containing
Visit your checkout page in a browser and view the page source (right-click, View Page Source). Search for wc-blocks or wp-block-woocommerce-checkout. If either string appears in the source, you are on the Blocks checkout. If you see woocommerce-checkout as a form class without the blocks references, you are on the classic checkout.
In your WordPress admin, go to WooCommerce > Status > Pages. This shows the status of your WooCommerce core pages including the Checkout page. The page status information will indicate whether the checkout page uses the WooCommerce Checkout block or the classic shortcode.
Why most checkout field editor plugins fail on WooCommerce Blocks
Understanding the specific failure modes of classic checkout field editors on the Blocks checkout helps you diagnose problems and evaluate whether a plugin’s claimed “Blocks compatibility” is genuine or superficial.
The most common failure mode. The plugin’s admin interface works normally — you can create and configure fields, set conditional logic, save settings. But none of it appears on the Blocks checkout page. The custom fields simply do not render. This happens because the plugin injects fields via PHP hooks that do not fire in the Blocks checkout environment. From the plugin’s perspective, everything is configured correctly. From the Blocks checkout’s perspective, the plugin simply does not exist.
Even when a plugin manages to partially render fields on the Blocks checkout through various workarounds, the required field validation often does not work correctly. Classic checkout validation runs on the server side when the form is submitted. Blocks checkout validation is handled client-side by the React application before the form submission even reaches the server. A plugin that adds server-side validation hooks will not prevent Blocks checkout form submission when a custom required field is left empty.
Even if a field renders and the customer fills it in, the data may not be saved to the WooCommerce order. Classic checkout field data is saved via WooCommerce’s checkout processing PHP hooks. Blocks checkout processes orders via a REST API endpoint that bypasses these classic PHP hooks entirely. A plugin relying on the classic data-saving hooks will not capture field values for orders placed through the Blocks checkout, leaving fields that appear to work but silently discard their data.
Cart-based and field-value conditional logic in classic field editors typically works through JavaScript that listens to events on the classic WooCommerce checkout form — field change events, cart update events, and similar DOM interactions. The Blocks checkout uses a completely different React state management system. Classic conditional logic JavaScript does not connect to the Blocks checkout’s state, meaning conditions never trigger, fields never show or hide in response to cart changes, and the entire conditional field system is non-functional.
What genuine WooCommerce Blocks compatibility actually means
Because “WooCommerce Blocks compatible” has become a marketing phrase that different plugins use to mean different things, it is worth being specific about what genuine compatibility requires technically. There are four distinct capability areas that a checkout field editor must address to be genuinely Blocks-compatible.
Genuine Blocks compatibility requires that the plugin uses WooCommerce’s official Blocks extension API — specifically the __experimentalRegisterCheckoutFilters and related JavaScript APIs — to inject custom fields into the Blocks checkout. Fields rendered this way are properly integrated into the React component tree, receive the correct styling context, and behave as native elements of the Blocks checkout rather than as afterthoughts injected via DOM manipulation.
Required field validation must be integrated with the Blocks checkout’s React state management — not handled as a separate server-side check after the form submits. When a customer attempts to place an order without completing a required custom field, the Blocks checkout’s native validation system must catch it, display the appropriate error message, and prevent order submission. This requires the plugin’s validation logic to communicate with the Blocks checkout application state.
Custom field values must be saved to WooCommerce orders through the Blocks checkout’s order processing pipeline — which flows through a REST API endpoint rather than PHP form submission hooks. The plugin must register its custom data with the Blocks checkout’s data store and ensure that data is included in the REST API order creation payload, then handle saving it to the order metadata on the server side when the API request is received.
Conditional field logic — show/hide based on cart content, shipping method, or other field values — must hook into the Blocks checkout’s React state system. The plugin needs to observe state changes within the Blocks application (cart updates, shipping method selection, field value changes) and reactively show or hide fields by updating their visibility state through the React component tree, not by manipulating the DOM with classic JavaScript event listeners.
How to verify that a checkout field editor is genuinely Blocks-compatible
Marketing claims are not a reliable way to evaluate Blocks compatibility. The only reliable method is direct testing. Here is a structured testing protocol you can run in an hour that will tell you definitively whether a checkout field editor is genuinely functional on your WooCommerce Blocks checkout.
Create a simple text field in the plugin and give it a distinctive label. Go to your Blocks checkout page in an incognito window. Does the field appear? If not, the plugin has zero Blocks rendering support. If it does appear, proceed to the next test.
Mark the text field as required. Leave it empty and attempt to place an order. Does the Blocks checkout stop you with an error message referencing the empty required field? If the order goes through anyway, the required validation is not working. If a different error appears (unrelated to your field), the validation may be absent.
Enter a distinctive test value in the field (e.g. “BLOCKS-TEST-VALUE-123”) and complete a test order. Find the order in WooCommerce admin and check the order details. Does the value “BLOCKS-TEST-VALUE-123” appear? If not, data is not being saved. This is a critical failure — fields that look functional but silently discard data are worse than fields that do not appear at all.
Set up a conditional field that should appear only when a specific product is in the cart. With a different product in the cart, confirm the field is hidden. Add the trigger product and confirm the field appears without a page reload. Remove the trigger product and confirm the field disappears. All three states must work correctly.
Set up a field that appears when a checkbox (the trigger) is checked. Confirm the dependent field is hidden when the checkbox is unchecked. Check the checkbox and confirm the dependent field appears immediately. Uncheck and confirm it disappears. All transitions must happen reactively without page reloads.
If a plugin passes all five tests, it has genuine Blocks compatibility. If it fails any of them, the specific test it fails tells you exactly where the Blocks support ends. Most plugins that claim Blocks compatibility pass Test 1 (basic rendering) but fail Tests 2, 3, 4, or 5 — meaning they have partial support that gives a false impression of full compatibility until you discover the gap during actual store operation.
Dual-environment support: why you need a plugin that works on both checkout types
Even if you are currently running the Blocks checkout, there is a practical reason to choose a checkout field editor that supports both classic and Blocks environments: flexibility during transitions.
Stores sometimes need to temporarily revert from Blocks to the classic checkout during a troubleshooting process, a theme conflict investigation, or while waiting for another plugin to add Blocks support. If your checkout field editor only supports Blocks, switching back to the classic checkout for any reason means your custom fields disappear until you switch back. A plugin that supports both environments maintains your checkout field configuration regardless of which checkout type is active.
The NEXU Advanced Checkout Field Editor handles both checkout environments from a single configuration. The field setup, conditional logic, per-product fields, and all other configurations you make in the plugin admin apply correctly whether your store is currently on the classic shortcode checkout or the WooCommerce Blocks checkout. There is no separate configuration for each environment — the plugin detects which checkout is active and handles rendering, validation, and data saving through the appropriate mechanism for that environment.
This matters practically during the migration process. A store that is planning to migrate from classic to Blocks checkout can make the switch confident that their custom field configuration will continue working correctly on the other side — no reconfiguration required, no rediscovery of which fields were set up and how, no regression testing to confirm that the post-migration checkout still behaves as intended.
The WooCommerce Blocks development landscape in 2026
Understanding where WooCommerce Blocks is in its development trajectory helps you make informed decisions about your store’s checkout architecture going forward. The Blocks checkout has matured significantly since its early experimental releases, and the API surface that plugins like the NEXU Advanced Checkout Field Editor use to integrate with it has stabilized considerably.
According to the WooCommerce developer documentation for Blocks, the extension APIs for cart and checkout blocks have moved from experimental to stable designations for core functionality. The filters and slots that third-party plugins use to inject custom content and behaviors into the Blocks checkout are now considered stable APIs that WooCommerce commits to maintaining backward compatibility for.
This stability is important because it was one of the early concerns about Blocks compatibility — plugin developers were hesitant to build deeply integrated Blocks support against APIs labeled “experimental” that might change breaking changes without warning. The stabilization of core extension APIs in 2024 and 2025 has made it viable to build production-quality checkout field editors with deep Blocks integration, which is the foundation of the NEXU Advanced Checkout Field Editor’s current implementation.
WooCommerce’s public roadmap and developer communications in 2025 and 2026 have consistently signaled continued investment in the Blocks checkout as the primary checkout experience going forward. The classic shortcode checkout will remain available and functional, but new checkout features will increasingly be developed for Blocks first. For stores choosing checkout tooling in 2026, the practical implication is clear: the right time to ensure your checkout field editor has genuine Blocks compatibility is now, before the classic-to-Blocks transition becomes a harder constraint rather than a choice.
Migrating your checkout field configuration to WooCommerce Blocks
If you are currently on the classic checkout and planning a migration to WooCommerce Blocks, here is how to approach the checkout field configuration aspect of the transition to minimize disruption.
Document every custom field currently active on your checkout — field type, label, conditional rules, which products they are attached to, and required/optional status. Export your current configuration using the NEXU plugin’s JSON export feature if you are already using it. This documentation is your baseline for verifying the post-migration state.
Switch to the Blocks checkout on a staging copy of your site, not on your live store. Run the five-test verification protocol described earlier in this guide against your staging environment. Confirm every field renders, validates, and saves data correctly. Fix any issues before touching the live site.
When you are confident the staging environment is working correctly, switch the live site’s checkout page to use the Blocks checkout block. Do this during your lowest-traffic period — typically early morning on a weekday. Have the classic checkout page ready to quickly revert to if any issues emerge.
Immediately after switching to Blocks on the live site, place a test order that exercises all of your custom fields. Verify the order in the WooCommerce admin shows all field values correctly. Check the order confirmation email. Confirm required fields block submission when left empty. Only after successful verification should you consider the migration complete.
What the NEXU Advanced Checkout Field Editor does on WooCommerce Blocks
To be concrete about what Blocks compatibility looks like in practice, here is a summary of how the NEXU Advanced Checkout Field Editor’s features function specifically on the WooCommerce Blocks checkout environment.
Checkout field customization is not a luxury feature for WooCommerce stores — it is a core operational requirement for any store with product types, customer segments, or fulfillment workflows that do not fit the generic default form. And as WooCommerce’s architecture evolves, the ability to implement that customization in the Blocks checkout environment becomes an increasingly fundamental requirement rather than a nice-to-have.
Choosing a WooCommerce checkout field editor with verified Blocks compatibility for 2026 means choosing a tool that your store will not outgrow as the platform evolves. The configuration work you invest in your checkout today — the conditional logic, the per-product fields, the custom field types — should be an asset that continues working through future WooCommerce versions, not a liability that needs rebuilding every time the platform architecture advances.
A checkout field editor built for WooCommerce in 2026 — both checkout environments, fully supported
NEXU Advanced Checkout Field Editor works on both classic shortcode and WooCommerce Blocks checkout — same configuration, both environments. All field types, conditional logic, per-product fields, required validation, and order data saving work correctly on Blocks in 2026.
How does this architectural shift to React based form rendering actually impact third party field validation logic at
I've been using this for a few months now, and it finally fixed the issue I was having with required fields not validating on my WooCommerce store. You know how annoying it is when customers skip fields and the order still goes through? that was happening all the time before. now everything checks out like it should no more headaches. I just followed the setup guide in the settings header, and it worked on the first try. Such a relief since I don't have time to mess with code all day.
Got it working, but took too much tweaking
Spent hours setting up custom fields. gone after update. Back to square one