Please let us know how this article can be improved.
Choose all that apply.*
Report a bad link
Out of date (instructions or screenshots)
Missing detail
Other
Troubleshoot errors when importing from WorldShip
Learn how to troubleshoot errors when importing from UPS WorldShip.
Jun 20, 2024
Article ID: SLN19709
Common alerts and their causes
A valid Order ID for this store was not found in the PackageReference5 field- This alert means that the row does not contain a valid Order ID for the store in the WorldShip PackageReference5 field.
Cause: The WorldShip import/export is not set up to map Order ID to PackageReference5.
Solution: Make sure your mappings in WorldShip use Order ID in the PackageReference5 field.
Cause: You are importing a csv file that contains orders for multiple stores.
Cause: You are importing a csv file that contains shipments unrelated to a store.
Valid UPS data appeared in a prior line for order #XXXX- this line will not be applied
Cause: An OrderID has multiple tracking numbers associated with it.
Solution: Update the ship status manually in Order Manager.
Cause: An OrderID has had multiple shipments processed, one or more of which may have been voided within WorldShip.
Solution: Update the ship status and the tracking numbers manually if necessary in Order Manager.
Invalid CSV File - Missing Required Fields in Header Row- The WorldShip-generated yahoo.csv file must include specific column header rows in order to properly import to your store. This alert indicates that your WorldShip export mapping is not configured properly.
Package Reference 5, which must include the full Turbify Order ID. Learn more about Reference Number changes.
