WooCommerce orders not syncing? Start with delivery, not the dashboard.
When an order is missing from inventory, fulfilment or accounting, first establish whether WooCommerce created the order, whether it sent the event, and whether the receiving system accepted it. A dashboard status rarely shows the whole path.
Last reviewed
Where an order handoff can break
WooCommerce webhooks send an event to a receiving URL when an order changes. Delivery can fail because the receiver is unavailable, credentials changed, a firewall blocks the request, the payload no longer matches the receiver’s expectations, or the endpoint responds too slowly. A successful HTTP response also does not prove that downstream processing finished.
Order state matters. A payment can leave an order pending before it reaches the status that triggers an integration. Some extensions listen only to selected status transitions, so a custom status or a manual edit may bypass the expected event.
Diagnose it in order
- Find the order ID and exact status history in WooCommerce.
- Inspect the webhook delivery log for event, destination, response code, response body and attempts.
- Check receiver logs at the same timestamp using a request ID, if one is available.
- Compare the receiver’s saved record with the original order, including currency, line items and customer identifiers.
- Replay a test event in staging and verify that replay does not create a duplicate.
Make recovery part of the integration
Use idempotent processing: the receiver should recognise the same order event again and update or ignore it safely. Retry transient errors with limits and backoff; route permanent validation errors to a visible queue. Reconcile orders by ID and status so an exhausted webhook retry cannot become a silent gap.
Do not replay production orders until the receiver’s duplicate behaviour is understood. A replay can multiply fulfilment or accounting actions if downstream processing is not idempotent.
When is it worth doing?
If a sync is one-way, low-volume and already has useful logs, repairing the endpoint or credentials may be enough. If orders cross several systems or failures affect fulfilment, stock or financial records, give the integration an owner, recovery path and regular reconciliation.
See our integration work, or request a written measurement.
Check these after the change
Order sync questions
Where can I see WooCommerce webhook failures?
Review the webhook delivery logs in WooCommerce and compare the attempt time and response with logs at the receiving system. The location and detail available depend on the WooCommerce version and extensions in use.
Should I manually resend a failed order webhook?
Only after confirming the receiver is safe to process a repeated event. Otherwise a retry may duplicate fulfilment, inventory or accounting actions.
Why do some order statuses not trigger a sync?
The integration may subscribe only to specific events or status transitions. Check its configured topics and how custom statuses are handled.
Can webhooks guarantee every order reaches the other system?
Delivery attempts alone cannot guarantee end-to-end processing. Durable logging, retry handling, receiver acknowledgments and reconciliation close the gaps.
GeneLean360: a named order path across three systems
The case study maps GoHighLevel sales and onboarding, WooCommerce commerce and membership, and ShipStation fulfilment using a shared SKU scheme.
Read the GeneLean360 integration study →Find the missing handoff.
We trace what happens between order creation and the system that needs to act on it.