Start by identifying whether your store uses the Checkout block or the classic [woocommerce_checkout] shortcode: their setup and customization controls differ. Then confirm the checkout page is assigned, check that payment gateways support the active checkout type, and verify that field and extension settings work together before changing a live store.
Identify your checkout implementation
Open the page assigned as your checkout page and inspect it in the editor. If it contains the Checkout block, the store uses block checkout; if it contains [woocommerce_checkout], it uses classic checkout. Stores started after WooCommerce 8.3, released in November 2023, default to Cart and Checkout blocks, but older or customized stores may still use the shortcode. WooCommerce’s blocks documentation describes the distinction.
As an Amazon Associate I earn from qualifying purchases.
This choice determines where to make changes. The block experience is configured in the editor or Site Editor; classic checkout’s documented field and policy controls are in the Customizer. A setting described for one implementation should not be assumed to exist in the other.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Choose between block and classic checkout
Neither checkout type is established by the cited documentation as universally better for sales. Choose based on your editing needs and the compatibility of your gateways and extensions.
#1 Best Overall
| Consideration | Checkout block | Classic shortcode |
|---|---|---|
| Editing workflow | Configure the Checkout block in the page editor; block themes also provide a Checkout template in the Site Editor. | Edit the shortcode-based page and use the Customizer for the documented checkout field and policy settings. |
| Field configuration | Use Checkout Fields block controls for supported fields, including Company, Address Line 2, Address, and Phone. | Use the Customizer to make Company, Address Line 2, and Phone optional, required, or hidden. |
| Payments | Displays available gateways compatible with block checkout, subject to gateway setup and order context. | Confirm that gateways are enabled and available for the store and order; check the gateway’s requirements for classic checkout. |
| Extensions | Extensions that add checkout fields or markup through hooks may require block-specific integration. | May be a practical fallback when an extension does not support block checkout. |
| Migration | The editor can offer a transform-to-classic option; Cart and Checkout should be reverted together when returning to classic. | Retains the shortcode-based checkout experience. |
These are workflow and compatibility differences, not evidence of a conversion-rate advantage for either mode. WooCommerce describes some design choices as conversion-focused, but its cited documentation does not provide a named, dated statistic measuring their sales effect.
Set up the Checkout block
Assign the checkout page
- Open WooCommerce > Settings > Advanced.
- Choose the page intended for checkout in the page setup and save the change.
- Open that page in the editor and confirm it contains the Checkout block.
WooCommerce says the page containing the Checkout block must be designated in these settings for the block to function properly. See the Checkout block documentation and WooCommerce page setup guidance.
Configure fields and totals
The Checkout block brings together customer details and order totals. The totals area can include the order summary, coupon form, and amounts used to calculate the total. Available content can respond to store settings and the current order.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Use the Checkout Fields block settings to adjust form-step headings and the documented visibility or requiredness options for Company, Address Line 2, Address, and Phone.
- Remove the Coupon Form from the totals section if it is not needed. WooCommerce describes most other totals blocks as locked.
- Do not infer that hiding fields increases sales. The documentation explains the controls but does not quantify the sales effect of field changes.
Adjust the Checkout template in a block theme
In a block theme, open Appearance > Editor > Templates > WooCommerce > Page: Checkout to edit the Checkout template. The default template uses a simplified header, and the editor lets you rearrange or style included blocks. WooCommerce presents the reduced-distraction header as a design rationale, not a quantified result from an identified study. More detail is in its Cart and Checkout customization documentation.
Understand Express Checkout
The Express Checkout block appears only when an active gateway supports an express method, such as WooPay, Apple Pay, or Google Pay. Availability depends on the store’s location and gateway setup; confirm support for the store’s geography and configuration rather than assuming every method will appear. WooCommerce recommends WooPayments where it is available, but the relevant availability must be checked for the store’s location.
Configure classic shortcode checkout
For a shortcode checkout, open the Customizer and use WooCommerce’s documented checkout settings. The Customizer covers whether Company, Address Line 2, and Phone are optional, required, or hidden. It also provides settings for assigning terms and privacy-policy pages and configuring privacy-policy text. The exact labels may vary with the site’s theme and WooCommerce version; use the Customizer documentation for the classic checkout rather than looking for block-editor controls: WooCommerce Customizer settings.
WooCommerce’s core-plugin guidance points users to community forums, Marketplace extensions, developer resources, and Agency Partners for advanced support or custom work. Use an extension or custom service only when it addresses a specific requirement, and check compatibility with the store’s actual WooCommerce version and checkout implementation.
Troubleshoot missing payment methods
“There are no payment methods available at checkout”
First check whether the active checkout type is compatible with the configured gateways. The Checkout block shows methods that are both available for the store and compatible with block checkout. If every active gateway is incompatible, the block can have no payment options to display. WooCommerce explains this behavior in its Checkout block troubleshooting documentation.
- In the gateway’s settings, confirm that it is enabled and configured.
- Check whether it is available for the store’s country or region, currency, and order details.
- Confirm that the gateway supports the checkout implementation currently in use and that the plugin version is current.
- If the gateway does not support block checkout and you need it, review the block editor’s option to switch to classic checkout. Test the full checkout flow after changing modes.
Compatibility can vary by gateway feature, geography, plugin version, and configuration. For example, WooCommerce’s PayPal Payments documentation describes support for selected block functionality, including some express buttons and card processing, while noting additional features were in development on that page. Treat that statement as page-specific rather than a guarantee for every method or setup, and check the current PayPal Payments integration documentation.
Check extension compatibility before migrating
Extensions that inject checkout markup through hooks, including some custom-field extensions, may need integration work to support Cart and Checkout blocks. WooCommerce says an incompatibility warning and an option to return to classic checkout can appear when a plugin declares incompatibility. Because Cart and Checkout blocks work together, revert both when returning to the classic experience; changing only one can leave the cart and checkout on mismatched implementations. See WooCommerce’s block compatibility and fallback guidance.
Compatibility statements on extension documentation can become outdated. WooCommerce’s Checkout Add-Ons documentation described that extension as not yet updated for block compatibility and recommended shortcodes at the time represented by that page. That is not enough to establish its status in 2026. Check the current extension documentation and test the exact version you plan to use before changing a live checkout: Checkout Add-Ons documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Check every checkout-field, add-on, shipping, and payment extension involved in the purchase flow.
- Verify the extension’s stated compatibility with your WooCommerce version and the chosen checkout type.
- Test customer details, delivery choices, taxes, coupons, payment, and order completion in a safe test environment before deploying changes.
Test the complete customer journey
A checkout page is working only when its page assignment, fields, delivery choices, payment methods, and extensions function together. After a setting or plugin change, test an order from cart to confirmation, including relevant shipping destinations and payment scenarios. The official guidance establishes the setup and compatibility considerations; it does not establish that a particular field layout or template change will improve conversion.
Quick Recap
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.
