Summary: Large batch import files fail when they are too big or when they reuse shipment numbers from orders that already shipped. Keep each file near 5,000 records, and map Order Number to CO Number to re-rate orders that already shipped.
Problem
A batch import file (often several thousand rows) errors on import. Sometimes the same orders already shipped on an earlier date, and re-importing them to pull fresh rates errors on those rows.
Cause
Two separate things cause this. First, very large files strain batch processing; a file of about 9,400 rows failed and processed cleanly once split to under 5,000. Second, Shipstore blocks reusing a shipment number and does not allow back-dating a shipment, so re-importing already-shipped orders under their original Order Number errors.
Fix
- Split any import file larger than about 5,000 records into smaller files and import each one.
- Confirm weight and dimensions are mapped to the package fields, not to the international or LTL commodity fields.
- To re-rate or compare rates on orders that already shipped, change the mapping from Order Number to CO Number so the original order number passes through to the results file instead of being reused.
- Re-run the import. Rows that failed on reused shipment numbers now rate.
What you should see
A file of 5,000 records or fewer completes without the size errors, and a CO Number mapping returns rates with the original order number in the results, with no reused-number errors.
Related articles
- Give each batch record a unique Order Number
- Large batches throw rating errors: use legacy mode