Custom Checkout Fields for WooCommerce contains explicit, code-level handling for a specific set of WordPress and WooCommerce integrations. This page lists only the integrations that exist as real code in version 1.9.5, what each one does, and what you need to configure. Plugins not listed here are not claimed as supported; they may still work, but Custom Checkout Fields contains no specific handling for them.
Summary #
| Integration | Purpose | Configuration needed |
|---|---|---|
| WooCommerce HPOS | Declared compatible with custom order tables | None |
| WPML | Product-based visibility and per-language field text | None for visibility; use the translate shortcode for text |
| WooCommerce Store Exporter | Adds custom fields to order exports | Select the fields in the exporter |
| One Page Checkout | Show fields when the cart is empty | One filter (see below) |
| Select2 | Enhanced searchable dropdowns | Enable per field |
| jQuery UI datepicker and timepicker addon | Date, week, and time fields | Bundled, no separate install |
WooCommerce HPOS (High-Performance Order Storage) #
Custom Checkout Fields declares compatibility with HPOS (custom order tables) using WooCommerce’s official feature declaration. You will not see an incompatibility warning on the WooCommerce features screen, and the plugin can be used with HPOS enabled. Field data is read and written through WooCommerce’s order objects, so it behaves the same under both storage modes.
WPML #
Two distinct WPML integrations exist.
Product-based visibility #
When you restrict a field to certain products under Visibility Options, and WPML is active, the plugin resolves each cart product to its default-language ID before matching. This means a visibility rule set against the original product also matches its translations in the cart.
Per-language field text #
The [alg_wc_ccf_translate] shortcode lets you supply different text per language inside field options such as the label or default value. It reads the current language from WPML’s ICL_LANGUAGE_CODE constant. If WPML is not active, the shortcode falls back to the “other languages” text.
Note: the translate shortcode relies on WPML’s language constant specifically. Verify your field text on each active language before relying on it.
WooCommerce Store Exporter #
When the “WooCommerce Store Exporter” plugin is active, Custom Checkout Fields registers each enabled field as an available order field and supplies its value for each exported order. Pick the fields you want in the exporter’s order-field list, and the values are included in the export.
One Page Checkout #
Some one-page checkout setups render the checkout while the cart is technically empty, which normally hides fields. The filter alg_wc_custom_checkout_fields_always_visible_on_empty_cart keeps fields visible in that case. Return true to force fields to render even when the cart is empty:
add_filter( 'alg_wc_custom_checkout_fields_always_visible_on_empty_cart', '__return_true' );Select2 #
Select and Multiselect fields can use Select2 for a searchable, taggable dropdown. Enable it per field with the Select/multiselect: “Select2” option, and translate its interface text with the Select2 custom-text fields. Select2 ships with WooCommerce, so nothing extra is installed.
jQuery UI datepicker and the timepicker addon #
The Datepicker, Weekpicker, and Timepicker field types are built on the jQuery UI datepicker plus the Trent Richardson timepicker addon, both bundled with the plugin. The date and time format options accept the formats documented for those libraries, which the field tabs link to.
A note on plugins not listed here #
Custom Checkout Fields adds its fields through standard WooCommerce checkout hooks, so many themes and plugins cooperate without any special handling. If you are evaluating a specific combination not listed here, test it on a staging site, paying attention to plugins that replace the checkout template or reorder its fields.
Need a hand? #
Our team answers every ticket on the Custom Checkout Fields support forum.