Choose a WooCommerce checkout format that supports your required payment methods, shipping tools and custom fields. The Checkout block provides a block-based interface, while classic checkout uses its established shortcode-based workflow and extension hooks.
IN THIS ARTICLE
01 Inventory the checkout dependencies
List payment gateways, express-payment buttons, shipping extensions, address tools, fees, subscriptions and custom fields. Check each developer's current compatibility statement for Cart and Checkout blocks. An extension working elsewhere in WooCommerce does not prove that it integrates with both checkout formats.
02 Test the intended format
- Back up the store and create an isolated staging copy.
- Inspect the assigned checkout page to identify whether it uses a Checkout block, a classic checkout block or the checkout shortcode.
- Review any compatibility warnings in the editor and the official documentation for essential extensions.
- Configure the chosen format on staging without placing both checkout implementations on one page.
- Test representative products, addresses, coupons and payment methods through complete sandbox orders.
- Deploy the tested change and verify the assigned page and cache exclusions.
Why is my payment gateway missing in the block checkout?
The gateway may lack block integration, be disabled, use incompatible currency or location settings, or fail to load its required scripts. Check its current documentation and logs rather than assuming the entire checkout is broken. An available classic integration does not automatically register the gateway in the block interface.
Should I switch to classic checkout to fix every issue?
Only when it is an appropriate supported choice for the store. A format switch can help isolate compatibility, but it will not correct invalid credentials, broken HTTPS or an unrelated server error. Record what changed and test the actual cause.
03 Verify more than appearance
Check guest and registered customers, mobile use, shipping recalculation, payment callbacks and order emails. Confirm that required checkout fields reach the order and fulfilment integration. Keep a recovery copy of the previous page and settings. After future extension updates, repeat the critical checkout tests because compatibility can change independently of the visible page design.