Skip to main content

Shippo Integration Known Limitations

Scope, design decisions and settings to confirm before go-live for the iPaaS.com Shippo integration, with what to do about each.

New here? This page is a configuration reference for teams implementing the Shippo integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.

Introduction

These are the known limitations of the Shippo integration. They are inherent to the current design of the integration and the capabilities of the Shippo platform and its API, and they apply to all subscribers at the time this documentation was written. For each limitation, this page describes how the integration behaves and what this means for you.

Platform Scope and Tested Versions

Item

Value

Remote platform

Shippo, the multi-carrier shipping platform, through the Shippo API

Host

Shippo API

Shippo versions its API by date and applies your account's default version to any call that doesn't name one (Shippo: API versions). The integration names no version, so it follows your account's default version. It was built against Shippo's documented production API as of 2026-11-17

Integration version

1.0.0

Last tested end to end

2026-11-17, in Shippo test mode

Data handled

Orders with their ship-to address and line items (FROM iPaaS.com); labels as tracking records, and carrier services as shipping methods (TO iPaaS.com)

Not built for:

  • Shippo's own store connections. Orders that reach Shippo from a store connected to Shippo directly (rather than through this integration) are not linked to iPaaS.com orders (see Orders that reach Shippo another way, below).

  • More than one Shippo account per subscription (see One Shippo account per subscription, below).

If Shippo releases a new API version with backwards-incompatible changes and your account is upgraded to it, this integration will not automatically support those changes.


1. An order is sent to Shippo once

Shippo's API can create, list and read orders, but it can't update or cancel them (Shippo API: Orders). So the integration sends each order to Shippo once. Later changes to the order in iPaaS.com, such as a new address or different items, are not sent. An order cancelled, refunded or returned in iPaaS.com after it was sent stays open in Shippo, and the integration reports it with SHPO-BIZL-1004 and never buys a label for it. An order that is already cancelled, refunded or returned when it first reaches the integration is not sent (SHPO-BIZL-1005). Because the status is how the integration tells a cancelled order from any other, an order with no TransactionStatus is not sent either (SHPO-VALD-1011).

What this means for you:

  • Keep the order collection's TransactionStatus mapping (the default template maps it from the transaction's status).

  • Send orders when they are ready to ship, by narrowing the order collection's filter.

  • Make changes to an order already in Shippo in Shippo itself.

  • For a cancelled order, cancel it in Shippo (and refund its label there if one was bought), then dismiss the error in Dashboard / Integration Monitoring / Error Logs.

  • With Automatic Label Purchase on, a later update of an order can still buy its label once, if none was bought yet.


2. Every order needs a weight, in one unit

Shippo refuses an order with no weight, even when no label is bought, so an order whose lines carry no weight never reaches Shippo. The integration adds up the line weights as plain numbers: lines in different units (for example 1 lb and 8 oz) give a wrong total, and the integration recognizes lb, oz, g and kg (and their spelled-out names), sending any other unit as pounds.

What this means for you:

  • Map a weight on every order line, or on the order.

  • Keep all weights in one unit, and map WeightUnit on the order collection when that unit isn't pounds.

  • Validate your weights in a staging subscription before relying on them in production.


3. Orders already in iPaaS.com are not sent at setup

Orders go to Shippo when iPaaS.com creates or updates them. There is no order initialization, so orders that were in iPaaS.com before the integration was turned on are not sent. Shipping methods can be initialized (see Carrier services from active carrier accounts, below).

What this means for you:

  • Such an order is sent the next time it changes in iPaaS.com, or when you resend it with a Manual Sync.


4. Orders Shippo already has are linked only with Remap and Link

An order Shippo already has, with the same order number and placed-at time, is a collision. The integration finds the existing Shippo order and returns it to iPaaS.com; the order collection's Collision Handling Method decides what happens:

  • Remap and Link links the order, its ship-to and its lines to the existing Shippo order.

  • Update and Link links the order, but not its ship-to or lines.

  • Update and No Link creates no second Shippo order and links nothing.

  • Error reports a data collision and creates nothing in Shippo.

Lines are linked in the order they appear. If the existing Shippo order lists its items in a different order, or has more or fewer lines, a line can be linked to another item's line. If Shippo has two or more orders with the same order number and placed-at time, the order isn't sent (SHPO-BIZL-1001): Shippo doesn't require unique order numbers, and the integration never guesses which one is the order.

What this means for you:

  • Set Collision Handling Method to Remap and Link on Add/Update Shippo Order FROM iPaaS.com.

  • When an existing Shippo order was created another way, check that its lines are in the same order as the iPaaS.com order's lines before relying on the line links.

  • For duplicate orders, delete or renumber the extra orders in Shippo; iPaaS.com retries the transfer.


5. Orders that reach Shippo another way are not linked

The integration links only the orders it sends. Orders that reach Shippo from a store connected to Shippo directly are not linked to iPaaS.com orders, and their labels don't come TO iPaaS.com through this integration.

What this means for you:

  • Leave those orders out of the order collection's filter, so Shippo doesn't get them twice.


6. One ship-to and one ship-from per order

A Shippo order has one ship-to address, so the order is sent with its primary shipping address only. The ship-from address is read from eight Transaction custom fields on the order, which you create in iPaaS.com and fill with your warehouse's address (see Placeholder Values to Replace Before Go-Live, below). Without a complete ship-from, an automatic label purchase is refused (SHPO-VALD-1007).

What this means for you:

  • Split orders that ship to several addresses before they reach iPaaS.com, or ship the extra addresses from Shippo.

  • Fill the ship-from custom fields from your source system or with a formula, or point the ship-from mappings at another source.


7. Orders are sent in USD unless Currency is mapped

iPaaS.com orders carry no currency for Shippo, so an order is sent in US dollars unless the order collection maps Currency.

What this means for you:

  • Map Currency on the order collection when you sell in another currency.


8. Shippo records can't be deleted through the integration

Shippo's API has no delete for orders, labels or carrier services. A delete sent to the integration is refused (SHPO-BIZL-1015).

What this means for you:

  • Use the Add/Update sync type on the Shippo collections.

  • Make the change in Shippo by hand if needed, then dismiss the error.


9. Supported directions only

The integration sends orders FROM iPaaS.com, and labels and carrier services TO iPaaS.com. A collection or scope for another direction or type, such as shipping methods FROM iPaaS.com or an order poll, is refused (SHPO-BIZL-1014).

What this means for you:

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

  • If your workflow needs another direction, submit a feature request to your iPaaS.com partner channel describing it; input like this informs future enhancement releases.


10. Shippo's rate limits

Shippo limits how many calls an account can make each minute, per endpoint and method, with lower limits for test tokens than for live ones; a call over the limit is answered with HTTP 429 (Shippo: Rate limits). A burst of many orders can reach the limit.

What this means for you:

  • Nothing: a transfer that reaches the limit is held and resumes automatically (SHPO-EXTN-1002).


11. International labels are bought in Shippo

International labels need a customs declaration, which iPaaS.com orders don't carry and the integration doesn't send. An order that ships to another country is created in Shippo, but its label is never bought automatically (SHPO-BIZL-1008). The integration compares the ship-to country with the ship-from country as they are mapped, so a country sent as a name (such as United States) rather than a two-letter code can make a domestic order look international.

What this means for you:

  • Add the customs declaration to the order in Shippo and buy the label there.

  • Keep the ship-to country as a two-letter code; the default template converts it.


12. Automatic label purchase: one parcel, a mapped carrier service

Each label is bought with one parcel: the Default Parcel template and the order's total weight, because iPaaS.com orders carry no package dimensions. A label is bought only for an order whose shipping method has a row in the Shippo Label Service translation, because the integration can't guess which carrier service you want. An update of an order already in Shippo that is older than Days of Label History never buys a label automatically, so that turning on Automatic Label Purchase doesn't buy labels for old orders; a first send is always bought.

What this means for you:

  • Buy multi-package shipments in Shippo.

  • Add a row to the Shippo Label Service translation for each shipping method your orders use.

  • Buy labels for older orders in Shippo, or raise Days of Label History and resend the order.


13. An unanswered label purchase is reported as unknown

In the rare case that Shippo doesn't answer a label purchase and no label shows up on the order afterwards, the outcome is reported as unknown (SHPO-EXTN-1005). Shippo has no way to make a purchase request safe to repeat, so the integration checks the order three times before reporting.

What this means for you:

  • Check the order in Shippo before buying a label by hand.

  • Resending the order is safe: the integration buys only when Shippo shows no label on the order.


14. A refunded label keeps its tracking record

iPaaS.com tracking records have no active flag an integration can set, so a refunded label's tracking record is kept, never deleted. Its Shippo Status custom field reads REFUNDED.

What this means for you:

  • Use Shippo Status in the filters of the systems that receive tracking from iPaaS.com, to leave out refunded labels.


15. Tracking status changes arrive by webhook

Shippo sends a tracking update to iPaaS.com through the track_updated webhook when the carrier's tracking status changes. The scheduled label check (label/poll) reads labels by date and catches new and changed labels; it is not relied on to catch a tracking status change missed by the webhook. The label check looks back Days of Label History (default 7).

What this means for you:

  • Keep the Shippo webhooks registered (see the installation instructions).

  • Raise Days of Label History before the first check if you want older labels brought TO iPaaS.com.


16. Labels bought outside the integration

A label is brought TO iPaaS.com only when its Shippo order is one this integration sent: the label is matched to the iPaaS.com order through that Shippo order's link. So a label bought separately for such an order, for example by hand in the Shippo web app, arrives through the webhooks or the scheduled label check (label/poll) and lands on that order. A label for an order that reached Shippo another way is skipped, with an information note in the transfer's activity log (SHPO-BIZL-1011).

What this means for you:

  • Buy labels by hand only for orders this integration sent, if you want their tracking in iPaaS.com.

  • Validate labels bought by hand in the Shippo web app in a staging subscription before relying on them in production.


17. A deleted shipping method must exist again before its labels arrive

A tracking record names its shipping method. When a label's shipping method was deleted in iPaaS.com, the tracking transfer is refused until the shipping method exists again; the integration doesn't recreate it first.

What this means for you:

  • Don't delete shipping methods that labels still use. To bring one back, run the shipping method initialization or transfer the carrier service again, then let iPaaS.com retry the tracking transfer.


18. Tracking: label link, cost currency and standard fields

  • The link to the label file is not brought TO iPaaS.com by default, because Shippo's label links expire and anyone holding one can download the label.

  • The postage cost on a tracking record has no currency: it is in your Shippo account's currency.

  • iPaaS.com replaces a tracking record's standard fields on every update and keeps its custom fields. Removing the Cost or ShippingMethodDescription mapping clears that field the next time Shippo changes the label (a refund or a carrier update).

  • A tracking record written TO iPaaS.com doesn't by itself reach your other systems: each receives it only through its own tracking flow FROM iPaaS.com.

What this means for you:

  • Map LabelUrl to a custom field on the tracking collection if another system prints labels from iPaaS.com.

  • Keep the Cost and ShippingMethodDescription mappings. To stop bringing a value, map it to a custom field instead, then remove the standard mapping.

  • Set up a tracking flow FROM iPaaS.com for each system that should receive tracking.


19. Carrier services from active carrier accounts

Carrier services are read from the carrier accounts that are active in Shippo. Services of a carrier account turned off in Shippo are not read, and existing shipping methods for them are left as they are. A shipping method field the collection doesn't map keeps its value in iPaaS.com when the service is transferred again.

What this means for you:

  • Turn on a carrier account in Shippo before initializing shipping methods for it.


20. One Shippo account per subscription

A subscription holds one Shippo API token, so it connects to one Shippo account. The API Url must be Shippo's own https address: a proxy or any other host is refused (SHPO-VALD-1001), because the API token is sent with every call. A wrong API Token or API Url shows on the transfer only as "Unable to connect to subscription with id N"; the reason, with its code (for example SHPO-AUTH-1001), is in the company's logs at the same time.

What this means for you:


Placeholder Values to Replace Before Go-Live

Two kinds of values need replacing before go-live: the ship-from address, which the default mappings read from custom fields you create and fill (see the Shippo Installation Instructions), and the one example row in the label service translation. Mapped values that still start with REPLACE are refused (SHPO-VALD-1003).

  • Placeholders in Add/Update Shippo Order FROM iPaaS.com

  • Placeholders in Shippo Order Ship-To Address FROM iPaaS.com

Placeholders in Add/Update Shippo Order FROM iPaaS.com

Where

Placeholder value

Replace with

Shippo Ship From Name (Transaction custom field)

none until you create it

Your warehouse, store or company name, for example Main Warehouse

Shippo Ship From Street

none until you create it

Your ship-from street, for example 100 Example St

Shippo Ship From City

none until you create it

Your ship-from city, for example Springfield

Shippo Ship From State

none until you create it

Your state or province as its postal abbreviation, for example IL

Shippo Ship From Postal Code

none until you create it

Your ship-from postal code, for example 62701

Shippo Ship From Country

none until you create it

A two-letter country code, for example US

Shippo Ship From Phone

none until you create it

A phone number (USPS requires one), for example 5555550100

Shippo Ship From Email

none until you create it

An email address (USPS requires one), for example shipping@example.com

Placeholders in Shippo Order Ship-To Address FROM iPaaS.com

Where

Placeholder value

Replace with

Shippo Label Service translation

One example row: REPLACE with your iPaaS.com shipping method name → usps|usps_priority

One row per iPaaS.com shipping method your orders use, each giving Shippo's carrier and service token, for example Standard Ground → usps|usps_ground_advantage


This page covers 20 known limitations of the Shippo integration, plus the placeholder values to replace before go-live. For the full behavior of each mapping collection, see its mapping collection description and its mapping documentation.

Related Documents

Did this answer your question?