How to Make Your WooCommerce Additional Checkout Fields Conditionally Visible in the Checkout Block

This feature requires a minimum version of WooCommerce 9.9.0

Conditional visibility allows you to create smart, adaptive checkout forms that only show relevant fields when needed, reducing form clutter and improving the customer experience.

Why Use Conditional Visibility?

Conditional fields help you:

• Reduce form complexity by hiding irrelevant fields
• Create dynamic checkout flows based on customer selections
• Show specialized fields only for specific products or customer types
• Improve conversion rates with cleaner, more focused forms
• Collect contextual information that's only relevant in certain situations

Understanding JSON Schema for Conditions

WooCommerce’s additional checkout fields use JSON Schema to define conditional logic. Don’t worry if you’re not familiar with JSON Schema – we’ll walk through practical examples that you can adapt for your needs.

The basic structure looks like this:

'required' => [
    // Define when the field must be filled in here
],
'hidden' => [
    // Define when the field should be hidden here
]

Where Each Field's Value Is Stored

Conditions are evaluated against a single JSON structure (internally called the document object) that mirrors the state of the cart, the customer, and the checkout. To reference another field in a condition, you need to point at the correct subtree for that field's location.

Field's location	Subtree the value lives in	Path to use in conditions
contact	customer.additional_fields	customer.additional_fields.<field-id>
order	checkout.additional_fields	checkout.additional_fields.<field-id>
address	customer.billing_address and customer.shipping_address. Also customer.address when the field being evaluated is itself at address.	customer.billing_address.<field-id> or customer.shipping_address.<field-id> or customer.address.<field-id>

Each field's value only appears in the subtree above, so a condition that points at the wrong subtree will silently have no effect.

Common Conditional Scenarios

Show Fields Based on Shipping Method

One of the most common use cases is showing fields only when specific shipping methods are selected (e.g., Local Pickup):

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/delivery-instructions',
		'label'    => __('Special delivery instructions', 'your-text-domain'),
		'location' => 'order',
		'type'     => 'text',
		'required' => [
			'cart' => [
				'properties' => [
					'prefers_collection' => [
						'const' => true
					]
				]
			]
		],
		'hidden' => [
			'cart' => [
				'properties' => [
					'prefers_collection' => [
						'const' => false
					]
				]
			]
		]
	)
);

Show Fields Based on Cart Contents

Display fields only when specific products are in the cart:

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/fragile-handling',
		'label'    => __('This order contains fragile items - special handling required?','your-text-domain'),
		'location' => 'order',
		'type'     => 'checkbox',
		'required' => [
			'cart' => [
				'properties' => [
					'items' => [
						'contains' => [
							'enum' => [2766, 456, 789] // Product IDs for fragile items
						]
					]
				]
			]
		]
	)
);

Show Fields Based on Cart Value

Display premium service options only for high-value orders:

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/white-glove-service',
		'label'    => __('Add white glove delivery service?', 'your-text-domain'),
		'location' => 'order',
		'type'     => 'checkbox',
		'hidden' => [
			'cart' => [
				'properties' => [
					'totals' => [
						'properties' => [
							'total_price' => [
								'maximum' => 50000 // Hide if cart total is less than $500 (in cents)
							]
						]
					]
				]
			]
		]
	)
);

Show Fields Based on Customer Location

Display fields only for customers from specific countries:

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/tax-exemption-number',
		'label'    => __('Tax exemption number', 'your-text-domain'),
		'location' => 'address',
		'type'     => 'text',
		'required' => [
			'customer' => [
				'properties' => [
					'address' => [
						'properties' => [
							'country' => [
								'enum' => ['US', 'CA'] // Required only for US and Canada
							]
						]
					]
				]
			]
		],
		'hidden' => [
			'customer' => [
				'properties' => [
					'address' => [
						'properties' => [
							'country' => [
								'not' => [
									'enum' => ['US', 'CA'] // Hide for countries other than US and Canada
								]
							]
						]
					]
				]
			]
		]
	)
);

Show Fields Based on Other Field Values

Create dependent fields where one field's visibility depends on another field's value. The schema path is determined by the source field's location (see Where Each Field's Value Is Stored), not the dependent field's.

Same-location example: both fields at order, so the rule looks under checkout.additional_fields.

// Source (order location) - value at checkout.additional_fields.<id>.
woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/service-type',
		'label'    => __('Type of service needed', 'your-text-domain'),
		'location' => 'order',
		'type'     => 'select',
		'options'  => array(
			array( 'value' => 'standard', 'label' => 'Standard' ),
			array( 'value' => 'express', 'label' => 'Express' ),
			array( 'value' => 'custom', 'label' => 'Custom' ),
		),
	)
);

// Dependent - shown only when "custom" is selected.
woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/custom-requirements',
		'label'    => __('Describe your custom requirements', 'your-text-domain'),
		'location' => 'order',
		'type'     => 'text',
		'required' => [
			'checkout' => [
				'properties' => [
					'additional_fields' => [
						'properties' => [
							'my-plugin/service-type' => [
								'const' => 'custom'
							]
						]
					]
				]
			]
		],
		'hidden' => [
			'checkout' => [
				'properties' => [
					'additional_fields' => [
						'properties' => [
							'my-plugin/service-type' => [
								'not' => [
									'const' => 'custom'
								]
							]
						]
					]
				]
			]
		]
	)
);

For a contact or address source field the shape is identical; swap the path for the one in the lookup table.

Mixing Locations

The two fields don't have to share a location. The rule always follows the source; see the lookup table for the subtree mapping.

warning

Address-location values are not stored under additional_fields. Assuming additional_fields is the universal path is a common cause of rules that silently have no effect.

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/customer-type',
		'label'    => __('Customer type', 'your-text-domain'),
		'location' => 'address',
		'type'     => 'select',
		'options'  => array(
			array( 'value' => 'private',  'label' => __('Private', 'your-text-domain') ),
			array( 'value' => 'business', 'label' => __('Business', 'your-text-domain') ),
		),
	)
);

woocommerce_register_additional_checkout_field(
	array(
		'id'       => 'my-plugin/invoice-notes',
		'label'    => __('Invoice notes', 'your-text-domain'),
		'location' => 'order',
		'type'     => 'text',
		'hidden' => [
			'customer' => [
				'properties' => [
					'billing_address' => [
						'properties' => [
							'my-plugin/customer-type' => [
								'not' => [
									'const' => 'business'
								]
							]
						]
					]
				]
			]
		]
	)
);

Practical Complete Example

Here’s a comprehensive example for a store that offers both digital and physical products:

add_action( 'woocommerce_init', function() {
	if ( ! function_exists( 'woocommerce_register_additional_checkout_field' ) ) {
		return;
	}

	// Delivery preference - only for physical products
	woocommerce_register_additional_checkout_field(
		array(
			'id'       => 'my-store/delivery-preference',
			'label'    => __('Delivery preference', 'your-text-domain'),
			'location' => 'order',
			'type'     => 'select',
			'options'  => array(
				array( 'value' => 'doorstep', 'label' => __('Leave at doorstep', 'your-text-domain') ),
				array( 'value' => 'neighbor', 'label' => __('Leave with neighbor', 'your-text-domain') ),
				array( 'value' => 'pickup_point', 'label' => __('Delivery to pickup point', 'your-text-domain') ),
			),
			'required' => [
				'cart' => [
					'properties' => [
						'needs_shipping' => [
							'const' => true
						]
					]
				]
			],
			'hidden' => [
				'cart' => [
					'properties' => [
						'needs_shipping' => [
							'const' => false
						]
					]
				]
			]
		)
	);

	// Delivery instructions - only when 'doorstep' is selected
	woocommerce_register_additional_checkout_field(
		array(
			'id'       => 'my-store/doorstep-instructions',
			'label'    => __('Specific doorstep delivery instructions', 'your-text-domain'),
			'location' => 'order',
			'type'     => 'text',
			'required' => [
				'checkout' => [
					'properties' => [
						'additional_fields' => [
							'properties' => [
								'my-store/delivery-preference' => [
									'const' => 'doorstep'
								]
							]
						]
					]
				]
			],
			'hidden' => [
				'checkout' => [
					'properties' => [
						'additional_fields' => [
							'properties' => [
								'my-store/delivery-preference' => [
									'not' => [
										'const' => 'doorstep'
									]
								]
							]
						]
					]
				]
			]
		)
	);

	// Digital delivery email - only for digital products
	woocommerce_register_additional_checkout_field(
		array(
			'id'       => 'my-store/digital-delivery-email',
			'label'    => __('Alternative email for digital products', 'your-text-domain'),
			'location' => 'contact',
			'type'     => 'text',
			'required' => [
				'cart' => [
					'properties' => [
						'needs_shipping' => [
							'const' => false
						]
					]
				]
			],
			'hidden' => [
				'cart' => [
					'properties' => [
						'needs_shipping' => [
							'const' => true
						]
					]
				]
			],
			'sanitize_callback' => function ( $field_value ) {
				return sanitize_email( $field_value );
			},
			'validate_callback' => function ( $field_value ) {
				if ( ! is_email( $field_value ) ) {
					return new \WP_Error( 'invalid_alt_email', __('Please ensure your alternative email matches the correct format.', 'your-text-domain') );
				}
			},
		)
	);
});

Available data for conditions

You can create conditions based on various checkout data:

1. Cart information under cart.*: total_price, items, shipping_rates, coupons, items_weight, needs_shipping, prefers_collection, and more.
2. Customer data under customer.*: id, billing_address, shipping_address, the contextual address, and additional_fields for contact-location values.
3. Checkout data under checkout.*: payment_method, create_account, customer_note, and additional_fields for order-location values.

When referencing another additional checkout field, pick the subtree that matches that field's location. See Where Each Field's Value Is Stored.

Next Steps

Conditional visibility transforms static checkout forms into dynamic, intelligent interfaces that adapt to your customers’ needs. Combined with the basic additional fields from our previous post, you can create sophisticated checkout experiences that collect exactly the right information at exactly the right time.

Start experimenting with simple conditions and gradually build more complex logic as you become comfortable with the JSON Schema syntax. Your customers will appreciate the cleaner, more relevant checkout experience!