alovio

WooCommerce / Alovio Checkout Fields

Classic & Block checkout

Alovio Checkout Fields renders and validates identically on the classic shortcode checkout and the WooCommerce Block checkout.

WooCommerce has two checkouts — the older classic (shortcode) checkout and the newer Block (Store API) checkout. Most field plugins support one well and the other poorly. Alovio Checkout Fields treats them as equals.

You don’t choose

There’s nothing to switch. The plugin detects which checkout your store uses and renders there. If you move from classic to Block (or run both), your fields, conditions and validation come along unchanged.

What’s identical

  • Field types and their settings.
  • Placement — the four checkout locations work on both.
  • Conditional logic — live show / hide / require behaves the same way.
  • Validation — required fields are enforced server-side on both, with clear messages.
  • Where data lands — values save to the same order, shown on the admin order screen and in emails.

So you can adopt the modern Block checkout without giving up the fields you depend on — and switch back without losing anything.

Good to know

  • The Block checkout needs a reasonably current WooCommerce with the Cart & Checkout blocks available; the plugin declares Block compatibility so WooCommerce treats it as Block-aware.
  • For no-JavaScript visitors, the correct initial visibility is computed on the server, so fields don’t flash in and out.
  • The plugin is HPOS (High-Performance Order Storage) compatible.

Next