Introduction to ShipStation
ShipStation is a shipping and order fulfillment platform that empowers merchants to manage label creation, carrier selection, and shipment tracking across multiple sales channels from one interface.
Used by SMB to mid-market eCommerce sellers managing orders from multiple storefronts and marketplaces
Popular with operations teams that want to streamline label printing, carrier rate comparison, and tracking in one tool
Connecting ShipStation to iPaaS.com enables order and shipment data to flow automatically between your Ecommerce, POS, and ERP systems, keeping fulfillment status and inventory accurate without manual updates
API Version Support
The integration works with both generations of the ShipStation API. Orders are sent to ShipStation as shipments through the ShipStation API V2, authenticated with a V2 API Access Key, and shipments and carrier services are read from ShipStation through the ShipStation API V1, authenticated with your ShipStation API Key and API Secret. See the ShipStation Connections and Settings and ShipStation API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and ShipStation, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to ShipStation
← iPaaS.com reads the data from ShipStation
↔ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from ShipStation when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | ShipStation | Allow Initialization? |
Order | → | Shipment | |
Order Tracking Number | ← | Shipment | |
Shipping Method | ← | Carrier Service | ✔️ |
Orders move from iPaaS.com to ShipStation as shipments, with their line items and destination addresses, and shipment tracking is captured from ShipStation. Shipping methods are captured from ShipStation as carrier services.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.4.
Version | Release Notes |
1.0.4 (current) | Orders are now sent to ShipStation as shipments through the ShipStation API V2, one shipment per destination address, so an order whose line items ship to several addresses can be split into separate, individually numbered shipments when the Enable Multi Address Shipment setting is on. Shipments arrive as Pending shipments for your team to complete in ShipStation, with the Ship From Location, store, currency, amounts, and weights pre-filled from custom fields your order source populates: ShipStation Ship From Location, ShipStation Store, Currency, Package Weight, Package Weight Unit, and Weight Unit, plus ShipToAddressExternalId for multi-address orders. New subscription settings: V2 API Base URL, V2 API Access Key, and Enable Multi Address Shipment. New mapping functions resolve a Ship From Location, a store, a carrier, or a carrier service by name. See Deprecated in 1.0.4 below for the order fields this release no longer sends. |
1.0.3 | Platform compatibility update to the current iPaaS.com integration framework. |
1.0.2 | Every error the integration can record in the iPaaS.com logs carries a stable, searchable code with its cause and resolution, and the ShipStation mapping functions are documented for use in your own formulas. |
1.0.1 | Orders transfer reliably regardless of the identifier values ShipStation returns, including orders without a ShipStation customer profile, and the outbound order flow was verified end to end against ShipStation. |
1.0.0 | Initial release: synchronize orders from iPaaS.com to ShipStation with their line items and addresses, and capture shipment tracking and carrier services from ShipStation into iPaaS.com. |
Deprecated in 1.0.4
Because orders are now created as ShipStation shipments rather than ShipStation orders, the following mappings from earlier releases no longer send data to ShipStation. Subscribers upgrading an existing subscription should not rely on them, and should move any values they still need to the equivalent field on the Add/Update ShipStation Shipment Address FROM iPaaS.com collection where one exists:
Order collection: Order Key, Order Date, Order Status (and its status translation), Customer Id, Order Total, Amount Paid, Tax Amount, Shipping Amount, Gift, Advanced Options, and International Contents. The order number and customer email are still used, as the shipment number and the ship-to email. Amount paid, shipping paid, and tax paid are now mapped on the shipment address collection.
Order Line Item collection: Line Item Key and the earlier Weight, Unit Price, Tax Amount, and line weight value and unit mappings. The line item's weight and its unit, unit price, and tax amount are now sent through the collection's Shipment_Item_ mappings, and the SKU, name, and quantity are still used.
Order Address collection: the earlier Add/Update ShipStation Order Address FROM iPaaS.com collection is replaced by the shipment address collection. Its label request fields, external shipment id, shipment number, and create-sales-order fields are no longer honored; the integration derives the shipment number and external shipment id itself and always creates the sales order.
Line item custom field: the destination custom field is now named ShipToAddressExternalId and carries the order source's address identifier; the earlier ShipToTransactionAddressId custom field name is no longer read.
Automatic label purchase is not performed. Labels are purchased in ShipStation.
Features by Release
The capabilities below are listed by the version in which they shipped. For the current behavior and any limitations of a given feature, see the linked reference articles and the ShipStation Integration Known Limitations article.
Version 1.0.4 (current) — Multi-address shipments through the ShipStation API V2
Orders as shipments: each iPaaS.com order is created in ShipStation as a Pending shipment with its line items, destination address, Ship From Location, store, amounts, and package weight.
Multi-address shipments: with Enable Multi Address Shipment on, an order whose line items name different destination addresses is split into one shipment per address, numbered "(1 of N)", "(2 of N)", and so on.
Shipment values from your order data: custom fields on the order supply each shipment's Ship From Location, store, currency, and package weight and unit, so every order carries its own values; an empty package weight is entered per package in ShipStation.
Name-based ShipStation lookups: mapping functions resolve a Ship From Location, a store, a carrier, or a carrier service from its name.
Version 1.0.2 — Coded error messages and mapping functions
Coded error messages: every error the integration can record in the iPaaS.com error logs carries a stable, searchable code, its cause, and a subscriber-actionable resolution.
Mapping functions reference: the integration's formula functions documented for use in Dynamic Formula mappings and filters.
Version 1.0.0 — Initial release
Order synchronization: orders sent from iPaaS.com to ShipStation with their line items and addresses.
Shipment tracking: shipment tracking numbers captured from ShipStation.
Shipping methods: carrier services captured from ShipStation.