Configure per-product which Woo checkout fields are required, optional or hidden. Free for the standard fields. PRO adds custom fields per product, conditional logic, per-category settings and validation patterns (Dutch postcode, KVK, IBAN, EU VAT).
Woo asks for the same 11 billing + 9 shipping + 1 order fields on every order. For a digital product, half is irrelevant. For a B2B order, you need VAT and project codes Woo doesn't have. Settings → Advanced is too coarse.
Asking for it kills conversion ("why do they need my address for a PDF?"). Free lets you hide all shipping + address fields per digital product.
Companies need a VAT field, a KVK, sometimes a project code. PRO's conditional logic shows them only when the customer is buying for a company.
Editing 200 products by hand is unworkable. PRO's per-category settings let you set the same rule for a whole category at once.
A wrong postcode = a returned shipment. PRO's validation patterns (Dutch postcode, KVK, EU VAT, IBAN) catch typos at checkout before they cost you.
All inside the standard Woo product edit screen — new "Checkout fields" tab in Product Data.
Configure
Open a product, click the new "Checkout fields" tab. Toggle each Woo standard field to Default / Required / Optional / Hidden.
Add (PRO)
In PRO, add custom fields per product (text, email, dropdown, …) and validation patterns. Or set defaults per product category. Or wire conditional logic ("show X when Y = Z").
Cart-aware checkout
When the cart contains multiple products, the strictest rule wins. One product requires phone → phone is required for the order. Custom fields collected at checkout land as order item meta — visible in admin orders, emails and PDF invoices.
No upsell tax on basic functionality — the strictest-wins resolver, hidden/required/optional toggle, multi-product carts and HPOS support are all in the free version.
The core feature, no limits.
Beyond Woo's standard set.
"Show X when Y = Z."
_cffw_conditions metaConfigure a whole category at once.
Catch typos at checkout.
1234 ABwoocommerce_checkout_process — blocks invalid ordersBuilt on standard Woo APIs.
Free runs on standard WordPress + Woo. PRO uses the OCW License Server for license validation + updates — that's it.
Free covers per-product field toggling. PRO is for B2B-leaning shops and bigger catalogs.
Checkout Fields for Woo
Per-product checkout field toggling, no limits.
Free forever · 1 site
No signup, no API keys required.
Checkout Fields for Woo PRO
For B2B-leaning shops and bigger catalogs.
per year · 1 site · excl. VAT
Per year. Instant access after payment. Cancellable annually.
Answers to the questions I get most often.
My cart has 3 different products with conflicting rules — which one wins?
Strictest wins. Required > Optional > Hidden > Default. If one product says "phone is required" and another says "phone is optional", phone becomes required for the whole order. Safe choice — never accidentally skips data.
Does it work with Cart & Checkout Blocks?
Yes. The plugin declares cart_checkout_blocks compatibility and ships a small JS shim (assets/js/checkout-blocks.js) that applies hidden/required rules in the block-based checkout too.
Where do PRO's custom field values end up?
As order item meta on the line item that triggered them. Woo automatically shows order item meta in the admin order screen, customer emails, and any PDF invoice plugin that respects order item meta. No manual hook needed.
What's the validation regex if I want a Dutch postcode?
Use the "Dutch postcode (1234 AB)" preset — the underlying regex is /^[1-9][0-9]{3}\\s?[A-Z]{2}$/i if you want to match the same pattern elsewhere.
Can I move a PRO license to another domain?
Yes. Clear the key on the old site (this triggers /deactivate on the license server) and enter it on the new site. Single Site = 1 active domain at a time.
How do PRO updates work?
Updates appear in your normal WordPress updates screen. The plugin checks the OCW License Server with your license key, and only an active license receives the new ZIP.