ThemeHigh is warning store owners about a source of missing checkout fields that is easy to overlook: a field configured for WooCommerce’s classic checkout is not automatically a field in Checkout Blocks. Its classic-versus-block guide separates the two editors and explains why a change can appear saved without showing on the active checkout.
The distinction is structural. A classic checkout uses the familiar shortcode-based page, while a block checkout is built with the Checkout block. Before rebuilding a field that seems to have disappeared, establish which page the store is actually serving.
The field’s destination matters as much as its appearance
In the Block Checkout Editor reference, ThemeHigh distinguishes order metadata from user metadata, along with options for displaying values in emails and order details. A delivery instruction for one purchase and a reusable customer preference are not necessarily the same piece of data.
Decide where each value belongs before collecting it. Then submit an order, open it in the dashboard and inspect the customer email. An extra box on the page is only useful when the person fulfilling the order can retrieve the answer.
Conditional fields still need validation
A company-only field is a good example. Check the business purchase that should reveal it, the ordinary purchase that should hide it, and an incomplete submission. The visible state, required-field validation and stored order should all follow the same rule.
The download here is Checkout Field Editor Pro 5.0.0 by ThemeHigh, as listed by GPLHub. The linked documentation describes the vendor’s current editors; it is not a claim that every option in today’s documentation was introduced in 5.0.0 or works with every checkout extension.
The nulled label does not add a vendor license or certify compatibility. Keep the checkout layout and field configuration in a staging test before replacing production files.
