Skip to main content
If some lanes fail to import, BidRight shows an error summary after the import run. Each error identifies the affected lane and explains why it could not be loaded. The goal is to standardize lane data so it is consistent across all bids and customers. Standardized data makes it much easier to search lanes, compare bids, and relate new bids to historical results.
A lane is missing required waypoint data for origin or destination.How to fix:
  • Check your source spreadsheet for blank origin or destination cells.
  • Verify your waypoint columns are mapped to the correct BidRight fields.
  • Fill in missing values and re-import.
Some zip codes were exported as numbers, which strips leading zeros (for example, 02108 becomes 2108).How to fix:
  • Format origin and destination zip columns as text in your spreadsheet.
  • Restore all leading zeros so each zip code is exactly 5 digits.
  • Save and re-import.
A zip code in the file is malformed or does not exist.How to fix:
  • Confirm each zip code is a valid 5-digit US zip.
  • Correct typos, placeholders, and non-numeric values.
  • If the customer provided bad zip data, request a corrected file before importing.
BidRight does not import duplicate lanes. Duplicates must be fixed in the source spreadsheet first.How to fix:
  • Find rows with the same lane definition (origin, destination, and lane attributes).
  • Remove or consolidate duplicates in the spreadsheet.
  • Re-import after the duplicate rows are cleaned up.
Trailer type is required for import. Lanes without trailer type cannot be standardized correctly.How to fix:
  • Populate trailer type for every lane in the source file.
  • Use consistent trailer values across rows.
  • Re-import once all lanes have trailer type values.
Some trailer values in the source file do not match BidRight’s standard trailer types.How to fix:
  • Map unrecognized values to the closest valid BidRight trailer type.
  • Standardize naming in the spreadsheet before re-importing.
  • If needed, assign custom customer terms to supported trailer types so future imports map cleanly.
Lane type is required to normalize data and compare similar lanes across bids.How to fix:
  • Fill in lane type for each lane in the source file.
  • Use consistent lane type terminology across the full file.
  • Re-import after all missing lane type values are completed.
After fixing source data, re-import the updated file from the bid record. Always verify final lane count, trailer types, and lane types after each import.
For a refresher on the full import process, see Import a Bid File.