A report that “WooCommerce checkout is not working” is urgent but incomplete. It might mean an empty cart, a loading spinner, missing delivery options, an absent payment method or an error after the customer submits payment. Each symptom points to a different stage of the purchase path.

Start by narrowing the report. Avoid changing several plugins and settings at once: doing so can make the original fault harder to reproduce and the eventual repair harder to explain.

Capture the scenario before changing the store

Record the time, product, quantity, checkout URL, device and whether the shopper was a guest. For shipping problems, capture the destination region and postcode needed to reproduce the issue without collecting unnecessary personal details. Note the visible message or the point at which progress stops.

If RevenueGuard raised the incident, open the failed step and evidence first. A masked screenshot and browser errors can help describe the failure even when a later manual check passes. Record the last known passing check too; it helps establish a useful investigation window.

Reproduce the same path in a fresh session

Use the same product, cart conditions and address region in a fresh guest browser. Confirm that the product is available and the cart contains the intended item before looking at checkout. A different basket can produce a different result.

Compare the result with the original report. If the issue appears only on one device, customer state or region, preserve that difference. Do not mark the incident resolved simply because a different path reaches payment.

Identify the first failing stage

  • Product or cart: does the expected item enter and remain in the basket?
  • Checkout loading: does the page render and finish calculating the order summary?
  • Shipping: does the entered destination produce an appropriate method?
  • Payment availability: does the expected option appear for this cart?
  • Payment submission: did a separate, authorized payment attempt fail after submission?

RevenueGuard covers the configured journey up to payment availability and visible pre-submission errors. It does not execute the final payment step. That distinction tells you when to move from browser evidence to gateway records and a separate payment test.

Investigate a persistent loading spinner

A spinner can indicate that checkout has not received the information it needs. WooCommerce’s official guide describes possible JavaScript conflicts and invalid checkout responses. Inspect the browser console and the relevant failed request with your developer; record the error before applying a change. WooCommerce’s loading-spinner guide provides the technical investigation steps.

For a missing delivery method, follow the shipping-options checklist. For a missing gateway, use the payment-availability checklist. This keeps the work focused on the stage that actually failed.

Review recent changes and test safely

List changes made before the incident: plugin updates, theme changes, gateway settings, shipping rules and optimization settings. RevenueGuard’s available recent-change context can help form that list, but it does not prove which change caused the failure.

Use a staging copy for disruptive plugin or theme conflict testing. Preserve a recovery point before changes. WooCommerce documents isolating conflicts by testing components methodically; follow its official conflict-testing procedure with someone who understands the store’s dependencies.

Close the incident with evidence

After a repair, repeat the original failing journey. Check a fresh browser session and the next scheduled monitor result. If payment completion was involved, verify that stage separately. Record the change, the successful result and any remaining untested scenarios.

Tell the next person on the team what was checked, not just that the store “looks fine.” A short record of the symptom and recovery makes the next incident easier to handle and gives customers a more reliable support response.

FROM GUIDANCE TO OBSERVATION

See the path your store depends on.

RevenueGuard brings configured checkout checks, store signals and incident evidence into one place. Early-access availability is limited; paid purchasing is not open yet.

Request early access Read the setup guide
About this guide

Written by the SamSiyu editorial team for RevenueGuard. Product coverage reflects the current pilot. Examples are illustrative unless explicitly identified as verified tests. Check the release notes for changes.