Q: In which section should each field be placed?

“Contact information” (saved to the order and user for next orders): any personal fields that are related to the user but not to the address, for example: VAT number Birthdate Passport number National ID number Preferred contact method (phone, email, WhatsApp) Newsletter opt-in “Addresses (shipping and billing)” (saved to the order and user for next orders): any fields that are related to the address but not the user (as they’re duplicated on both addresses), for example: Contact person at the address Second phone number Location hints (landmark, gate code, floor/apartment number) Business hours for deliveries Tax ID for that specific address (if different from the user’s own) “Additional order information” (saved only to the order and not to the user): any fields that are related to this specific order only, for example: Delivery date or preferred time window Include gift wrap Message to include on package Purchase order (PO) number, for B2B orders How did you hear about us?

Q: Can the custom fields be ordered and placed between the core fields?

“Contact information” and “Additional order information” fields can only be shown after the core fields, but you can set the order of your custom fields after that. “Addresses (shipping and billing)” fields can be placed in 5 positions: after the country, after the name fields, after the company field, after the country/address/city/postcode/state fields, and after all core fields. Inside each position, you can set a second position for your custom fields if you have more than one in each position.

Question 1

How to request technical support?

Accepted Answer

If the issue you need technical support with is not covered on this page, click the link next to the license key, on the plugin settings, and fill out the ticket with your request.

Question 2

Where do I report security vulnerabilities found in this plugin?

Accepted Answer

You can report any security bugs found in the source code of this plugin through the Patchstack Vulnerability Disclosure Program.

The Patchstack team will assist you with verification, CVE assignment, and take care of notifying us.

Question 3

Does this plugin support the legacy/classic WooCommerce checkout experience?

Accepted Answer

No. This plugin allows you to manage and add custom checkout fields only on the new Block-based WooCommerce checkout experience.

Question 4

How to transfer the license to another domain?

Accepted Answer

You should ask for the domain change in your customer area, next to the original order details.

After you receive our reply confirming the license key is free, go to the old website settings, remove the key, and save. Then go to the new website settings, insert the same key, and save. If you cloned the website, the license key is in the database: you need to remove it, save, insert it again, and save again.

Question 5

What happens if my license expires?

Accepted Answer

The plugin keeps working, your existing custom fields keep showing on the checkout, and their data keeps being saved normally. Two features are capped until you renew:

Conditional visibility and required rules for custom and core fields stop being available
Managing WooCommerce’s own core checkout fields (renaming labels, changing visibility or required status per field or per country) stops being available

Renew your license to restore these settings.

Renewing your license helps us continue improving the plugin, respond to changes in WordPress and WooCommerce, and provide you with reliable support. We highly recommend keeping it active.

Question 6

What's the difference between disabling and deleting a custom field?

Accepted Answer

Disabling a field (“Disabled” toggle) hides it from the checkout, but keeps its definition and any previously saved values: you’ll still see it on the order edit screen for orders that already have it.

Deleting a field removes its definition and settings entirely. As mentioned above, its previously saved order and user data isn’t erased from the database, it just stops being editable or visible through this plugin’s admin screens. If you later add a new field using the exact same slug, that old data resurfaces again, since it’s stored and read using the slug alone.

Question 7

In which section should each field be placed?

Accepted Answer

“Contact information” (saved to the order and user for next orders): any personal fields that are related to the user but not to the address, for example:

VAT number
Birthdate
Passport number
National ID number
Preferred contact method (phone, email, WhatsApp)
Newsletter opt-in

“Addresses (shipping and billing)” (saved to the order and user for next orders): any fields that are related to the address but not the user (as they’re duplicated on both addresses), for example:

Contact person at the address
Second phone number
Location hints (landmark, gate code, floor/apartment number)
Business hours for deliveries
Tax ID for that specific address (if different from the user’s own)

“Additional order information” (saved only to the order and not to the user): any fields that are related to this specific order only, for example:

Delivery date or preferred time window
Include gift wrap
Message to include on package
Purchase order (PO) number, for B2B orders
How did you hear about us?

Question 8

Can the custom fields be ordered and placed between the core fields?

Accepted Answer

“Contact information” and “Additional order information” fields can only be shown after the core fields, but you can set the order of your custom fields after that.

“Addresses (shipping and billing)” fields can be placed in 5 positions: after the country, after the name fields, after the company field, after the country/address/city/postcode/state fields, and after all core fields. Inside each position, you can set a second position for your custom fields if you have more than one in each position.

Question 9

Why is one of my address fields alone on its own line, stretched?

Accepted Answer

WooCommerce lays the address form out two fields per line. Some fields always take a whole line on their own (the country, company and address fields, and any checkbox), and the remaining ones pair up two by two. When the fields before it do not add up to a full line, a field is left alone on its line and stretched to fill it.

Which fields end up paired depends on how many are shown, so it changes if you add custom fields, remove core fields, or use conditional rules to show a field only in some situations. It is not something the plugin can decide for you.

To control it, edit the field, go to the “Advanced options” tab, and turn on “Full width”. The field then always takes a whole line, and the fields after it pair up again from a clean start. The option is only available for “Addresses (shipping and billing)” fields, since the other sections are single column, and it is not shown for checkbox fields, which WooCommerce already renders full width.

Note that this is a manual setting, not an automatic fix: if you later change which fields are shown, you may need to revisit it.

Question 10

What are conditional rules, and which are available?

Accepted Answer

You can use conditional rules to make custom fields visible and/or required or not. You can create complex OR and AND rules with as many conditions as you want.

Most text-type conditions (any custom Text or Select field, and the core Email, First name, Last name, Company, Address 1, Address 2, City, and Postcode fields) share the same set of operators: is / is not / contains / does not contain / matches pattern / does not match pattern / is empty / is not empty. Custom Checkbox fields instead use is checked / is not checked.

These are the conditions you can use (version 7.3):

Contact
- Core
  - Email (text-type operators)
- Custom
  - Any custom field (operators depend on its type: text-type operators for Text/Select fields, “is checked / is not checked” for Checkbox fields)
Address
- Core
  - First name, Last name, Company, Address 1, Address 2, City, Postcode (text-type operators)
  - State, Country: is one of / is not one of / is empty / is not empty, picked from a list
  - Phone (text-type operators)
- Custom
  - Any custom field (same rule as under Contact, above)
- If the field you’re setting the rule on is not itself in the “Addresses” section, address conditions are offered twice, as separate “Billing Address” and “Shipping Address” groups, so you can target either one specifically
Order (additional fields)
- Custom
  - Any custom field (same rule as under Contact, above)
Cart and Checkout
- Core (provided natively by WooCommerce)
  - Payment method: is one of / is not one of, picked from your installed payment gateways
  - Needs Shipping: true / false
  - Order Total (with tax): is more than or equal to / is less than or equal to
  - Shipping Method: is one of / is not one of, picked from your store’s shipping zones and methods
  - Total Quantity in Cart: is more than or equal to / is less than or equal to. This is the sum of every product’s quantity, so a cart with 2 of product A and 3 of product B counts as 5
- Custom (computed by the plugin, since WooCommerce doesn’t expose this data natively)
  - Order Total (without tax), Order Sub-total (only products, with tax), Order Sub-total (only products, without tax): is more than or equal to / is less than or equal to
  - Number of Different Products in Cart: is more than or equal to / is less than or equal to. This counts distinct products/lines, not quantities, so a cart with 2 of product A and 3 of product B still counts as 2 (as opposed to Total Quantity in Cart, above, which would count 5)
  - Product Categories, Product Tags, Product Brands: cart contains one of / cart does not contain one of, picked from your store’s terms
  - Any other product taxonomy/attributes via the swcbcf_conditional_cart_product_taxonomies filter
  - Product: cart contains one of / cart does not contain one of, searched dynamically by name so it works even with thousands of products. If you pick a variable product itself, any of its variations in the cart will match; if you pick a specific variation, only that exact variation will match
Customer
- Core (provided natively by WooCommerce)
  - Logged-in: true / false
- Custom (computed by the plugin, since WooCommerce doesn’t expose this data natively)
  - User Role: is one of / is not one of, picked from your site’s roles, plus a “Guest” option to also match logged-out visitors directly within this same condition
  - Customer First Order: true / false. true if the customer has no previous orders, checking by account for logged-in customers and by email address for guests

Question 11

Is it possible to reorder WooCommerce Blocks' core checkout fields?

Accepted Answer

Unfortunately, no (or not yet). The API is evolving constantly, and we are committed to including all the future possibilities in this plugin.

You can, however, remove/hide core address checkout fields, like “Last name”, “Company name”, “Street address”, “Apartment, suite, unit, etc.”, “City”, “State / County”, “Postcode / ZIP”, and “Phone”, as well as making them required or not, globally or per country.

Question 12

What's the "Pattern" option for?

Accepted Answer

That’s a way to limit the pattern/format of the inserted value on a text input by using regular expressions.

You can pick one of the common patterns below directly from the “Insert a common pattern…” dropdown next to the field, which fills it in for you (you can still edit it afterward), or type your own.

Here are the built-in examples:

Only numbers: ^[0-9]+$
Alphanumeric only: ^[A-Za-z0-9]+$
Letters only: ^[A-Za-zÀ-ÿ\s'-]+$
Email address: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
URL (starts with http:// or https://): ^https?://.+$
Phone number: ^[+]?[0-9\s()-]{7,}$
At least 8 characters: ^.{8,}$

Question 13

Why does the title attribute set on the advanced options tab not show when the customer hovers the mouse over the field?

Accepted Answer

The plugin sets the title attribute on the field, and there’s no specific implementation for tooltips; it’s just the HTML title attribute. Depending on the browser (including its privacy and accessibility settings), device, and the speed at which the user moves the mouse 😏, the tooltip might not show up.

Question 14

Why aren't the customizations applied in full to the My Account account information and address forms?

Accepted Answer

WooCommerce’s My Account “Account details” and address forms don’t yet use the same Blocks checkout field engine as the checkout itself. Your custom fields will still show up there, since WooCommerce reuses the same field registry, but conditional rules, custom validation, and other checkout-specific behavior aren’t guaranteed to work consistently on those forms, as they’re not running the full Blocks checkout experience.

Question 15

How are the fields stored in the database, and how can I fetch them?

Accepted Answer

The fields are stored on orders and users’ meta on the _wc_other/swcbcf/field-slug, _wc_billing/swcbcf/field-slug and _wc_shipping/swcbcf/field-slug meta keys.

You can see the meta key for each field by editing it and clicking on “Show advanced options”:

Field edit screen showing the “Show advanced options” section with the meta key

You ~~can~~ should use our helper functions to get each field value if you need to use them in your custom code. The PHP to be used for each field is also shown when you click on “Show advanced options”.

There are two helper functions:

swcbcf_get_order_field - To get order fields

Arguments:

$order_id - The order ID
$location - The location: ‘other’ (for contact or additional fields), ‘billing’ or ‘shipping’ (for address fields)
$field_slug - The field slug

swcbcf_get_user_field - To get user fields

Arguments:

$user_id - The user ID
$location - The location: ‘other’ (for contact fields), ‘billing’ or ‘shipping’ (for address fields)
$field_slug - The field slug

Question 16

Is there a way to list every field this plugin has registered?

Accepted Answer

Yes, if you’re integrating with this plugin from your own code. swcbcf_get_registered_fields_keys() returns every field currently registered, including the ones coming from bundled field definitions, grouped by section:

array(
    'contact' => array(
        'meta_location' => array( 'other' ),
        'fields'        => array( 'field-slug', 'another-field-slug' ),
    ),
    'address' => array(
        'meta_location' => array( 'billing', 'shipping' ),
        'fields'        => array( 'field-slug' ),
    ),
    'order'   => array(
        'meta_location' => array( 'other' ),
        'fields'        => array( 'field-slug' ),
    ),
)

Combine the slug with one of the meta_location values to build the meta key, or pass them to the helper functions above. Call it on woocommerce_init or later, so that all the fields have been registered.

Question 17

Is it possible to validate each field with custom PHP?

Accepted Answer

Since version 1.0, you can validate each field individually, but without having access to the other fields and values of the checkout, which means you still can’t do cross-validation between several fields.

It might be possible to get those values by accessing the customer or order object; however, this is not supported, and there are no guarantees regarding backward compatibility in future versions.

For individual field validation, you need to use our filter swcbcf_validate_callback_{location}_{field-slug} and return a string with the error description or nothing if the validation has passed, like in this example.

The complete filter name for each field is available on the field edit interface, under “developer info.”.

This filter is internal of our plugin and it’s called on a generic validation function we’ve defined at the validate_callback parameter for all fields when registering them with WooCommerce.

Question 18

Is it possible to bundle field definitions with a plugin or theme?

Accepted Answer

Yes. If you’re a developer, you can ship a set of custom fields and core field overrides with your own plugin or theme, in a versioned, Git-controllable way, instead of asking your users to set them up by hand.

The workflow reuses our existing export tool: set the fields up on a dev or staging site using this plugin’s admin screen, click “Export field definitions”, and bundle the resulting JSON file with your plugin or theme. Then register its path with our filter:

add_filter( 'swcbcf_bundled_field_definition_files', function ( $files ) {
    $files[] = __DIR__ . '/checkout-fields.json';
    return $files;
} );

The path must be absolute, as in the example above. Relative paths are not resolved, and the file will be reported as not found.

Register the filter early: directly in your plugin’s main file, on plugins_loaded, or in your theme’s functions.php. The definitions are read the first time something needs them, which is when we register the fields with WooCommerce on woocommerce_init. A filter added after that point is never seen, and your fields simply won’t show up.

To change the fields later, set them up again on your dev or staging site and export a new file. Don’t edit the JSON by hand: its structure can change between plugin versions, and hand-written files aren’t supported. Exporting is what makes the file safe to commit, diff, and roll back like any other part of your code.

Fields and core field overrides loaded this way are never written to the database. They’re read fresh from the file on every request, so they always match what’s in your plugin or theme’s code. In the admin UI, they appear locked (no Edit or Delete option), with a lock icon showing which file they came from.

If an admin already created a custom field with the same slug as a bundled one, the bundled definition takes precedence. The admin’s field is left in the database untouched, but it’s flagged as inactive in the admin UI until it’s renamed or removed.

You can register more than one file. If two files define the same slug or the same core field, the first one registered wins, and a warning is shown in the admin UI.

Nothing fails silently. This plugin’s settings screen warns you when a file can’t be found or read, when it isn’t valid JSON, when a field entry is missing its slug, label or type (that entry is skipped and the rest of the file still loads), and when a slug or core field override is already defined by another bundled file.

Core field bundling only supports the “address” section, matching the rest of this plugin’s core field support.

There is currently no way to unlock a bundled field from the admin UI.

Question 19

How to translate the field labels to additional languages when using WPML and WooCommerce Multilingual?

Accepted Answer

Whenever you create or edit a field, the label should be set and is registered on WPML for translation under the website’s default language.

To translate to additional languages, you need to go to WPML > String translation > Filter by the “simple-woo-checkout-blocks-cf” domain and then translate each string.

Simple Checkout Fields Manager for WooCommerce Documentation and FAQ

Support

How to request technical support?

Where do I report security vulnerabilities found in this plugin?

Does this plugin support the legacy/classic WooCommerce checkout experience?

Licensing

How to transfer the license to another domain?

What happens if my license expires?

General operation

Getting started guide

What’s the difference between disabling and deleting a custom field?

In which section should each field be placed?

Can the custom fields be ordered and placed between the core fields?

Why is one of my address fields alone on its own line, stretched?

What are conditional rules, and which are available?

Is it possible to reorder WooCommerce Blocks’ core checkout fields?

What’s the “Pattern” option for?

Why does the title attribute set on the advanced options tab not show when the customer hovers the mouse over the field?

Why aren’t the customizations applied in full to the My Account account information and address forms?

Advanced operation

How are the fields stored in the database, and how can I fetch them?

Is there a way to list every field this plugin has registered?

Is it possible to validate each field with custom PHP?

Is it possible to bundle field definitions with a plugin or theme?

WPML Integration

How to translate the field labels to additional languages when using WPML and WooCommerce Multilingual?

Third-party compatibility

Create User Account from WooCommerce Guest Order

Shop as Client Pro

Multi-currency plugins

Known issues and limitations

Other types of fields are not available

The option to hide custom fields on order confirmation is not working consistently

It’s not possible to add masks to input fields, in order to get formatted values like Portuguese Cartão do Cidadão, Brazilian CPF or CNPD, Phone numbers, etc

It’s not possible to add extra classes or “data-” attributes to custom fields

A conditional rule that depends on another custom field can misfire on the very first page load

Core field customizations (label, visibility, required, order) and custom field order don’t apply until a country is selected

Resolved limitations

After the validation fails, the error message will not go away, even if the field is corrected

Validation callback not running for fields conditionally shown