Skip to main content

Orderful Error Messages

Orderful errors explained

This document catalogs the error messages you may encounter in iPaaS.com when synchronizing data with Orderful, grouped by mapping collection flow. Each entry shows the message text, what causes it, and how to resolve it.

Supported Flows

  • Orderful Shipping Method To iPaaS.com

  • Orderful Transaction From iPaaS.com

  • Orderful Transaction To iPaaS.com

  • Orderful Ship Notice Transaction Tracking Number To iPaaS.com

Error Collection

Orderful Shipping Method To iPaaS.com

Shipping Method Not Found

Could not find any shipping method associated with the provided ID.

  • Description: Occurs when retrieving a shipping method if the provided ID is null, empty, or does not correspond to an existing shipping method.

  • Resolution: Provide a valid shipping method ID (the carrier identification code) and confirm the shipping method exists before retrying.

Orderful Transaction From iPaaS.com

Transaction Address Missing

Transaction could not be created because the Address information is missing.

  • Description: Occurs while creating a transaction in Orderful when the address information is null or empty. At least one address is required.

  • Resolution: Provide at least one valid address (with the required address fields) on the transaction before retrying.

Transaction Line Items Missing

Transaction creation failed. No line items were provided.

  • Description: Occurs while creating a transaction in Orderful when no line items are present. At least one line item is required.

  • Resolution: Provide one or more valid line items (with quantity, unit price, and product identifiers) before retrying.

Transaction Creation Failed

Order creation in Orderful failed while executing the transaction create.

  • Description: Occurs when Orderful does not return a valid response or transaction ID after a create attempt.

  • Resolution: Confirm the Orderful connection settings are correct and reachable and that the transaction data and mappings are valid. Review the integration error logs, then retry. If the problem persists, contact iPaaS.com Product Support for assistance.

Orderful Transaction To iPaaS.com

Invalid Transaction Type

The Transaction Type is not valid.

  • Description: Occurs when the Orderful API call succeeds but the returned transaction is empty or has no valid transaction ID — typically because the transaction type is not supported by this integration.

  • Resolution: Confirm the transaction type is supported, that the provided transaction ID exists in Orderful, and that the correct mapping collection is being used before retrying.

Transaction Polling Error

An error occurred in GetTransactionForPolling.

  • Description: Occurs when an error happens while polling transactions, applying the last-modified date filter, or handling paginated responses.

  • Resolution: Confirm the poll filter and any date settings are valid and retry on the next poll. If the error continues, contact iPaaS.com Product Support for assistance.

Orderful Ship Notice Transaction Tracking Number To iPaaS.com

Transaction Not Found (Purchase Order Number)

Transaction Tracking Number matched with PurchaseOrderNumber but could not locate any transaction associated with the provided PurchaseOrderNumber.

  • Description: Occurs when the Transaction Tracking Match Method is set to PurchaseOrderNumber but no transaction in iPaaS.com has that purchase order number.

  • Resolution: Confirm the purchase order number exists in iPaaS.com and that its transaction was created before the tracking transfer runs.

Purchase Order Reference Is Null

Transaction Tracking Number matched with PurchaseOrderNumber but the PurchaseOrderReference response is null.

  • Description: Occurs when matching by PurchaseOrderNumber but the transaction does not contain a valid purchase order reference.

  • Resolution: Ensure the transaction has a valid purchase order reference before tracking number matching.

Shipment Identification Not Found

Transaction Tracking Number matched with ShipmentIdentification but could not locate any transaction associated with the provided ShipmentIdentification.

  • Description: Occurs when the match method is ShipmentIdentification but no transaction has that shipment identification.

  • Resolution: Confirm a transaction with that shipment identification exists in iPaaS.com.

Shipment Identification Is Null or Empty

Transaction Tracking Number matched with ShipmentIdentification but the shipmentIdentification response is null or empty.

  • Description: Occurs when the match method is ShipmentIdentification but the ship notice (856) does not provide a shipment identification value.

  • Resolution: Ensure the ship notice (856) carries a valid shipment identification before matching.

Fallback Match Found No Transaction

Fallback transaction tracking number matching failed. No tracking was found using either PurchaseOrderNumber or ShipmentIdentification.

  • Description: Occurs when the match method is Fallback but the transaction cannot be found by either purchase order number or shipment identification.

  • Resolution: Confirm the transaction exists and that at least one of purchase order number or shipment identification is correctly populated.

Fallback Failed (Both Values Missing)

Fallback transaction tracking number matching failed. PurchaseOrderReference is null and ShipmentIdentification did not return any transaction tracking.

  • Description: Occurs when the match method is Fallback but both the purchase order reference and the shipment identification are missing or null for the transaction.

  • Resolution: Ensure the transaction has at least one of a valid purchase order reference or a valid shipment identification, and confirm the integration settings are correct for tracking resolution.

Tracking Failed (No Match Method, Purchase Order Not Found)

Transaction tracking number transfer failed. Tracking number was null or empty, and no transaction was found for the PurchaseOrderNumber.

  • Description: Occurs when no Transaction Tracking Match Method is set, so matching falls back to the purchase order number, but no transaction has that purchase order number.

  • Resolution: Confirm the transaction has a valid purchase order number and that it exists in iPaaS.com before retrying.

Tracking Data Not Found

The purchase order number and the shipping method both do not exist for the provided ID.

  • Description: Occurs when retrieving tracking information for a transaction ID that contains neither a valid purchase order number nor shipment/tracking information.

  • Resolution: Confirm the transaction ID exists and contains at least one of a valid purchase order number or a valid shipment identification.

Related Documents

Did this answer your question?