See what the Linnworks integration can do →
Overview
This article catalogs the error messages the Linnworks integration can record in the iPaaS.com error logs, grouped by mapping collection flow. Each error carries a stable error code so you can find it here quickly. Every entry lists the code, the message a subscriber sees, what causes it, and how to resolve it.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Transaction To iPaaS.com
Transaction Line To iPaaS.com
Transaction Tracking Number From iPaaS.com
Product Inventory From iPaaS.com
Product Variant Inventory From iPaaS.com
Product and Variant From iPaaS.com
Error Collection
Transaction To iPaaS.com
No items available
LNWK-BIZL-1001 - No items are available, so the order will not be transferred.
Description: Raised by the order mapping filter when the order has no line items, or none of its item SKUs exist as Products in iPaaS.com.
Resolution: Ensure the order includes at least one line item and that those items' SKUs exist as Products in iPaaS.com before transferring the order.
Email address not found
LNWK-BIZL-1002 - No email address is provided in either the shipping or billing address.
Description: Raised by the order mapping filter when the order has no email address on either its shipping or billing address.
Resolution: Add a valid email address to the order's shipping or billing address in Linnworks, then re-sync the order.
Unable to link existing transaction
LNWK-BIZL-1003 - Unable to dynamically link to existing Linnworks transaction using NumOrderId {NumOrderId}. This may result in duplicate transaction records.
Description: Raised when the integration cannot link an incoming order to an existing iPaaS.com Transaction by its order number, which can lead to duplicate Transactions.
Resolution: Verify the order number (NumOrderId) is consistent between Linnworks and iPaaS.com so the transfer can match the existing Transaction. If a duplicate Transaction results, your Managed Integration Service Provider (MiSP) can help reconcile it.
Transaction Line To iPaaS.com
Item not available
LNWK-BIZL-1004 - Item {ItemNumber} is not available in iPaaS.com, so it cannot be transferred.
Description: Raised by the line mapping filter when a line item's SKU does not exist as a Product in iPaaS.com.
Resolution: Transfer the matching Product to iPaaS.com, then re-sync the order so the line can be transferred.
Transaction Tracking Number From iPaaS.com
Invalid ID
LNWK-VALD-1001 - Invalid Id: value is null or empty.
Description: The shipment Id sent to the integration is null or empty, so the tracking record cannot be identified.
Resolution: Ensure the shipment Id is provided in the expected format (a combined value such as <SalesOrderId>|<TrackingNumberId>) before sending the request.
Missing postal service ID or order ID
LNWK-VALD-1002 - Invalid Id '{Id}': missing postalServiceId or orderId.
Description: The shipment Id is missing its postal-service or order portion, so the integration cannot link the shipment.
Resolution: Ensure both the postal service and order portions of the shipment Id are present before sending the request.
Order not found or shipping info missing
LNWK-NFND-1001 - Order not found or ShippingInfo is null for OrderId: {orderId}.
Description: The integration could not find the order for the given OrderId, or the order has no shipping information.
Resolution: Verify the OrderId corresponds to an existing order that has shipping details before triggering the transfer.
Transaction not found
LNWK-NFND-1002 - No Transaction found for the order (orderId: {Id}) and Order Tracking: (trackingId: {Id}). Cannot add Shipping Info.
Description: Raised by the shipment mapping filter when no Linnworks order can be found for the originating Transaction, so shipping information cannot be added.
Resolution: Ensure the order has been transferred to Linnworks before adding its shipment.
Unable to create shipment
LNWK-EXTN-1001 - Unable to create Shipment in Linnworks from iPaaS.
Description: The integration attempted to create a shipment in Linnworks but the required data was missing or invalid, or Linnworks rejected the request.
Resolution: Verify the order, postal service, tracking number, and shipping details are populated and valid, and that the Linnworks order and postal service exist, then retry.
Unable to update shipment
LNWK-EXTN-1002 - Unable to update Shipment in Linnworks from iPaaS.
Description: The integration attempted to update a shipment in Linnworks but the shipment could not be found or the data was rejected.
Resolution: Ensure the shipment already exists in Linnworks and that the tracking, postal service, and order details are valid before retrying.
Product Inventory From iPaaS.com
Missing required field
LNWK-VALD-1003 - SKU, LocationId, and Level are required to properly create inventory and must not be null or empty.
Description: A product inventory record is missing one of the required values — SKU, LocationId, or Level.
Resolution: Ensure each product inventory record maps a non-empty SKU, LocationId, and Level.
Missing required field on update
LNWK-VALD-1005 - SKU, LocationId, and Level are required to properly update inventory and must not be null or empty.
Description: A product inventory record is missing one of the required values — SKU, LocationId, or Level — when updating its stock level.
Resolution: Ensure each product inventory record maps a non-empty SKU, LocationId, and Level.
Product not found
LNWK-NFND-1003 - Product could not be found by SKU {SKU} in Linnworks. Please make sure product exists.
Description: The integration could not find a Linnworks product for the given SKU, so its stock level cannot be set.
Resolution: Transfer the product to Linnworks (or confirm the SKU matches an existing Linnworks product) before setting its stock level.
Unable to create product prerequisite
LNWK-EXTN-1003 - Unable to create Product in Linnworks. This will prevent the transfer of the inventory.
Description: The integration attempted to create the product needed for the inventory transfer but the creation failed.
Resolution: Verify the product's required fields are mapped and valid, then retry. If it keeps failing, your Managed Integration Service Provider (MiSP) can investigate and involve iPaaS.com Support if needed.
Product Variant Inventory From iPaaS.com
Missing required field
LNWK-VALD-1004 - SKU, LocationId, and Level are required to properly create inventory and must not be null or empty.
Description: A product variant inventory record is missing one of the required values — SKU, LocationId, or Level.
Resolution: Ensure each variant inventory record maps a non-empty SKU, LocationId, and Level.
Missing required field on update
LNWK-VALD-1006 - SKU, LocationId, and Level are required to properly update inventory and must not be null or empty.
Description: A product variant inventory record is missing one of the required values — SKU, LocationId, or Level — when updating its stock level.
Resolution: Ensure each variant inventory record maps a non-empty SKU, LocationId, and Level.
Product variant not found
LNWK-NFND-1004 - Product Variant could not be found by SKU {SKU} in Linnworks. Please make sure product variant exists.
Description: The integration could not find a Linnworks product variant for the given SKU, so its stock level cannot be set.
Resolution: Transfer the product variant to Linnworks (or confirm the SKU matches an existing Linnworks variant) before setting its stock level.
Unable to create product prerequisite
LNWK-EXTN-1004 - Unable to create Product for Variant Inventory. This will prevent the transfer of the product variant inventory.
Description: The integration attempted to create the product needed for the variant inventory transfer but the creation failed.
Resolution: Verify the product's required fields are mapped and valid, then retry. If it keeps failing, your Managed Integration Service Provider (MiSP) can investigate and involve iPaaS.com Support if needed.
Product and Variant From iPaaS.com
Unable to create variation group
LNWK-EXTN-1005 - Unable to create variation group with variants in Linnworks and saved external ids in iPaaS.com.
Description: The integration created the product's variants in Linnworks but could not assemble them into a variation group. The external IDs generated up to that point were saved to iPaaS.com.
Resolution: Verify the variation group and variant fields are mapped and valid, then re-sync the product. Because the external IDs were saved, the re-sync reconciles with the existing records rather than duplicating them. If it continues to fail, your Managed Integration Service Provider (MiSP) can investigate and involve iPaaS.com Support if needed.
Unable to create inventory item
LNWK-EXTN-1006 - Unable to create inventory item in Linnworks and saved external ids in iPaaS.com.
Description: The integration could not create the product in Linnworks. The external IDs generated for the transfer were saved to iPaaS.com.
Resolution: Verify the product's required fields are mapped and valid, then retry. Because the external IDs were saved, the retry reconciles with the existing record rather than duplicating it.
Unable to update inventory item
LNWK-EXTN-1007 - Unable to update inventory item in Linnworks and saved external ids in iPaaS.com.
Description: The integration could not update the product in Linnworks. The external IDs generated for the transfer were saved to iPaaS.com.
Resolution: Verify the product's required fields are mapped and valid, then retry. Because the external IDs were saved, the retry reconciles with the existing record rather than duplicating it.
Product variants could not be created
LNWK-EXTN-1009 - One or more product variants could not be created in Linnworks.
Description: One or more of the product's variants could not be created in Linnworks, so the product transfer did not complete. The specific variant failures are appended to the message.
Resolution: Verify the variant fields (SKU and any required attributes) are mapped and valid, then re-sync the product. If a variant's SKU already exists, see Duplicate SKU below.
Product variants could not be updated
LNWK-EXTN-1010 - One or more product variants could not be updated in Linnworks.
Description: One or more of the product's variants could not be updated in Linnworks, so the product transfer did not complete. The specific variant failures are appended to the message.
Resolution: Verify the variant fields are mapped and valid, then re-sync the product.
Duplicate SKU
LNWK-EXTN-1008 - Item with this SKU already exists.
Description: Linnworks rejected a product or variant because a product with the same SKU already exists and the mapping collection's Collision Handling Method is set to Error, so duplicates are rejected rather than reconciled.
Resolution: Either give each product or variant a unique SKU, or open the mapping collection's settings page and change Collision Handling Method from Error to a method that reconciles duplicates — Update and Link, Remap and Link, or Update and No Link — then re-transfer.
External Linnworks API Errors
These can occur on any flow when a call to the Linnworks API fails.
Linnworks API call failed
LNWK-EXTN-1011 - Error calling Linnworks CallWrapper.{action}: {details} (Http Code: {code})
Description: A call from the integration to the Linnworks API failed. The message names the operation ({action}, for example
SalesOrder.GET), the detail Linnworks returned, and the HTTP status code. Common causes include an invalid identifier or parameter — for example, transferring an order by an id that is not an open order in Linnworks — or Linnworks otherwise rejecting the request.Resolution: Review the operation and detail in the message. For an invalid id or parameter, confirm the record exists and the identifier is correct (for example, that the order is still an open order in Linnworks). If the cause is unclear, share the operation and detail with your Managed Integration Service Provider (MiSP), who can investigate and, if needed, raise it with iPaaS.com Support.