WooCommerce & integrations
WooCommerce checkout customization has changed with block-based checkout. New work should use the documented block and Store API extensibility interfaces rather than assuming legacy shortcode hooks apply unchanged.
Direct answer
Current WooCommerce checkout fields can be added in contact, address or order locations. Customization should preserve tax, payment and fraud requirements, use supported validation, and verify the stored order/API data after checkout.
Current facts
Answer scope
WooCommerce currently documents three locations for additional checkout fields: contact, address and order information. The field should be placed where its data ownership and lifecycle make sense.
Decide whether the value belongs to the customer account, an address or only the order.
WooCommerce cautions that address fields may be used by tax, fraud and payment systems.
A shorter form can create failed payments or incorrect tax when required data is removed indiscriminately.
The Checkout block exposes documented JavaScript, PHP and Store API extension points. Some legacy hooks have alternatives or different behavior.
The implementation should declare and test compatibility with the checkout architecture in use.
Validation messages should identify the field and correction. Current WooCommerce checkout utilities can run validation and focus the first failing field.
Server-side validation remains important for business rules that must not be bypassed by browser requests.
A field is only useful if the value reaches the correct order/customer record and any email, admin screen, webhook or fulfillment system that needs it.
Test the complete data path rather than only the rendered form.
Questions
Current WooCommerce documentation defines contact, address and order field locations.
Some can, but not all. WooCommerce provides documented block-specific extensibility and hook alternatives.
It depends on the data. Reusable identity/address information may belong to customer/address records, while one-time fulfillment instructions usually belong to the order.
Evidence
First-party platform documentation and clearly labelled public market benchmarks used for factual claims on this page. A source link does not imply endorsement.
Current extension model for block-based cart and checkout, including JavaScript, PHP and Store API integration boundaries.
Current supported locations and behavior for additional WooCommerce checkout fields.
Current checkout validation interfaces and error-handling behavior, last updated May 2026.
Start a conversation
Send the current setup and the result you need. I will review the problem and suggest the most practical next step.