Connection and Authentication

Products

Product Categories

Customers

Company and B2B

Orders

Invoices

Shipments

Description: Adobe Commerce rejected or failed the API call the integration made. The message names the action attempted, the HTTP status code, and the response your store returned. A common example is a duplicate being rejected — such as "A customer with the same email address already exists in an associated website." — which happens when more than one collection tries to create the same record, or the record already exists in your store.

Resolution: Read the Adobe Commerce response included in the message to see exactly what your store rejected, and correct the data or configuration it points to before re-running the record. If the message is a duplicate-customer response, check whether more than one add collection covers the same records and let a single add collection (or the update collection) maintain each record; the Adobe Commerce/Magento 2 Known Limitations article has more on this. If the response is not clear enough to act on, your MiSP can review the mapping and connection setup for the affected flow.

Description: 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; your MiSP can help if you are unsure which credential set your store uses.

Description: The integration reached your store but the login was rejected. The message includes the response Adobe Commerce returned, which usually indicates an invalid or expired credential.

Resolution: Confirm the credentials in the connection settings are current and that the account is active in Adobe Commerce, then re-run the record. If the credentials are correct and login still fails, your MiSP can verify the store's integration/OAuth configuration.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: 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 and the error persists, your MiSP can investigate the attribute setup.

Description: The named attribute exists in Adobe Commerce but not with global scope. The integration requires the attribute to have global scope before it can use it in a transfer.

Resolution: In Adobe Commerce, set the attribute's scope to Global, then re-run the record. This is a change in your store's attribute configuration.

Description: The named multi-select attribute exists in Adobe Commerce but not with global scope. The integration requires it to have global scope before it can use it in a transfer.

Resolution: In Adobe Commerce, set the multi-select attribute's scope to Global, then re-run the record. This is a change in your store's attribute configuration.

Description: 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, your MiSP can review the attribute configuration with you.

Description: 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, your MiSP can review the configurable-product setup with you.

Description: 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, share the detail shown in the message with your MiSP to investigate.

Description: 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, your MiSP can review the attribute's option list with you.

Description: 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.

Description: 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.

Description: The integration automatically tried to match the incoming product category to an existing Adobe Commerce category or catalog by name and could not find a confident match, so a new category or catalog may be created instead of reusing the existing one. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the product category name on the source record matches the existing category or catalog in your store, then re-run the record. If a duplicate was created, reconcile the categories in your store. If the match is consistently missed, your MiSP can review the category naming and source data.

Description: 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, your MiSP can review the shared-catalog setup.

Description: 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 and the customer still is not created, your MiSP can investigate the customer configuration in your store.

Description: The customer reached the integration without any address marked as primary billing or primary shipping. Adobe Commerce requires at least one default billing or shipping address.

Resolution: In iPaaS.com, set either IsPrimaryBilling or IsPrimaryShipping to true on one of the customer's addresses, then re-run the record. This is a change you can make yourself.

Description: The integration automatically 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. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the email address on the source record matches the existing customer, then re-run the record. If a duplicate was created, reconcile the records in iPaaS.com. If matches are consistently missed, your MiSP can review the source data and mapping.

Description: The integration automatically 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. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the email address matches an existing customer in Adobe Commerce, then re-run the record. If a duplicate was created, reconcile the records in your store. If matches are consistently missed, your MiSP can review the source data and mapping.

Description: The integration automatically 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. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the address fields on the source record match the existing address, then re-run the record. If a duplicate address was created, reconcile the addresses in your store. If matches are consistently missed, your MiSP can review the address source data.

Description: The integration automatically tried to match the incoming customer category to an existing Adobe Commerce customer group by name and could not find a confident match, so a new customer group may be created instead of reusing the existing one. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the customer category name on the source record matches the existing customer group in your store, then re-run the record. If a duplicate was created, reconcile the customer groups in your store. If the match is consistently missed, your MiSP can review the naming and source data.

Description: 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 and the error persists, your MiSP can investigate.

Description: A company was sent to Adobe Commerce without an email address, which the integration requires to create or update the company.

Resolution: Map an email address for the company and re-run the record. This is a mapping change you can make yourself.

Description: The integration automatically 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. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the email address on the source record matches the existing company, then re-run the record. If a duplicate was created, reconcile the records in iPaaS.com. If matches are consistently missed, your MiSP can review the source data and mapping.

Description: 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, your MiSP can review the company and category setup.

Description: 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 and the error persists, your MiSP can investigate.

Description: 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 and the error persists, your MiSP can investigate.

Description: The company's designated super user could not be used because that customer does not exist in iPaaS.com, or is already the super user of another company in Adobe Commerce. A company can have only one super user, and a customer can be the super user of only one company.

Resolution: Confirm the mapped super user exists in iPaaS.com and is not already the super user of another company, then correct the source data or mapping and re-run the record. This is a change you can make yourself.

Description: 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 and the error persists, your MiSP can investigate.

Description: 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.

Description: 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.

Description: 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.

Description: 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.

Description: The integration automatically tried to match the incoming transaction to an existing Adobe Commerce transaction by transaction number and could not find a confident match, so a new transaction may be created instead of reusing the existing one. This automatic matching is built into the integration; it is not a configurable collision setting.

Resolution: Confirm the transaction number on the source record matches the existing transaction, then re-run the record. If a duplicate was created, reconcile the transactions in your store. If matches are consistently missed, your MiSP can review the source data and mapping.

Description: A line item on the named order is marked as a gift card, but no gift card information was provided for it, so the line cannot be processed.

Resolution: Provide the gift card information for the marked line through the mapping or source data, then re-run the record. This is a change you can make yourself.

Description: A line item on the named order is marked as a gift voucher, but the gift card information needed to process it was not found.

Resolution: Confirm the gift voucher line supplies its gift card information through the mapping or source data, then re-run the record. This is a change you can make yourself.

Description: 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.

Description: 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.

Description: 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.

Description: A shipment reached the integration without the Shipment Items value it needs to match shipped items back to the order, so the shipment cannot be processed.

Resolution: Confirm the Shipment Items value is populated for the shipment through the mapping or source data, then re-run the record. This is a change you can make yourself.

Description: 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.

Adobe Commerce/Magento 2 Integration Known Limitations

Understanding iPaaS.com API Error Codes