What field types does the plugin support?
Twenty-plus types: text, textarea, number, email, tel, password, URL, select, multiselect, radio, checkbox, single checkbox, date picker, time picker, file upload, country, state, heading, paragraph, hidden, and HTML. Every type accepts a custom label, placeholder, default value, and CSS class.
Can a field show or hide based on what's in the cart?
Yes. Each field has conditional rules that can trigger on cart total, specific products in the cart, product categories, user role, customer country or state, payment method, shipping method, or even the value of another custom field. Rules combine with AND/OR logic.
Can a checkout field add a fee to the order?
Yes. Any field can be tied to a fee: fixed amount per choice, percentage of cart total, or a per-unit multiplier. Pick the gift-wrap checkbox, the $5 charge appears in the cart totals immediately, and lands on the final order as a proper WooCommerce fee.
Where exactly can the fields be placed on the checkout page?
Fourteen-plus locations: above/below the billing block, above/below the shipping block, before/after the order notes, before/after each payment gateway, before/after the order total, in the order review table, and in three custom sections you can name yourself.
Will the captured values appear in the admin order and customer emails?
Yes. Each field has independent toggles for: admin order page, customer order email, admin order email, order confirmation (thank-you) page, and the My Account order details view. Sensitive fields can be hidden from the customer-facing surfaces.
Does the plugin work with the WooCommerce block checkout?
Yes for the classic checkout (full feature set) and partial support for the block checkout. WooCommerce's block checkout exposes a limited subset of customization hooks; the plugin uses every one available and ships an opt-in classic-checkout fallback for stores that need the full field library.
Can the same field require different things for different customers?
Yes. Required-versus-optional is itself a conditional rule. A VAT number can be required only when the country is in the EU. A company name can be required only when the cart total crosses a B2B threshold. The rule engine drives required state, visibility, and fee triggers from the same condition set.
What validation rules are built in?
Numeric range, character length min/max, regex patterns, email format, URL format, date range, and a free-form custom error message. The validator runs on the server, so customers cannot bypass it by editing the HTML.
Will this slow my checkout?
No. Field definitions are stored as options (no extra database tables). Conditional logic evaluates client-side via a small inline script and re-validates server-side on submission. Frontend impact is a few kilobytes of inline JS and zero AJAX calls in the default config.
Is the plugin HPOS-compatible?
Yes. HPOS (High-Performance Order Storage) is declared compatible. Custom field values are written to both the new high-performance order tables and the legacy postmeta layer, so other plugins reading order meta the old way still see the data.
What is the refund policy?
14 days on the yearly and lifetime plans; 30 days on All Access. No questions asked. The yearly plan also includes an upgrade credit toward Lifetime or All Access. Lifetime never renews. Yearly auto-renew can be turned off in your account.
Is there a free version?
Yes. The free version on WordPress.org covers the core field-builder UI and the basic field types (text, textarea, select, checkbox, date). The Pro version adds the full 20-plus field library, conditional logic, fees from field choices, validation rules, file upload, and import/export.