New here? This page is a configuration reference for teams implementing the ShipHero 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 ShipHero integration for iPaaS.com. They are inherent to the current design of the integration and to the capabilities of the ShipHero API, and they apply to all subscribers.
Platform Scope and Tested Versions
Built for: ShipHero, the cloud-based warehouse management system, via its public GraphQL API (see the ShipHero Developer documentation).
API: ShipHero's public GraphQL API at
https://public-api.shiphero.com(a single production environment). ShipHero does not publish a stable, versioned public API namespace; the integration was built and reviewed against ShipHero's documented production API as of July 2026.Integration version: 1.0.0.
Not built for: any warehouse management or fulfillment platform other than ShipHero. This integration connects only to ShipHero. If ShipHero introduces a separate product line or a materially different API in the future, this integration will not automatically support it.
1. Record deletion is not propagated
Deleting a record in one system does not delete the corresponding record in the other. The integration transfers new and updated records; it does not process deletions in either direction.
What this means for you: If you delete a product, order, or other record in iPaaS.com or in ShipHero, remove it in the other system as well if you need the two to match. There is no automatic delete propagation.
2. Bulk initialization on first connect is not supported
The integration does not perform a one-time bulk import of existing data when the subscription is first connected. Synchronization runs on an ongoing basis instead.
What this means for you: Existing records are brought across as they are added or updated, delivered by ShipHero in real time (inventory and shipments) or transferred from iPaaS.com as records change (products, kits, and orders). You can also sync any record on demand from the iPaaS.com Manual Sync page. To bring historical records across at go-live, sync them manually.
3. Kits are rebuilt on each transfer
When a product kit that already has components is transferred to ShipHero, its existing components are removed and the kit is rebuilt from the incoming data.
What this means for you: The kit's composition in ShipHero always reflects the latest transfer from iPaaS.com. Manage a kit's components in iPaaS.com as the source of truth, since each transfer replaces the component set in ShipHero.
4. Order addresses and line items are written after the order header
When an order is created or updated in ShipHero, the header is written first, then its addresses and line items are written in a following step (in batches for large orders).
What this means for you: On a newly transferred order, the addresses and line items appear in ShipHero a moment after the header rather than all at once. This is normal; no action is required.
5. Inventory and shipment transfers require the related records to exist in iPaaS.com first
Inventory and shipment records coming from ShipHero are attached to existing iPaaS.com records: inventory attaches to a product (or variant) matched by SKU and a location matched to the ShipHero warehouse name; a shipment attaches to the order it belongs to and to a shipping method matched by carrier name.
What this means for you: Make sure the matching product or variant, location, order, and shipping method exist in iPaaS.com before the related inventory or shipment is transferred. When a match is missing, the record is not processed and the iPaaS.com error log names what to create — see the ShipHero Error Messages article. Create the missing record, then re-sync.
6. Warehouse pricing and value come from configured custom fields
The warehouse price, value, and customs value written to ShipHero products are sourced from iPaaS.com custom fields named Warehouse Price, Warehouse Value, and Warehouse Custom Value.
What this means for you: Configure these custom fields in iPaaS.com (Subscription Settings → Custom Fields) so the corresponding warehouse values reach ShipHero. When the price custom field is empty, the product's default price is used.
7. Mapped fields are overwritten on each transfer
For records transferred from iPaaS.com to ShipHero (products, variants, kits, and orders), each transfer writes the mapped values to ShipHero, so iPaaS.com is the source of truth for the fields that are mapped. For records captured from ShipHero into iPaaS.com (inventory and shipments), each update refreshes the corresponding iPaaS.com record from ShipHero.
What this means for you: Maintain the mapped fields in the system that is the source of truth for each flow — iPaaS.com for products, kits, and orders; ShipHero for inventory and shipment data — because those values are refreshed on every transfer. If your workflow needs a different behavior, submit a feature request through your iPaaS.com partner channel describing your requirement.
8. Placeholder Values to Replace Before Go-Live
The integration ships with one example value that each subscriber must replace before enabling the affected collections:
Where | Placeholder value | Replace with |
The Warehouse_WarehouseId mapping on the Product, Product Variant, and Product Variant Standalone collections | 128297 | Your own ShipHero warehouse ID |
What this means for you: Until you replace the example warehouse ID with your own, the warehouse details on transferred products would be applied to the wrong warehouse. Update this value on each affected mapping before enabling those collections.
This document covers eight known limitations. For detailed technical documentation of each mapping collection, see the ShipHero mapping collection descriptions in iPaaS.com.