Why a stop was scheduled outside its time window
The optimiser treats windows as soft by default. Here’s how to make one hard.
Last updated · Routing & dispatch
By default the optimiser treats delivery windows as soft: it prefers them, but will schedule outside one if that saves significant total time. That’s why a stop can show a planned arrival after its window.
Soft vs hard windows
A soft window adds a lateness penalty the optimiser weighs against driving time. A hard window is a constraint — the plan is infeasible rather than late, and the stop is flagged for a dispatcher instead.
Making a window hard
Open the order and edit the delivery window.
Toggle “strict” on the window.
Re-optimise the route; if the stop can’t fit, it moves to the Unplannable list rather than being scheduled late.
NoteService-level defaults (e.g. all B2B orders strict) live in Settings → Order defaults, so you don’t toggle per order.
Was this helpful?
Related articles
Still stuck?
An AI agent answers now; a human can join.