Fixing unassigned shipments in route planning

Overview

Unassigned shipments indicate a constraint, data, or configuration issue. This article walks through a quick checklist to move shipments from “unassigned” onto feasible routes.

Step 1: Check basic shipment details

Verify for each unassigned shipment:

• Service date matches the current planning horizon

• Time window is present and realistic

• Service time is not abnormally long for the stop type

If any field looks wrong, correct it and re‑run planning.

Step 2: Validate location and address

Open the shipment or stop on the map and confirm:

• The pin sits in the expected city and service area

• No obvious state/ZIP/city mismatch

If the pin is clearly off:

• Correct the Location / Customer address

• Adjust the geocode if tools allow

• Refresh affected shipments and re‑run planning

Step 3: Review tags and asset skills

Look for requirement tags such as:

• LFGT, 26FT, HAZ, FRZN, or other specialized tags

Then confirm:

• At least one asset in the planning scope carries matching skills

• Filters in the planning view did not exclude those assets

If no compatible asset exists, either:

• Adjust asset skills (admin), or

• Decide how to handle the shipment operationally (different day/terminal).

Step 4: Check constraints

If shipment details and skills look correct, test constraints:

• Temporarily relax:

  • Route duration limits

  • Capacity thresholds

  • Soft window penalties (where configurable)

Re‑run optimization:

• If the shipment places after relaxing constraints, the original rules are too strict and need adjustment.