This article catalogs the error messages the iPaaS.com Mailchimp integration can produce while sending records to Mailchimp. Each entry gives the message text, what causes it, how to resolve it, the flow it belongs to, and whether you can edit the underlying rule yourself.

When any of these errors occurs, the full message is recorded in your iPaaS.com Dashboard under Integration Monitoring, in the Error Logs for the affected transfer. Start there to see which record and which flow raised the error.

Message: Could not create product because product SKU contains special characters and no Special Character Replacement is specified. {Id} — (and the matching "Could not update product…" on updates)

Cause: The product SKU contains a reserved character (the forward slash, question mark, or hash characters) and no Special Character Replacement value is set in the Subscription Settings. Mailchimp cannot accept those characters in a product id, so the transfer stops.

Resolution: Either remove the reserved characters from the source SKU, or set a Special Character Replacement value in the Subscription Settings so those characters are swapped for a safe one before the product is sent.

Flow: Product From iPaaS.

Editable: Not subscriber-editable.

Message: Could not create product because no store is provided for product: {Id} — (and the matching "Could not update product…" on updates)

Cause: The product payload has no store associated with it. Without a store, the integration does not know which Mailchimp store the product belongs to.

Resolution: Make sure each product is mapped to at least one valid Mailchimp store before it is sent. Confirm the source system supplies a store value and that it is mapped through to the product.

Flow: Product From iPaaS.

Editable: Not subscriber-editable.

Message: Could not create product because the Variant External Id Delimiter setting is not specified in the subscription settings — (and the matching "Could not update product…" on updates)

Cause: The Variant External Id Delimiter setting is empty. The integration needs this delimiter to build the combined product-and-variant external ids, so product processing cannot continue without it.

Resolution: Set a Variant External Id Delimiter in the Subscription Settings (for example, the vertical bar character) before transferring products or variants.

Flow: Product From iPaaS.

Editable: Not subscriber-editable.

Message: Failed to create product in Mailchimp: {detail} — (and the matching "Failed to update product…" on updates)

Cause: Mailchimp rejected the product create or update request. The appended detail is the reason Mailchimp returned, which is usually a missing required field or an invalid value.

Resolution: Read the appended detail in the Error Log, then make sure all required product fields are populated and the required Subscription Settings are configured. Correct the data or mapping and re-run the transfer.

Flow: Product From iPaaS.

Editable: Not subscriber-editable.

Message: Could not create product variant because variant SKU contains special characters and no Special Character Replacement is specified. {Id} — (and the matching "Could not update product variant…" on updates)

Cause: The variant SKU contains a reserved character (the forward slash, question mark, or hash characters) and no Special Character Replacement value is set in the Subscription Settings.

Resolution: Remove the reserved characters from the source SKU, or set a Special Character Replacement value in the Subscription Settings so those characters are swapped before the variant is sent.

Flow: Product Variant From iPaaS.

Editable: Not subscriber-editable.

Message: Could not create product variant because no store is provided for product variant: {Id} — (and the matching "Could not update product variant…" on updates)

Cause: The variant payload has no store associated with it, so the integration cannot determine which Mailchimp store it belongs to.

Resolution: Make sure each variant is mapped to at least one valid Mailchimp store before it is sent.

Flow: Product Variant From iPaaS.

Editable: Not subscriber-editable.

Message: Could not create product variant because the Variant External Id Delimiter setting is not specified in the subscription settings — (and the matching "Could not update product variant…" on updates)

Cause: The Variant External Id Delimiter setting is empty, so the integration cannot build or parse the combined product-and-variant external id.

Resolution: Set a Variant External Id Delimiter in the Subscription Settings (for example, the vertical bar character) before transferring variants.

Flow: Product Variant From iPaaS.

Editable: Not subscriber-editable.

Message: Failed to create product variant in Mailchimp: {detail} — (and the matching "Failed to update product variant…" on updates)

Cause: Mailchimp rejected the variant create or update request. The appended detail is the reason Mailchimp returned.

Resolution: Read the appended detail in the Error Log, populate all required variant fields, confirm the parent product exists and is linked, then re-run the transfer.

Flow: Product Variant From iPaaS.

Editable: Not subscriber-editable.

Message: {ParentId}: the parent product for this variant is not yet linked to Mailchimp.

Cause: The variant's parent product has not yet been created or linked in Mailchimp, so the integration cannot attach the variant to a parent. This message comes from the filter on the standalone Product Variant Add/Update flow.

Resolution: Make sure the parent product has been transferred to and linked in Mailchimp before sending its variants. Confirm the parent product has a valid Mailchimp external id.

Flow: Product Variant Add/Update From iPaaS Standalone.

Editable: Subscriber-editable — this message is produced by the collection filter on the standalone variant flow, which you can open and adjust in the iPaaS.com mapping interface.

Message: Could not delete the product. {detail}

Cause: An error occurred while deleting a product in Mailchimp. The appended detail describes the underlying failure.

Resolution: Confirm the product still exists in Mailchimp, that the product id being sent is valid, and that Mailchimp is reachable at the time of deletion. Review the appended detail for the specific failure.

Flow: Product Delete From iPaaS.

Editable: Not subscriber-editable.

Message: Could not delete product variant because the Variant External Id Delimiter setting is not specified in the subscription settings

Cause: The Variant External Id Delimiter setting is empty. The delete operation needs the delimiter to split the variant external id into its product id and variant id parts, so the delete cannot proceed.

Resolution: Set a Variant External Id Delimiter in the Subscription Settings (for example, the vertical bar character) before deleting variants.

Flow: Product Variant Delete From iPaaS Standalone.

Editable: Not subscriber-editable.

Message: Could not delete the product variant. {detail}

Cause: An error occurred while deleting a variant in Mailchimp. The appended detail describes the underlying failure.

Resolution: Confirm the variant still exists in Mailchimp, that the variant id being sent is valid, and that Mailchimp is reachable at the time of deletion. Review the appended detail for the specific failure.

Flow: Product Variant Delete From iPaaS Standalone.

Editable: Not subscriber-editable.

Message: No value is specified for ListId. This is a required field. — (on updates, the variant: "No value is specified for ListId. This is a required field on updates.")

Cause: No List Id (Mailchimp Audience id) was supplied when creating or updating a member. The List Id identifies which Audience the contact belongs to and is mandatory.

Resolution: Provide and map a valid Mailchimp List Id (Audience id) in the Customer flow.

Flow: Customer From iPaaS.

Editable: Not subscriber-editable.

Message: Mailchimp indicated that there was a duplicate email for {emailAddress}, but a search for that email returned no exact matches

Cause: Mailchimp reported the email address as already existing in the Audience, but a follow-up search for that exact email returned no match. The integration cannot reconcile the contact.

Resolution: Confirm the email actually exists in the correct Audience and that the List Id is correct. Check for formatting differences (such as case or trailing spaces) between the source email and the one in Mailchimp. If the contact exists, update it rather than re-creating it.

Flow: Customer From iPaaS.

Editable: Not subscriber-editable.

Message: To look up a customer, both the customer email and the store id must be provided.

Cause: A customer lookup was attempted without both the customer email and the store id; both are required to locate an e-commerce customer.

Resolution: Make sure both the customer email and the store id are provided and mapped before the lookup runs.

Flow: Customer From iPaaS (e-commerce customer lookup).

Editable: Not subscriber-editable.

Message: To look up a customer, both the customer id and the store id must be provided.

Cause: A customer lookup was attempted without both the customer id and the store id; both are required to locate an e-commerce customer.

Resolution: Make sure both the customer id and the store id are provided and mapped before the lookup runs.

Flow: Customer From iPaaS (e-commerce customer lookup).

Editable: Not subscriber-editable.

Message: The specified merge field does not exist, so we attempted to create it. However the field name is invalid as a merge field tag. Only numbers or capital letters are supported and the length must be less than 10.

Cause: The integration tried to create a Mailchimp merge field whose tag does not meet Mailchimp's rules. Merge field tags may contain only uppercase letters (A–Z) and digits (0–9) and must be fewer than 10 characters.

Resolution: Adjust the merge field name so it uses only uppercase letters or numbers and is fewer than 10 characters.

Flow: Customer From iPaaS.

Editable: Not subscriber-editable.

Message: The order ID exceeds the 49-character limit allowed by Mailchimp.

Cause: The Order id is longer than Mailchimp's 49-character limit, so the order cannot be sent.

Resolution: Make sure every Order id is 49 characters or fewer before it is transferred.

Flow: Order From iPaaS.

Editable: Not subscriber-editable.

Message: The customer is not linked to Mailchimp. Provide a customer that is already linked to Mailchimp.

Cause: The order has no linked Mailchimp customer (the customer id is missing). Mailchimp requires every order to reference a valid customer in the store.

Resolution: Make sure the order's customer has already been created in Mailchimp and is correctly linked, and that the customer id is mapped from the source system, before sending the order.

Flow: Order From iPaaS.

Editable: Not subscriber-editable.

Message: The store ID is not provided in the order's custom fields. — (a related lookup raises: "Store Id is not provided in Custom fields of the order. The Custom field name must be one of the following: 'store_id', 'Store Id', 'Store ID', or 'Store_Id'.")

Cause: The order does not carry a store id in its custom fields, so the integration cannot determine which Mailchimp store the order belongs to. The store id custom field must be named one of: store_id, Store Id, Store ID, or Store_Id.

Resolution: Add a valid store id to the order's custom fields using one of the accepted field names, then re-run the transfer.

Flow: Order From iPaaS.

Editable: Not subscriber-editable.

Message: Store Id is not provided in Custom fields of the Customer. The Custom field name must be one of the following: 'store_id', 'Store Id', 'Store ID', or 'Store_Id'.

Cause: While preparing the order's customer, no store id was found in the customer's custom fields. The store id custom field must be named one of: store_id, Store Id, Store ID, or Store_Id.

Resolution: Add a valid store id to the customer's custom fields using one of the accepted field names.

Flow: Order From iPaaS (customer prerequisite).

Editable: Not subscriber-editable.

Message: The customer does not exist in Mailchimp or iPaaS.com.

Cause: The Order's customer id formula could not resolve a Mailchimp customer id from either the supplied customer id or the customer's email address. This message comes from the CustomerId Dynamic Formula on the Order Add/Update flow.

Resolution: Confirm the order's customer exists in Mailchimp (or can be created), and that the customer id or email is mapped correctly so the lookup can resolve it.

Flow: Order Add/Update From iPaaS.

Editable: Subscriber-editable — this message is produced by a Dynamic Formula on the Order flow, which you can open and adjust in the iPaaS.com mapping interface.

Message: The store ID is missing for this order line. — and — The SKU is missing for this order line.

Cause: An order line's product id or variant id formula could not run because the store id (read from the parent order's custom fields) or the SKU was empty. The store id and SKU are both needed to look up the matching Mailchimp product or variant. These messages come from the ProductId and ProductVariantId Dynamic Formulas on the Order Line flow.

Resolution: Make sure the parent order carries a valid store id in its custom fields and that each order line has a SKU, so the product and variant lookups can resolve.

Flow: Order Line Add/Update From iPaaS (child of Order Add/Update).

Editable: Subscriber-editable — these messages are produced by Dynamic Formulas on the Order Line flow, which you can open and adjust in the iPaaS.com mapping interface.

Message: Deleting members is not currently supported

Cause: The integration does not support deleting Audience members. A delete request for a member is rejected with this message.

Resolution: This is expected behavior. Manage member removal directly in Mailchimp (for example, by archiving or unsubscribing the contact) rather than through a delete from iPaaS.com.

Flow: Customer From iPaaS.

Editable: Not subscriber-editable.