Which Checkout Field Plugins Support the Block Checkout (and Which Ones Do Not)

Three questions that decide this

Work through these in order. Most stores have an answer by question two.

1. Are you on the block checkout? Open your Checkout page in the editor. If you see a single WooCommerce Checkout block, you are. If you see a shortcode, you are on the classic checkout and every plugin below works for you.
2. Do you need rules, or just extra fields? A plain set of always-visible fields is the cheap case, and several free plugins cover it. Fields that appear only in certain circumstances are the expensive case, and that is where the market divides.
3. Does a field need to change the total? Gift wrap, express handling, insurance and engraving all mean a fee attached to a field. Only a handful of tools do this, and almost all of them charge for it.

What core gives you with no plugin

Worth knowing before you buy anything, because core covers more than most people expect.

Source: the WooCommerce developer documentation on additional checkout fields and conditional fields.

Use core if you have a developer, need a handful of fields, and text, select, checkbox and date are enough. Look at a plugin if the person running the store needs to change fields without a deployment, or you need a textarea, radio button, multi-select or file upload, none of which core offers.

Block support, plugin by plugin

Every line below is quoted or summarised from the vendor's own listing or documentation, read on 28 September 2026.

ThemeHigh is the only vendor that names exactly which field types work on blocks. That is a point in its favour. Everywhere else, "compatible with Cart and Checkout Blocks" may cover every field type or only some, and the listing does not say.

Conditional rules: included or extra

This is the question that decides most purchases, because a checkout field plugin without rules is a form builder, and core can already build a form.

Alovio is the one to know about if budget decides it. It includes conditional rules, field fees and file upload with no paid tier, and states it behaves the same on both checkouts. It is also version 1.5.0 with roughly 100 active installations. That is a young plugin on the one page of your store where a fault costs an order, so weigh the saving against that. If it suits your store, it is the cheapest route to conditional fields that exists.

Fees, repeating fields and sections

Repeating fields are the least common capability here and the one most often needed by print, engraving and ticketing stores, where every item in the cart needs its own line of text.

Field types available

Counts are not directly comparable between vendors, since some list a date field and a date picker separately, and a count given for the classic checkout may not all carry over to blocks. Use this for rough scale, then check the specific type you need.

Choosing between them

Conditional Checkout Fields, by FMEAddons

Conditional Checkout Fields & Edit Checkout Fields for WooCommerce is our own plugin, sold on the WooCommerce Marketplace at $49 per year. It sits in the group that supports both checkouts with rules built from dropdowns rather than code.

Which one fits your situation

You need extra fields, no rules, and no budget. ThemeHigh's free version has the widest range of field types at 20, and 400,000 active installations behind it. Acowebs' free version states full block support with 12 types. Either will do the job.

You need rules and no budget. Alovio, with the caveat about its size above, or core if a developer is available.

You need a file upload field for free. QuadLayers includes it without limit, but only on the classic checkout. On blocks, Alovio includes a secure file upload.

You are already on WP Desk's Flexible Checkout Fields. Add Checkout Fields for Blocks, then price the conditional logic and field pricing add-ons before committing, since both are sold separately.

You need rules that combine the cart, the customer and other fields, on both checkouts, without code. This is where the paid tools sit, including ours.

Skip regardless of price if you are on the block checkout: Woo's own Checkout Field Editor and QuadLayers' Checkout Manager, on their own statements.

Five questions to ask before you buy

These are the points no listing we read answers, ours included. Asking them before you pay will save a refund request.

1. Which of your field types work on the block checkout? Not whether the plugin is compatible, but which types. Only one vendor publishes the list.
2. Are conditional rules enforced on the server, or only hidden in the browser? Core checks rules on the server. A rule that only hides a field can be bypassed by a submission that goes straight to the Store API, which matters if the field controls a price or a discount.
3. Do custom sections render on the block checkout? Section-based layouts are the most common thing that works on classic and silently does not on blocks. Ours is an example: our custom sections are classic only, and on blocks those fields go in the Additional section.
4. Where does the data appear afterwards? Admin order screen, customer email, thank you page, My Account, CSV export and the Store API are six different places, and plugins vary in how many they cover.
5. Is HPOS declared, and is there translation support? High-Performance Order Storage is now the default for new stores, and WPML or Polylang support is often absent from the free tier.

How this guide was put together

Every claim comes from the vendor's own listing or documentation, read on 28 September 2026, and every source is linked below. Where a vendor does not state something, the table says so rather than guessing, because silence on a capability is itself worth knowing when you are choosing.

We publish one of the plugins listed here, which is why we have used each vendor's own words rather than our description of them, and why the guide points to free tools where a free tool is the right answer.

We are also putting these through a test store on WooCommerce 11.1, including the server-side enforcement question above, and will add the results here.

Sources

• Core: Additional checkout fields and conditional fields
• ThemeHigh: WordPress.org listing
• WP Desk: Flexible Checkout Fields and Checkout Fields for Blocks
• QuadLayers: WordPress.org listing
• Acowebs: free version and Pro
• Alovio: WordPress.org listing
• Addify: Marketplace listing
• WPExperts: Marketplace listing
• Woo: Marketplace listing
• FMEAddons: Marketplace listing and documentation

FAQ