WooCommerce webhooks not working: how I trace missing orders
WooCommerce webhooks not working? How I trace missing orders through delivery logs, background jobs and receiving systems before scoping an integration fix.

An order appears in WooCommerce, but it never reaches the warehouse, CRM or internal application that should receive it. Checkout worked. The customer has an order number. Your team is still copying the details across by hand.
If the connection uses WooCommerce webhooks, I would trace one missing order through the delivery journey: the event in the store, the outbound request, the receiving application and the final saved record. Each stage needs evidence. A green delivery result is useful, but it does not prove the business task completed.
First, confirm how the order sync actually works
A webhook sends an event notification to another system. WooCommerce supports events involving orders, products, customers and other resources, as its webhook documentation explains.
Some integration plugins instead fetch orders on a schedule, or combine polling with webhooks. Before changing settings, I would identify which mechanism your connection uses and which system owns it.
I would then choose one missing order and one successful order to compare. Their creation times, statuses, payment methods and relevant custom fields can help narrow the problem. I would also confirm the expected rule: should every new order sync, or only orders that have reached an agreed stage?
Check the webhook status, topic and destination
The core webhook settings are under WooCommerce, Settings, Advanced, then Webhooks. I would check whether the relevant webhook is Active, whether its topic matches the event the integration expects and whether its delivery URL still points to the right endpoint.
An order-created event is not the same requirement as “send this order when payment is confirmed”. The receiving application may need to interpret later changes as well. That business rule should be documented rather than inferred from a webhook's name.
A hosting move or application deployment is a reason to check the endpoint again. I would compare the configured destination with the receiving application's current route, including its hostname and path.
Read the delivery log for the missing order
WooCommerce's delivery logs are available under WooCommerce, Status, Logs; the current interface lets you filter for webhooks-delivery. They provide delivery and response information, described in the official webhook guide.
I would correlate the event time with the receiving application's logs, allowing for different time zones. The useful evidence includes the endpoint, response code, duration and any available delivery identifier.
A not-found response points towards checking the route. An access-denied response calls for checking which layer rejected it. A timeout requires looking at both the connection and how long the receiver spends handling the request. Those are investigation paths, not diagnoses based on one status code.
If the integration has no delivery record for the event, I would check the trigger and background processing before assuming the receiving application is at fault.
A disabled webhook needs a cause and a recovery plan
WooCommerce can disable a webhook after repeated unsuccessful deliveries. Its documentation describes that failure behaviour. I would investigate the failures before reactivating it.
If the endpoint is still rejecting requests, switching the webhook back on does not fix the connection. I would first confirm the destination can accept the expected event.
I would also list the orders affected during the interruption. Reactivation is not evidence that those missing orders have been recovered. A controlled backfill needs an agreed date range, clear matching rules and a way to avoid creating duplicate records.
Orders are arriving in the store but missing elsewhere?
Tell me which systems should be connected, when the sync stopped and what your team is doing manually. I can scope a focused review of the integration.
Discuss your WooCommerce integration
Check background processing when deliveries are delayed
WooCommerce core includes a background delivery path for webhooks, visible in its webhook scheduling source. I would check the installed version and integration behaviour rather than assume every connection runs immediately.
Where Action Scheduler is involved, its administration screen exposes pending, failed and completed actions with details useful for investigation. I would correlate the relevant action with the missing order and inspect its history.
An unrelated failed action does not explain the integration fault. I would identify the hook and arguments involved, then check why that work is waiting or failing. Clearing a queue without understanding its contents can remove work the business still needs.
Check signature verification without bypassing it
A receiving application should verify that an event came from the expected source. WooCommerce's webhook code reference describes its payload signature: a base64-encoded HMAC-SHA256 value. The signature is generated from the encoded body using the configured secret.
If verification fails, I would compare the secret configuration and the exact body used by the receiver. Parsing and rebuilding JSON before checking the signature can change the bytes. I would inspect that handling rather than remove the check.
The initial activation ping is also not a complete order-processing test. Receiving it successfully does not demonstrate that a real order payload is verified, mapped and stored correctly.
A successful response still needs a processed record
The receiver may accept the request and put work onto its own queue. In that design, I would check that acceptance means the event was safely recorded, then follow the processing job to its result.
A warehouse reference, CRM record or internal order identifier provides stronger evidence than an HTTP response alone. I would check the fields that matter to the workflow, including quantities, addresses and any agreed custom data.
Repeated notifications and later order updates also need deliberate handling. The integration should prevent repeating a business action while still accepting legitimate changes. A blanket rule that ignores every subsequent event for an order could discard an update the receiving system needs. My article on duplicate orders in Laravel integrations explores that related issue.
Verify the whole journey and reconcile missing orders
I would use test data in an isolated setup that cannot accidentally dispatch goods or send live customer notifications. The checks should follow the same event and rules as the affected workflow.
The verification plan should establish that:
- The intended event produces a delivery.
- The receiver accepts and verifies the payload.
- Any queued processing finishes and records an outcome.
- The destination contains the correct order and required fields.
- Repeating an event does not repeat the business action.
- A legitimate later update is handled as agreed.
After that, I would reconcile the affected live orders through a controlled recovery process. I would also agree how future failures become visible, who responds and what information they need. Monitoring should cover the final processing outcome as well as the outbound request.
What to send when you need integration help
A useful enquiry names the systems involved, the expected trigger and when the problem began. Include whether all orders are affected or only a particular type. Sanitised log excerpts can help; secrets and customer details should stay out of an initial message.
I am Adam Dawson. My WooCommerce development work includes custom plugins, third-party integrations and focused code reviews. If your store's order flow relies on an external system, I can help define where the connection is failing and scope the work needed.
Find where your order sync breaks
Start with the systems involved and the business task that is not completing. I will help define a focused investigation before changes are made.
Talk to Adam about missing orders
Explore WooCommerce support
Need a hand with this?
Get help with a broken order journey, custom store features or ongoing WooCommerce care.
Find the right support
- Help with a broken WooCommerce checkout
- Speed up a slow WooCommerce store
- Fix WooCommerce order emails that are not sending
- Fix GA4 purchase tracking for WooCommerce
- WooCommerce development and custom features
- WordPress and WooCommerce care plan prices
- WooCommerce label and PDF designer, with practical printing tutorials
A related project
A custom price history feature for WooCommerceBespoke plugin work to record product price changes and present the history by date, delivered through an agency.
Related Articles
Building a WooCommerce Store Versus Maintaining One -- Why They Are Different Jobs
Building a WooCommerce store and maintaining one that handles complex business logic are completely different types of work. Here is what changes when a store becomes operational infrastructure.
Why WordPress Sites Get Slow and How to Fix Them
A slow WordPress site is almost always caused by one of a handful of fixable problems. Here is how to diagnose what is actually slowing yours down and how to address it properly.
Why WordPress Agencies Should Build Their Own Blocks Plugin
Custom WordPress blocks can save time, reduce messy theme code, and make sites easier to manage. DawsonyWeb builds reusable blocks, plugins and WooCommerce tools for businesses and agencies.