Summary
This mapping collection sends a single iPaaS.com Product Variant to Mailchimp on its own, independently of a full Product transfer. Each variant is written as a Mailchimp e-commerce product variant under its parent product on the matching Mailchimp store, carrying the variant's identifier, SKU, title, and price so the variant catalog in Mailchimp stays aligned with the iPaaS.com source. It is a combined Add/Update flow: a variant that is not yet linked to Mailchimp is created, and one that is already linked is updated. All data moves in one direction, from iPaaS.com to Mailchimp.
This is the Standalone variant collection. It re-syncs one variant directly once its parent Product is already linked to Mailchimp, which is useful when only a variant has changed and the whole parent Product does not need to be resent. It differs from the child Product Variant collection, which transfers variants as part of a full parent Product transfer; see Duplicate or Conflicting Mappings below.
ID Format
Manual Sync ID
On the iPaaS.com Manual Sync page, enter the iPaaS.com Product Variant ID to send a single variant on demand.
External ID
After a successful transfer, iPaaS.com records a composite identifier as the external-id link on a dedicated external-id record, so later changes to the same variant are routed to the same Mailchimp variant rather than creating a duplicate. The composite combines the Mailchimp variant identifier, the parent product identifier, and the store identifier(s) the variant was written to, in the form {variant id}|{product id}|{store ids} (for example, PV12345|P67890|StoreA-StoreB). The pipe-separated segments are assembled using the variant external-id delimiter configured in the subscription settings; if that delimiter is not set, the transfer fails.
Deleted Record Support
Removing a variant from Mailchimp through this Add/Update collection is not supported; this collection adds and updates variants only. Variant removal is handled by a separate Delete Product Variant Standalone collection, which deletes the variant from Mailchimp under its parent product on each store the variant was written to. That delete builds no record body and has no field mappings by design — it identifies the variant entirely from the stored external-id link saved during the original Add/Update transfer (see the note under Mappings below). A variant that was never linked to Mailchimp has no external-id link and cannot be deleted through that collection.
Custom Field Support
Custom fields are not supported for this mapping collection.
Mapping Collection Status
Enabled. Trigger events: the integration sends a Product Variant when the iPaaS.com Product Variant created and Product Variant updated outbound triggers fire (enabled under Outbound Data Flows), or on demand from the Manual Sync page.
Duplicate or Conflicting Mappings
Two collections write Product Variants to Mailchimp:
Product Variant Standalone (this collection) re-syncs a single variant directly once its parent Product is already linked to Mailchimp.
The child Product Variant collection transfers variants as child records during a parent Product transfer.
Both target the same Mailchimp variants. Review their filters and Add/Update settings before enabling so a variant is not unexpectedly written from two paths at once. Use the Standalone collection for variant-only re-syncs and the child collection for full Product transfers; treat the parent Product link as the source of truth for which store and product a variant belongs to. No collision-handling method is configured for this collection.
Supported Child Collections
None. This collection writes a single variant and has no dependent child collections.
Mailchimp System Caveats
The variant identifier is limited to 40 characters in Mailchimp. A longer value is rejected.
A variant in Mailchimp belongs to a parent product on a specific store. The variant cannot be written until that parent product exists and is linked to Mailchimp.
iPaaS.com System Caveats
The composite external id is assembled using the variant external-id delimiter configured in the subscription settings. If that delimiter is not set, the transfer fails.
The store identifier(s) and parent product identifier are read from the parent product's Mailchimp link, not from the variant record itself. The parent Product must already be linked to Mailchimp for these values to resolve.
Setup Requirements
Automatic transfers run only when the subscriber enables the Product Variant created and Product Variant updated outbound triggers under Outbound Data Flows in the subscription configuration. Until those are enabled, variants transfer only through Manual Sync. 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. The parent Product must already be linked to Mailchimp before a Standalone variant transfer can succeed.
Integration Flow
Confirm the variant's parent Product is already linked to Mailchimp. If it is not, the transfer is skipped (see the Mapping Filter under Mappings).
Resolve the parent product's Mailchimp link to obtain the parent product identifier and the store identifier(s) the variant belongs to.
For each resolved store, create or update the variant under that store's parent product. A variant that is not yet linked is created; a variant that is already linked is updated.
Record the composite external-id link so later changes route to the same Mailchimp variant.
Mappings
Product Variant Standalone to Mailchimp
Mapping Filter. This collection has a mapping filter applied. The transfer proceeds only when the variant's parent Product is already linked to Mailchimp. When the parent Product has not yet been linked, the variant is skipped and the transfer ends with an error indicating the parent product for this variant is not yet linked to Mailchimp. To resolve a skipped transfer, sync the parent Product to Mailchimp first, then re-sync the variant.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Field | Sku | Id | Required. The Mailchimp variant identifier, taken from the iPaaS.com Product Variant SKU. Mailchimp identifies the variant by this value and limits it to 40 characters; a longer SKU is rejected. Forms part of the composite external-id link. |
Dynamic Formula | Parent product's Mailchimp external id (segment before the final delimiter) | ProductId | Required. Identifies the Mailchimp parent product the variant is created under, resolved from the parent Product's Mailchimp link. The parent Product must already be linked to Mailchimp for this value to resolve. |
Dynamic Formula | Store identifier(s) from the parent product's Mailchimp external id (segment after the final delimiter) | StoreId | Required. The Mailchimp store(s) the variant belongs to, resolved from the parent Product's Mailchimp link. The variant is addressed under a specific store's product, so the transfer cannot complete without it. |
Dynamic Formula | Parent product name, with the variant's option values appended when present | Title | Recommended. The variant title shown in Mailchimp, so the variant is identifiable in the catalog. When the variant has no option values, the title is just the parent product name. |
Field | Sku | Sku | Optional. Records the variant SKU on the Mailchimp variant for catalog completeness. |
Field | DefaultPrice | Price | Optional. The variant price, taken from the iPaaS.com Product Variant default price. When no default price is available, no value is sent. |
Static | "c27a7d4008" | ListId | Optional. The Mailchimp audience (list) identifier associated with the store; not required for the variant write itself. Placeholder — replace during implementation with your own Audience ID (Mailchimp: Audience → Manage Audience → Settings → Audience name and campaign defaults). |
Product Variant delete (folded)
The Delete Product Variant Standalone collection has no field mappings by design. The delete is keyed entirely on the stored external-id link saved during the original Add/Update transfer (the composite described under ID Format); for each store encoded in that link, the variant is removed under that store's parent product. A variant that was never linked to Mailchimp cannot be deleted through this collection.
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 the parent product for this variant not being linked to Mailchimp (the variant is skipped until the parent Product is synced), a missing variant external-id delimiter in the subscription settings, and a SKU that exceeds the 40-character variant identifier limit. All errors appear in the iPaaS.com Dashboard / Integration Monitoring / Error Logs.
Testing and Validation
Sync a parent Product to Mailchimp, then transfer one of its variants through this collection and confirm the variant is created under the parent product on the correct store and the external-id link is stored.
Transfer an update to the same variant and confirm the existing Mailchimp variant is updated in place rather than duplicated.
Attempt a Standalone variant transfer before the parent Product is linked and confirm the transfer is skipped with the parent-not-linked message in the Error Logs.
Confirm the variant Title resolves to the parent product name plus the variant's option values, and that a variant with no option values transfers with just the product name.
Delete a previously synced variant and confirm it is removed from each store it was written to; confirm a variant that was never linked cannot be deleted.
Additional Notes
Before enabling this collection in production, replace the placeholder audience identifier noted in the mapping table. See the Mailchimp Known Limitations article for the full placeholder list.
This documentation reflects the integration's behavior at the time it was written.