Mailchimp for WooCommerce keeps a local sync table at wp_mailchimp_carts for abandoned carts and synchronizes WooCommerce customers and orders to a Mailchimp audience through the Mailchimp API. Each audience member carries a status field with values subscribed, unsubscribed, cleaned, pending, and transactional. The plugin tracks the local sync state through option values and the audience itself lives on Mailchimp's hosted infrastructure, accessible via the v3 API the plugin uses every day.

SleekView Kanban talks to the same Mailchimp v3 API the plugin uses, with the connection details pulled from the plugin's settings. Pick the audience member status as the group column and every contact becomes a card slotted under Pending, Subscribed, Unsubscribed, or Cleaned. Card fronts show the customer email, the linked WooCommerce customer name, the total spent according to Mailchimp's e-commerce data, and the date the subscriber was last updated, so the email team has the context they need to act on every record.

Dragging a card between columns calls the Mailchimp v3 PATCH /lists/{list_id}/members/{subscriber_hash} endpoint with the new status. The audience member updates immediately, automations gated on subscription status fire or pause accordingly, and the plugin's local sync state catches up on its next pass, exactly as it would after a manual status change in the Mailchimp admin or through an account-level workflow update.

Stores using Mailchimp for WooCommerce keep audience management split across two systems. WooCommerce holds the customer and order data. Mailchimp holds the subscriber status, engagement signal, and segmentation.

The plugin syncs between them on a schedule but the email team and the store team still need to switch tabs every time they want to see how a specific customer is doing across both systems. The disconnect shows up in the worst places. A repeat customer with $2000 lifetime value quietly unsubscribes and nobody on the WordPress side notices.

A complaint comes in through the support inbox and the support agent does not know whether to mark the subscriber Unsubscribed in Mailchimp or just delete the row. New double opt-in signups sit in Pending forever because nobody manages that column. A kanban view that reads and writes the same Mailchimp audience the plugin syncs to keeps the team in lockstep with the email infrastructure.

Every drag is a real API call, every column count reflects what Mailchimp's deliverability engine sees, and the cards themselves carry enough context for a new email manager to triage on day one without learning two admin screens.