WooCommerce: blank checkout or expired session after going back?

After removing the last item, the browser’s Back button leads to an empty checkout or a session-expired message. An old success notice may remain visible at the same time. The reviewed report describes different behaviour on desktop and mobile, but does not establish a confirmed cause. Q1

Understand which state is failing

A checkout without purchasable items is different from a populated cart whose session has been lost. The browser may also display an earlier view while the current cart is already empty. An HTTP 200 response only shows that a request received a response; it does not establish that the complete checkout is usable.

The following comparisons are a diagnostic method, not a claim about a particular WooCommerce defect. Use a test product and stop before completing payment. Keep the product, account state and navigation sequence consistent between comparisons.

Run four controlled comparisons

1. Start fresh: Open a new private window, add one item and navigate directly to checkout. If it loads correctly, the basic route works for that session.
2. Use an empty cart: Remove the item and visit checkout directly again. Record the redirect or empty-cart message. This provides the baseline for the history-navigation test.
3. Use the Back button: Repeat the original navigation sequence. Determine whether the browser merely shows an old view or sends a new request that fails with a session error. Preserve the first console or network error, rather than only the messages caused by it.
4. Compare browser and product type: Repeat the same steps in another browser. If the affected product is a subscription, compare it with a simple product on staging. A difference narrows the involved route; it does not, by itself, prove that the subscription extension is faulty.

Act on the result

Inspect the cache rules and actual responses for dynamic store pages. WooCommerce documents exclusions for these routes. If the response already shows cache bypass, continue investigating instead of declaring caching the cause without further evidence. Q2

If only history navigation fails, examine the theme and checkout extensions’ handling of changing state on a test copy. If every fresh visit fails, follow the specific server or JavaScript error first. Repeated automatic reloads can conceal the failure and discard customer input without correcting the underlying transition.

Frequently asked questions

Does “back_forward” prove that a browser cache is broken?

No. It describes the navigation category. It does not identify the cache layer in use or establish the cause of the checkout failure.

Should I delete every customer session?

Not as the first experiment. That removes useful evidence and can affect other carts. Begin with an isolated test session that you control.

Is an empty checkout always a payment problem?

No. If no payment request is made, the observed failure occurs earlier. Network inspection helps establish that boundary. Q3

Information for a useful support request

Provide the browser, device, checkout type, product type, exact click sequence, WooCommerce version and redacted response messages. Do not publish session cookies or payment information in screenshots.

KAN KAI WORKS can investigate the affected navigation path and session transitions. Get help with this case.