Overview
This document provides a comprehensive overview of all error messages explicitly defined within the integration code. Its purpose is to maintain clarity, accuracy, and consistency across all error handling. Each error entry includes the error title, detailed message, trigger condition, and the proposed resolution.
Supported Flows
Product Inventory From iPaaS
Transaction Tracking Number From iPaaS
Transaction To iPaaS
Transaction Tracking Number To iPaaS
Transaction Address To iPaaS
Transaction Line To iPaaS
Transaction Note To iPaaS
Transaction Payment To iPaaS
Product and Variant From iPaaS
Error Collection
Product Inventory from iPaaS
Missing Field
SKU, LocationId, and Level are required to properly create inventory and must not be null or empty.
Description: This issue may occur in the Product Inventory flow from iPaaS when the integration rejects a Product Inventory due to missing or invalid required fields such as SKU, Location ID, and Level.
Resolution: To avoid this error, make sure every Product Inventory includes a valid (non-empty) SKU, LocationId, and Level.
Missing StockItemId and StockLocationId
Unexpected response from API.
Description: StockItemId and StockLocationId were either not returned, or we were unable to extract them API response. This error can occur in the ProductInventory from the iPaaS flow. It happens when the Linnworks integration rejects a Product Inventory because the StockItemId and StockLocationId are mandatory in the Linnworks, but were not supplied.
Resolution: To prevent this issue, ensure that these fields are always provided through mappings before sending data to the integration.
Transaction Tracking Number (Shipping & Packaging) From iPaaS
Invalid ID
Invalid Id: value is null or empty.
Description: This error occurs when the Id value sent to the integration is null, empty, or not in the expected format. In this flow, the Id represents the internal iPaaS identifier for a tracking number. If the Id is missing or formatted incorrectly, the system cannot extract the unique tracking number portion, which is required to retrieve the related transaction tracking number.
Resolution: To prevent this issue, ensure the Id is not null or empty and is provided in the correct iPaaS format, which is a concatenated value like <SalesOrderId>|<TrackingNumberId>. The system splits this Id using the pipe (|) and extracts the unique tracking-number portion to fetch the correct transaction. Make sure the Id follows this exact structure before sending it.
Missing Postal Service ID or Order ID
Invalid Id: missing postalServiceId or orderId.
Description: This error occurs when the required fields, postalServiceId or orderId, are missing in the request. The integration needs both values to correctly process and link the shipment information, and if either is missing, the system cannot continue.
Resolution: Make sure that both postalServiceId and orderId are provided and not empty before sending the request. These fields are required for the system to identify the shipment service and the related order, so the request must always include valid values for both. These fields may be supplied through mapping.
ShippingInfo is null
Order not found or ShippingInfo is null for OrderId: {orderId}.
Description: This error appears when the system cannot find the order corresponding to the provided OrderId, or when the order exists but its ShippingInfo section is missing or not populated. Without ShippingInfo, the integration cannot proceed with shipment-related processing.
Resolution: Verify that the OrderId being sent is valid and corresponds to an existing order, and ensure that the order contains complete ShippingInfo before triggering the integration; the request must include an OrderId that exists in the system and has correctly populated shipping details.
Transaction Not Found
No Transaction found for the order (orderId: {Id}) and Order Tracking: (trackingId: {Id}). Cannot add Shipping Info.
Description: This error occurs during the mapping filter when the system attempts to fetch the external ID for a given transaction. If the external ID is null, it indicates that the transaction does not exist in the external system. Without a valid transaction, shipping information cannot be added.
Resolution: Verify that a Transaction exists for the given OrderId in the external system.
Unable To Create
Unable to create a Shipment in Linnworks from iPaaS.
Description: This issue occurs when iPaaS attempts to create a shipment in Linnworks, but the required data (such as tracking details, order information, or postal service settings) is missing, invalid, or rejected by Linnworks. API failures, incorrect mappings, or missing shipment fields can all trigger this error.
Resolution: Verify that all required shipment details, such as OrderId, postalServiceId, tracking number, and ShippingInfo, are correctly populated before sending the request, and ensure the Linnworks postal service and order exist and are valid so the shipment can be created successfully.
Unable To Update
Unable to Update Shipment in Linnworks from iPaaS.
Description: This error occurs when iPaaS attempts to update an existing shipment in Linnworks, but the shipment cannot be found, the provided fields (such as tracking number, postal service, or order details) are invalid, or Linnworks rejects the update due to missing or incorrect data.
Resolution: Ensure the shipment you are trying to update already exists in Linnworks and that all required fields, such as OrderId, postalServiceId, tracking number, and ShippingInfo, are valid and correctly populated before sending the update request.
Transaction To iPaaS
No Items are available
No items are available, so the order will not be transferred.
Description: This error occurs in the mapping filter for Transaction to iPaaS when the order contains no line items or all items are missing or invalid. Since there are no products to process, the system cannot transfer the order to the target platform.
Resolution: Ensure the order includes at least one valid line item before sending it to the integration. Confirm that each item has the required details (SKU, quantity, etc.) so the system can successfully transfer the order.
Email Address not found
No email address is provided in either the shipping or billing address.
Description: This error occurs in the mapping filter for Transaction to iPaaS, when the system attempts to process an order, but cannot find a valid email address in either the shipping or billing information. Without an email address, order-related notifications and integration processes cannot proceed.
Resolution: Verify that the order contains a valid email address in either the shipping or billing details. Ensure that the email field is not null, empty, or whitespace. If the email is missing, update the order before triggering any integration or processing steps.
Product and Variant From iPaaS
Unable to Create Variation Group
Unable to create variation group with variants in {Identity.AppName} and saved external ids in iPaaS.com
Description: This issue occurs when the system attempts to create a variation group along with its variants in Linnworks but the creation process fails. As a result, the external IDs for the variation group and variants are not saved in iPaaS.com. This failure is typically caused when required fields for variations are missing, invalid, or not mapped correctly in the integration.
Resolution: Verify that all required fields for creating a variation group and its variants are correctly mapped in the integration. Once all necessary fields are provided and the data is valid, trigger the integration again to allow iPaaS.com to capture and store the correct external IDs.
Unable to Create Inventory Item
Unable to create inventory item in {Identity.AppName} and saved external ids in iPaaS.com
Description: This error occurs when the system tries to create a new inventory item in Linnworks but transfer fails. As a result, the inventory item is not created, and the external IDs cannot be saved in iPaaS.com. This usually happens due to missing or invalid data in the payload and incorrect field mapping.
Resolution: To resolve this issue, verify that the request payload contains all required fields and that each field is mapped correctly. Review the technical logs to check the serialized request and the API response for any errors or missing information.
Unable to Update Inventory Item
Unable to update inventory item in {Identity.AppName} and saved external ids in iPaaS.com
Description: This error occurs when the system attempts to update an existing inventory item in Linnworks but the API call fails or does not return a successful response. As a result, the changes to the inventory item are not applied, and the external IDs or updated data are not reflected in iPaaS.com. Common causes include missing or invalid fields in the request payload or incorrect mapping issues with the target platform.
Resolution: To resolve this issue, verify that the request payload contains all required fields and that each field is mapped correctly. Review the technical logs to check the serialized request and the API response for any errors or missing information.
Invalid Match
Invalid match field: {fieldMatch}
Description: This error occurs when the integration code receives an unexpected value in the fieldMatch variable. The current implementation only supports "SKU" as a valid field for processing collisions and assigning existing stock item IDs. If fieldMatch contains any other value, the system cannot handle it and throws the exception Invalid match field: {fieldMatch}. This typically indicates a configuration issue or incorrect data mapping in the integration.
Resolution: To resolve this issue, verify the value being passed to fieldMatch and ensure it is set to "SKU" for inventory collision handling, or implement the necessary functionality to handle the other field as well.
Duplicate SKU
Item with this SKU already exists.
Description: This error can occur in Product or Product Variant from iPaaS flow. It happens when the Linnworks integration rejects a Product or Product Variant because the SKU provided already exists in the target system only if the collision handling for the product variant or product is not enabled.
Resolution: To prevent this issue, ensure that each Product or Product Variant has a unique SKU, or enable collision handling from the mapping collection before sending data to the integration.