In a batch rate analysis, some UPS rows show 0 for Estimated Days In Transit. This happens because UPS drops the transit-time value when too many rate requests arrive at once. Re-run the batch in Legacy Mode to slow the requests down so UPS returns the transit days.

Problem

You run a batch rate analysis across services (for example FedEx Ground, FedEx Home Delivery, and UPS Ground). Some rows show Estimated Days In Transit as 0. Only the UPS rows show 0; some UPS rows have a value and some do not.

Cause

UPS limits how many rate requests it will fully answer in a short time. When your batch sends a lot of requests quickly, UPS still returns the rate but leaves out the Days In Transit value, which shows as 0. This is UPS slowing down its own rating responses, not a Shipstore math error, which is why some rows have transit days and some do not. FedEx rows are not affected.

Fix

  1. Re-run the batch rate in Legacy Mode. Legacy Mode sends the rate requests more slowly, so UPS returns the transit days.
  2. Expect the batch to take longer in Legacy Mode. That is the trade-off for full transit-day data.
  3. If some rows still show 0 in Legacy Mode, make the batch smaller or split it so fewer UPS rate requests go out at once.

What you should see

The re-run batch shows real Estimated Days In Transit for the UPS rows that used to show 0.

Related articles

  • Large batches throw rating errors: use legacy mode