Mailchimp for WooCommerce · Help

Mailchimp for WooCommerce has stopped syncing?

Trace connection, job execution and one specific order to the intended Mailchimp audience.

Source date: 5 November 2026Editorial team: KAN KAI WORKSEditorially updated:

Quick answer

An old Mailchimp sync timestamp does not identify whether the store connection, a task or destination mapping failed. Trace one test order through the connected account, store ID and audience to its log and response. Check possible downstream automations before resynchronising. Technical transfer and newsletter subscription are separate states; marking every contact subscribed does not repair an integration failure.

Source basis: Q1 · Q2 · Q3

Applies to
Mailchimp for WooCommerce with missing new shop data or connection errors. Reconnection helped the original reporter but is not a universal first repair step.
How to verify the result
The original test order and a further controlled change reach the correct destination, with task processing and expected commerce data aligned without unintended status changes.
Your first check

Does the store connection fail, or are only new records left unprocessed?

Select a known test order and compare store identity, audience, queue state and Mailchimp result. An old timestamp alone does not identify the failing stage.

Mailchimp shows an old sync time, new orders are missing or setup says the store cannot be created or updated. These states need separate investigation. In the reviewed report, reconnecting helped after connection problems; that does not make deleting every stalled integration a suitable first step. Q1

Follow one record rather than a timestamp alone

Choose an identifiable test order using your own test identity. Record its creation time and expected destination. A global timestamp does not reliably show whether that particular order is missing, a job is waiting or only the interface is stale.

Mailchimp documents connection troubleshooting and management of sync operations. Select the guidance that matches the observed stage. Q2 Q3

Trace the transfer path

  1. Check destination mapping: Confirm the connected account, store association and audience. A record arriving in another audience is a mapping issue, not proof that no transfer occurred.
  2. Separate connection from later work: Can the plugin connect the store and retrieve its basic information? An authentication failure during setup needs a different response from a job stalled after successful setup.
  3. Find the sample’s task: Inspect available plugin logs and the scheduled-task mechanism used by this installation. Record state, last execution and the first error. A long task list alone does not identify which operation is blocking progress.
  4. Compare execution and response: Does the task start, fail during the external request or fail to process an otherwise successful response? Match evidence to the same timestamp and record.
  5. Resynchronise with a defined scope: Use a supported retry only after understanding the failure and its extent. First check which downstream automations could be triggered by data arriving again.

Preserve context when reconnecting

If the connection itself needs rebuilding, record audience, store identifier, settings and relevant automation relationships. Follow the documented connection procedure and then confirm that the correct shop reaches the correct destination. Q4

Technical synchronisation is also different from permission to receive marketing. A correctly transferred customer can remain unsubscribed. Do not change those states indiscriminately to make the sync appear successful.

Verify the original sample order after recovery, then observe a subsequent controlled change. This provides stronger evidence than an updated global timestamp without any corresponding shop data.

Frequently asked questions

Should I uninstall the plugin immediately?

Not before documenting connection, mapping and failure stage. Rebuilding the integration can change relationships and make diagnosis harder.

Does an existing contact prove that an order synced?

No. The contact and specific commerce data are separate objects to check. Inspect the expected order or activity.

Can I mark all contacts subscribed?

That is not a technical repair. Transfer state and valid marketing permission must remain separate.

Information for assistance

Provide plugin version, timestamp, redacted sample identifier, destination mapping and the first error. Do not publish entire contact lists or API keys.

KAN KAI WORKS can investigate the data path from the store to its Mailchimp connection. Get help with this case.

Support with this issue

KAN KAI WORKS can investigate the data path from the store to its Mailchimp connection.

Describe your case →Related service: AI & automation

Sources and scope

Sources checked: 5 November 2026. The original incident has not been independently reproduced.