The short answer
When WooCommerce checkout is not working, record the exact failing step, affected device and order reference before changing anything. Separate a payment failure from a missing delivery option, a confirmation problem or an unfulfilled order. Reproduce the issue safely on staging with the relevant payment testing setup, then test the complete journey after a fix.
What to take from this guide
- An unpaid order, a declined payment and a missing email are different problems.
- Preserve order and payment evidence before asking a customer to try again.
- Test on staging because test orders can trigger emails and connected systems.
1. Describe the failure in terms a customer would recognise
“Checkout is broken” leaves too many possible causes. A useful report says which product was in the basket, which delivery location was selected, what the customer clicked and what appeared next. Include the approximate time, browser and device, without collecting card details.
Record whether the problem affects everyone or one combination, such as a particular delivery method or payment option. Screenshots can help, but remove personal details before sharing them. Preserve any order reference so the support team can compare the store record with the payment provider record.
Our WooCommerce development and support expertise starts with the existing store and the operational problem. A clearer report makes it easier to investigate without replacing working parts unnecessarily.
2. Separate the failure from its visible symptom
A customer may see a failed confirmation page after a payment has already been recorded. A missing email can look like a failed purchase even though an order exists. Check the available store and payment records before asking someone to pay again.
WooCommerce order statuses help describe the stage reached, but the status alone is not a diagnosis. Read the associated order notes and the payment provider information. Keep the person investigating payments connected to the colleague responsible for dispatch or kitchen work.
| Reported problem | Evidence to check |
|---|---|
| No delivery option | The basket, address and configured delivery conditions |
| Payment will not complete | Order notes and the payment provider record |
| No confirmation email | Whether an order exists and what notification records show |
| Order exists but work never starts | The handover to staff or connected systems |
3. Reproduce the problem in a controlled environment
WooCommerce recommends testing orders on a staging site. Test orders can create emails, affect reports and reach other integrations, so check the complete setup rather than assuming that a payment sandbox makes every connected service harmless.
Use the payment provider’s documented testing method and approved test details. Reproduce the smallest version of the failing journey, with the same relevant product and delivery conditions. Ask the person responsible for integrations what will happen to stock, accounting or fulfilment during that test.
4. Test one plausible change at a time
A fault that appeared after an update is a useful lead, not proof of the cause. Keep a record of the last known working state and the changes made since. Your developer can use that evidence to narrow the investigation on staging.
Avoid switching off several live extensions simply to see what happens. Agree how a test will be run, how its result will be recognised and how the previous state will be restored. If recurring updates are exposing the same fault, discuss WordPress maintenance responsibilities alongside the individual repair.
5. Recheck the whole order, not just the payment button
After a fix, follow the order from basket to confirmation and the next internal action. Check the amount, delivery choice, email content and the record your staff use. Include an unsuccessful payment scenario using the provider’s test method so the message is understandable.
For collection or restaurant orders, the online promise must match staff capacity. The restaurant online ordering checklist covers time slots, alerts and handover. For a retail shop, agree equivalent checks for stock and dispatch.
6. Give support a short, usable handover
Close the investigation with the cause established, the change made and the journeys tested. If something remains uncertain, record it. Keep the support contact and the next action visible to the person looking after customers.
If the issue is part of a wider backlog, ecommerce support for Belfast businesses can help organise the priorities. A platform move is a separate decision: the Shopify versus WooCommerce guide is useful once the operational requirements are clear, rather than as an automatic response to one fault.
Common questions
Should I ask the customer to pay again?
Check the store and payment provider records first. An unclear confirmation does not establish whether money was taken. Use the approved customer support process to resolve uncertainty.
Should I test on my live WooCommerce store?
WooCommerce recommends staging for test orders. Check payment testing settings and connected services because emails, reports and fulfilment integrations can still react to test activity.
Does a checkout problem mean I need a new website?
Not necessarily. Identify the cause and whether a targeted repair is proportionate before comparing a larger rebuild or migration.
Sources and further reading
Primary references used in this guide. Platform details and requirements should be checked again when scoping a project.
Prepared by the Podium team. Illustrative examples are not client results.