Shipment tracking details from an Orderful ship notice/manifest (856) can be transferred to iPaaS.com and recorded against the originating transaction. The integration captures the tracking number and shipping method and links them to the transaction the ship notice relates to.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the Orderful transaction ID. Example: 1009.
External ID Format
After a successful sync, iPaaS.com saves the Orderful transaction ID as the external ID on a dedicated external-ID record, which is the primary match for subsequent updates to the same tracking record.
Deleted Record Support
Outbound delete is not supported. Deletions are not propagated to Orderful, and delete mappings are not included in the default templates.
Custom Field Support
Custom fields are not used by this mapping collection.
Mapping Collection Status
Status: Enabled
Trigger Events: Retrieved by polling. Subscribers schedule the poll cadence or trigger an on-demand poll from Dashboard / Integration Monitoring / Events.
Duplicate or Conflicting Mappings
None. This is the only mapping collection that records Orderful ship-notice tracking numbers in iPaaS.com.
Supported Child Collections
None — this is a standalone collection. The tracking record links to its parent transaction through the matched transaction's external ID rather than through a child collection.
System Caveats
Orderful Caveats
Tracking is delivered on a ship notice/manifest (856). The integration matches the ship notice to an existing transaction using the Transaction Tracking Match Method subscription setting (purchase order number by default, shipment identification, or fallback). If the configured match field is missing or no transaction matches, the tracking transfer reports an error.
iPaaS.com Caveats
The parent transaction must already exist in iPaaS.com for the tracking to attach to it.
Integration Flow
A ship notice/manifest (856) is retrieved from Orderful.
The integration identifies the originating transaction using the Transaction Tracking Match Method (purchase order number, shipment identification, or fallback) and matches it by external ID.
The tracking number and shipping method are recorded against the matched transaction.
Mappings
Add/Update Orderful Ship Notice Tracking Number TO iPaaS.com
This mapping collection does not have a mapping filter applied. All ship-notice tracking records are processed.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Matched transaction reference | ParentId | Required. Identifies the transaction the tracking attaches to, matched by the Transaction Tracking Match Method (purchase order number by default, shipment identification, or fallback). |
Field | Carrier identification code (856) | ShippingMethod | Recommended. The carrier identification code from the ship notice. |
Dynamic Formula | Tracking number (856) | TrackingNumber | The shipment tracking number. The default offers several example source values; replace it with the single source that holds your tracking number before go-live. |
Error Handling
See the Orderful Error Messages article for the full catalog. Errors specific to this flow occur when the configured match field (purchase order number or shipment identification) is missing or does not match an existing transaction — for example, "Transaction Tracking Number matched with PurchaseOrderNumber but could not locate any transaction associated with the provided PurchaseOrderNumber." Resolution: confirm the match field is populated on the transaction and that the transaction exists in iPaaS.com.
Testing & Validation
Test Scenarios
Process a ship notice (856) whose purchase order number matches an existing transaction and verify the tracking number and shipping method are recorded on that transaction.
Process a ship notice whose match field does not match any transaction and confirm the expected error is reported.
Switch the Transaction Tracking Match Method to ShipmentIdentification and verify matching behaves accordingly.
Validation Checklist
Tracking attaches to the correct transaction per the configured match method.
The tracking number maps from the intended source value.
An unmatched ship notice produces a clear error rather than silently succeeding.
Related Documents