This article lists the error messages you may encounter with the iPaaS.com Akeneo integration — primarily errors written into the integration's own logic, together with the Akeneo API error subscribers most commonly encounter during product and bundle transfers. It does not cover other errors returned by the iPaaS.com platform or the Akeneo API. Each entry lists the message text, what triggers it, and how to resolve it. These errors appear under Dashboard / Integration Monitoring / Error Logs, where you can identify, understand, and resolve issues encountered during data synchronization.

Product and Variant Linking

These errors occur during a transfer when the integration tries to link an incoming Akeneo product or variant to an existing record in iPaaS.com and cannot establish the link. They are duplicate-prevention safeguards.

Unable to dynamically link an existing product or variant

"Unable to dynamically link to existing Akeneo product using SKU: {sku}. This may result in duplicate product records in Akeneo." Variants produce the equivalent message for a variant, and the message appears in an Identifier form when the subscription uses the Identifier ID format (for example, "...using Identifier: {identifier}...").

Explanation: The integration tried to match the incoming product (or variant) to an existing iPaaS.com record by its SKU or identifier so it could update that record instead of creating a new one, but no reliable link could be made. Continuing could create a duplicate.
Resolution: Confirm the product (or its parent product) has already been transferred to iPaaS.com and that its SKU/identifier in Akeneo matches the value stored in iPaaS.com. Resolve any SKU or identifier mismatch in Akeneo, then re-sync. Confirm the Akeneo Product ID Format subscription setting (UUID vs Identifier) matches your Akeneo environment, since it determines which identifier is used to match.

Prerequisite Transfers

The integration transfers some records (variants, related products, kit/bundle components) only after the product they depend on exists in iPaaS.com. When that prerequisite product cannot be created first, the dependent transfer is stopped to avoid orphaned or duplicate data.

Unable to create a prerequisite product

"Unable to create the prerequisite product dependency. This will prevent the transfer of the product. ExternalId {externalId}" (variations reference the product SKU instead of the ExternalId).

Explanation: Before transferring the current record, the integration tried to create or transfer a product it depends on and that prerequisite transfer failed, so the current transfer cannot proceed.
Resolution: Review the error logs for the failed prerequisite product transfer and resolve its underlying error first (for example, a missing required field on that product), then re-sync. If the dependency is a related product you do not need enforced, the Skip Related Product Pre-requisite subscription setting controls whether related-product prerequisites are required.

Unable to create a prerequisite kit (bundle) component

"Unable to create the prerequisite Akeneo bundle component product. This will prevent the transfer of the product. Sku: {sku}" (a similar message references the default bundle component).

Explanation: While transferring a bundle (kit), the integration tried to create a component product the bundle depends on, and that component could not be created — so the bundle transfer is stopped.
Resolution: Confirm the component product identified by the SKU in the message exists in Akeneo and can transfer to iPaaS.com on its own, then re-sync the bundle. The Create Missing Bundle Items subscription setting controls whether the integration attempts to create missing bundle component products.

Unable to create a parent product for a variant

"Unable to create the prerequisite Akeneo parent product. This will prevent the transfer of the product variant. Sku: {sku}"

Explanation: A variant was being transferred but its parent product could not be created in iPaaS.com first, so the variant transfer is stopped. Variants transfer only as children of their base product.
Resolution: Transfer the base (parent) product successfully first, then re-sync the variant. Review the error logs for the parent product's own transfer error if it failed.

Referenced product does not exist in Akeneo

"Product "{sku}" does not exist or you do not have permission to access it" — this message is returned by Akeneo with an HTTP 404 (Not Found) response.

Explanation: A bundle item (kit component) or a related product references a product SKU that does not exist in Akeneo, or the connected credentials do not have permission to read it. When the integration resolves the referenced product against Akeneo during a product or bundle transfer, Akeneo returns this message. For example, if the SKU OPTIONTESTINGPROD is listed as a bundle item on the SANDWICHCOMBO kit but no product with that SKU exists in Akeneo, resolving the bundle item fails with this error.
Resolution: Confirm the referenced SKU exists in Akeneo and that the connection's user has permission to read it. If the product should exist, create it in Akeneo (or correct the SKU on the association) and re-sync; if the association is invalid, remove the referenced product from the bundle's items or from the related-product association. For a bundle item, enabling the Create Missing Bundle Items subscription setting lets the integration create the missing item in iPaaS.com, provided it resolves in Akeneo. This does not apply to related products — a related product must exist in Akeneo (or be removed from the related-product association) for the transfer to succeed. Bundle items and related products are different relationship types; see the Akeneo Connections and Settings article for how these two settings differ.

Akeneo Integration Error Messages