This article lists the error messages the Adobe Commerce (Magento 2) integration can report, explains what each one means, and gives the steps to resolve it. Use it to interpret an error you see against a record and decide whether the fix is a change you can make yourself or something to raise with iPaaS.com Support.

When a record cannot be processed, the integration records the error against that record so you can find it from the Dashboard, in Integration Monitoring, and in the Error Logs. Each entry shows the message text exactly as it is reproduced below, so you can match what you see to the corresponding section in this article.

Some errors come from Dynamic Formula mappings, which you configure in the iPaaS.com mapping interface. When an error tells you to use a particular function or to complete a mapping, you can resolve it yourself by editing the mapping or the connection settings. Other errors come from the integration's own connection and processing logic; these are not editable from the mapping interface, and when the resolution below says to contact iPaaS.com Support the fix has to be made by the iPaaS.com team. Individual errors below are marked where this distinction matters.

Error message: Magento login must have one of the following: a saved login token, an oath key, or a username/password

Cause: The connection could not authenticate to your store because none of the supported credential sets is present. The integration needs a saved login token, an integration access token (the OAuth key), or an Adobe Commerce username and password.

Resolution: Open the integration's connection settings and provide one complete credential set, then re-run the record. This is a settings change you can make yourself.

Error message: No Magento API Url specified for system {system ID}. Please verify your settings

Cause: The Adobe Commerce store URL is missing from the connection settings, so the integration has no address to call.

Resolution: Enter your store's REST URL in the connection settings and re-run the record. This is a settings change you can make yourself.

Error message: Attribute Set is required for new products

Cause: A new product was sent to Adobe Commerce without an attribute set. Adobe Commerce requires every product to belong to an attribute set.

Resolution: Map an attribute set for the product and re-run the record. This is a mapping change you can make yourself.

Error message: Error creating SKU {SKU}: Attempt to create product with no attribute set id. This is not allowed.

Cause: Product creation was attempted for the named SKU but no attribute set id was resolved for it, so Adobe Commerce would reject the product.

Resolution: Make sure the product's attribute set is mapped and resolves to a valid attribute set in your store, then re-run the record. This is a mapping change you can make yourself.

Error message: Error: Product Sku field is not populated

Cause: The product record reached the integration without a SKU. Adobe Commerce identifies products by SKU, so the record cannot be created or updated without one.

Resolution: Map a value to the product SKU field and re-run the record. This is a mapping change you can make yourself.

Error message: Error: Price List was attempted without completing the required configuration. Preset (Price List Field Separator) and (Price List Record Delimiter) must be populated.

Cause: Tier or price-list pricing was sent for a product, but the two presets that tell the integration how to read the price-list values are blank.

Resolution: In the integration's connection settings, populate the Price List Field Separator and Price List Record Delimiter presets, then re-run the record. This is a settings change you can make yourself.

Error message: Unable to assign the custom attribute to the attribute set. Attribute set: {attribute set ID}, attribute code: {attribute code}

Cause: The integration tried to add the named custom attribute to the named attribute set in Adobe Commerce, and the store rejected the assignment.

Resolution: Confirm the attribute code exists and can be added to that attribute set in Adobe Commerce, then re-run the record. If the attribute and set look correct in your store, contact iPaaS.com Support.

Error message: Unable to assign the gridded attribute to the attribute set. Attribute set: {attribute set ID}, attribute code: {attribute code}

Cause: The integration tried to add the named grid (configurable) attribute to the named attribute set so that product variants could be created, and the store rejected the assignment.

Resolution: Confirm the attribute code exists and is valid for configurable products in that attribute set, then re-run the record. If it looks correct in your store, contact iPaaS.com Support.

Error message: Unable to find any groups for the specified attribute set: {attribute set ID}. Unable to fully complete attribute creation.

Cause: The integration needs an attribute group within the attribute set to complete attribute creation, but the named attribute set returned no groups.

Resolution: Confirm the attribute set exists in Adobe Commerce and has at least one attribute group, then re-run the record. If the attribute set is configured correctly, contact iPaaS.com Support.

Error message: Unable to retrieve the Attribute Set Attributes for the specified attribute set id: {attribute set ID}. Message: {details}

Cause: The integration could not read the list of attributes for the named attribute set from Adobe Commerce. The message includes the detail returned by the store.

Resolution: Confirm the attribute set id is valid in your store and that the store is reachable, then re-run the record. If the attribute set exists and the store is healthy, contact iPaaS.com Support with the detail shown in the message.

Error message: Unable to re-assign attribute code value: {attribute code}, value: {value}

Cause: The integration tried to set the named value on the named attribute for a product variant, and Adobe Commerce did not accept it.

Resolution: Confirm the value is a valid option for that attribute in Adobe Commerce, then re-run the record. If the option exists and is valid, contact iPaaS.com Support.

Error message: You must use ChildBarcodeOverrideField function when mapping to UnitBarcodeChildOverride

Cause: A mapping targets the child barcode override field directly instead of supplying its value through the required function, so the integration cannot resolve the correct barcode for each variant.

Resolution: Edit the mapping so the child barcode override value is produced by the ChildBarcodeOverrideField function, then re-run the record. This is a mapping change you can make yourself.

Error message: You must use ChildBarcodeOverrideField function when mapping to UnitBarcodeParentOverride

Cause: A mapping targets the parent barcode override field directly instead of supplying its value through the required function, so the integration cannot resolve the correct barcode.

Resolution: Edit the mapping so the parent barcode override value is produced by the ChildBarcodeOverrideField function, then re-run the record. This is a mapping change you can make yourself.

Error message: Product Category Assignment Delete Attempt Failed: The supplied id was not in the correct format. It should be <product_id>|<category_id>. Id={ID}

Cause: A request to remove a product from a category supplied an identifier that does not match the required combined format of the product id and category id separated by a vertical bar.

Resolution: Make sure the value mapped as the assignment id produces the product id and category id joined by a vertical bar, then re-run the record. This is a mapping change you can make yourself.

Error message: Recieved request to remove category {category ID} from product {SKU} but the product was not found

Cause: The integration was asked to remove the named category from the named product, but no product with that SKU exists in Adobe Commerce.

Resolution: Confirm the product exists in your store and that the SKU is correct. If the product was intentionally deleted, the removal is no longer needed and the error can be dismissed. If the product should exist, transfer it first and re-run the record.

Error message: Unable to create product catalog from prerequisite in Magento B2B. This will prevent the transfer of the product category.

Cause: Before transferring the product category, the integration tried to create the required B2B product catalog and could not, so the category transfer cannot continue.

Resolution: Confirm your store's B2B (shared catalog) features are enabled and that the catalog data is complete, then re-run the record. If the B2B configuration looks correct, contact iPaaS.com Support.

Error message: Could not Create Customer in AdobeCommerce.

Cause: The integration attempted to create the customer in Adobe Commerce and the store did not return a created customer record.

Resolution: Review the customer data for missing required fields such as email, first name, last name, and website, then re-run the record. If the data is complete and valid, contact iPaaS.com Support.

Error message: Unable to dynamically link to existing iPaaS customer using email address. This may result in duplicate customer records.

Cause: The integration tried to match the incoming customer to an existing iPaaS.com customer by email address and could not find a confident match, so a new customer record may be created instead of reusing the existing one.

Resolution: Confirm the email address on the source record matches the existing customer, then re-run the record. If a duplicate was created, review and merge the records in iPaaS.com. If matches are consistently missed, contact iPaaS.com Support.

Error message: Unable to dynamically link to existing Magento customer using email address. This may result in duplicate customer records.

Cause: The integration tried to match the incoming customer to an existing Adobe Commerce customer by email address and could not find a confident match, so a new customer record may be created in your store instead of reusing the existing one.

Resolution: Confirm the email address matches an existing customer in Adobe Commerce, then re-run the record. If a duplicate was created, review and merge the records in your store. If matches are consistently missed, contact iPaaS.com Support.

Error message: Unable to dynamically link to existing Magento customer address after comparing it with city, country, first name and last name fields. This may result in duplicate address records.

Cause: The integration compared the incoming address against the customer's existing Adobe Commerce addresses by city, country, first name, and last name and could not find a confident match, so a new address may be added instead of reusing the existing one.

Resolution: Confirm the address fields on the source record match the existing address, then re-run the record. If a duplicate address was created, review and clean up the addresses in your store. If matches are consistently missed, contact iPaaS.com Support.

Error message: Unable to create customer from Customer Address prerequisite in Magento B2B. This will prevent the transfer of the customer address.

Cause: Before transferring the customer address, the integration tried to create the customer it belongs to and could not, so the address transfer cannot continue.

Resolution: Review the underlying customer data for missing required fields, then re-run the record so the customer and its address transfer together. If the customer data is complete, contact iPaaS.com Support.

Error message: Unable to create Magento-Category as iPaaS category in HandlePrerequisite for company. This will prevent the transfer of the Customer Company.

Cause: Before transferring the customer company, the integration tried to create the category the company depends on and could not, so the company transfer cannot continue.

Resolution: Confirm the related category data is complete and that your store's B2B features are enabled, then re-run the record. If the configuration looks correct, contact iPaaS.com Support.

Error message: Unable to create Magento-Company as iPaaS compnay in HandlePostActions for customer-company relationship. This will prevent the transfer of the Customer company

Cause: While completing the customer-company relationship, the integration tried to create the company and could not, so the relationship cannot be established.

Resolution: Review the company data for missing required fields and confirm your store's B2B features are enabled, then re-run the record. If the data is complete, contact iPaaS.com Support.

Error message: Unable to create Magento-Customer as iPaaS customer in HandlePrerequisite for customer-company relationship. This will prevent the transfer of the Customer Company.

Cause: Before establishing the customer-company relationship, the integration tried to create the customer it depends on and could not, so the company transfer cannot continue.

Resolution: Review the customer data for missing required fields, then re-run the record so the customer and company transfer together. If the customer data is complete, contact iPaaS.com Support.

Error message: Unable to dynamically link to existing iPaaS Company using email address. This may result in duplicate company records.

Cause: The integration tried to match the incoming company to an existing iPaaS.com company by email address and could not find a confident match, so a new company record may be created instead of reusing the existing one.

Resolution: Confirm the email address on the source record matches the existing company, then re-run the record. If a duplicate was created, review and merge the records in iPaaS.com. If matches are consistently missed, contact iPaaS.com Support.

Error message: Unable to create customer in HandlePrerequisite. This will prevent the transfer of the order.

Cause: Before transferring the order, the integration tried to create the customer the order belongs to and could not, so the order transfer cannot continue.

Resolution: Review the customer data for missing required fields, then re-run the order so the customer and order transfer together. If the customer data is complete, contact iPaaS.com Support.

Error message: Order status cannot be cancelled because all items have been shipped and invoiced.

Cause: A cancellation was requested, but every item on the order has already been shipped and invoiced. Adobe Commerce does not allow an order in that state to be cancelled.

Resolution: An order that is fully shipped and invoiced cannot be cancelled; if it should be reversed, process a credit memo or return in Adobe Commerce. Once the situation is resolved this error can be dismissed.

Error message: Order status cannot be cancelled because order status is closed.

Cause: A cancellation was requested for an order whose status is already closed. A closed order cannot be cancelled in Adobe Commerce.

Resolution: No cancellation is possible or needed for a closed order; this error can be dismissed.

Error message: iPaaS could not cancel the order due to previously invoiced items. A credit memo must be performed manually in Magento for cancelled items to close the order and this error can be dismissed once resolved.

Cause: A cancellation was requested for an order that has invoiced items. Those items must be credited before the order can close.

Resolution: In Adobe Commerce, create a credit memo for the cancelled items to close the order. Once that is done, this error can be dismissed.

Error message: Order status cannot be marked as completed because not all items have been shipped and invoiced.

Cause: The order was set to complete, but not every item has been both shipped and invoiced. Adobe Commerce only moves an order to complete once shipping and invoicing are finished.

Resolution: Finish shipping and invoicing the remaining items, then re-run the status update, or leave the order in its current status until fulfillment is complete.

Error message: iPaaS could not create an invoice in Magento:The order has already been fully invoiced.

Cause: An invoice was requested for an order that is already fully invoiced, so there is nothing left to invoice.

Resolution: No further invoice is needed; this error can be dismissed. If you expected additional items to invoice, confirm the order lines in Adobe Commerce.

Error message: iPaaS could not create a shipment in Magento: This order is already fully shipped.

Cause: A shipment was requested for an order whose items have all already been shipped, so there is nothing left to ship.

Resolution: No further shipment is needed; this error can be dismissed. If you expected additional items to ship, confirm the order lines in Adobe Commerce.

Error message: Shipment failed: Magento reports insufficient inventory at the selected location. Please check Magento error logs for more details.

Cause: Adobe Commerce rejected the shipment because the selected source location does not have enough inventory for the items being shipped.

Resolution: Confirm the inventory available at the selected source location in Adobe Commerce, adjust the stock or the source, and check your store's error logs for the specific item, then re-run the record.

Error message: Not all shipment products provided in the custom field value could be located on the original Magento order.

Cause: The shipment lists one or more products that do not appear on the original Adobe Commerce order, so the integration cannot match every shipped item back to an order line. This value is produced by a Dynamic Formula mapping.

Resolution: Confirm the products in the shipment custom field all belong to the original order, then correct the mapping or the source data and re-run the record. Because the value comes from a Dynamic Formula mapping, you can adjust it yourself in the iPaaS.com mapping interface.