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 a stable error code you can search for on this page, 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.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Sales Order Transfer
Product and Kit Transfer
Warehouse Product Inventory Transfer
Warehouse Product Variant Inventory Transfer
Shipment Transfer
API Communication (all flows)
Error Collection
Sales Order Transfer
Sales Order missing required Id for update
SHHE-VALD-1001 - SalesOrder 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 was first transferred through the Add Sales Order flow so it exists in ShipHero, then re-run the update. If the order should already exist, review the Add Sales Order transfer history; your Managed Integration Service Provider (MiSP) can confirm the order-transfer sequence and mappings if it isn't clear.
Line item product could not be created
SHHE-BIZL-1001 - 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 could not 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 has valid details for creation in ShipHero, then re-sync the order.
Line item variant could not be created
SHHE-BIZL-1002 - Unable to create variant sku: {Sku}. This will prevent the transfer of the order.
Description: A line item references a product variant that does not exist in ShipHero, and the integration could not create it automatically as a prerequisite.
Resolution: Confirm that a product variant with the SKU shown in the message exists in iPaaS.com with valid details, then re-sync the order.
Order could not be linked to an existing ShipHero order
SHHE-BIZL-1003 - Unable to dynamically link order {transactionNumber} to an existing ShipHero Sales Order by Transaction Number. This may result in duplicate Transaction records.
Description: The integration tried to link the order to an existing ShipHero order by its Transaction Number but could not, so a duplicate order may be created.
Resolution: Verify that the order number shown in the message is unique and consistent between iPaaS.com and ShipHero so the transfer can match the existing order. If a duplicate results and you are unsure how to reconcile it, your Managed Integration Service Provider (MiSP) — who manages your integration — can help.
Order line could not be linked to an existing ShipHero order line
SHHE-BIZL-1004 - Unable to dynamically link to existing ShipHero Sales Order Line using Transaction Number. This may result in duplicate Transaction Line records.
Description: The integration tried to link an order line to an existing ShipHero order line by Transaction Number but could not, so a duplicate line record may be created.
Resolution: Verify that the order and its line items are consistent between iPaaS.com and ShipHero. If duplicate line records result, your MiSP can help reconcile them.
Unexpected API response - order Id not returned
SHHE-EXTN-1002 - 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 — no order Id was returned.
Resolution: Retry the transfer — this error is often transient. If it persists, note the error timestamp and the affected order number and contact your Managed Integration Service Provider (MiSP); they can investigate and involve iPaaS.com Support if needed.
Unexpected API response - no order lines returned
SHHE-EXTN-1003 - Unexpected response from API after attempting to create newly added order line items. No lines were returned in the API response, and no error was reported
Description: While adding new line items during an order update, ShipHero returned no created lines and reported no error, so the integration could not confirm the line items were created.
Resolution: Retry the transfer — this error is often transient. If it persists, note the error timestamp and the affected order number and contact your Managed Integration Service Provider (MiSP); they can investigate and involve iPaaS.com Support if needed.
Product and Kit Transfer
Kit's product could not be created
SHHE-BIZL-1005 - Unable to create the product for kit {Kit.Sku}. 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.
Resolution: Confirm that the product for the kit's SKU shown in the message exists in iPaaS.com and can be created in ShipHero, then re-sync. Ensure SKUs are valid and consistent between the two systems.
Kit component's product could not be created
SHHE-BIZL-1006 - Unable to create the product for kit component {kitComponent.Sku}. This will prevent the transfer of the kit Component.
Description: A kit component is built on a ShipHero product identified by SKU. That product did not exist in ShipHero and could not be created automatically, so the kit component cannot be built.
Resolution: Confirm the product for the kit component's SKU shown in the message exists in iPaaS.com and can be created in ShipHero, then re-sync.
Kit could not be linked to an existing ShipHero product kit
SHHE-BIZL-1007 - Unable to dynamically link to existing ShipHero product kit using iPaaS.com Kit: {finalKitExternalId}. This may result in duplicate product kit records.
Description: The integration tried to link the kit to an existing ShipHero product by SKU but could not, so a duplicate kit record may be created.
Resolution: Verify that the kit SKU is unique and consistent between iPaaS.com and ShipHero. If a duplicate kit record results, your MiSP can help reconcile it.
Kit component could not be linked to an existing ShipHero product kit component
SHHE-BIZL-1008 - Unable to dynamically link to existing ShipHero product kit component using iPaaS.com kit component: {Sku}. This may result in duplicate product kit component records.
Description: The integration tried to link a kit component to an existing ShipHero product by SKU but could not, so a duplicate kit component record may be created.
Resolution: Verify that the kit component SKU shown in the message is unique and consistent between iPaaS.com and ShipHero. If a duplicate kit component record results, your MiSP can help reconcile it.
Product SKU mismatch on update
SHHE-BIZL-1009 - Product SKU mismatch. Unable to update the product because the existing SKU {existingSku} does not match the requested SKU {requestedSku}.
Description: The product targeted for update in ShipHero is linked to a different SKU than the one being sent, so the update was stopped to avoid overwriting the wrong product.
Resolution: Verify that the SKU in iPaaS.com matches the ShipHero product it is linked to. If the SKUs are correct but the records are linked incorrectly, your Managed Integration Service Provider (MiSP) can review and correct the link.
Product variant SKU mismatch on update
SHHE-BIZL-1010 - Product Variant SKU mismatch. Unable to update the product variant because the existing SKU {existingSku} does not match the requested SKU {requestedSku}.
Description: The product variant targeted for update in ShipHero is linked to a different SKU than the one being sent, so the update was stopped to avoid overwriting the wrong variant.
Resolution: Verify that the variant SKU in iPaaS.com matches the ShipHero variant it is linked to. If the SKUs are correct but the records are linked incorrectly, your MiSP can review and correct the link.
Kit component's variant could not be created
SHHE-BIZL-1011 - Unable to create the variant for kit component {kitComponent.Sku}. This will prevent the transfer of the kit Component.
Description: A kit component is built on a ShipHero product variant identified by SKU. That variant did not exist in ShipHero and could not be created automatically, so the kit component cannot be built.
Resolution: Confirm the variant for the kit component's SKU shown in the message exists in iPaaS.com and can be created in ShipHero, then re-sync.
Warehouse Product Inventory Transfer
Location not found in iPaaS.com
SHHE-NFND-1001 - 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
SHHE-NFND-1002 - 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
SHHE-NFND-1001 - 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
SHHE-NFND-1003 - 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
SHHE-NFND-1004 - 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
SHHE-NFND-1005 - 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.
API Communication (all flows)
ShipHero API call failed
SHHE-EXTN-1001 - Error calling ShipHero CallWrapper.{action}: {response body} (Http Code: {code})
Description: ShipHero rejected or failed an API call while transferring a record. The message includes ShipHero's own error detail and the HTTP status code.
Resolution: Review the ShipHero error detail and HTTP status shown in the message. Transient errors (timeouts, rate limits, HTTP 5xx) usually succeed on re-sync; if the message points to invalid data, correct the record in iPaaS.com and re-sync. If it persists, share the error detail and timestamp with your Managed Integration Service Provider (MiSP), who can investigate and, if needed, raise it with iPaaS.com Support.
Error during a batch operation
SHHE-EXTN-1004 - Received an exception during batch run on {Action}. {detail}
Description: One or more calls in a batched operation to ShipHero failed, which stopped the batch.
Resolution: Retry the transfer. If it persists, note the error timestamp and contact your Managed Integration Service Provider (MiSP); they can investigate and involve iPaaS.com Support if needed.