Custom fields in WooCommerce Checkout Blocks.

Will your field work in Blocks?

Supported follow-ups still use text, select or checkbox fields. The source answer must come from an earlier, enabled, unconditional select or checkbox in the same location.

First, identify your checkout

Edit the checkout page in WordPress. A page containing the Checkout block uses Checkout Blocks. A page built around the [woocommerce_checkout] shortcode uses Classic checkout. A theme or checkout extension may add another layer of customization, so verify the page your store actually serves.

The Cartdini editor reports the checkout type above its controls. Use that information when choosing fields rather than assuming every option behaves the same way.

Choose the right field location

For a first test, add one optional text field in Order information. The delivery-instructions walkthrough includes saving and order checks.

What differs from Classic checkout?

Cartdini’s custom text, select and checkbox fields work in both systems. Free also includes textarea, email and telephone on Classic. Pro adds number, date and radio on Classic. None of those six types is registered in Blocks in this release.

Cartdini’s optional core-field overrides apply to Classic. For core Checkout Blocks fields, use the checkout editor and the options WooCommerce provides. Custom placeholders are not applied in Blocks; help text is an input tooltip and does not appear for select fields.

Reordering works within a field location. Moving a question to another part of checkout is a location decision, not a promise of arbitrary layout placement. Your theme still controls the rendered design.

Set up conditional fields in Blocks

With Pro, start with the Gift order or Business purchase details recipe in WooCommerce → Cartdini → Tools & restore → Ready recipes. Both use supported Order information fields. Follow the step-by-step conditional workflow guide to review, save and test them.

Use up to five rules per field with Match all rules (AND) or Match any rule (OR). Blocks answer rules use earlier, enabled, unconditional select or checkbox fields in the same location. Product and final-total rules, and conditional Contact information fields, need WooCommerce 10.1+.

For product rules, select exact simple-product or variation IDs; a variable parent does not include all its variations. Total rules use the final store-currency amount after discounts, including tax and shipping. A required follow-up applies only while its conditions match, and answers to hidden fields are excluded from the submitted order.

Test matching and nonmatching answers, products and totals. Change a coupon, address or shipping option to trigger recalculation, then check the saved order and email output. Unsupported saved definitions stay retained but are not displayed in Blocks. See the complete rule boundaries before combining workflows.

Order storage and HPOS

Blocks field values use WooCommerce’s native additional-field API. Free includes independent admin-order, customer-order, admin-email and customer-email display controls. They default to on. Current display choices apply to existing and new orders while the field exists; deleted fields use their saved snapshot choices, with older snapshots defaulting to visible. These are presentation controls, not access restrictions or encryption. Cartdini does not require legacy order-post storage. Inspect an actual test order and its emails after adding or changing a field; don’t rely only on the editor preview.

See the release test matrix for the recorded WordPress, WooCommerce and PHP combinations and the limits of that testing.