Orderful shipping methods can be transferred to iPaaS.com so that the carriers referenced by your transactions and tracking records exist as shipping method records. A shipping method is created or updated whenever a carrier identification code is encountered while an Orderful ship notice/manifest (856) is processed.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the carrier identification code that identifies the shipping method. Example: Ground, Air, or Ocean.
External ID Format
After a successful sync, iPaaS.com saves the carrier identification code as the external ID on a dedicated external-ID record. That record is the primary match for any later update to the same shipping method, so re-syncing the same code updates the existing record rather than creating a duplicate.
Deleted Record Support
Outbound delete is not supported. Deleting a shipping method in iPaaS.com does not remove it in 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: Created or updated automatically while an Orderful ship notice/manifest (856) is processed. There is no separate schedule or webhook for this collection.
Duplicate or Conflicting Mappings
None. This is the only mapping collection that maintains Orderful shipping methods in iPaaS.com.
Supported Child Collections
None — Shipping Method is a leaf collection.
System Caveats
Orderful Caveats
A shipping method is derived from the carrier identification code on the ship notice; Orderful does not expose a dedicated shipping-method record, so the code itself is the identifier.
iPaaS.com Caveats
The shipping method name (the carrier identification code) is recommended so the record is identifiable.
Integration Flow
A carrier identification code is encountered while an Orderful ship notice/manifest (856) is processed.
The integration creates or updates a shipping method in iPaaS.com, using the code as the name and a fixed label ("From Orderful") as the description.
The carrier identification code is saved as the external ID for the shipping method.
Mappings
Add/Update Orderful Shipping Method TO iPaaS.com
This mapping collection does not have a mapping filter applied. All shipping methods encountered during ship notice processing are created or updated.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Field | Carrier identification code (856) | Name | Recommended. The shipping method name, taken from the carrier identification code on the ship notice. Example: Ground, Air, or Ocean. |
Static | "From Orderful" | Description | A fixed label applied to every shipping method this collection creates, so the origin of the record is clear. This is a static value and can be changed. |
Error Handling
See the Orderful Error Messages article for the full catalog. The error specific to this flow:
Could not find any shipping method associated with the provided ID. — Occurs when the provided ID is null, empty, or does not match a shipping method. Resolution: provide a valid carrier identification code and confirm the shipping method exists.
Testing & Validation
Test Scenarios
Process an Orderful ship notice (856) that references a new carrier and verify a shipping method is created in iPaaS.com with the carrier code as its name.
Process a second ship notice referencing the same carrier and verify the existing shipping method is updated rather than duplicated.
Manually sync a shipping method by its carrier identification code and confirm success.
Validation Checklist
A shipping method is created for each new carrier code found on a ship notice.
Re-processing the same carrier code updates the existing shipping method.
The shipping method name matches the carrier identification code.
Related Documents