Troubleshooting Centre
WooCommerce webhook not working: why is the order missing from the ERP?
If an order exists in the store but not in the ERP, first find the step where the notification stopped. Re-enabling the webhook or resending every order is not a solution on its own.
Short answer: Check event creation, the background job, HTTP delivery and ERP order acceptance separately. Do not resend until you have brought together evidence for all four stages for the same store and order ID. A successful HTTP response does not prove a valid order record exists in the ERP.
This guide covers order notifications sent by WooCommerce to an external system. Payment notifications sent by a payment provider to the store travel in the opposite direction; success in one does not verify the other. For example, the Stripe integration's webhook settings relate to payment integration. If you receive an authorisation error when calling the store's REST API, use the WooCommerce REST API 401 guide.
At which step did the notification stop?
Stock transfer from Mikro ERP to WooCommerce is a separate data flow. Updated stock does not prove that an order notification reached the ERP from the store; track acceptance records for both flows separately.
First narrow the investigation to one real issue, using an order ID and a time range with its time zone. The table below suggests a diagnostic sequence; a single log entry does not establish a definitive root cause.
| Observed condition | Evidence to require | Next decision |
|---|---|---|
| Order exists; no delivery record | Webhook status, selected event and the background job for the same order | Distinguish whether the event never occurred, the job is pending or records were deleted. Missing logs alone do not mean “not sent”. |
| Job pending or failed | Job time, latest error record and queue delay | First determine why the handler is not progressing. Do not run or delete the entire queue at once. |
| Delivery timeout, 4xx or 5xx | Destination URL, status code and the receiver's acceptance record at the same time | Separate address or access errors from processing errors. After a timeout, check whether the ERP may already have been updated. |
| HTTP success; ERP order not found | The receiver's durable acceptance record, job status and ERP document number | Investigate product, customer account, tax or warehouse mapping errors. Do not immediately recreate the order. |
| Webhook disabled | Last successful delivery, subsequent errors and affected order range | Resolve the cause and run a limited check; reconcile earlier gaps separately. |
Which WooCommerce screens should you check?
Settings → Advanced → Webhooks: check the status, topic and delivery address. The ping sent when an active webhook is first saved does not test whether a real order was processed in the ERP. Status → Logs: inspect the webhooks-delivery source. WooCommerce may disable a webhook after consecutive delivery failures; the threshold can vary with the installed version and filters. Official webhook management and error behaviour.
Status → Scheduled Actions: review pending and failed jobs for the relevant time range. Delayed background jobs can also delay delivery. WooCommerce's scheduled actions documentation explains this screen and its relationship with WP-Cron. In the current core code, the default asynchronous delivery job is named woocommerce_deliver_webhook_async ; plugins can alter the flow. Official queue implementation.
Compare log retention periods and time zones. A successful general health check does not prove that a particular order job ran. Do not create a test order that could trigger a new payment, email, invoice or shipment for a real customer; use a test environment with controlled side effects.
What can you check for a signature error without disabling security?
The default WooCommerce signature is the Base64-encoded HMAC-SHA256 of the sent body, carried in the X-WC-Webhook-Signature header. The receiver should use the incoming raw body rather than reformatting the JSON before calculating the signature, and verify the matching secret in an authorised environment. A filter can change the signature algorithm. Official signature and delivery implementation.
Compare signatures using suitable constant-time verification; do not treat a missing or invalid signature as permission to process an order. Separate the ping flow from the order flow. Do not disable signature verification or the firewall wholesale to resolve the issue. Do not share secrets, customer information or the full order body in support tickets; a sanitised error code, time and operation ID may be sufficient.
HTTP 200 was returned; why is there no ERP order?
If the receiver returns success as soon as it sees a request, subsequent work can be lost. In our proposed design, success is tied to durable acceptance of a verified notification or completion of the operation. If a queue is used, distinguish “received”, “processing”, “accepted by ERP” and “review required”, with a clear owner for failures. The integration must implement this behaviour; WooCommerce alone does not guarantee it.
A delivery ID helps tracing; use the store and order IDs as well to deduplicate business records. Creation and update notifications for the same order are different operations. Apply updates according to business rules rather than ignoring them, and prevent an older notification from overwriting a newer state. Detailed ownership and acceptance decisions are covered in the ERP integration planning guide.
Example: how are two missing notifications reconciled?
Illustrative scenario — not customer data: During an outage, delivery outcomes for store orders 4101 and 4102 are uncertain. In this example, the orders are eligible for ERP transfer; a real project must also apply payment, cancellation and refund rules.
| Order | ERP check | Controlled action |
|---|---|---|
| Store A / 4101 | An ERP record matches the external reference; lines and amount agree | Do not create another order. Link the existing document to the transfer record and reconcile the result as “accepted by ERP”. |
| Store A / 4102 | An authorised query finds no match, and no job is in progress | Verify the current order status and mappings. Perform one controlled transfer with deduplication protection, then verify ERP acceptance. |
| Outcome uncertain for either order | ERP is unavailable or records conflict | Stop automatic retries and await review by the responsible person. Do not assume uncertainty means failure. |
Deduplication must also stop two concurrent jobs from independently finding “no record” and both creating an order. Verify the ERP's support for a unique external reference or the integration's atomic operation protection during the project. Bound the number of attempts, waiting interval and total processing time, and assign notification responsibility. Verify successful queue-job completion and ERP record acceptance separately.
Do not assume re-enabling a webhook replays every earlier notification. Record the affected time range and reconcile store orders with ERP records. Transfer only verified missing orders in a controlled way; resending the entire history can duplicate stock, invoicing and shipping operations.
When is integration support needed?
If business acceptance cannot be traced despite apparently successful delivery, older events overwrite current data, or missing orders cannot be identified after an outage, the problem may extend beyond a single setting. Acceptance records, deduplication and reconciliation must be designed together.
Sources checked and content updated: 18 October 2026. Core-code links point to the development branch; the installation's WooCommerce version, plugins and filters must be verified separately. Scenarios and decision tables are architectural suggestions, not claims of customer results, testing on a running WooCommerce installation or manufacturer partnerships.
Let's clarify your order flow together
We can assess ERP acceptance and recovery after errors through our custom software development service.
Let's discuss your needs →