Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsStart by checking whether your store uses the classic shortcode checkout or the block-based Checkout experience. That determines which native settings and extensions can change the page. WooCommerce already supports selected layout and field edits; plugins are useful when you need more field types, conditional rules, or order-level options such as tips and gift wrapping.
The available product information supports several examples, not a verified ranking of 14 “essential” plugins. The options below are organized by task, with compatibility caveats called out so you can check the fit before installing.
As an Amazon Associate I earn from qualifying purchases.
How to customize the WooCommerce checkout page
First identify the checkout architecture. WooCommerce’s [Checkout Documentation] says the classic customizer’s field visibility controls apply to the shortcode checkout. For the Checkout Block, make changes in the Site Editor instead. WooCommerce notes: “If you are using the Checkout Block (default for all new WooCommerce installs), you’ll see a link directing you to the site editor to make changes.”
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchClassic shortcode checkout
The classic checkout customizer lets you set Company name, Address line 2, and Phone to optional, required, or hidden. It also provides settings for the terms and privacy pages. These controls may be enough if your goal is simply to remove a field customers do not need or make a selected field mandatory.
#1 Best Overall
Checkout Block
Open Appearance > Editor to edit the checkout template. The Checkout Block combines customer details, shipping or delivery, payment methods, and order review. Its documented settings include a dark-mode input option, guided form-step options, and visibility or requiredness controls for Company, Address Line 2, and Phone. You can edit, move, or remove blocks in the Site Editor. See WooCommerce’s Cart and Checkout Block documentation and Checkout Block documentation.
Which checkout field editor works with WooCommerce Checkout Blocks?
There is no universal answer: compatibility is specific to each extension and can change with updates. WooCommerce explains that extensions declared incompatible may cause a store to switch back to classic checkout, and integrations that inject checkout markup through hooks may need changes to work with Blocks. Check the extension’s current documentation and test it on a staging site before using it on a live checkout.
| Option | Useful for | Architecture and caveat |
|---|---|---|
| Conditional Checkout Fields & Edit Checkout Fields (FMEAddons) | Adding extra field types, conditional display, and field fees. | The marketplace page claims Cart and Checkout Block compatibility. The product’s documentation distinguishes its features from the core block checkout’s supported additional field types: text, select, checkbox, and date. Confirm the current feature and compatibility details on the product page. |
| Checkout Field Manager (Checkout Manager) (QuadLayers) | Adding, editing, removing, or reordering billing, shipping, and additional fields; the listing also describes multiple input types and conditional fields. | The cited listing does not establish Checkout Block compatibility. Check its current documentation before choosing it for Blocks. See the WordPress.org listing. |
| Checkout Field Editor And Manager (Acowebs) | Visual field management and conditional controls. | WooCommerce documentation describes a form builder, conditional controls, and block support. The WordPress.org listing reports version 3.0.7, dated 2026-09-09, with support for WooCommerce 11.1 and WordPress 7.1; confirm those details against your installed versions. See the WooCommerce documentation and WordPress.org listing. |
| Cashier Checkout Field Editor | Editing, removing, rearranging, and adding billing, shipping, or additional fields. | The cited product documentation does not establish compatibility with current Checkout Blocks. Check its current compatibility information before installation. See the Cashier documentation. |
How can I add conditional fields to WooCommerce checkout?
Choose a field editor that explicitly documents the rules you need and supports your checkout architecture. Conditional display can show a field only when a relevant choice is made, rather than presenting every shopper with every question. Verify which field types and conditions the extension supports; a general claim that a plugin “customizes checkout” does not establish those details.
Recommended Free Tools
Before installing a field editor
- Confirm whether the store uses the shortcode checkout or Checkout Block.
- Check the current product documentation for explicit compatibility with that architecture and your WooCommerce and WordPress versions.
- Confirm the field types, conditional rules, fees, and data handling you actually need.
- Test field display, validation, order placement, and saved order details on staging before deploying.
When do order add-ons make more sense than a field editor?
Use an order add-on when you want customers to select an extra service or contribution, such as a tip, gift wrapping, rush handling, or a gift message. These are different from editing the core billing or shipping fields. WooCommerce’s Checkout Add-ons documentation describes those use cases, but says the extension had not yet been updated for Cart and Checkout Blocks and recommends the classic shortcode route. It also says: “As of WooCommerce 8.3, Cart and Checkout blocks are available as the default experience.” Because extension compatibility can change, verify the current status before relying on this recommendation.
Rank #3
When should you use custom code instead?
Custom code is appropriate for a bespoke field or an integration that does not fit an available extension, provided a developer can maintain it. WooCommerce’s checkout-fields guide covers shortcode-era hooks and points block developers to a separate additional checkout fields registration API with defined locations. Do not assume that code written for classic checkout hooks will work unchanged with Checkout Blocks.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to choose without overloading checkout
Match the tool to one clearly defined requirement: use native controls for the documented layout and field changes; a field editor for additional or conditional fields; an order add-on for optional services or fees; and custom code for a bespoke integration. Before deploying, make sure the chosen extension supports the checkout architecture in use, is maintained for your installed versions, and stores or displays the resulting information where your team needs it. The product pages describe their publishers’ features; they do not establish an independently measured conversion lift.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
