Summary
This mapping collection sends an iPaaS.com Product to Mailchimp as an e-commerce product on one or more Mailchimp stores. Mailchimp e-commerce products are what audience members shop, view, and purchase, and they power Mailchimp's product-based automations, recommendations, and reporting. The collection keeps the product's title, identifier, price, inventory, image, and store assignment aligned with the current iPaaS.com Product record. It is a combined Add/Update flow: a Product that is not yet present on a store is created, and a Product that already exists on that store is updated. All data moves in one direction, from iPaaS.com to Mailchimp.
Every Mailchimp e-commerce product must have at least one variant. When the iPaaS.com Product is a simple product with no variants of its own, the integration creates a single default variant automatically and copies the product-level title, identifier, price, inventory, image, and URL onto it. When the Product carries variants, those are written through the related Product Variant child collection instead.
ID Format
Manual Sync ID
On the iPaaS.com Manual Sync page, enter the iPaaS.com Product ID (for example, 197689) to send a single Product on demand. The same Product ID is used to run a single Product delete on demand.
External ID
After a successful transfer, iPaaS.com records the external-id link on a dedicated external-id record, so later changes to the same Product are routed to the same Mailchimp product on the same stores rather than creating a duplicate. For a product the stored link combines the product identifier (the SKU) with the store identifiers it was written to, in the form SKU followed by a pipe delimiter and the comma-separated store identifiers (for example, DEMO1000001 with the stores iPaaS.com,iPaaS.com2). The default mappings also write the SKU into the Mailchimp product Id field, which is how the product is matched on each store.
Each variant carries its own external-id link that combines the variant identifier, the parent product identifier, and the store identifiers, which is how a variant is tied back to its parent product and store. A Variant External Id Delimiter value must be configured in the subscription settings; without it the product transfer cannot complete, because the integration uses that delimiter to build each variant's external-id link.
Deleted Record Support
Deleting a Product through this integration is supported by a separate Delete collection (Delete Mailchimp Product FROM iPaaS.com, collection 288600). When an iPaaS.com Product is deleted, the integration removes the matching e-commerce product (and its variants) from each Mailchimp store the product was written to, keyed on the stored external-id link. A Product that was never added or updated through the integration has no external-id link and therefore cannot be deleted through this collection. The Delete collection has no field mappings, by design; see Mappings below.
Custom Field Support
iPaaS.com-side custom fields are not supported as a configurable feature in this integration. The Add/Update collection does read the store assignment from the Product's Store IDs custom field to determine which Mailchimp stores to write to; the custom field name on the Product must be Store IDs. This is a mapping input, not a configurable custom-field surface. The Product Variant child collection does not use custom fields.
Mapping Collection Status
Enabled. Trigger events: the integration sends a Product when the iPaaS.com Product created and Product updated outbound triggers fire (enabled under Outbound Data Flows), or on demand from the Manual Sync page. The Delete collection runs on the Product deleted outbound trigger or a Manual Sync delete. Variants transfer as part of the parent Product and have no independent trigger.
Duplicate or Conflicting Mappings
This single Add/Update collection handles both create and update. Routing depends on whether the product already exists on the targeted store: the integration looks the product up by identifier on each store and updates the existing product when one is found, otherwise it creates a new product. Adding and updating products is handled here; removing products is handled by the separate Delete collection. No collision-handling method is configured for these collections. Review which collections are enabled and their outbound triggers before turning them on, so that create, update, and delete behave as intended for your data.
Supported Child Collections
Add/Update Mailchimp Product Variant FROM iPaaS.com (collection 288604): Writes the Product's variants to Mailchimp under this product on each store. When the iPaaS.com Product carries variants, they are sent through this child collection rather than as the automatic default variant. The parent Product transfer supplies the store and product context; this child collection contributes each variant's own fields. To re-sync a single variant directly once its parent Product is already linked to Mailchimp, use the separate Standalone variant collection (documented in its own article).
Mailchimp System Caveats
A Mailchimp e-commerce product belongs to a specific store. The product is written once per store identifier supplied, so the same iPaaS.com Product becomes a separate product record on each targeted store, and a delete removes the product from each store identifier recorded in the external-id link.
Every Mailchimp e-commerce product must have at least one variant. For a simple iPaaS.com Product with no variants, the integration creates one default variant automatically from the product-level values; for a Product with variants, the variants are written through the child collection.
The product identifier (SKU) is limited to 40 characters, and the variant identifier is limited to 40 characters. A longer value is rejected.
If the SKU contains the characters /, ?, or #, a Special Character Replacement value must be configured in the subscription settings, or the product cannot be created or updated.
iPaaS.com System Caveats
The Mailchimp store identifiers are read from the Product's Store IDs custom field, which may hold one or more identifiers. A Product without a store identifier is not transferred, because Mailchimp e-commerce products belong to a store.
A Variant External Id Delimiter value must be configured in the subscription settings; without it the product transfer cannot complete.
The audience (list) identifier mapped to ListId is an audience-level reference and is optional for the product write itself.
The variant title is built from the parent Product name plus the variant's option values. A variant with no option values is titled with the parent Product name alone.
Setup Requirements
Automatic transfers run only when the subscriber enables the Product created and Product updated outbound triggers (and, for deletes, the Product deleted trigger) under Outbound Data Flows in the subscription configuration. Until those are enabled, Products transfer only through Manual Sync. The Variant External Id Delimiter and, when SKUs contain reserved characters, the Special Character Replacement value are configured in the Subscription Settings. The Mailchimp connection (API Url and API Key) is configured in the Subscription Settings — see the Mailchimp Connections and Settings article. Mailchimp does not send change webhooks to the integration, so no iPaaS.com-side webhook receiver is involved.
Integration Flow
Resolve the Mailchimp store identifiers from the Product's Store IDs custom field. If no store is supplied, the transfer does not proceed.
For each store identifier, resolve the product on the store by its identifier (the mapped SKU). If a product with that identifier already exists on the store, it is updated; otherwise a new product is created.
If the Product has no variants of its own, create one default variant from the product-level values (title, identifier, price, inventory, image, URL). If the Product carries variants, they are written by the related Product Variant child collection, each linked back to its parent product and store through the variant's external-id link.
Repeat for each additional store identifier so the product is present on every targeted store.
Record the external-id link so later changes route to the same Mailchimp product on the same stores.
Mappings
Product to Mailchimp
This collection does not have a mapping filter applied; every Product reached through an enabled outbound trigger or Manual Sync is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Field | Name | Title | Required. The product's title; Mailchimp requires a title on every e-commerce product, so a Product without a title cannot be created. Also copied to the auto-created default variant for a simple Product with no variants. |
Field | Sku | Id | Required. The Mailchimp product identifier, supplied from the Product SKU; how the product is matched on each store and part of the external-id link. Limited to 40 characters. If the SKU contains /, ?, or #, a Special Character Replacement value must be configured. |
Dynamic Formula | Store IDs custom field, returns the list of store identifiers | StoreId | Required. Resolves the Mailchimp store identifiers from the Product's Store IDs custom field; the product is created or updated on each store returned, and the transfer cannot proceed if no store is supplied. |
Field | DefaultPrice | DefaultVariantPrice | Recommended. Populates the price on the auto-created default variant so a simple Product with no variants carries a usable price. Has no effect on a Product that carries its own variants. |
Static | "c27a7d4008" | ListId | Optional for the product write. The Mailchimp audience (list) identifier associated with the product. Placeholder — replace during implementation with your own Audience ID (Mailchimp: Audience → Manage Audience → Settings → Audience name and campaign defaults). |
Field | InStockThreshold | DefaultVariantInventoryQuantity | Optional. Sets the inventory quantity on the auto-created default variant for a simple Product with no variants. |
Static | "variant_backorders" | DefaultVariantBackorders | Optional. Sets the backorders setting on the auto-created default variant. Placeholder — replace during implementation: this is an example token, not a working backorders value; replace it with the value your store expects, or remove the mapping. |
Static | "variant_visibility" | DefaultVariantVisibility | Optional. Sets the visibility setting on the auto-created default variant. Placeholder — replace during implementation: this is an example token, not a working visibility value; replace it with the value your store expects, or remove the mapping. |
Static | Url | Optional. Sets the product URL on the auto-created default variant. Placeholder — replace during implementation: this is an example link and does not point to your product page; repoint it to the Product's URL, or remove the mapping. | |
Static | ImageUrl | Optional. Sets the image URL on the auto-created default variant. Placeholder — replace during implementation: this is an example image link and does not point to your product image; repoint it to the Product's image URL, or remove the mapping. |
The DefaultVariant mappings (DefaultVariantPrice, DefaultVariantInventoryQuantity, DefaultVariantBackorders, DefaultVariantVisibility) and the product-level Url and ImageUrl exist because Mailchimp requires every product to have at least one variant. For a simple iPaaS.com Product with no variants of its own, the integration creates a single default variant and populates it from these values. They have no effect on a Product that carries its own variants — those variants are written through the child collection below.
Product Variant to Mailchimp
This child collection does not have a mapping filter applied. Variants transfer as part of the parent Product: when a Product is sent to Mailchimp, its variants are written through this collection under the parent product on each store. The parent product identifier and store identifier(s) are supplied by the parent Product transfer rather than by mappings on this collection.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Field | Sku | Id | Required. The Mailchimp variant identifier, supplied from the variant SKU; how Mailchimp identifies the variant. Limited to 40 characters; a longer value is rejected. |
Dynamic Formula | Parent product name, plus the variant's option values when present | Title | Recommended so the variant is identifiable in the Mailchimp catalog. Composes the parent product name with the variant's option values; a variant with no option values is titled with the parent product name alone. |
Field | Sku | Sku | Optional. Records the SKU on the Mailchimp variant. |
Field | DefaultPrice | Price | Optional. Sets the variant price from the variant default price; when no default price is available, no value is sent. |
Product Delete
The Delete collection (288600) has no field mappings, by design. A delete does not compose a product record — it identifies the product to remove using the external-id link iPaaS.com recorded when the product was added or updated, which combines the SKU with the store identifiers (see ID Format). The integration uses that link to remove the product and its variants from each of those stores, so there are no required, recommended, or optional fields to map.
Error Handling
Errors raised by this flow are catalogued in the Mailchimp Errors article, with the message text, cause, and resolution. The most common for this flow are a missing store identifier (the Store IDs custom field is empty), a SKU that exceeds 40 characters or contains reserved characters with no Special Character Replacement configured, and a missing Variant External Id Delimiter that prevents the variant links from being built. All errors appear in the iPaaS.com Dashboard / Integration Monitoring / Error Logs, and a failed transfer can be retried via Manual Sync.
Testing and Validation
Transfer a new simple Product (no variants) with at least one store identifier and confirm an e-commerce product is created on each store, that a default variant is created from the product-level values, and that the external-id link is stored.
Transfer an update to the same Product and confirm the existing product is updated on each store rather than duplicated.
Transfer a Product that carries variants and confirm each variant is written under the parent product on each store with its title composed from the parent name and option values.
Transfer a Product with no store identifier and confirm it is not transferred and the missing-store error appears in the Error Logs.
Delete a previously transferred Product and confirm it is removed from each store recorded in the external-id link; confirm a Product that was never transferred cannot be deleted through this collection.
Additional Notes
Before enabling these collections in production, replace the placeholder values noted in the mapping table (audience identifier, the example backorders and visibility tokens, and the example product URL and image URL). See the Mailchimp Known Limitations article for the full placeholder list.
The Variant External Id Delimiter must be configured in the Subscription Settings, and a Special Character Replacement value is required when SKUs contain /, ?, or #.
This documentation reflects the integration's behavior at the time it was written.