Why an order went unassignedCopy link
The optimizer does not break the constraints you set. When an order cannot be served within them, it is left off the routes instead, counted in the red UNASSIGNED metric, and listed in a red Unassigned panel pinned above the route cards, each order with its reason.
This tutorial plan overloads one van, so the panel shows real reasons:
Reading the panelCopy link
Each unassigned order shows one of these reason kinds:
- A solver diagnosis. A short explanation of what blocked the order, for example that the shift ran out of time. Press (MORE) to expand it: proposed solutions and, where relevant, a Conflicts with: list naming the orders competing for the same scarce resource.
- A placement suggestion. A green line like "Best if assigned to route 2 after stop 7", or "Best if the order is assigned to a new route" naming a vehicle. This is the position where forcing it in by hand costs the least.
- "Removed from planned route manually." You dragged it out of the route. It stays out until you drag it back or re-optimize.
- Alternatives. Orders in the same alternative group are mutually exclusive, so when one is served the rest read "Alternative not chosen, served another order in group X". These sit in their own Alternatives (not chosen) section.
- Transfer pair messages. Pickup and delivery transfers ride together, so when one half cannot be placed the reason names the pair. See Pickup & delivery transfers.
On very large plans the panel does not detail every entry: after the detailed entries it collapses the rest into a line like "+12 more not detailed (mostly shift duration)", which names the dominant cause.
Who gets dropped: priorityCopy link
When not everything fits, the solver drops the cheapest-to-lose orders first. That is what Priority (1 to 1000, default 1) controls: higher priority orders are kept, lower priority ones go unassigned first. In the tutorial plan above, the two VIP orders at priority 100 always make the route while ordinary stops fall off.
Priority is a tie-breaker under scarcity, not a guarantee. If an order is physically impossible to serve (its window is outside every shift, no vehicle carries its required tag), no priority value will place it.
Fixing each causeCopy link
| The reason points at | What to try |
|---|---|
| Not enough time (shift ends, window missed) | Lengthen the shift, add a vehicle or raise its Available count, shorten service durations, widen the order's time window |
| Not enough capacity | Raise vehicle capacity, add a vehicle, allow reloads (Max reloads), check the order's load is realistic |
| Tags / restrictions | Give a vehicle the required tag, or drop the tag from the order. See Tags: vehicle-order compatibility |
| No drivable road connection | The pin is mislocated (water, pedestrian zone). Fix the address or drag the pin. See Fix unrecognized or mislocated addresses |
| Release time | The goods are not at the depot early enough for any feasible trip; move the release time or the window |
| Max time in vehicle | No route reaches the order inside its shelf life. Raise Max time in vehicle, raise Max ride overtime on a linked (pickup & delivery) order, or add a vehicle so it is delivered sooner. On a vehicle with driver breaks, a break between pickup and delivery counts toward the same ride time: allow breaks at more stops, or relax the rule. See Max time in vehicle |
| Product segregation | The order's Load class cannot share a route with what the candidate vehicles already carry. Add a vehicle for the conflicting class, or drop the pair from the vehicles' Do not mix load classes groups. See Product segregation |
| Inapplicable field | The order sets a field that does not apply to its kind, so it cannot be planned. Max ride overtime is the case to check: it belongs only to linked (pickup & delivery) orders. Clear the value, or link the order into a transfer |
| Alternative not chosen | Nothing to fix unless the wrong member won; then raise the preferred order's priority |
After changing inputs, press Optimize again: unassignment is recomputed from scratch on every run.
To act on the green suggestion, drag the order out of the Unassigned panel onto that route position. The engine recalculates the route, and any rule you break is reported as a red problem line. See Edit routes by hand.
Next stepCopy link
Forced assignments and hand edits are flagged rather than refused. The flags are explained in Problems and warnings, explained.