List Sync for WooCommerce

Your customers, in the list you already send from, with enough of their purchase history to build a segment out of — and nothing more than that.

Four rules, and they are the reason to choose this over the vendors' own plugins.

Nobody reaches your list without saying yes. The checkout asks, above the pay button, with the box unticked. The words they agreed to are stored on their order beside the answer and the time, so rewriting your opt-in text next month never changes what a past customer agreed to. And somebody who unsubscribed at your provider stays unsubscribed — their next order does not quietly put them back on the list, which is the complaint that ends with a shop's sending domain in a blocklist.

Nothing is sent from the request that caused it. The obvious version calls Mailchimp inside the checkout — and then Mailchimp having a slow afternoon is your checkout having a slow afternoon, and an unreachable Brevo is an error in the middle of somebody paying. Here a contact is queued and written a moment later in a request of its own.

A failure is kept, not dropped. A contact that cannot be written is retried on a widening delay — a minute, then two, then four — and after enough tries it is left on the screen with the provider's own reason beside it, for somebody to look at. The usual causes are a key that has been rotated and a list that has been deleted, and both are five-second fixes once you can see them. Fire and forget is why a shop discovers, months later, that the afternoon its provider was down is a gap in its list.

A marketing list is not a copy of your order book. What leaves your shop is an email address, a first and last name, how many orders, how much in total, when the last one was, and your tags. Not the shipping address, not the phone number, not the line items, not the order numbers. When a SaaS vendor is breached — and they are — what leaks is a name and an email rather than your customer file.

What it does

* Mailchimp and Brevo, chosen on one screen, with your own key * A consent box at the checkout, in your own words, recorded on every order * Order count, total spent and last order date as merge fields, so "spent over £200" and "has not bought since March" are segments you can actually build * Your own tags on every contact, and optionally a tag per category they bought from * The status that counts as a customer is yours to choose — the default is Processing, because an order nobody has paid for is not a customer * A queue you can see, with the reason beside anything stuck, and two buttons

Rules that are enforced rather than documented

* Only the provider's own host is ever contacted. Mailchimp's is derived from your key's own datacentre suffix, so there is nothing to mistype and nothing a stored setting could redirect; Brevo's is one fixed host. Both are checked again immediately before every request. * Your API key is stored, never rendered. The screen shows a mask, and a submitted mask means "unchanged", so a screenshot of this screen is not the credential to your whole mailing list. * No error message ever carries the key, its base64 form, or the datacentre host it names. * A store that has not finished setting up queues nothing at all, rather than filling a queue with rows that can only fail.

Free edition

A free edition is on wordpress.org: one provider, subscribers only — the same consent rule, the same off-the-request queue, the same host allowlist and the same minimum. Settings are shared, so upgrading keeps everything.

Every license includes

• One year of updates and priority support, delivered straight to your WordPress dashboard.
• Use on 1, 5 or 25 sites depending on your license — local, staging and development sites are always free.
• 30-day money-back guarantee — full refund, no questions asked.
• Keeps working after expiry — if you choose not to renew, the plugin keeps running exactly as installed; it simply stops receiving updates and support until you do.

Requires WordPress 6.4+ · PHP 7.4+ · tested up to WordPress 7.0. Works with the classic and block checkout alike.