Overview
This article catalogs the errors the iPaaS.com Mailchimp integration can record in your error logs while sending records to Mailchimp. Each entry lists a stable error code, the message text, what causes it, and how to resolve it. When an error 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 flow raised it. Every code is unique and permanent, so you can search this page (Ctrl+F) for the code shown in your log to jump straight to its cause and resolution.
Some resolutions refer to your Managed Integration Service Provider (MiSP) — the team that manages your iPaaS.com integration on your behalf, including your mappings, subscription settings and credentials, and data reconciliation. If a resolution calls for a mapping or configuration change you do not manage yourself, your MiSP is the right first point of contact.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Product From iPaaS
Product Variant From iPaaS
Product Variant Delete From iPaaS
Customer From iPaaS
Order From iPaaS
Order Line From iPaaS
Error Collection
Product From iPaaS
Special characters in product SKU
MCHP-VALD-1001 - Could not create or update product because product SKU contains special characters and no Special Character Replacement is specified. {Id}
Description: The product SKU contains a character Mailchimp cannot accept in a product id (such as a forward slash, question mark, or hash) and no Special Character Replacement value is set in the Subscription Settings, so the product cannot be sent.
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.
No store provided for product
MCHP-VALD-1002 - Could not create or update product because no store is provided for product: {Id}
Description: The product payload has no store associated with it, so the integration cannot determine 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.
Variant External Id Delimiter not configured
MCHP-VALD-1003 - Could not create or update product because the Variant External Id Delimiter setting is not specified in the subscription settings.
Description: 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 value in the Subscription Settings (for example, the vertical bar character) before transferring products or variants.
Product Variant From iPaaS
Special characters in variant SKU
MCHP-VALD-1004 - Could not create or update product variant because variant SKU contains special characters and no Special Character Replacement is specified. {Id}
Description: The variant SKU contains a character Mailchimp cannot accept in an id (such as a forward slash, question mark, or hash) 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.
No store provided for variant
MCHP-VALD-1005 - Could not create or update product variant because no store is provided for product variant: {Id}
Description: 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.
Variant External Id Delimiter not configured
MCHP-VALD-1006 - Could not create or update product variant because the Variant External Id Delimiter setting is not specified in the subscription settings.
Description: 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 value in the Subscription Settings (for example, the vertical bar character) before transferring variants.
Parent product not linked
MCHP-NFND-1002 - {ParentId}: the parent product for this variant is not yet linked to Mailchimp.
Description: 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 check comes from the filter on the standalone Product Variant Add/Update flow.
Resolution: Transfer and link the parent product to Mailchimp before sending its variants, and confirm the parent product has a valid Mailchimp external id. This filter is part of your mappings; if it needs adjusting, your MiSP can update it in the iPaaS.com mapping interface.
Unable to create product prerequisite
MCHP-BIZL-1007 - Unable to create the parent product ({ParentId}). This will prevent the transfer of the product variant.
Description: The integration attempted to create the parent product as a prerequisite for the variant, and that product creation failed, so the variant cannot be transferred.
Resolution: Review the parent product's own error in the same transfer to see why it failed, correct that product, then re-run the variant transfer.
Product Variant Delete From iPaaS
Variant External Id Delimiter not configured (delete)
MCHP-VALD-1007 - Could not delete product variant because the Variant External Id Delimiter setting is not specified in the subscription settings.
Description: 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 value in the Subscription Settings (for example, the vertical bar character) before deleting variants.
Customer From iPaaS
List Id is required
MCHP-VALD-1008 - No value is specified for ListId. This is a required field.
Description: 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.
Customer lookup requires email and store id
MCHP-VALD-1009 - To look up a customer, both the customer email and the store id must be provided.
Description: An e-commerce customer lookup was attempted without both the customer email and the store id; both are required to locate the customer.
Resolution: Make sure both the customer email and the store id are provided and mapped before the lookup runs.
Invalid merge field name
MCHP-VALD-1010 - The specified merge field does not exist, so we attempted to create it. However the field name '{name}' is invalid as a merge field tag. Only numbers or capital letters are supported and the length must be less than 10.
Description: 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.
Invalid birthday value (MM/DD)
MCHP-VALD-1014 - The birthday value provided is not a valid month/day (MM/DD) date: {input}
Description: A birthday value mapped through the month/day formatter could not be read as a valid date, so it cannot be formatted for Mailchimp.
Resolution: Make sure the source birthday value is a valid date before it is mapped. Correct the source data, then re-run the transfer.
Invalid birthday value (DD/MM)
MCHP-VALD-1015 - The birthday value provided is not a valid day/month (DD/MM) date: {input}
Description: A birthday value mapped through the day/month formatter could not be read as a valid date, so it cannot be formatted for Mailchimp.
Resolution: Make sure the source birthday value is a valid date before it is mapped. Correct the source data, then re-run the transfer.
Duplicate email reported but not found
MCHP-BIZL-1001 - Mailchimp indicated that there was a duplicate email for {emailAddress}, but a search for that email returned no exact matches.
Description: Mailchimp reported the email address as already existing in the Audience, but a follow-up search for that exact email returned no match, so the integration could not reconcile the contact.
Resolution: Confirm the email exists in the correct Audience and that the List Id is correct, and 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. If the record still cannot be reconciled, your MiSP can review the Audience data.
Members cannot be deleted
MCHP-BIZL-1002 - Deleting members is not currently supported.
Description: The integration does not support deleting Audience members, so a delete request for a member is rejected.
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.
Order From iPaaS
Order id exceeds 49 characters
MCHP-VALD-1011 - The order ID exceeds the 49-character limit allowed by Mailchimp.
Description: 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.
Store id missing from order custom fields
MCHP-VALD-1012 - The store ID is not provided in the order's custom fields.
Description: The order does not carry a store id in its custom fields, so the integration cannot determine which Mailchimp store the order belongs to.
Resolution: Add a valid store id to the order's custom fields, then re-run the transfer.
Store id missing from order custom fields (customer prerequisite)
MCHP-VALD-1013 - Store Id is not provided in Custom fields of order {TransactionNumber}. The Custom field name must be one of the following: 'store_id', 'Store Id', 'Store ID', or 'Store_Id'.
Description: While preparing the order's customer, no store id was found in the order'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 order's custom fields using one of the accepted field names, then re-run the transfer.
Customer not linked to Mailchimp
MCHP-NFND-1001 - The customer is not linked to Mailchimp. Provide a customer that is already linked to Mailchimp.
Description: The order has no linked Mailchimp customer. Mailchimp requires every order to reference a customer that already exists 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.
Customer does not exist
MCHP-NFND-1003 - The customer does not exist in Mailchimp or iPaaS.com.
Description: The order's customer id could not be resolved to a Mailchimp customer from either the supplied customer id or the customer's email address. This check comes from the CustomerId 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. This formula is part of your mappings; if it needs adjusting, your MiSP can update it in the iPaaS.com mapping interface.
Unable to link existing order
MCHP-BIZL-1003 - Unable to dynamically link to existing Mailchimp Order Id. This may result in duplicate order records.
Description: The integration could not dynamically link the order to an existing Mailchimp order, which may result in a duplicate order being created.
Resolution: Confirm the order's identifiers are mapped consistently so the existing Mailchimp order can be matched. If duplicate orders appear, your MiSP can review the order linkage in your mappings.
Unable to create product prerequisite
MCHP-BIZL-1005 - Unable to create product for SKU {Sku}. This will prevent the transfer of the order.
Description: The integration attempted to create a product required by the order and that product creation failed, so the order cannot be transferred.
Resolution: Review the product's own error in the same transfer to see why it failed, correct that product, then re-run the order transfer.
Unable to create customer prerequisite
MCHP-BIZL-1006 - Unable to create customer. This will prevent the transfer of the order.
Description: The integration attempted to create the customer required by the order and that customer creation failed, so the order cannot be transferred.
Resolution: Review the customer's own error in the same transfer to see why it failed, correct the customer data, then re-run the order transfer.
Order Line From iPaaS
Store id missing for order line
MCHP-VALD-1016 - The store ID is missing for this order line.
Description: An order line's product or variant lookup could not run because the store id, read from the parent order's custom fields, was empty. The store id is needed to look up the matching Mailchimp product or variant.
Resolution: Make sure the parent order carries a valid store id in its custom fields so the order-line product and variant lookups can resolve. This check comes from a formula in your mappings; if it needs adjusting, your MiSP can update it.
SKU missing for order line
MCHP-VALD-1017 - The SKU is missing for this order line.
Description: An order line's product or variant lookup could not run because the line's SKU was empty. The SKU is needed to look up the matching Mailchimp product or variant.
Resolution: Make sure each order line has a SKU so the product and variant lookups can resolve. This check comes from a formula in your mappings; if it needs adjusting, your MiSP can update it.
Unable to link existing order line
MCHP-BIZL-1004 - Unable to dynamically link to existing Mailchimp Order line Id. This may result in duplicate order line records.
Description: The integration could not dynamically link the order line to an existing Mailchimp order line, which may result in a duplicate order line being created.
Resolution: Confirm the order line's identifiers are mapped consistently so the existing Mailchimp order line can be matched. If duplicate order lines appear, your MiSP can review the order-line linkage in your mappings.
Unable to create product variant prerequisite
MCHP-BIZL-1008 - Unable to create product variant for order line SKU {Sku}. This will prevent the transfer of the order.
Description: The integration attempted to create a product variant required by an order line and that variant creation failed, so the order cannot be transferred.
Resolution: Review the variant's own error in the same transfer to see why it failed, correct that variant, then re-run the order transfer.
All Flows
Mailchimp API call failed
MCHP-EXTN-1001 - Error calling Mailchimp {action}: {details} (HTTP {code})
Description: Mailchimp rejected or failed an API request. The
{action}names the operation that failed,{details}is the reason Mailchimp returned (often a missing required field or an invalid value), and{code}is the HTTP status. This can occur on any flow that sends data to Mailchimp.Resolution: Read the details and HTTP status in the error log, then correct the underlying data or mapping — for example, populate a missing required field or fix an invalid value — and re-run the transfer. If the returned detail does not point to a data issue you can correct, your MiSP can help investigate the request.
Unable to create or resolve Mailchimp store
MCHP-EXTN-1002 - Unable to create or resolve the Mailchimp store '{id}', so the record cannot be transferred.
Description: The record references a store id that does not yet exist in your Mailchimp e-commerce account, and the integration could not create or resolve that store, so the customer, order, or product cannot be sent to it.
Resolution: Confirm the store id on the record is correct and that the store exists (or can be created) in your Mailchimp e-commerce account. If the store id is mapped from a source custom field, verify that field carries the intended Mailchimp store value. If the store should already exist in Mailchimp, your MiSP can confirm the store setup.