This article catalogs the error messages a subscriber or their MiSP may encounter while running the iPaaS.com ShipStation integration. Each entry lists the message or symptom as it appears, the likely cause, and the steps to resolve it. All of these errors surface in the iPaaS.com Dashboard, in Integration Monitoring, and in the Error Logs for the affected transfer. Reviewing the failed transfer in those locations is the starting point for every error below.

The order line item and order address collections transfer as part of the order, and the shipping method collection surfaces only the connection and authentication errors described below, so any errors from those collections appear under the flows listed above.

Message: OrderDate Is Required

Description: An order was sent to ShipStation without an order date. ShipStation requires every order to carry a date, so the integration stops the transfer before it reaches ShipStation when the mapped Order Date value is empty.

Resolution: Confirm the source record has an order date and that the Order Date field is mapped on the Add/Update ShipStation Order FROM iPaaS.com collection. If the source can produce orders with no date, populate the Order Date mapping with a value that is always present, then re-run the transfer. Subscribers should validate the behavior in a staging environment before relying on it in production.

Message: A validation or invalid-request error returned by ShipStation, identifying the missing or invalid order data.

Description: ShipStation accepted the request but rejected the order because the order data was incomplete or invalid. The most common cause is a missing or malformed ship-to address, but it can also be triggered by other required order data that the source did not supply. The text comes from ShipStation and describes which part of the order it could not accept.

Resolution: Open the failed transfer in Integration Monitoring and read the message ShipStation returned to identify the field at fault. Confirm the order has a complete ship-to address (at minimum a country, and ideally name, street, city, region code, and postal code) and that the address mappings on the Order Address collection are populated. Correct the source record or the mapping, then re-run the transfer. If the message points to data the subscriber cannot supply or correct, contact iPaaS.com Support at support@ipaas.com.

Message: Shipment Id {id} not found

Description: A Manual Sync was requested for a specific shipment, but ShipStation has no shipment with that identifier. This usually happens when the identifier was mistyped, the shipment was voided or removed in ShipStation, or the shipment had not yet been created when the sync ran.

Resolution: Confirm the shipment exists in ShipStation and that the identifier used for the Manual Sync is correct. If the shipment is valid and present, allow the regular inbound polling to pick it up, or re-run the Manual Sync with the correct identifier. If the shipment exists in ShipStation but still cannot be retrieved, contact iPaaS.com Support at support@ipaas.com.

Message: A transfer failure indicating the shipment's related order could not be matched in iPaaS.com.

Description: Inbound shipments attach to an order that must already exist in iPaaS.com. The integration does not automatically create a missing parent record, so a shipment whose order has not yet been transferred into iPaaS.com cannot be matched and the transfer fails.

Resolution: Make sure the related order has been transferred into iPaaS.com before the shipment is processed. Re-run the order transfer first, then re-run the shipment transfer or allow the next inbound poll to retry. If the order is present in iPaaS.com but the shipment still cannot be matched, contact iPaaS.com Support at support@ipaas.com.

Message: An authentication or authorization failure returned by ShipStation (for example, an unauthorized response).

Description: ShipStation rejected the integration's credentials. This is caused by an incorrect API Key or API Secret, or by an API Url that does not point at ShipStation. Because the connection test does not currently verify credentials, an authentication problem is usually first seen when a real transfer fails rather than when the connection is saved.

Resolution: In the ShipStation subscription settings, confirm the API Url, API Key, and API Secret are entered correctly with no extra spaces, and that the API credentials are still active in ShipStation. After correcting them, verify the fix by running a test transfer rather than relying on the connection test alone. If the credentials are confirmed correct and transfers still fail to authenticate, contact iPaaS.com Support at support@ipaas.com.

Message: A transfer failure whose message references internal field, type, or processing details rather than a clear subscriber action.

Description: Some failures surface a message that describes the integration's internal handling instead of a subscriber-correctable cause. These are not something a subscriber or their MiSP can resolve by changing source data or mappings.

Resolution: Capture the message and the affected transfer from Integration Monitoring and contact iPaaS.com Support at support@ipaas.com so the underlying cause can be investigated.