An Old Dominion (ODFL) LTL shipment can fail with an error that Old Dominion returns, while other Old Dominion shipments work. Confirm it is a carrier-side problem with a manual test, then work with Old Dominion. No Shipstore setting change is needed.

Problem

Processing an Old Dominion LTL shipment (LTL means less-than-truckload freight) returns an error, even though other Old Dominion shipments processed on the same account the same day. The message comes from Old Dominion's own system, not from Shipstore.

Cause

The error is returned straight from Old Dominion's rating and shipping system. When Shipstore sent a well-formed request and a similar request succeeded on the carrier's side a short time earlier, a new failure points to a carrier-side condition (a short outage, or a data or coverage issue on the account), not a Shipstore problem.

Fix

  1. Process the shipment again once. Short carrier errors often clear on a retry.
  2. Run a manual test shipment for the same lane and account. If the carrier returns the same error on the manual test, the order data is not the cause.
  3. Note any detail that is different from the shipments that worked (for example a long pallet, an extra service, or an unusual destination), so the carrier can look into it.
  4. If the error is confirmed to be on Old Dominion's side, contact Old Dominion with the shipment details and the error text. No Shipstore change is needed.
  5. If you are not sure whether the problem is Old Dominion or Shipstore, email support@shipstore.com with the shipment number and the exact error text.

What you should see

A manual test on the same lane reproduces or clears the error on its own. After the carrier-side condition clears, the shipment processes on a retry with no Shipstore change.

Related articles

  • Old Dominion (ODFL) stopped working: legacy API endpoint retired
  • Estes LTL rates come back on the wrong account or tariff