Summary
This article documents the Add/Update ShipBob Order Tracking Number TO iPaaS.com mapping collection. It captures ShipBob shipment tracking details into iPaaS.com. When a shipment is created or updated in ShipBob, the integration reads the shipment and records its tracking number, carrier shipping method, tracking URL, and cost against the matching order in iPaaS.com.
The business outcome is that each iPaaS.com order carries the ShipBob tracking information for its fulfilled shipments, so downstream processes and customer-facing notifications can reference the carrier, the tracking number, and the tracking link without leaving iPaaS.com. This is a capture flow only: it reads tracking from ShipBob into iPaaS.com and never writes changes back to ShipBob.
ID Format
Manual Sync ID. When a subscriber or their MiSP runs a Manual Sync for this collection, the identifier to enter is the ShipBob shipment identifier (for example, 215846).
External ID saved after sync. After a successful transfer, iPaaS.com stores the ShipBob shipment identifier as the external ID on a dedicated external-ID record, following the identifier format {{id}} where {{id}} is the ShipBob shipment identifier. This link routes any subsequent transfer for the same ShipBob shipment to the existing iPaaS.com tracking record rather than creating a duplicate, so repeat transfers update the record in place.
Deleted Record Support
Not supported. This collection adds and updates tracking records. It does not remove tracking records from iPaaS.com, and it does not process shipment deletions from ShipBob. To retire a tracking record, subscribers or their MiSP manage it directly in iPaaS.com.
Custom Field Support
None. This collection maps a fixed set of tracking fields onto the parent order and does not support custom fields.
Status and Trigger Events
The collection is Enabled. It is a polling-only flow, kept in sync by scheduled polling and available on demand through Manual Sync. ShipBob does not push change notifications for this data, so tracking changes are picked up on the next scheduled poll rather than in real time.
The events that lead to a capture are:
A shipment is created in ShipBob.
A shipment is updated in ShipBob, including when ShipBob first assigns a tracking number to it.
A scheduled poll retrieves shipments that are new or changed since the previous poll.
A subscriber or their MiSP runs a Manual Sync for a specific ShipBob shipment.
A shipment is only captured once it has a tracking number. See System Caveats and the Mappings filter below.
Duplicate or Conflicting Collections
None. This is the only collection that captures ShipBob shipment tracking details into iPaaS.com, so there is no competing collection that could write the same tracking record.
Supported Child Collections
None. This collection captures a single tracking record onto its parent order and has no dependent child collections.
System Caveats
Parent order must already exist in iPaaS.com. The tracking record attaches to an existing iPaaS.com order. The related order must already be synced to iPaaS.com before its tracking can be captured. If the order is not yet present, the tracking transfer cannot resolve its parent and does not complete. Ensuring orders are synced first is a reference-data prerequisite for this flow.
Tracking-number filter behavior. A tracking number is assigned by ShipBob when a shipment ships. Until then the shipment is skipped by the collection filter. This is a silent skip, not an error: the shipment is simply not captured until it has a tracking number, at which point a later shipment update or scheduled poll captures it.
Rate limits. ShipBob applies a rate limit of 150 requests per minute. When ShipBob rate-limits a request, the transfer is rescheduled automatically to resume after the limit window resets, and no subscriber action is required.
Integration Flow
A shipment is created or updated in ShipBob, a scheduled poll runs, or a subscriber or their MiSP runs a Manual Sync for a shipment.
The integration reads the shipment from ShipBob and evaluates the collection filter. If the shipment has no tracking number, it is skipped silently and no record is created.
For a shipment that has a tracking number, the integration resolves the parent iPaaS.com order from the ShipBob order behind the shipment. If no matching order exists in iPaaS.com, the transfer cannot resolve its parent and does not complete.
The integration creates or updates a Transaction Tracking Number record on that order, carrying the tracking number, carrier shipping method, tracking URL, and cost. Whether the result is an Add or an Update depends on whether the tracking record is already linked to an iPaaS.com record by its external ID.
Mappings
Add/Update ShipBob Order Tracking Number TO iPaaS.com
iPaaS.com data type: Transaction Tracking Number
Mapping Filter
Tracking != null
Filter Description. This collection processes a shipment only when ShipBob has assigned it a tracking number. A shipment whose tracking value is present passes the filter and is captured. A shipment with no tracking number yet does not pass the filter: it is skipped and no tracking record is created. This is a silent skip, not an error. The shipment is simply not captured until it has a tracking number, at which point a later shipment update or scheduled poll captures it. Subscribers or their MiSP can use Manual Sync to capture a specific shipment once it has a tracking number.
The table below lists the fields written to the iPaaS.com tracking record.
Destination Field | Source | Description |
TrackingNumber | ShipBob shipment tracking number | Records the ShipBob tracking number for the shipment. Required: it is the primary reason this record exists. Because the collection processes only shipments that already have a tracking number, every captured record carries this value. |
ParentId | Resolved iPaaS.com order behind the ShipBob shipment | Resolves the iPaaS.com order that this tracking record attaches to, using the ShipBob order behind the shipment. Required: if a matching order already exists in iPaaS.com, its identifier is returned and the tracking record is linked to it; otherwise no parent is resolved and the transfer does not complete. The related order must already be synced to iPaaS.com. |
ShippingMethod | ShipBob carrier service | Records the carrier shipping method reported by ShipBob for the shipment. Recommended: it captures the carrier service used to fulfill the shipment. |
ShippingMethodDescription | ShipBob shipment tracking URL | Records the shipment's tracking URL from ShipBob, which links directly to the carrier's tracking page. Recommended: it makes the tracking link available on the iPaaS.com order alongside the tracking number. |
Cost | ShipBob shipment invoice amount | Records the shipment cost reported by ShipBob against the tracking record. Recommended: the tracking record is captured without it, but mapping it keeps the shipment cost available alongside the tracking details. |
Error Handling
Errors from this flow appear in the iPaaS.com Dashboard under Integration Monitoring and Error Logs. For the specific messages this integration can produce, their causes, and how subscribers or their MiSP resolve each one, see the ShipBob Error Messages article.
Testing and Validation
Confirm the related order is already synced to iPaaS.com. If it is not, sync the order first so the tracking record has a parent to attach to.
In ShipBob, identify a shipment that has a tracking number, and note its shipment identifier.
On the iPaaS.com Manual Sync page, select the Add/Update ShipBob Order Tracking Number TO iPaaS.com collection and enter the ShipBob shipment identifier.
Run the Manual Sync and confirm the transfer completes without error.
Open the parent order in iPaaS.com and confirm the Transaction Tracking Number record carries the expected tracking number, carrier shipping method, tracking URL, and cost.
To confirm the filter behavior, attempt a Manual Sync for a shipment that has no tracking number yet and confirm it is skipped silently rather than reported as an error.
Additional Notes and Out of Scope
No write-back to ShipBob. This collection captures tracking from ShipBob into iPaaS.com. It does not push tracking changes back to ShipBob.
Tracking is not deleted. This collection adds and updates tracking records. It does not remove tracking records from iPaaS.com.
Capture only after a tracking number exists. Shipments without a tracking number are skipped by the filter rather than captured with an empty value, so a shipment's tracking appears in iPaaS.com only after ShipBob has assigned a tracking number and a later shipment update or poll captures it.
Parent order prerequisite. Capturing a shipment's tracking depends on its related order already existing in iPaaS.com. Subscribers or their MiSP should ensure the order is synced first and validate this behavior in a staging environment before relying on it in production.