WooCommerce Checkout block customization is an editor-based task, but it also depends on store settings and extension compatibility. The block-based checkout is built from configurable inner blocks rather than one indivisible form. Depending on the store configuration, these can include Checkout Fields, Checkout Totals, Terms and Conditions, Actions, Payment Options and delivery-related blocks.
This distinction matters when you plan a layout change. Some options are available directly in the Checkout editor, while features such as Local Pickup are configured under WooCommerce settings. Payment methods are displayed dynamically according to gateway availability and compatibility with the Checkout block. Before editing, confirm that the designated checkout page uses the block-based Checkout block, not the classic checkout. Also remember that block themes provide Site Editor access to store templates, while non-block themes do not provide the same template access.
What the WooCommerce Checkout Block Controls
Editor Controls and Store Settings
Open the Checkout page in the editor and use the inner blocks to identify the part of the customer journey you want to change. The Checkout Fields block controls documented standard address information. Checkout Totals manages the order summary and related totals content. Terms and Conditions handles confirmation of store policies, while Actions includes navigation such as Return to Cart.
Other behavior is controlled outside the editor. Local Pickup, for example, requires configuration under WooCommerce > Settings > Shipping > Local Pickup, as well as a block-based Checkout page. Treat the editor and WooCommerce settings as connected but separate configuration areas. If an extension adds checkout fields, payment methods or fulfillment behavior, do not assume that its controls or compatibility are covered by the native Checkout block settings.
Managing Checkout Fields and Section Numbers
Native Field Visibility and Required Status
The documented native visibility controls cover three fields: Company, Address Line 2 and Phone. You can use the Checkout Fields block settings to decide whether these fields are shown. The same area also allows you to control whether Address and Phone fields are required.
These settings are shared with the Shipping Address and Billing Address blocks. Consequently, changing visibility or required status in one location changes the corresponding behavior in the others. This shared behavior should be checked before publishing a change, especially when billing and shipping information serve different purposes in the store’s order process.
Native controls should not be presented as a complete manager for every possible checkout field. Custom fields supplied by third-party extensions may require an extension that supports the block-based checkout. After editing, test the most relevant customer paths:
- Guest checkout and logged-in checkout.
- Mobile checkout layouts.
- Orders using different shipping and billing addresses.
- Orders where Address or Phone is required.
Numbered Checkout Sections
Form Step Options can add numbers to checkout section headings. This is a presentation and guidance control: it helps shoppers understand the order of the checkout sections without changing which customer data the store requests.
Use numbering when the arrangement of sections benefits from a clearer sequence. After enabling it, review the complete flow in the editor and in a customer-facing checkout. Section headings, field visibility and delivery choices should still form a coherent path on both desktop and mobile layouts.
Terms, Privacy Links and Return-to-Cart Controls
Terms and Conditions Configuration
Select the Terms and Conditions inner block in the Checkout editor to configure customer confirmation. The block includes a Require Checkbox setting. When enabled, customers must actively confirm agreement before proceeding.
WooCommerce can automatically link the Terms and Conditions and Privacy Policy pages in the block content when those pages are specified in the store settings. Check that the intended pages are selected before publishing the checkout. The checkbox and page links are configuration features; enabling them alone does not establish legal compliance for a particular jurisdiction. Review the wording and policy setup against the store’s legal and privacy requirements.
Return-to-Cart Navigation
The Actions block controls the Return to Cart link. You can show or hide this link and, when it is enabled, select the page to which shoppers are returned. This gives the store owner control over whether customers can easily leave checkout to review or change their cart.
After selecting the destination, use the link in a test order journey. Confirm that it leads to the intended page and that returning to the cart does not create confusing navigation for shoppers.
Coupon Form and Checkout Totals Layout
Locked and Movable Totals Blocks
The Checkout Totals block contains the order summary, coupon entry form and cost breakdown. Most inner blocks in this area are locked. Their position can generally be moved up or down, but the documented controls do not allow them to be removed.
Use List View and the contextual block controls to understand what is available in the current checkout configuration. A movement control is not the same as a deletion control. The exact blocks and restrictions can vary with the store context, so do not treat the documented behavior as a complete inventory of every totals-related block that could appear.
Removing the Coupon Form
The Coupon Form is the documented exception in the Checkout Totals area. It can be removed, while most other totals-related inner blocks remain locked. Removing it can simplify the visible checkout for a store that does not want customers entering coupons at this stage.
Before saving the change, decide whether existing customer journeys depend on coupon entry during checkout. Then test a complete order and review the resulting totals layout. If the block is repositioned rather than removed, check that the order summary, cost breakdown and payment area remain understandable.
Payment Block Behavior and Compatibility Checks
Why Payment Methods May Be Missing
Payment Options are dynamic. The block displays payment methods that are active in the store and compatible with the Checkout block. Activation alone is therefore not enough to ensure that a gateway appears in block checkout.
If an active gateway is incompatible, it may not be displayed. WooCommerce may offer a switch back to the classic checkout as a compatibility path. This should not be treated as a universal solution or as proof that another checkout configuration will support every extension.
Before changing a live checkout, inspect the active payment methods and verify block compatibility with the relevant extension provider. After customizing or switching to the Checkout block, confirm that each intended gateway appears and completes a test transaction. Also test the checkout with the store’s other payment, tax, subscription and fulfillment extensions rather than assuming that they work with blocks.
Setting Up Local Pickup with the Checkout Block
Local Pickup Prerequisites
Local Pickup in Blocks requires the block-based Checkout page. Configure the feature under WooCommerce > Settings > Shipping > Local Pickup and add at least one pickup location. Without a configured pickup location, the option does not appear at checkout.
Before enabling the method, confirm that the designated checkout page contains the Checkout block. Then review the pickup-location information and prepare separate test paths for customers choosing shipping and customers choosing pickup. Local Pickup configuration is not only an editor task: the WooCommerce setting and the block-based page must work together.
Customer Choice at Checkout
When Local Pickup is enabled, the Checkout block can display the Delivery, Shipping Options and Pickup Method inner blocks. Customers use Delivery to choose shipping or pickup. After that choice, the checkout shows the relevant shipping methods or configured pickup locations.
For pickup, the Pickup Method block presents the available configured locations. For shipping, the relevant shipping options are shown instead. Review both paths after making changes, because a checkout that looks correct for one delivery choice may still need separate validation for the other.
Local Pickup Limitations and Pre-Launch Testing
Address, Tax and Shipping-Zone Behavior
The block-based Local Pickup method does not require the customer to enter a shipping address before choosing a pickup location. Taxes are calculated using the address of the selected pickup location. The method is also available regardless of shipping zones.
This last point is important for stores that need geographic restrictions. If pickup must be limited through shipping zones, consider the legacy Local Pickup method instead. Do not select the block-based method without first checking whether its availability and tax behavior match the store’s operational model.
Avoid enabling both the new block-based method and legacy local pickup without checking the customer-facing result. Two similar choices can create confusing duplicate options. Verify the addresses assigned to pickup locations and confirm tax behavior through test orders.
Final Checkout Validation
Test on a staging site or after creating a reliable backup before applying checkout changes to a live store. A practical validation sequence should cover the configuration areas that can affect the order journey:
- Confirm that the page uses the Checkout block and review the inner blocks in List View.
- Test Company, Address Line 2 and Phone visibility, plus Address and Phone required status.
- Check guest and logged-in checkout, mobile layouts, and different billing and shipping addresses.
- Test terms confirmation, policy links and the Return to Cart destination.
- Review the totals layout after moving blocks or removing the Coupon Form.
- Verify that every active compatible payment method appears and completes a test transaction.
- Test shipping and pickup separately, including the selected pickup location and tax behavior.
- Review compatibility with third-party checkout, payment, tax, subscription and fulfillment extensions.
WooCommerce Checkout block customization is most reliable when each change is treated as a separate configuration decision. Native field settings cover Company, Address Line 2 and Phone visibility, while Address and Phone can also be required. Form Step Options adds numbered sections, and the Terms and Conditions and Actions blocks manage confirmation and navigation. In Checkout Totals, most blocks are movable but locked, while Coupon Form can be removed. Payment visibility depends on active gateway compatibility. Local Pickup requires a block checkout page, a configured setting and at least one location, with important address, tax and shipping-zone limitations. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.