FAQ & troubleshooting

Does it work with the Block checkout?

Yes. Fields render and conditionally show / hide on both the classic shortcode checkout and the WooCommerce Block (Store API) checkout, and values are validated server-side and saved to the order on both. See Classic & Block checkout.

Is it really 100% free?

Yes — there is no Pro version. The full conditional engine (multi-condition AND/OR, every operator, every condition source), all 13 field types including date, time and secure file upload, and field-driven fees all ship in the one free plugin. See Conditional logic and Fees.

Are file uploads safe to offer at checkout?

The upload endpoint is hardened by default: an extension whitelist with real MIME verification, a size cap, a per-IP rate limit, randomized file names, and automatic purging of uploads that never become an order. See Field types.

Where are the field values stored?

On the order (HPOS-safe), shown on the admin order screen and in order emails. See Order data & emails.

A required field is blocking checkout when it shouldn’t

A field set to require only enforces when it’s visible. If it’s blocking unexpectedly, check its conditional rule — the field is probably visible in that scenario. Hidden fields never block an order.

Will it slow down my checkout?

No. Conditions are evaluated by a small shared engine on the page and re-checked on submit — there’s no extra page load and no heavy dependency.

Is it compatible with HPOS?

Yes. Alovio Checkout Fields declares High-Performance Order Storage compatibility and uses standard order APIs.

Can I translate it?

Yes — the plugin is fully translation-ready (text domain corelabs-checkout-fields) and ships a .pot template.

My Block checkout fields aren’t appearing

Make sure you’re on a current WooCommerce with the Cart & Checkout blocks, and that your checkout page actually uses the Checkout block (not the classic shortcode). Both are supported — the plugin just renders into whichever one your page uses.