Skip to main content

Shippo Error Messages

Catalog of the errors the iPaaS.com Shippo integration reports, with what causes each one and how to resolve it.

Overview

This article catalogs the errors subscribers can meet with the Shippo integration, grouped by flow. Each error carries a stable code you can search for on this page, followed by the message, what causes it, and how to resolve it. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who set up and manages your iPaaS.com integration, including its mappings, its connection settings and credentials, and any reconciliation between Shippo and iPaaS.com.

Each code below comes from the Shippo integration and has three segments, such as SHPO-VALD-1001. Errors iPaaS.com itself records, with two-segment codes such as VALD-1036, are explained in Understanding iPaaS.com API Error Codes. In the messages below, words in braces are filled in when the error happens, for example {order number}. A few codes are information notes the integration writes to the transfer's activity log rather than errors; each says so.

When a transfer fails, iPaaS.com retries it automatically while its error is active, so fix the cause first; the next retry, or a re-send of the record, then succeeds. Dismiss an active error only when the record should not be retried: dismissing it stops the retry.

Situations the integration handles without an error are described in the Shippo Integration Known Limitations and in the mapping documentation for each data type.

Supported Flows

  • Connection and settings

  • Order FROM iPaaS.com

  • Tracking TO iPaaS.com

  • Webhook scopes

  • Any flow

Error Collection

Connection and settings

The integration checks the connection at the start of a transfer. When the check fails, the transfer's error reads only "Unable to connect to subscription with id N", and the integration's coded reason is in Logs at the error's time.

Shippo refused the API Token

SHPO-AUTH-1001 - Shippo refused the API Token (HTTP 401): {Shippo's reason}. Create a token in Shippo (API Configuration > Developer keys) and paste it into the subscription's API Token setting; iPaaS.com retries the transfer.

SHPO-AUTH-1001 - {action} failed (HTTP 401): {Shippo's reason}. Create a token in Shippo (API Configuration > Developer keys) and paste it into the subscription's API Token setting; iPaaS.com retries the transfer.

  • Description: The API Token is wrong, was revoked, or belongs to another Shippo account.

  • Resolution: Create a current API token in the Shippo API portal (API Configuration, then Developer keys) and paste it into the API Token setting. A test token begins with shippo_test_, a live token with shippo_live_. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

API Token setting is empty

SHPO-AUTH-1002 - The API Token setting is empty. Create a token in Shippo (API Configuration > Developer keys) and paste it into the subscription's API Token setting.

  • Description: The subscription's API Token setting has no value.

  • Resolution: Paste a Shippo API token from the Shippo API portal (API Configuration, then Developer keys) into the API Token setting. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

Shippo refused the call for this token's account

SHPO-AUTZ-1001 - {action} failed (HTTP 403): {Shippo's reason}. In Shippo, check that the account is active and allowed this action; iPaaS.com retries the transfer.

SHPO-AUTZ-1001 - Shippo accepted the API Token but refused this account the connection check (HTTP 403): {Shippo's reason}. In Shippo, check that the account is active and allowed this action; iPaaS.com retries the transfer.

  • Description: The token is valid but its Shippo account isn't allowed this call (for example, a restricted or unverified account).

  • Resolution: In Shippo, check the account's status and permissions, or paste a token from an account that has access into API Token, then resend the record. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

API Url setting isn't Shippo's https API address

SHPO-VALD-1001 - The API Url setting isn't Shippo's https API address, so the API Token isn't sent to it. Set API Url to https://api.goshippo.com.

  • Description: The API Url setting isn't an https address on Shippo's own host (goshippo.com), or carries a user name. The value is never quoted, in case a token was pasted there.

  • Resolution: Set API Url to https://api.goshippo.com, or leave it blank. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

A setting holds a Shippo API token

SHPO-VALD-1010 - The {setting} setting holds a Shippo API token. Put the token only in API Token, and set {setting} to its own value (see the installation instructions). The value isn't shown here.

  • Description: A Shippo API token was pasted into API Url, Default Parcel or Label File Type. The value is never quoted, because the error log is readable by anyone with access to the subscription's errors.

  • Resolution: Clear that setting and give it its own value (API Url: https://api.goshippo.com); keep the token only in API Token. If the token was a live token, consider replacing it in Shippo. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

Shippo could not be reached

SHPO-EXTN-1003 - Shippo could not be reached at {API Url}: {network reason}. Check the API Url setting (leave it blank for Shippo's default) and Shippo's status page; iPaaS.com retries the transfer.

  • Description: A network problem, a Shippo outage, or a wrong API Url.

  • Resolution: Check the API Url setting (blank uses https://api.goshippo.com) and Shippo's status page; iPaaS.com retries the transfer. At connection time the transfer's error may read only "Unable to connect to subscription with id N"; this code and its reason are in the company's Logs at the error's time.

Order FROM iPaaS.com

Errors for orders sent to Shippo, and for automatic label purchase.

The order has no Order Number

SHPO-VALD-1002 - The order has no Order Number; map one in the Shippo order collection.

  • Description: The OrderNumber mapping is missing, or the order's transaction number is empty.

  • Resolution: Map OrderNumber on the order collection (the default template maps the transaction number), then resend the order.

A mapping still holds the template's placeholder

SHPO-VALD-1003 - "{field}" still holds the template's placeholder. Replace it in the Shippo order collection, then send the order again.

  • Description: A mapped value still reads "REPLACE with ..." from the default template.

  • Resolution: Replace the placeholder in the named mapping with your own value, then resend the order.

The order has no usable shipping address

SHPO-VALD-1004 - Order {number} has no primary shipping address. Shippo needs a ship-to: flag the order's shipping address as primary shipping, or keep such orders out with the order collection's filter.

SHPO-VALD-1004 - Order {number}'s shipping address has no {Street, Name, City, Country}; Shippo requires them. Add them to the order's shipping address in iPaaS.com; iPaaS.com retries the transfer.

  • Description: No address is flagged primary shipping (the default filter keeps such orders out; a subscriber's own filter may not), or that address lacks a street, name, city or country.

  • Resolution: Mark one address as the primary shipping address and fill in its name, street, city and country, then resend. Check the address collection's mappings.

The order has no Placed At

SHPO-VALD-1005 - Order {number} has no Placed At, so the integration can't tell whether Shippo already has the order (a retry could create a second one). Map Placed At in the order collection (the template maps the transaction's created date); iPaaS.com retries the transfer.

  • Description: The PlacedAt mapping was removed or its source is empty. Without it the integration can't tell whether Shippo already has the order.

  • Resolution: Map PlacedAt on the order collection (the default template maps the transaction's created date), then resend the order.

No Label Service for the order's shipping method

SHPO-VALD-1006 - Order {number} has no Label Service for its shipping method "{method}", so no label was bought; the order is in Shippo. Add "{method}" to the Shippo Label Service translation with a Shippo carrier service such as usps|usps_priority, or buy this label in Shippo.

SHPO-VALD-1006 - Order {number}'s Label Service "{value}" isn't a Shippo carrier service, so no label was bought; the order is in Shippo. Write it as carrier|service, for example usps|usps_priority (each Shipping Method's description shows its value), or buy this label in Shippo.

SHPO-VALD-1006 - Order {number} has no shipping method and no Label Service (carrier|servicelevel), so no label was bought; the order is in Shippo. Give the order a shipping method, or buy this label in Shippo.

  • Description: The order's shipping method has no row in the Shippo Label Service translation, the row's value isn't written as carrier|service, or the order has no shipping method at all.

  • Resolution: Add the shipping method to the Shippo Label Service translation with a Shippo carrier service (carrier|service, e.g. usps|usps_priority), then resend the order. The order is already in Shippo.

The order has no ship-from address

SHPO-VALD-1007 - Order {number} has no ship-from address, so no label was bought; the order is in Shippo. Fill the Shippo Ship From custom fields on the order (or map the ship-from fields in the order collection), or buy this label in Shippo.

  • Description: Automatic purchase needs a complete ship-from address, which the order collection reads from the eight Shippo Ship From custom fields on the order.

  • Resolution: Fill the eight Shippo Ship From custom fields on the order (name, street, city, state, postal code, country, and for USPS a phone and email), or point the order collection's ship-from mappings at another source, then resend the order. The order is already in Shippo.

Default Parcel isn't set

SHPO-VALD-1008 - Order {number} was sent to Shippo, but no Default Parcel is set, so no label was bought. Set the Default Parcel setting (a Shippo carrier parcel template, e.g. USPS_SmallFlatRateBox); iPaaS.com retries the transfer, or buy this label in Shippo.

  • Description: Automatic Label Purchase is on but the Default Parcel setting is empty.

  • Resolution: Fill in Default Parcel with a Shippo carrier parcel template such as USPS_SmallFlatRateBox, then resend the order. The order is already in Shippo.

The order has no weight

SHPO-VALD-1009 - Order {number} has no weight (order or lines), so no label was bought; the order is in Shippo. Map Weight on the order or its lines, or buy this label in Shippo.

  • Description: Neither the order nor its lines carry a weight.

  • Resolution: Map Weight on the order lines (the default template maps line weight) or on the order, then resend the order.

The order has no Transaction Status

SHPO-VALD-1011 - Order {number} has no Transaction Status, so the integration can't tell whether it was cancelled, refunded or returned, and nothing was sent to Shippo. Map Transaction Status from the transaction's Status in the order collection (the template maps it); iPaaS.com retries the transfer.

  • Description: The TransactionStatus mapping was removed from the order collection, or the transaction has no status. Without it a cancelled order would look like any other, and could be sent or have its label bought.

  • Resolution: Map TransactionStatus from the transaction's status on the order collection (the default template has this mapping). iPaaS.com retries the transfer.

No carrier account offers the service

SHPO-NFND-1002 - No active Shippo carrier account offers {carrier|service}. Check that value in the Shippo Label Service translation, or turn the carrier account on in Shippo, then resend the order. The order is in Shippo.

  • Description: The translated carrier service isn't offered by any active carrier account in Shippo.

  • Resolution: Check the Shippo Label Service translation value, or turn the carrier account on in Shippo, then resend the order.

Shippo has two or more orders with this number

SHPO-BIZL-1001 - Shippo has {n} orders numbered {number} placed at the same time ({ids}), so the integration can't tell which one is this order and sent nothing. In Shippo, delete or renumber the extra orders, then iPaaS.com retries the transfer.

  • Description: Shippo doesn't require unique order numbers, and more than one Shippo order has this order's number and placed-at time. The integration never guesses which one to link.

  • Resolution: In Shippo, delete or renumber the extra orders. iPaaS.com retries the transfer and then hands the single match to the order collection's collision handling.

Shippo already has this order: handed to collision handling

SHPO-BIZL-1002 - Shippo already has order {number} ({id}); returned to iPaaS.com's collision handling, which decides whether to link it.

  • Description: An order with the same number and placed-at time is already in Shippo (for example, sent before a lost answer, or entered in Shippo). The integration returns it to iPaaS.com instead of creating a second one. This is an information note in the transfer's activity log, not an error.

  • Resolution: Set the order collection's Collision Handling Method to Remap and Link: iPaaS.com then links the order, its ship-to and its lines to the Shippo order. Update and Link links the order but not its ship-to or lines, and Update and No Link links nothing. With Error, iPaaS.com reports a data collision and nothing is created in Shippo.

Order update not sent

SHPO-BIZL-1003 - Shippo orders can't be changed after they are sent; order {number} ({id}) was not updated. Change it in Shippo if needed.

  • Description: Shippo has no way to update or cancel an order through its API. This is an information note in the transfer's activity log, not an error.

  • Resolution: Change or cancel the order in Shippo by hand if needed.

Order cancelled, refunded or returned after it was sent

SHPO-BIZL-1004 - Order {number} was {cancelled/refunded/returned} in iPaaS.com after it was sent to Shippo (Shippo order {id}), and Shippo orders can't be cancelled through its API, so nothing was changed in Shippo. In Shippo, cancel the order and refund its label if one was bought, then dismiss this error.

  • Description: The order's status in iPaaS.com is Cancelled, Refunded or Returned, and the order is already in Shippo. No label is bought for it.

  • Resolution: Cancel the order in Shippo and refund its label there if one was bought, then dismiss the error. iPaaS.com retries it until it is dismissed.

Order already cancelled, refunded or returned: not sent

SHPO-BIZL-1005 - Order {number} is {cancelled/refunded/returned} in iPaaS.com, so it was not sent to Shippo and no label was bought. Nothing needs doing in Shippo: dismiss this error.

  • Description: The order reached the integration for the first time with status Cancelled, Refunded or Returned.

  • Resolution: Nothing in Shippo. Dismiss the error. iPaaS.com retries it until it is dismissed.

Live label purchase not allowed

SHPO-BIZL-1006 - The API Token isn't a Shippo test token, and Allow Live Label Purchases is off, so no label was bought (live labels cost real postage). Turn Allow Live Label Purchases on to buy live labels.

  • Description: Automatic Label Purchase is on with a live token, but Allow Live Label Purchases is off. Live labels cost real postage.

  • Resolution: Turn Allow Live Label Purchases on to buy live labels, or turn Automatic Label Purchase off. The order is in Shippo either way.

Development build never buys live

SHPO-BIZL-1007 - This development build never buys labels with a token that isn't a Shippo test token. Nothing was bought. Contact iPaaS.com Support: a released integration doesn't show this.

  • Description: A development build of the integration was run with a live token.

  • Resolution: Contact iPaaS.com Support at support@ipaas.com with the error's reference id: a released integration doesn't show this.

International labels aren't bought automatically

SHPO-BIZL-1008 - Order {number} ships to another country; international labels aren't bought automatically. The order is in Shippo: add customs there and buy the label.

  • Description: The ship-to country differs from the ship-from country; international labels need customs information.

  • Resolution: Add customs in Shippo and buy the label there. The order is already in Shippo.

Old order not bought

SHPO-BIZL-1009 - order {number} is older than Days of Label History ({n}); no label was bought automatically. Buy it in Shippo if it's still needed.

  • Description: An update arrived for an order already in Shippo that was placed longer ago than Days of Label History, for example after turning Automatic Label Purchase on. A first send is always bought. This is an information note in the transfer's activity log, not an error.

  • Resolution: Buy the label in Shippo, or raise Days of Label History and resend the order.

The order already has a label

SHPO-BIZL-1010 - order {number} already has label {id} in Shippo; nothing was bought.

  • Description: A label (bought, queued or waiting) is already on the Shippo order. This is an information note in the transfer's activity log, not an error.

  • Resolution: Nothing: a label is never bought twice.

Shippo refused the label

SHPO-EXTN-1004 - Shippo refused the label for order {number}: {Shippo's reason}. The order is in Shippo: fix what Shippo names (address, parcel or service) and iPaaS.com retries, or buy this label in Shippo.

SHPO-EXTN-1004 - Shippo couldn't create the label for order {number} (status ERROR): {messages}. The order is in Shippo: fix what Shippo names (address, parcel or service) and iPaaS.com retries, or buy this label in Shippo.

  • Description: Shippo rejected the purchase, for example a missing sender email or phone, an invalid address or an unknown parcel.

  • Resolution: Fix what Shippo's reason names, then resend the order, or buy the label in Shippo. Nothing was charged.

Label purchase outcome unknown

SHPO-EXTN-1005 - Shippo didn't answer the label purchase for order {number}, and no label is on the order yet. Check the order in Shippo before buying by hand.

  • Description: Shippo timed out or failed while buying, and three checks afterwards found no label.

  • Resolution: Check the order in Shippo before buying by hand. Resending is safe: the integration buys only when Shippo shows no label on the order.

Tracking TO iPaaS.com

Errors for labels brought TO iPaaS.com as tracking records.

The label's carrier service isn't a shipping method in iPaaS.com

SHPO-NFND-1003 - Shipping Method {carrier|service} isn't in iPaaS.com and couldn't be transferred: {reason}. Run the Shipping Method initialization, then resend label {id}.

SHPO-NFND-1003 - Shipping Method {carrier|service} isn't in iPaaS.com and couldn't be transferred ({reason}). Check the Shipping Method collection, then resend label {id}.

SHPO-NFND-1003 - Shipping Method {carrier|service} still isn't in iPaaS.com: the Shipping Method collection's filter may leave it out, or its carrier account is no longer active in Shippo. Let the Shipping Method collection take it, then resend label {id}.

  • Description: A tracking record must name an iPaaS.com shipping method, and the label's carrier service couldn't be added: the transfer failed, the Shipping Method collection's filter left it out, or its carrier account is no longer active.

  • Resolution: Let the Shipping Method collection take that carrier service (check its filter), or turn the carrier account on in Shippo; run the shipping method initialization; then resend the label.

Label for an order this integration didn't send

SHPO-BIZL-1011 - label {id} belongs to no order this integration sent (Shippo order {id}); the Tracking collection's filter skips it.

  • Description: The label was bought in Shippo for an order that reached Shippo another way. This is an information note in the transfer's activity log, not an error.

  • Resolution: Nothing.

Failed label attempt not transferred

SHPO-BIZL-1012 - {id} is a failed label attempt (status ERROR), not a label; nothing to transfer.

  • Description: Shippo records a failed purchase as a transaction with status ERROR. This is an information note in the transfer's activity log, not an error.

  • Resolution: Nothing.

Tracking after a purchase couldn't be queued

SHPO-INTL-1002 - label {id}'s tracking transfer failed ({reason}); the webhook or the scheduled label check brings it TO iPaaS.com.

  • Description: The tracking transfer started right after a purchase failed to queue. It is written to the transfer's activity log as a warning.

  • Resolution: Nothing: the track_updated webhook or the scheduled label check (label/poll) brings the tracking TO iPaaS.com.

Webhook scopes

Errors when a Shippo scope is set active or inactive under Inbound Data Flows.

Shippo refused the webhook

SHPO-EXTN-1006 - Shippo refused the {event} webhook: {Shippo's reason}. Check the API Token, then set the {event} scope inactive and active again under Inbound Data Flows; the scheduled label check keeps tracking flowing meanwhile.

  • Description: Shippo didn't accept the webhook registration.

  • Resolution: Read Shippo's reason in the message, check the API Token, then set the webhook scope inactive and active again under Inbound Data Flows. The scheduled label check keeps tracking flowing meanwhile.

No webhook address from iPaaS.com

SHPO-INTL-1003 - iPaaS.com didn't supply this subscription's webhook address or key; save the subscription again, then set the webhook scope active under Inbound Data Flows.

  • Description: The subscription has no webhook address or key yet.

  • Resolution: Save the subscription, then set the webhook scope inactive and active again under Inbound Data Flows.

Any flow

Errors any transfer can meet.

A Shippo object wasn't found

SHPO-NFND-1001 - {action} failed (HTTP 404): {Shippo's reason}. Check that the object still exists in the Shippo account the API Token belongs to; if it was deleted, dismiss this error.

  • Description: The Shippo order, label or webhook no longer exists, or belongs to another Shippo account (for example after switching between a test and a live token).

  • Resolution: Check that the object still exists in the Shippo account the API Token belongs to. If it was deleted, or the token was changed between test and live, dismiss the error.

A collection for a data type the integration doesn't support

SHPO-BIZL-1013 - The Shippo integration doesn't support this data type ({type}). It supports Transaction, Transaction Address and Transaction Line FROM iPaaS.com, and Transaction Tracking and Shipping Method TO iPaaS.com. Remove or turn off the mapping collection.

  • Description: A mapping collection was added for a data type or direction the integration has no support for.

  • Resolution: Remove or turn off that mapping collection.

A direction the integration doesn't send

SHPO-BIZL-1014 - {record} {direction} only, so this transfer was not run and nothing was changed in Shippo. Remove or turn off the mapping collection or scope that asks for it, then dismiss this error.

  • Description: A mapping collection or scope asks for a supported data type in the other direction (for example Shipping Method or Transaction Tracking FROM iPaaS.com, or orders polled from Shippo), or for an order's address or line on its own.

  • Resolution: Remove or turn off that mapping collection or scope, then dismiss the error.

Shippo has no delete for the record

SHPO-BIZL-1015 - Shippo has no delete for {records}, so nothing was changed in Shippo. {What to do in Shippo} Then dismiss this error.

  • Description: A delete reached the integration (for example a Delete sync type on a collection). Shippo's API can't delete or cancel orders, labels or carrier services.

  • Resolution: Make the change by hand in Shippo if it's needed (cancel the order and refund its label, refund a label, or turn a carrier service off), then dismiss the error. Use the Add/Update sync type on Shippo collections.

A Shippo call failed

SHPO-EXTN-1001 - {action} failed (HTTP {status}): {Shippo's reason}. iPaaS.com retries the transfer; if it keeps failing, check Shippo's status page, then contact your MiSP, then iPaaS.com Support, with this error.

SHPO-EXTN-1001 - Shippo answered the connection check with HTTP {status}: {Shippo's reason}. iPaaS.com retries the transfer; if it keeps failing, check Shippo's status page, then contact your MiSP, then iPaaS.com Support, with this error.

SHPO-EXTN-1001 - A Shippo call failed during {action}: {reason}. iPaaS.com retries the transfer; if it keeps failing, check Shippo's status page, then contact your MiSP, then iPaaS.com Support, with this error.

  • Description: Shippo refused or failed a request for a reason other than the token, a missing object or the rate limit. HTTP 0 means Shippo didn't answer: a timeout or a network failure.

  • Resolution: Read Shippo's reason in the message. iPaaS.com retries a failed transfer; a 4xx needs the data or setting it names fixed, then resend the record.

Shippo's rate limit was reached

SHPO-EXTN-1002 - Shippo's rate limit was reached; iPaaS.com retries after one minute.

  • Description: Too many Shippo calls in a minute (Shippo allows fewer calls with a test token than a live one). The transfer is returned to iPaaS.com as over quota and held until Shippo's limit resets. It is written to the transfer's activity log as a warning.

  • Resolution: Nothing: the transfer is retried. If it keeps happening, send fewer orders at once.

An iPaaS.com API call failed

SHPO-INTL-1001 - iPaaS.com could not complete {action} (HTTP {n}). iPaaS.com retries the transfer; if it keeps failing, contact your MiSP, then iPaaS.com Support, with this error's reference id.

  • Description: A call the integration makes to iPaaS.com's own API (a lookup or an external id) failed. The response is kept in the technical log only.

  • Resolution: Nothing at first: iPaaS.com retries the transfer. If it keeps failing, contact your MiSP, then iPaaS.com Support at support@ipaas.com, with the error's reference id.

Internal problem

SHPO-INTL-1004 - The Shippo integration hit an internal problem ({what}). Contact your MiSP, then iPaaS.com Support, with this error's reference id.

  • Description: A guard only a defect in the integration can reach.

  • Resolution: Contact your MiSP, then iPaaS.com Support at support@ipaas.com, with the error's reference id.

Related Documents

Did this answer your question?