What we do
Tools
Industries
Department
How we workLet's talk →
Home/WooCommerce/Customize WooCommerce Checkout, Block or Classic
WooCommerce checkout

How to Customize the WooCommerce Checkout Page, for the Checkout You Actually Have

You pasted a woocommerce_checkout_fields snippet from a tutorial, saved it, reloaded checkout, and nothing changed. Or Checkout Field Editor is installed and its new fields never appear. Both usually mean the same thing: the store runs the block-based Checkout, and that tool was written for the classic shortcode checkout. WooCommerce now has two checkouts, and almost every customization question starts with which one is live on your site.

The short version

Find out which checkout is live. Open the Checkout page in the editor. A Checkout block means the block version. A Shortcode block means classic. Stores set up after WooCommerce 8.3 get the block version by default.

Pages All Pages Checkout Edit

On the block Checkout, select the Checkout block and use its sidebar to show, hide or require Company, Address line 2 and Phone. Brand-new fields come from the Additional Checkout Fields API or an extension that lists block support.

On the classic checkout, the Checkout Field Editor extension or a woocommerce_checkout_fields filter adds, edits and removes fields, and the classic action hooks still fire.

The block Checkout and the classic shortcode checkout, compared

Block Checkout

Built in the editor, extended through an API

  • Laid out with blocks, so sections, order notes, terms and the return-to-cart link are rearranged in the editor rather than in code.
  • Field toggles for Company, Address line 2 and Phone, each Optional or Required when shown.
  • New fields registered with woocommerce_register_additional_checkout_field() on WooCommerce 8.9 or later, in the contact, address or order section, as text, select, checkbox or date.
  • The page talks to the Store API, so the PHP filters and actions written for classic checkout don't run here.
Classic shortcode

The [woocommerce_checkout] template and its hooks

  • Checkout Field Editor works here, and only here: WooCommerce's own documentation says it supports the legacy checkout.
  • Fields added, changed or removed with the woocommerce_checkout_fields filter, and markup added at hooks such as woocommerce_after_order_notes.
  • Older field plugins and most one-page checkout plugins were written for this version.
  • Any block checkout can go back to it: select the Checkout block, choose Transform, then Classic Shortcode, and do the same on the Cart page.

If an extension or snippet you depend on only supports classic, switching back is a reasonable call, not a step backwards. If you're starting fresh, stay on blocks and add fields through the API. WooCommerce says native field customization is coming to the block checkout.

Adding a custom field to the block Checkout

For a developer, or a site owner comfortable adding a small plugin. Do it on a staging copy first.

  1. 1

    Confirm the WooCommerce version

    Plugins Installed Plugins WooCommerce

    The Additional Checkout Fields API needs WooCommerce 8.9 or later. On anything older, update first or use the classic checkout's filters.

  2. 2

    Register the field

    In a small custom plugin, call woocommerce_register_additional_checkout_field() with an ID that includes a namespace (for example my-store/delivery-note), a label, a location (contact, address or order) and a type.

    Watch for: the hook. Register on woocommerce_init or later. Registering earlier can cause initialization and translation problems.

  3. 3

    Decide when it is required or hidden

    A field can simply be required, or required and hidden can take JSON Schema rules that look at other fields, such as showing a business license field only when a company name is entered. The rules run in the browser and are checked again on the server.

    Watch for: rule complexity. WooCommerce warns that heavy schemas can slow checkout down.

  4. 4

    Know where the answer is saved

    Contact fields save to the customer's account and appear under Account details. Address fields save to the customer and the order. Order fields save to the order only. Values are stored as meta with the _wc_billing/, _wc_shipping/ or _wc_other/ prefix.

  5. 5

    Test with your real payment gateway and theme

    Place a test order with each gateway you take money through, and on the theme or page builder the live store uses. Then open the order in the admin and confirm the value is where your team expects to read it.

Why the checkout change you made isn't showing

A woocommerce_checkout_fields snippet that does nothing

How you'll know: The code is active, there's no error, and checkout looks exactly the same.

Fix: The block Checkout never calls that filter. Register the field through the Additional Checkout Fields API instead, or switch the page to the classic shortcode if you'd rather keep the snippet.

Checkout Field Editor's fields are missing

How you'll know: Fields you set up in the extension's settings don't render for shoppers.

Fix: It works with the legacy checkout only. Transform the Checkout block to Classic Shortcode, or rebuild those fields with the API or an extension that says it supports the Checkout block.

"There are no payment methods available"

How you'll know: Shoppers see this on the block Checkout even though a gateway is switched on.

Fix: The active gateway doesn't support the block Checkout yet. Select Configure Payment Options in the editor to review methods, update the gateway, or use classic until it catches up.

The field saves, and nothing happens with the answer

How you'll know: Delivery instructions and VAT numbers sit on the order screen, and the warehouse or finance team only sees them if someone thinks to look.

Fix: Saving a field is only half the job. Something has to move its value to the system that acts on it, which is the work described next.

Where a checkout answer has to go after the order

A field editor or the fields API stores what the shopper typed on the order. It doesn't know that a delivery instruction belongs on the packing slip your 3PL prints, that a VAT number on a wholesale order changes how the order is taxed in your accounting system, or that a "trade account" answer should send the order to a different fulfillment queue. Showing or hiding a field based on another answer is possible at checkout now. What happens next, in another system, isn't.

That's the piece n-frames builds for WooCommerce stores: the checkout value read from the order through the WooCommerce REST API or a webhook, then written into the warehouse, shipping or accounting system in the field that system actually uses. Fields that change pricing or what's being bought, rather than what happens after, are usually better handled by product add-ons.

Fields, plugins and page builders at checkout

Can I remove fields from the WooCommerce checkout page?

Some, without code. On the block Checkout, the sidebar hides Company, Address line 2 and Phone. On classic checkout with a classic theme, the Customizer's WooCommerce › Checkout panel has the same three options. Core fields such as name and address lines stay. Removing those means Checkout Field Editor or an unset() in the woocommerce_checkout_fields filter on classic, and payment gateways sometimes expect them, so test an order afterwards.

What is a one-page checkout in WooCommerce?

A layout that puts cart review, shipping and payment on a single page, sometimes with the product selection on the same page too. It comes from a plugin, not a WooCommerce setting, and most of those plugins were built around the classic checkout, so confirm block support before installing one.

Do I need a plugin to add a custom field to WooCommerce checkout?

No. On the block Checkout, a few lines registering the field with the Additional Checkout Fields API do it, and on classic, the woocommerce_checkout_fields filter does. A plugin is the easier route if nobody on your side maintains custom code, as long as it supports whichever checkout your store runs.

Does WooCommerce checkout customization work with page builders like Elementor?

Mostly. The trouble starts when a page builder's own checkout widget or template renders the classic form while you're customizing the block one, or the reverse, so changes seem to vanish. Check which checkout the builder's page actually outputs, and try any field change on a staging copy before the live store.

Who can make a custom checkout field reach our fulfillment or accounting system?

That's work n-frames does. We read the field from each WooCommerce order and write it into the system that acts on it: gift messages onto packing slips, delivery notes into the 3PL, tax IDs onto the customer and invoice in accounting, with orders that fail a rule flagged for a person.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.