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 From iPaaS
Product 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, LocationID, 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
Description: 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
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.