WooCommerce Custom Fields Break After 8.3 Here's the Fix

This isn't a bug; it's a fundamental incompatibility. The classic checkout relies on server-side PHP hooks like woocommerce_checkout_fields and woocommerce_after_order_notes, but the Blocks checkout renders client-side via React. Those hooks never fire, and without a Blocks-compatible solution, your fields simply don't exist in the new system. The fix isn't to roll back WooCommerce, it's to use a tool like NEXU Advanced Checkout Field Editor, which maintains native support for both architectures under a single configuration.

Why Classic Fields Fail in Blocks (and Vice Versa)

The classic checkout and Blocks checkout don't just look different, they operate differently. Classic fields depend on PHP hooks that inject HTML into server-rendered templates. Blocks, however, uses the Store API and React's Slot/Fill system, which ignores PHP hooks entirely. A field added via woocommerce_checkout_fields won't appear in Blocks, just as a Blocks-specific field registered through __experimental_woocommerce_blocks_checkout_fields won't work in the classic checkout.

Even validation and data storage diverge:

• Classic checkout: Uses woocommerce_checkout_process for validation and woocommerce_checkout_update_order_meta to save data.
• Blocks checkout: Requires Store API schema extensions and woocommerce_store_api_checkout_update_order_from_request for the same tasks. Without a bridge between these systems, fields break, and manually rewriting them for both environments is impractical for most stores.

How NEXU Advanced Checkout Field Editor Solves This

Instead of forcing you to choose between checkouts or maintain duplicate configurations, NEXU Advanced Checkout Field Editor implements native compatibility for both systems simultaneously. Here's how it works:

1. Dual Rendering Engines
   The plugin detects whether your store uses the classic shortcode or the Blocks checkout and renders fields accordingly. Classic fields use PHP hooks; Blocks fields use the Store API and React Slot/Fill system, without requiring you to configure them separately.

2. Unified Validation and Storage
   Field validation and order metadata storage adapt to the active checkout. In classic mode, it uses woocommerce_checkout_process. In Blocks mode, it registers validation via the Store API's ExtendSchema system. The result? Required fields block submission in both checkouts, and data saves to orders reliably.

3. No Migration Rework
   If you're already using custom fields (via another plugin or custom code), NEXU's editor can replicate their behavior in Blocks without rebuilding from scratch. Conditional logic, file uploads, and per-product fields, all ported automatically.

The Practical Path Forward

WooCommerce isn't reverting to the classic checkout. Blocks is the default for new installations (since 8.3) and will eventually replace the classic system entirely. The question isn't if you'll need to support Blocks, but when, and whether you'll scramble to fix broken fields after the fact or prepare now.

For stores with existing custom fields:

1. Audit your current setup: Identify which fields use PHP hooks (e.g., woocommerce_after_order_notes).
2. Test in a staging environment: Switch to the Blocks checkout and check for missing fields.
3. Deploy a compatible solution: Tools like NEXU Advanced Checkout Field Editor eliminate the need to rewrite fields or maintain separate configurations.

For new stores:
Start with the Blocks checkout and a Blocks-compatible field plugin from day one. Avoid PHP hook-based customizations that will break in future updates.

The transition from classic to Blocks isn't just a WooCommerce update, it's a shift in how checkout customization works. The stores that handle it smoothly are those that recognize the architectural change and adapt their tools accordingly. With the right plugin, your custom fields won't just survive the transition; they'll work seamlessly in both worlds.