Help for owners
My WooCommerce orders are not reaching my accounting software
Short answer
WooCommerce disables a webhook automatically after more than five consecutive delivery failures, and its background tasks depend on a scheduler that can fall behind. Either leaves the accounting side empty. Check WooCommerce status for the webhook, do not re-enter orders, and send your developer the last order that synced.
Does this sound like your situation?
- New orders are in WooCommerce but not in my accounting software.
- A webhook shows as Disabled in the settings.
- The sync worked until the site was moved or updated.
- My bookkeeper is typing orders in by hand.
- Some orders went through twice.
Why does this happen?
WooCommerce switches off failing webhooks
WooCommerce states that it automatically disables a webhook after more than five consecutive delivery failures, where a failure is any response other than 2xx, 301 or 302. A short outage on the receiving side can therefore leave it off for good.
Confirmed by woocommerce.com
The delivery log shows the receiver's answer
WooCommerce saves logs of events that trigger a webhook, under WooCommerce, Status, Logs, filtered by the webhooks-delivery source. They show the response from the receiving server.
Confirmed by woocommerce.com
Background tasks can run late
Action Scheduler, the task queue used by WordPress shops, is by default started by WP-Cron. Its documentation says some past-due actions are normal but several more than a day old need investigating.
Confirmed by actionscheduler.org
The accounting side rejects the record
A missing tax code, an unknown customer or a renamed account in the accounting software makes it refuse an order, and a badly built connector then stops at that record.
The site moved or an update changed the connection
A new address, a certificate problem or a plugin update can break the link between WooCommerce and the connector, even though the shop looks healthy.
What can I do about it today?
- Find the last order that syncedNote its order number and date, and the first that is missing.
- Look at the webhook statusIn WooCommerce settings, open the webhooks list and see whether the status is Active, Paused or Disabled. Do not delete anything.
- Do not re-enter orders by handWhen the sync is repaired, catch-up may create them again. Keep a list of missing numbers.
- Ask what changedA site move, plugin updates, a new accounting plan or a changed password on the accounting side.
- Send the notes to your developerThe numbers, the webhook status and the name of the plugin or service that does the sync.
When should I bring someone in?
- Month-end or a tax filing is near.
- Orders reached accounting twice or with wrong amounts.
- You cannot tell which plugin does the sync.
How do I handle it?
- Compare shop and ledgerI list the orders in WooCommerce and the entries in accounting for the period, so missing and double ones are exact.
- Find the first failureI read the webhook delivery log and the task queue to see when and why the sync stopped.
- Repair the causeConnection, scheduler or a rejected record. A rejected record is set aside with a reason and the rest go on.
- Catch up without duplicatesMissing orders are sent once each, checked against order numbers.
- Add a checkA regular count comparison and an alert if the webhook is disabled.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Does it matter which accounting software I use?
The cause is found the same way: I read that software's official documentation and its logs first and tell you what it allows before changing anything.
Can I just re-enable the webhook?
It can help if the cause was brief, but it will be disabled again if the receiver still fails. The cause needs finding first.
Are my orders safe?
Yes. They are stored in WooCommerce. The problem is the link to accounting.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.