New here? This page is a configuration reference for teams implementing the ShipHawk 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.
These are the known limitations of the ShipHawk integration. They are inherent to the current design of the integration and the capabilities of the ShipHawk API, and they apply to all subscribers at the time this documentation was written.
Platform Scope and Tested Versions
Platform: ShipHawk, integrated through the ShipHawk REST API (the
/api/v4/endpoints at your ShipHawk API URL, provided by ShipHawk in the form https://[tenant].tms.myshiphawk.com).Tested: the integration was validated against the ShipHawk production API endpoints as of July 2026. ShipHawk does not publish a dated, versioned API scheme beyond the
/api/v4/namespace.Not built for: this integration targets ShipHawk. If ShipHawk introduces a separate product line or a materially different API version in the future, this integration will not automatically support it.
Shipment updates are not transferred
Only the creation of a shipment in ShipHawk transfers tracking information to iPaaS.com. ShipHawk sends a webhook event for newly created shipments only, not for later changes to an existing shipment.
What this means for you: tracking details captured at shipment creation are synced; if a shipment is later edited in ShipHawk, those changes are not sent to iPaaS.com. Treat the initial tracking transfer as the record of the shipment.
Deleted records are not propagated
Deleting an order in iPaaS.com, or a shipment in ShipHawk, is not propagated to the other system.
What this means for you: remove records directly in each system where needed; deletions do not sync automatically.
Carriers must exist as iPaaS.com Shipping Methods
A shipment's carrier must match a Shipping Method that already exists in iPaaS.com, and the match is case-sensitive.
What this means for you: create a Shipping Method in iPaaS.com for each ShipHawk carrier you use, matching the carrier name and its letter casing. If a carrier does not match, the shipment transfer fails until the Shipping Method is created. Subscribers or their MiSP can adjust the collection filter to compare values case-insensitively.
Orders must exist before shipment tracking transfers
Shipment tracking is attached to the transaction that represents the order. The order must already exist in iPaaS.com, with its external ID linking it to ShipHawk, before the shipment tracking can transfer.
What this means for you: transfer orders to iPaaS.com first; a shipment whose order is not yet in iPaaS.com is skipped.
Line items rely on consistent SKUs
Order line items are matched by external ID, and by SKU when no external ID is present. Missing or inconsistent SKUs can produce duplicate line items in ShipHawk.
What this means for you: keep SKUs consistent between iPaaS.com and ShipHawk so line items match correctly on updates.
ShipHawk packaging defaults to one package per unit
Until packing rules or package definitions are configured in ShipHawk, ShipHawk's default packaging splits a shipment into one package per unit.
What this means for you: configure packing rules in ShipHawk if you need units grouped into packages differently.
Line item dimension and currency fields use custom fields
The line item Currency, Length, Width, and Height values, and the address Phone value, come from iPaaS.com custom fields that must exist in the subscription for those values to be sent.
What this means for you: confirm these custom fields are present in your iPaaS.com subscription if you rely on those values.
Bulk initialization is not supported
The integration does not support initialization (bulk import of existing records on first connect); mappings are configured during setup.
What this means for you: to load a large set of existing records, use the bulk sync using Postman approach.
This document covers 8 limitations. For detailed technical documentation of each mapping, see the ShipHawk Mapping Collections.