Overview
This article catalogs the error messages you may encounter while synchronizing data between iPaaS.com and ShipHero, grouped by the flow that produces them. Each entry lists the message as it appears in the iPaaS.com error logs (under Dashboard → Integration Monitoring → Error Logs), what causes it, and how to resolve it. Values shown in braces (for example, the SKU or warehouse name) are filled in with the specific record's details when the error occurs.
Supported Flows
Sales Order Transfer
Product and Kit Transfer
Warehouse Product Inventory Transfer
Warehouse Product Variant Inventory Transfer
Shipment Transfer
Sales Order Transfer
Order not yet created in ShipHero
Sales Order Id is null or empty, and it is required for the sales order update.
Description: An update was dispatched for an order that is not yet linked to a ShipHero order. An order must be created in ShipHero before it can be updated.
Resolution: Make sure the order has been transferred through the Add Sales Order flow (so it exists in ShipHero) before an update is sent. If the order was expected to exist, contact iPaaS.com Support at support@ipaas.com.
Line item product could not be created
Unable to create product sku: {Sku}. This will prevent the transfer of the order.
Description: A line item references a product that does not exist in ShipHero, and the integration was unable to create it automatically as a prerequisite. The order cannot be completed without its line-item products.
Resolution: Confirm that a product with the SKU shown in the message exists in iPaaS.com and can be created in ShipHero (valid SKU and product details), then re-sync the order. A variant-specific form of this message ("Unable to create variant sku…") indicates the same condition for a variant.
Order could not be matched to an existing ShipHero order
Unable to dynamically link to existing Sales Order using Transaction Number. This may result in duplicate Transaction records.
Description: The integration tried to link the order to an existing ShipHero order by its order number but could not, so a duplicate order may be created. A line-level form of this message ("…existing ShipHero Sales Order Line…") indicates the same condition for a line item.
Resolution: Verify that the order number is unique and consistent between iPaaS.com and ShipHero. If duplicate orders appear in ShipHero, contact iPaaS.com Support at support@ipaas.com.
Unexpected API response
Unexpected response from API. Id was either not returned, or we were unable to extract it from the API response.
Description: ShipHero returned a response the integration could not process while creating or updating the order or its line items.
Resolution: Retry the transfer. If the error persists, contact iPaaS.com Support at support@ipaas.com with the error timestamp and the affected order number.
Product and Kit Transfer
Kit's product could not be created
Unable to create product. This will prevent the transfer of the kit.
Description: A kit is built on a ShipHero product identified by SKU. The underlying product did not exist in ShipHero and could not be created automatically, so the kit cannot be built. A component-specific form of this message ("…transfer of the kit Component") indicates the same condition for a kit component.
Resolution: Confirm that the product for the kit's SKU exists in iPaaS.com and can be created in ShipHero, then re-sync. Ensure SKUs are valid and consistent between the two systems.
Kit could not be matched to an existing ShipHero product
Unable to dynamically link to existing ShipHero product kit using iPaaS.com Kit: {Kit}. This may result in duplicate product kit records.
Description: The integration tried to link the kit (or a kit component) to an existing ShipHero product by SKU but could not, so a duplicate kit record may be created.
Resolution: Verify that the kit and component SKUs are unique and consistent between iPaaS.com and ShipHero. If duplicate kit records appear, contact iPaaS.com Support at support@ipaas.com.
Warehouse Product Inventory Transfer
Location not found in iPaaS.com
This location ({WarehouseIdentifier}) does not exist in iPaaS.com. Please create it manually in iPaaS.com.
Description: ShipHero reported inventory for a warehouse that has no matching location in iPaaS.com. Inventory is recorded against an iPaaS.com location, matched to the ShipHero warehouse by name.
Resolution: Create a location in iPaaS.com whose name matches the ShipHero warehouse shown in the message, then re-sync the inventory.
Product not found in iPaaS.com
There is no product in iPaaS.com by this sku: {Sku}. Cannot add an inventory.
Description: ShipHero reported inventory for a product that does not exist in iPaaS.com. Inventory attaches to an iPaaS.com product, matched by SKU.
Resolution: Make sure a product with the SKU shown in the message exists in iPaaS.com (transfer or create it), then re-sync the inventory.
Warehouse Product Variant Inventory Transfer
Location not found in iPaaS.com
This location ({WarehouseIdentifier}) does not exist in iPaaS.com. Please create it manually in iPaaS.com.
Description: ShipHero reported variant inventory for a warehouse that has no matching location in iPaaS.com.
Resolution: Create a location in iPaaS.com whose name matches the ShipHero warehouse shown in the message, then re-sync the variant inventory.
Product variant not found in iPaaS.com
There is no product variant in iPaaS.com by this sku: {Sku}. Cannot add an inventory.
Description: ShipHero reported inventory for a product variant that does not exist in iPaaS.com. Variant inventory attaches to an iPaaS.com product variant, matched by SKU.
Resolution: Make sure a product variant with the SKU shown in the message exists in iPaaS.com (transfer or create it), then re-sync the variant inventory.
Shipment Transfer
Shipment's order not found in iPaaS.com
Transaction Tracking Number is not linked to any Transaction.
Description: ShipHero reported a shipment whose order does not have a matching Transaction in iPaaS.com. A shipment's tracking details are recorded against the order it belongs to.
Resolution: Make sure the order the shipment belongs to has been synced to iPaaS.com before the shipment, then re-sync the shipment.
Shipping method not found in iPaaS.com
Shipping Method ({Carrier}) needs to be created manually in iPaaS.com first.
Description: The shipment's carrier has no matching shipping method in iPaaS.com.
Resolution: Create a shipping method in iPaaS.com that matches the carrier name shown in the message, then re-sync the shipment.