This article lists the known limitations of the iPaaS.com Mailchimp integration. Every flow in this integration runs in one direction — FROM iPaaS.com → Mailchimp — and writes to the Mailchimp Marketing API. The behaviors described here reflect the integration and the Mailchimp platform at the time this documentation was written; Mailchimp may change platform behavior, and the integration may add capabilities, after that date.

Review this article alongside the Connections and Settings, Installation Instructions, API Endpoints, Error Messages, and the per-collection Mapping Documentation articles before enabling the integration in production.

This integration was validated against the Mailchimp Marketing API v3.0 (the /3.0/ lists/members and e-commerce stores namespaces), using unversioned production endpoints as tested on 2026-06-29. The integration authenticates to the Mailchimp Marketing API using your Mailchimp API key against your account's data-center base URL (for example, a server prefix such as us13). The behaviors below were confirmed at the time this documentation was written and may change if Mailchimp revises its platform.

Mailchimp does not send change webhooks back to this integration, so there is no inbound flow. Every collection runs only when an enabled iPaaS.com outbound trigger fires or a Manual Sync is requested. Changes made directly in Mailchimp are not pulled back into iPaaS.com. This reflects the integration's design at the time this documentation was written.

The integration does not support initialization — that is, there is no bulk backfill that loads all existing iPaaS.com records into Mailchimp in a single operation. Records reach Mailchimp through enabled outbound triggers or one record at a time through Manual Sync. For a one-time load of a large set of existing records, subscribers or their MiSP can perform a bulk sync using Postman. This reflects the integration's behavior at the time this documentation was written.

When the integration updates an existing Mailchimp record, it sends a partial update of the mapped fields rather than replacing the entire record. Fields that are not mapped, or that resolve to no value, are left as they are in Mailchimp rather than being cleared. Because of this, there is no full-replace overwrite risk from this integration. The integration also does not implement collision handling: when both systems have changed the same record, there is no automatic reconciliation of the two versions — the outbound write applies the iPaaS.com values for the fields it sends. This reflects the integration's behavior at the time this documentation was written.

Removing an audience contact (member) from Mailchimp through this integration is not supported; the Customer collection adds and updates contacts only. An attempt to delete a member reports that deleting members is not currently supported. This reflects the integration's behavior at the time this documentation was written.

Deleting a Mailchimp e-commerce order, or an individual order line, through this integration is not supported; the Order and Order Line collections add and update only. This reflects the integration's behavior at the time this documentation was written.

Order lines are children of their order and transfer as part of the parent order. There is no Manual Sync entry point for an individual line, and there is no separate trigger for a single line. A change to one line is reflected in Mailchimp only by re-syncing the parent order. This reflects the integration's behavior at the time this documentation was written.

When a Product carries its own variants, those variants transfer as children of the parent Product. The child Product Variant collection has no independent Manual Sync entry point. To re-send a single variant on its own, use the Standalone Product Variant collection (which requires the parent Product to be linked to Mailchimp first). This reflects the integration's behavior at the time this documentation was written.

Product and Product Variant deletes are keyed entirely on the external-id link iPaaS.com records when the record is first added or updated. A Product or variant that was never added or updated through the integration has no such link and therefore cannot be deleted through the corresponding Delete collection. This reflects the integration's behavior at the time this documentation was written.

Variants can reach Mailchimp through two collections: the child Product Variant collection (during a full Product transfer) and the Standalone Product Variant collection (a single-variant re-sync). Both target the same Mailchimp variants. If both are enabled with overlapping triggers, a variant can be written from two paths. Review the collections' filters and Add/Update settings before enabling them so a variant is not written unexpectedly from two paths at once. This reflects the integration's behavior at the time this documentation was written.

In Mailchimp, an audience contact belongs to one and only one audience (list). The default mappings pass a single audience as a static value. To assign different Customers to different audiences, use a dynamic formula or multiple filtered mappings rather than the single static value. This reflects the Mailchimp platform behavior at the time this documentation was written.

Mailchimp merge-field tags must be uppercase and 10 characters or fewer, or Mailchimp rejects the field. Any merge field mapped through this integration must satisfy that rule. If a mapped merge field does not yet exist in the audience, the integration creates it and then populates it. This reflects the Mailchimp platform behavior at the time this documentation was written.

The opt-in status applied by the integration never changes the opt-in preference of a contact that already exists in the audience; it applies to contacts added through the e-commerce path. A contact who does not opt in is added as a transactional member. This reflects the integration's behavior at the time this documentation was written.

Several Mailchimp identifiers are length-limited, and a value that exceeds the limit causes the transfer to fail:

These reflect the Mailchimp platform behavior at the time this documentation was written.

If a product or variant identifier (SKU) contains the reserved characters /, ?, or #, a Special Character Replacement value must be configured in the subscription settings, or the product or variant cannot be created or updated. This reflects the integration's behavior at the time this documentation was written.

The integration builds each variant's external-id link from a composite of the variant, parent product, and store identifiers, separated by the Variant External Id Delimiter configured in the subscription settings. Without that delimiter configured, product transfers that create variants, and variant transfers and deletes, cannot complete. This reflects the integration's behavior at the time this documentation was written.

A Mailchimp e-commerce order, product, e-commerce customer, and variant all belong to a specific store, so a store identifier is mandatory for those records. The store identifier is read from an iPaaS.com custom field whose name must be one of store_id, Store Id, Store ID, or Store_Id (for the Product write flow the store identifiers are read from the Product's Store IDs custom field). Without a store identifier, the e-commerce record is not written. This reflects the integration's behavior at the time this documentation was written.

A Customer's address fields are read from the Customer's primary billing address. A Customer without a primary billing address sends no address values. This reflects the integration's behavior at the time this documentation was written.

The integration does not expose iPaaS.com-side custom fields as a configurable mapping feature. It does read specific values from named iPaaS.com custom fields (the store identifier and, for Customers, the opt-in status), but these are routine mapping inputs rather than a configurable custom-field surface. Mailchimp merge fields are how custom contact data is carried into an audience. This reflects the integration's behavior at the time this documentation was written.

Mailchimp limits the Marketing API to 10 simultaneous connections per account and returns a rate-limit response (HTTP 429) when that limit is exceeded; it also enforces a 120-second timeout on API calls (Mailchimp API Fundamentals, retrieved 2026-06-29: https://mailchimp.com/developer/marketing/docs/fundamentals/). If the Mailchimp API is temporarily unavailable or rate-limited when a transfer runs, the transfer fails. The error appears in the iPaaS.com Dashboard / Integration Monitoring / Error Logs and can be retried via Manual Sync (for an order line, by re-syncing its parent order). To reduce throttling, stagger large transfer jobs rather than running many at once. This reflects the Mailchimp platform behavior at the time this documentation was written.

The integration ships with template mappings that contain example values. These are intended to demonstrate the mapping and must be replaced or removed during implementation before enabling the collections in production:

This reflects the shipped template mappings at the time this documentation was written.

This article documents 19 known limitations of the iPaaS.com Mailchimp integration at the time it was written.