Overview
This article catalogs the error messages the ShipBob integration can produce, grouped by the flow that raises them. For each error it explains what the message means, what causes it, and how to resolve it. Errors appear in the iPaaS.com Dashboard under Integration Monitoring and Error Logs. Some errors come from mapping formulas that subscribers or their MiSP can edit in the iPaaS.com mapping editor; others come from the integration or from ShipBob directly and are resolved by correcting configuration or data rather than by editing a formula. Each entry notes which case applies.
Supported Flows
Connection and Authentication
Add ShipBob Order FROM iPaaS.com
Add ShipBob Order Products FROM iPaaS.com
Add ShipBob Product Inventory TO iPaaS.com
Add ShipBob Product Variant Inventory TO iPaaS.com
Manual Sync Record Identifiers
ShipBob API Errors
Connection and Authentication
Missing authorization value
Unable to complete the ShipBob authorization because a required value is not specified.
Description: Raised during the ShipBob authorization step when one of the required authorization values is missing — the application client id, the application client secret, the requested scope, the authorization code, or the redirect URL. This usually means the connection settings were not fully completed before authorizing.
Resolution: Open the subscription's ShipBob connection settings, confirm every required credential and setting is filled in, and run the authorization step again. This message comes from the integration and is not editable in the mapping editor.
Authorization did not return a token
Unable to complete the ShipBob authorization because the temporary code could not be exchanged for a permanent token.
Description: Raised at the end of the authorization step when ShipBob does not return an access token in exchange for the temporary authorization code. This typically means the credentials are incorrect, the authorization code has expired, or the redirect URL does not match the one registered with ShipBob.
Resolution: Confirm the ShipBob credentials and redirect URL are correct and current, then repeat the authorization step promptly so the temporary code does not expire. If it continues to fail, contact iPaaS.com Support. This message comes from the integration and is not editable in the mapping editor.
Connection validation failed
The ShipBob connection could not be validated.
Description: Raised when the integration establishes the connection but the validation check against ShipBob does not succeed. The message shown is the validation result returned during the check. This usually indicates expired or revoked credentials, or a ShipBob-side availability issue.
Resolution: Re-authorize the ShipBob connection from the subscription's connection settings. If validation still fails, confirm the ShipBob account is active and reachable, then contact iPaaS.com Support. This message comes from the integration and is not editable in the mapping editor.
Add ShipBob Order FROM iPaaS.com
Default shipping method not found
Could not find Default or any Shipping Method for creation of this order.
Description: Raised while creating a ShipBob order when the shipping method formula falls back to the default shipping method but no shipping methods exist in ShipBob to choose from. An order cannot be created without a shipping method.
Resolution: Confirm at least one shipping method exists in ShipBob, or map the order's shipping method to a specific value. This message comes from the integration and is not editable in the mapping editor; the shipping method mapping itself is editable.
Shipping method name not found
Could not find Shipping Method by this name for creation of this order.
Description: Raised while creating a ShipBob order when the shipping method resolved from the order's primary shipping address does not match the name of any shipping method that exists in ShipBob. The order is stopped so the shipping method can be corrected before fulfillment.
Resolution: Confirm the shipping method name sent from iPaaS.com matches a shipping method configured in ShipBob, create the matching shipping method in ShipBob, or adjust the shipping method mapping formula to produce a valid name. The shipping method mapping is editable in the iPaaS.com mapping editor.
Add ShipBob Order Products FROM iPaaS.com
ShipBob product not found
The ShipBob product does not exist and your mappings are configured to raise an error in this condition.
Description: Raised while adding a product line to a ShipBob order when the line cannot be matched to an existing ShipBob product — the integration searches first by the product reference id and then by product name, and neither finds a match. The product line mapping is configured to raise an error in this case rather than silently skip the line.
Resolution: Create the product in ShipBob so the reference id or name matches, correct the reference id or name sent from iPaaS.com, or adjust the product line mapping formula if a different match behavior is wanted. Using the same reference id in ShipBob as the iPaaS.com SKU makes the match succeed directly. This error is produced by an editable mapping formula in the iPaaS.com mapping editor.
Add ShipBob Product Inventory TO iPaaS.com
Product not found for inventory
Cannot create product inventory because the SKU does not exist in iPaaS.com.
Description: Raised while capturing ShipBob product inventory into iPaaS.com when the parent product cannot be resolved from the configured match value (the reference id by default). The inventory record must attach to an existing iPaaS.com product.
Resolution: Confirm the product exists in iPaaS.com and that its identifier matches the value the mapping uses to look it up, or adjust the match method in the mapping formula (reference id, SKU, barcode, GTIN, or UPC) to match how your products are identified. This error is produced by an editable mapping formula in the iPaaS.com mapping editor.
Add ShipBob Product Variant Inventory TO iPaaS.com
Product variant not found for inventory
Cannot create variant inventory because the SKU does not exist in iPaaS.com.
Description: Raised while capturing ShipBob product variant inventory into iPaaS.com when the parent variant cannot be resolved from the configured match value (the reference id by default). The variant inventory record must attach to an existing iPaaS.com product variant.
Resolution: Confirm the product variant exists in iPaaS.com and that its identifier matches the value the mapping uses to look it up, or adjust the match method in the mapping formula to match how your variants are identified. This error is produced by an editable mapping formula in the iPaaS.com mapping editor.
Manual Sync Record Identifiers
Invalid record identifier
The record identifier entered for Manual Sync is not in the expected format.
Description: Raised during a Manual Sync when the identifier entered does not match the format the selected collection expects — for example a whole number where a number is required, or a composite identifier that must contain the correct number of separator characters. The transfer cannot proceed until the identifier is valid.
Resolution: Re-enter the identifier in the format the collection expects. For composite identifiers, include each part separated by the required separator character. Confirm you are using the identifier type described for that collection in its mapping documentation. This message comes from the integration and is not editable in the mapping editor.
ShipBob API Errors
Error returned by ShipBob
An error was returned by ShipBob during a transfer, shown with ShipBob's message and the HTTP status code.
Description: Raised when ShipBob rejects a request during a transfer. The message includes the operation being performed, the detail ShipBob returned, and the HTTP status code (for example, a 400 for a validation problem or a 404 for a record that does not exist). The exact wording depends on the ShipBob response.
Resolution: Read the ShipBob detail and status code in the error to identify the cause — commonly a missing required value, a value ShipBob does not accept, or a referenced record that does not exist in ShipBob. Correct the data or configuration and retry the transfer. If the ShipBob message is unclear or the problem persists, contact iPaaS.com Support. This message reflects ShipBob's response and is not editable in the mapping editor.