WooCommerce checkout: blocks, setup and checks
Changing WooCommerce checkout? Check blocks and payment compatibility, configure the order flow and verify that customers can complete a purchase.
- Published
- Last updated
To configure WooCommerce checkout, choose the block or classic version your extensions support, assign its page and verify a complete test purchase. A checkout can look ready while a required payment method is missing.
Make the change on a staging store with a backup and administrator access. Keep its payment credentials in test mode and disconnect live fulfilment. Send test emails to addresses you control.
Choose a checkout that supports the store
Use the Checkout block when your required extensions support it. Retain classic checkout when a required extension depends on that version.
The Checkout block is edited through the WordPress block editor. Classic checkout renders the purchase form from [woocommerce_checkout]. WooCommerce made blocks the default for new installations from version 8.3, while keeping the classic page shortcodes available.
Choose by what customers must do. A subscription payment, a postcode-based delivery rate or a required business field must work in the chosen checkout. A visual redesign cannot compensate for a missing payment integration.
Treat a one-page checkout extension as another compatibility dependency. Putting product selection and payment on one page still requires working basket validation and payment processing.
Check extensions before switching
Check each checkout dependency against its official block support statement and installed version before replacing the page.
Record the WooCommerce version and theme alongside each extension’s version. Include these dependencies in your review:
- Payment gateways, wallets and recurring-payment extensions.
- Shipping rates, collection locations and delivery restrictions.
- Tax calculation and tax-exemption extensions.
- Checkout field editors, address lookup and order add-ons.
- Coupons, product bundles and other extensions that change the basket total.
WooCommerce Marketplace product pages show block compatibility. The editor can warn about declared incompatibility, and an incompatible gateway can disappear from the checkout. Use the official compatibility guidance to distinguish declared support from an assumption based on the plugin being active.
Read the extension’s release notes for the supported WooCommerce version and the features your store uses. Support for ordinary card payments does not prove that the same integration supports your recurring-payment flow.
Keep a small record of the required feature, documented support and staging result. If a necessary feature fails, retain the working checkout while you resolve that dependency.
Configure the checkout journey
Assign the checkout page first, then configure the account and delivery choices customers will see.
- Open the checkout page in the WordPress editor. Use the Checkout block for a supported block setup. For classic checkout, use a Shortcode block containing
[woocommerce_checkout]. - Set the matching cart experience. When reverting blocks to classic, use the block toolbar’s transform control and choose Classic Shortcode for both Cart and Checkout. Save the pages.
- Open WooCommerce > Settings > Advanced > Page setup. Assign the Cart and Checkout pages to their respective fields, then save. The page assignments tell WooCommerce where to send customers.
- Open WooCommerce > Settings > Accounts & Privacy. Enable guest checkout if customers can buy without registering. Choose whether to allow login and account creation during checkout. Save, then check the form while signed out.
- Configure delivery under WooCommerce > Settings > Shipping. Match a test address to its intended zone and confirm the available methods. Configure local pickup separately if the store uses it.
- For blocks, select Checkout Fields in List View. Set Company, Address line 2 and Phone visibility, then choose Optional or Required for visible fields. Check the Shipping Address and Billing Address blocks for the shared settings.
- Configure any additional field through a checkout field editor that supports your checkout version. Submit an empty required field, then a valid value. Confirm that the accepted value reaches the order or downstream record that needs it.
The account settings control the guest and registration journey. Enabling guest checkout does not remove account requirements for subscriptions. Test the actual product type, including the password setup email when account creation uses an emailed link.
The Checkout block reference identifies the built-in field controls. They do not replace a custom-field extension’s own validation and saved-order behaviour.
Restrict destinations, methods or customers
Use store settings or a compatible rules extension to enforce the restriction during checkout. Hiding the Place order button with styling leaves other submission routes available.
For destination restrictions, configure Shipping location(s) under General and the relevant Shipping zones. WooCommerce uses the first matching zone. Put specific postcode zones before broad regions. An address matching a zone without methods receives a no-shipping message, as the shipping-zone documentation explains.
To remove a shipping method from checkout, disable that method in the matching zone. Check other zones separately. Keep shipping configured for physical products even if another basket contains only products that need no delivery.
For customer-role or product-specific rules, use a compatible restriction extension with documented support for the condition you need. WooCommerce’s restriction settings include global and product-level rules for payment methods, shipping methods and destinations. These controls need the relevant extension installed.
For example, restrict a bulky product to supported delivery postcodes. Show a reason such as “Delivery is unavailable for this item at your postcode”. Give customers a working recovery path, such as removing the item or choosing an eligible collection option.
Test the same product with an allowed postcode and a blocked postcode. The allowed basket must reach payment. The blocked basket must reject the restricted delivery during submission, including a direct visit to checkout. Repeat customer-role rules with eligible and ineligible accounts. Confirm that changing the basket or address recalculates eligibility.
Keep basket data and prices consistent
Carry the exact variant and quantity into checkout, then let WooCommerce calculate the payable total from the current basket.
Use this hypothetical staging basket to trace the result. A navy shirt in size M costs $60 including tax. Two shirts cost $120. A coupon discounts those products by $12, and delivery costs $10 including tax. The expected total is $118.
Check the product variation in the basket, its quantity and coupon application. At checkout, confirm the same selection, the $108 discounted product total and the $118 payable total. The created order must retain that variation, quantity and discount. Tax lines must agree with the store’s configured inclusive-price calculation.
A store assistant must obtain the current variant’s price and stock before recommending it and again when adding it to the basket. A cached parent-product price cannot establish the price of a selected size. Recalculate delivery and discounts after the customer changes an address or quantity.
On staging, change the selected variant’s availability before submission. Confirm that checkout stops an unavailable purchase or follows the store’s configured backorder policy. Explain the changed availability and let the customer choose another variant. Preserve the basket while they recover.
Verify orders, payments and confirmations
Verify checkout with a payment provider’s supported test mode on staging, then reconcile the browser result with the order and payment records.
WooCommerce’s test-order guidance warns that test orders can trigger emails and connected services. Keep warehouse dispatch disconnected and use a test mailbox before placing an order.
For a store using WooPayments, follow this sequence:
- Open Payments > Settings on staging. Select Enable test mode, confirm it and save. Confirm the test-mode notice before entering payment details.
- Add the test basket and complete the checkout fields. Use a test card from the WooPayments testing instructions, with its supported expiry and security-code values.
- Place the order once. Expect an Order received page and find the matching order under WooCommerce > Orders. Match its total to the test transaction under Payments > Transactions.
- Inspect the order notes and stock movement. For a paid physical-product order, Processing normally means payment received and stock reduced. Confirm that the customer and merchant test emails reference the same order.
- Repeat with the provider’s documented declined-payment card. Expect a decline message and no successful payment for that attempt. Inspect the order status and notes even when the customer sees an error.
- Test an interrupted return from the payment flow. Before retrying, search the order and gateway records for that attempt. If payment succeeded, recover the existing order’s confirmation instead of requesting a second payment.
WooPayments marks test orders and prefixes its order emails with [Test]. Use another gateway’s own test instructions if that is what the store runs.
WooCommerce’s order status definitions distinguish Pending payment from paid Processing orders. Block checkout can also create Draft records before submission. A delayed confirmation can leave an order On hold, so the browser message alone cannot establish whether money moved.
Keep order and payment records while investigating. For a mismatch, collect the order number and provider transaction reference, then reconcile the provider’s confirmation with the order notes before taking payment again.
Diagnose broken blocks and missing methods
For a missing gateway, check block compatibility and payment eligibility before changing the checkout layout.
| Symptom | Fastest useful check | Recovery to verify on staging |
|---|---|---|
| Gateway appears in settings but not checkout | Check the integration’s block support, enabled state and supported currency or customer location | A supported test basket displays the method and completes its test payment |
| No shipping options | Check the address’s first matching zone, enabled methods and applicable restriction rules | An allowed address returns the intended rate, while a blocked destination keeps its explanation |
| A required field never appears | Check whether the field editor supports blocks or only classic checkout | The field appears, rejects an empty value and saves a valid value |
| Checkout remains blank or shows a script error | Check the browser console and recent theme or extension changes | The same basket renders and submits without that error |
| Confirmation page fails after payment | Find the existing order and payment reference before retrying | The paid order shows the correct status and its confirmation can be recovered |
Follow WooCommerce’s plugin and theme conflict procedure on staging. Use a default theme and retain WooCommerce plus the gateway under test. Re-enable other extensions individually and repeat the failing action after each change.
Send the responsible extension developer the exact reproduction steps, checkout type and software versions. Include a redacted console error, relevant gateway log and order reference. Keep card details, credentials and customer personal data out of the report. Verify the repaired flow on staging before applying the checked configuration to the live store.
Speed up a slow WooCommerce checkout
Measure each checkout stage to locate the delay before changing extensions or hosting.
Open the browser’s Network panel on staging and keep the same basket and address for each comparison. Record the initial page request, address-change recalculation and payment submission separately. Match slow requests to server logs or the gateway’s test records.
| Slow stage | What to inspect | Isolated change and expected result |
|---|---|---|
| Page appears late or controls become usable late | Document response time, large assets and script errors | Remove an unnecessary checkout asset on staging. Expect a shorter download or less script work, with the same checkout controls |
| Shipping or tax spins after an address change | The recalculation request and the rate or tax service’s response | Repair the failing service configuration or conflicting extension. Expect the request to return valid totals without the earlier delay or error |
| Place order waits after submission | Checkout request timing, gateway response and order notes | Correct a failing payment connection or synchronous integration identified in logs. Expect the same test payment to confirm without that recorded wait |
| Requests stay slow with the minimum supported extensions | Server response timings, worker saturation and memory errors | Ask the host to address the measured resource limit. Expect lower response time under the same test conditions |
WooCommerce’s slow-site guidance covers extension load, theme behaviour and hosting capacity. Make one staging change at a time. Re-run the same purchase after each change, including its order and stock checks. Keep the change only when the measured delay improves and the purchase remains correct.
Exclude the cart and checkout from full-page caching. WooCommerce’s page troubleshooting guide explains that these pages contain session-specific data. After correcting cache rules, use two separate private sessions with different baskets. Each session must retain its own items and fresh totals after a reload.
Preserve the payment and order records while diagnosing timing problems. Finish with a successful payment and the nearest failed-payment case, using the tested configuration you intend to release.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.