See what the Orderful integration can do →
Overview
This document catalogs the error messages you may encounter in iPaaS.com when synchronizing data with Orderful, grouped by mapping collection flow. Each entry carries a stable error code you can search for on this page, the message text as it appears in the log, what causes it, and how to resolve it.
Some resolutions reference your Managed Integration Service Provider (MiSP) — the partner who configured and maintains your Orderful integration, including its mappings, EDI settings, and transaction tracking configuration. Where a resolution goes beyond what you can adjust yourself, your MiSP is the first point of contact.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
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
Orderful API and Connection
Error Collection
Orderful Shipping Method To iPaaS.com
Shipping method not found
ORDF-NFND-1010 - 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 in Orderful before retrying.
Orderful Transaction From iPaaS.com
Transaction address missing
ORDF-VALD-1001 - 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. If the source record has an address but it is not reaching Orderful, your MiSP can review the address mapping.
Transaction line items missing
ORDF-VALD-1002 - 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. If the source record has line items but they are not reaching Orderful, your MiSP can review the line-item mapping.
Transaction creation failed
ORDF-EXTN-1002 - Order creation in Orderful failed while executing the TransactionCreate method.
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, then review the integration error logs and retry. If the failure persists on valid data, your MiSP can review the transaction mapping and the Orderful trading-partner configuration.
Orderful Transaction To iPaaS.com
Invalid transaction type
ORDF-BIZL-1001 - 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. If you are unsure which transaction types are supported, your MiSP can confirm the configured EDI document types.
Transaction polling error
ORDF-EXTN-1003 - An error occurred in GetTransactionForPolling: {reason}
Description: Occurs when an error happens while polling transactions, applying the last-modified date filter, or handling paginated responses. The reason returned is shown in the message.
Resolution: Confirm the poll filter and any date settings are valid and retry on the next poll. If the error continues, your MiSP can review the poll configuration against the Orderful API.
Orderful Ship Notice Transaction Tracking Number To iPaaS.com
Transaction not found by purchase order number
ORDF-NFND-1001 - Transaction Tracking Number Matched with PurchaseOrderNumber clause but couldn't locate any transactions associated with the provided PurchaseOrderNumber : {purchase order number}
Description: The Transaction Tracking Match Method is set to PurchaseOrderNumber, but no transaction in iPaaS.com has the purchase order number shown.
Resolution: Confirm the purchase order number shown exists in iPaaS.com and that its transaction was created before the tracking transfer runs.
Purchase order reference is null
ORDF-NFND-1002 - Transaction Tracking Number transfer failed. Tracking Number was null or empty, so matching was redirected to the PurchaseOrderNumber clause, but the PurchaseOrderReference response was null.
Description: Matching fell back to 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. Your MiSP can confirm which field supplies the purchase order reference for your EDI setup.
Transaction not found by shipment identification
ORDF-NFND-1003 - Transaction Tracking Number Matched with ShipmentIdentification clause but couldn't locate any transactions associated with the provided ShipmentIdentification : {shipment identification}
Description: The match method is ShipmentIdentification, but no transaction has the shipment identification shown.
Resolution: Confirm a transaction with the shipment identification shown exists in iPaaS.com.
Shipment identification is null or empty
ORDF-NFND-1004 - Transaction Tracking Number Matched with ShipmentIdentification but the response of shipmentIdentification is null or empty.
Description: 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. Your MiSP can confirm which segment supplies the shipment identification.
Fallback match found no transaction
ORDF-NFND-1005 - Fallback Transaction Tracking Number matching failed. No Tracking was found using either PurchaseOrderNumber or ShipmentIdentification as search filters.
Description: 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 with both values missing
ORDF-NFND-1006 - Fallback Transaction Tracking Number matching failed. PurchaseOrderReference is null and ShipmentIdentification did not return any Transaction Tracking.
Description: 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. If the values should be present, your MiSP can confirm the tracking-resolution settings.
Tracking failed with no match method and purchase order not found
ORDF-NFND-1007 - Transaction Tracking Number Transfer failed. Tracking Number was null or empty, and no Transaction was found for PurchaseOrderNumber '{purchase order number}'.
Description: No Transaction Tracking Match Method is set, so matching falls back to the purchase order number, but no transaction has the purchase order number shown.
Resolution: Confirm the transaction has a valid purchase order number and that it exists in iPaaS.com before retrying.
Purchase order reference null with no match method
ORDF-NFND-1008 - Tracking Number was null or empty so matching was redirected to the PurchaseOrderNumber clause, but the PurchaseOrderReference response is null.
Description: No Transaction Tracking Match Method is set and the tracking number was empty, so matching fell back to the purchase order number, but the transaction has no valid purchase order reference.
Resolution: Ensure the transaction has a valid purchase order reference, or configure a Transaction Tracking Match Method. Your MiSP can confirm the tracking configuration.
Tracking data not found
ORDF-NFND-1009 - The Purchase order number and shipping method both do not exist for the provided ID {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 shown exists and contains at least one of a valid purchase order number or a valid shipment identification.
Orderful API and Connection
Orderful returned an error
ORDF-EXTN-1001 - {Orderful API error detail}
Description: A call to the Orderful API failed. The integration surfaces Orderful's own error detail (the message the Orderful API returned, or the HTTP status and response body) in the Error Logs entry.
Resolution: Read the returned detail. Frequent causes are invalid credentials or an unreachable endpoint — confirm the Orderful Connections and Settings are correct. Correct the reported cause and retry. If the detail points to the request contents, your MiSP can review the mapping that produced it.
Connection could not be established
ORDF-AUTH-1001 - {Orderful connection validation error}
Description: The integration could not validate the connection to Orderful during setup. The message shows the reason Orderful returned (for example, invalid credentials or an unreachable endpoint).
Resolution: Verify the Orderful API credentials and endpoint in Connections and Settings, then retry the connection. If the values are correct and validation still fails, your MiSP can confirm the credentials in Orderful.