Summary
This mapping collection sends an iPaaS.com Transaction to Mailchimp as an e-commerce order on a Mailchimp store. Each order carries its totals, currency, processing date, and the customer it belongs to, and is written to the store identified by the order's store identifier. The order's line items transfer with it through the child Order Line collection, so a single transfer writes the order and its lines together. It is a combined Add/Update flow: an order 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.
When the order references a customer, products, or product variants that are not yet in Mailchimp, the integration creates them first as part of the same transfer, so subscribers do not need to pre-sync those records.
ID Format
Manual Sync ID
On the iPaaS.com Manual Sync page, enter the iPaaS.com Transaction ID (for example, 197689) to send a single order on demand. Its line items transfer with it; there is no separate Manual Sync entry point for an individual line.
External ID
After a successful transfer, iPaaS.com records the Mailchimp order identifier as the external-id link on a dedicated external-id record, so later changes to the same Transaction are routed to the same Mailchimp order rather than creating a duplicate. An example Mailchimp order identifier is 1008766. This external-id record is the primary match for subsequent updates. The default mappings also write the iPaaS.com Transaction Number into the Mailchimp order Id field; this provides the order's identifier in Mailchimp and serves as a fallback match — when no external-id record yet exists, the integration looks for an existing Mailchimp order on the store whose identifier matches the Transaction Number and links to it rather than creating a duplicate. The Mailchimp order identifier is limited to 49 characters; a longer value causes the transfer to fail. Remapping the Id field to a different source is supported but disables that fallback auto-link for orders created before the external-id record existed.
Deleted Record Support
Removing an order from Mailchimp through this integration is not supported; the collection adds and updates orders only. Manage order removal directly in Mailchimp. The same applies to the order's line items — they are managed only through their parent order and cannot be removed through this integration.
Custom Field Support
This collection does not configure custom fields in Mailchimp. The order's store identifier is read from an iPaaS.com Transaction custom field as a routine mapping source rather than as a configurable custom-field implementation. The custom field name on the Transaction must be one of store_id, Store Id, Store ID, or Store_Id. iPaaS.com-side custom fields are otherwise not supported in this integration.
Mapping Collection Status
Enabled. Trigger events: the integration sends an order when the iPaaS.com Transaction created and Transaction updated outbound triggers fire (enabled under Outbound Data Flows), or on demand from the Manual Sync page.
Duplicate or Conflicting Mappings
This single Add/Update collection handles both create and update. Routing depends on whether the order is already linked to Mailchimp: the integration updates the existing Mailchimp order when an external-id link is found, otherwise it creates a new order. There are no other collections that write Mailchimp orders or order lines. No collision-handling method is configured for this collection.
Supported Child Collections
Order Line: transfers the order's line items as part of the same order. The line items are read from the Transaction's lines and written with the order in a single operation; there is no separate Manual Sync entry point for an individual line.
Mailchimp System Caveats
A Mailchimp e-commerce order is created on a specific store, so a store identifier is mandatory. If the value mapped to StoreId does not exist as an e-commerce store and a valid ListId is mapped, the store is created automatically; remove the ListId mapping to prevent automatic store creation.
Mailchimp requires every e-commerce order to reference an existing customer. The order cannot be written until its customer is present in Mailchimp.
The Mailchimp order identifier is limited to 49 characters. A longer value causes the transfer to fail.
Each order line references a Mailchimp product and product variant on the order's store. The integration resolves these from the line's SKU; a line whose SKU cannot be resolved blocks the order transfer.
iPaaS.com System Caveats
The order's store identifier is read from the Transaction's store custom field. The custom field name must be one of store_id, Store Id, Store ID, or Store_Id. Without it, the order is not written.
By default, when the order's customer is created in Mailchimp, the customer's own store-id custom field is used. To always use the store identifier provided on the order instead, set the subscription setting Use Store Id From Transaction to true and set Customer Store Id Custom Field Name to the iPaaS.com customer custom field that should be checked first.
Setup Requirements
Automatic transfers run only when the subscriber enables the Transaction created and Transaction updated outbound triggers under Outbound Data Flows in the subscription configuration. Until those are enabled, orders 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.
Integration Flow
Resolve the order's store identifier from the Transaction's store custom field. If no store identifier is present, the transfer stops with an error before any order is written.
Ensure the order's prerequisites exist in Mailchimp. When the order's customer, products, or product variants are not yet linked to Mailchimp, the integration creates them first as part of the same transfer — the customer first, then each line item's product and product variant on the order's store. If a prerequisite cannot be created, the order transfer fails.
Resolve the Mailchimp customer for the order, first by the iPaaS.com customer identifier and then by email address. If neither resolves to a Mailchimp customer, the transfer stops with an error.
Create or update the e-commerce order on the resolved store, including its line items, in a single operation.
Record the Mailchimp order identifier as the external-id link so later changes route to the same order.
Mappings
Order to Mailchimp
This collection does not have a mapping filter applied; every iPaaS.com Transaction reached through an enabled outbound trigger or Manual Sync is processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Field | TransactionNumber | Id | Required. The order's identifier in Mailchimp, supplied from the iPaaS.com Transaction Number. Limited to 49 characters; a longer value causes the transfer to fail. After the first successful transfer the external-id link becomes the primary match, and this value serves as the fallback match for orders created before that link existed. |
Field | Total | OrderTotal | Required. The order total. Mailchimp requires a total to create an e-commerce order. |
Field | Custom field: currency code | CurrencyCode | Required. The three-letter ISO 4217 currency code for the order (for example, USD), read from the Transaction's currency-code custom field. Mailchimp requires a currency to create an e-commerce order. |
Field | Custom field: store_id | StoreId | Required. The Mailchimp store identifier the order belongs to, read from the Transaction's store custom field. Without it, the order cannot be created. The custom field name must be one of store_id, Store Id, Store ID, or Store_Id. |
Dynamic Formula | Mailchimp customer resolved by the iPaaS.com customer identifier, then by email address | CustomerId | Required. The Mailchimp customer the order belongs to. The formula first resolves the customer by the iPaaS.com customer identifier on the order's store, then by email address; if neither resolves, the transfer stops with the error "The customer does not exist in Mailchimp or iPaaS.com." The customer is created automatically as a prerequisite when not yet linked, so this normally succeeds. |
Dynamic Formula | Transaction created date and time, converted to UTC ISO 8601 | ProcessedAtForeign | Recommended. The date and time the order was processed, in UTC, so Mailchimp reporting and automations reflect the correct order timing. |
Field | DiscountAmount | DiscountTotal | Optional. The total discount applied to the order. Improves the completeness of the order's financial breakdown. |
Field | TaxAmount | TaxTotal | Optional. The order's tax total. Improves the completeness of the order's financial breakdown. |
Field | ShippingAmount | ShippingTotal | Optional. The order's shipping total. Improves the completeness of the order's financial breakdown. |
Static | "c27a7d4008" | ListId | Optional. The Mailchimp audience (list) identifier, used only to create the e-commerce store automatically when the value mapped to StoreId does not yet exist as a store; it is not written onto the order itself. Remove this mapping to prevent automatic store creation. Placeholder — replace during implementation with your own Audience ID (Mailchimp: Audience → Manage Audience → Settings → Audience name and campaign defaults). |
Order Line to Mailchimp
This child collection does not have a mapping filter applied; every line item of a processed Transaction is sent with its parent order. The line items are read from the Transaction's lines and written together with the order in a single operation; there is no independent transfer path for a single line.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Mailchimp) | Description |
Dynamic Formula | Mailchimp product resolved from the line's SKU and the parent order's store | ProductId | Required. The Mailchimp product the line references. If the parent product is not yet on the store, the integration creates it as a prerequisite during the order transfer. The transfer stops with an error if the store identifier or the SKU is missing: "The store ID is missing for this order line." / "The SKU is missing for this order line." |
Dynamic Formula | Mailchimp product variant resolved from the line's SKU and the parent order's store | ProductVariantId | Required. The Mailchimp product variant the line references. If the variant is not yet on the store, the integration creates it as a prerequisite during the order transfer. The transfer stops with an error if the store identifier or the SKU is missing: "The store ID is missing for this order line." / "The SKU is missing for this order line." |
Field | Qty | Quantity | Required. The quantity of the line item. Mailchimp requires a quantity on each order line. |
Field | ExtendedPrice | Price | Required. The price of the line item, from the Transaction line extended price. Mailchimp requires a price on each order line. |
Dynamic Formula | The Transaction line identifier | Id | Required. The line item's identifier in Mailchimp, supplied from the iPaaS.com Transaction line identifier. |
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 on the order, a customer that resolves to neither Mailchimp nor iPaaS.com ("The customer does not exist in Mailchimp or iPaaS.com."), an order line missing its store identifier ("The store ID is missing for this order line.") or SKU ("The SKU is missing for this order line."), and an order identifier longer than 49 characters. All errors appear in the iPaaS.com Dashboard / Integration Monitoring / Error Logs.
Testing and Validation
Transfer a new order and confirm an e-commerce order is created on the configured store with its line items, and the external-id link is stored.
Transfer an update to the same order and confirm the existing Mailchimp order is updated in place rather than duplicated.
Transfer an order whose customer, products, or variants are not yet in Mailchimp and confirm the integration creates those prerequisites first, then writes the order.
Transfer an order with no store identifier on the Transaction and confirm the transfer stops with the missing-store-identifier error in the Error Logs.
Transfer an order whose customer resolves to neither Mailchimp nor iPaaS.com and confirm the "The customer does not exist in Mailchimp or iPaaS.com." error appears in the Error Logs.
Transfer an order line missing its SKU and confirm the "The SKU is missing for this order line." error appears in the Error Logs.
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.