SolverForge
Search docs Ctrl K

Urban delivery routing

82 Philadelphia deliveries. 10 vehicles. Ordered routes you can inspect.

Delivery routing proves list-variable planning: each vehicle owns an ordered route while capacity, time windows, travel time, retained snapshots, route geometry, and insertion recommendations stay inspectable.

82 Deliveries
10 Vehicles
3 City datasets
4 Constraints
3 / 1 Hard / soft split
Retained Job lifecycle

A delivery plan is not just assignment. Vehicle order matters, time windows matter, capacity matters, and changes need repair workflows that preserve useful route structure instead of throwing the plan away.

The current app exposes the route map, vehicle timeline, delivery timeline, recommendations, score analysis, retained snapshots, and REST endpoints as one planning surface.

Assignment coverage Every delivery must belong to exactly one route.
Vehicle capacity Route load stays within vehicle capacity.
Time windows Deliveries stay inside the promised service window.
Travel time Soft pressure keeps total route travel efficient.
Route geometry Retained snapshots expose the route path and ordered stops.
Insertion recommendations Route repair suggestions can be inspected before action.
Runtime walkthrough Watch ordered routes take shape, then inspect route geometry, insertion recommendations, and the retained-job workflow. Narrated walkthrough (2:49): route ownership, vehicle and delivery timelines, error repair with recommendations, score analysis, and the REST surface of one retained route solve.
Route Overview Route ownership stays visible as both ordered vehicle lists and map geometry.
  1. Vehicle route cards keep stop order and load visible.
  2. The map renders retained route geometry from the same solve snapshot.
Vehicle Timeline Vehicle timelines expose route pressure across the fleet instead of reducing the plan to a table.
  1. Each lane owns an ordered route and capacity context.
  2. Timeline placement makes route density and idle gaps inspectable.
Delivery Timeline Delivery-level timing makes service-window pressure visible across the day.
  1. Delivery rows expose service-window and assignment context.
  2. Time placement shows where the route sequence is under pressure.
Recommendations Recommendations turn retained plans into inspectable repair options instead of opaque reruns.
  1. Insertion options are ranked before a user commits a repair.
  2. The affected delivery remains visible while alternatives are inspected.
Score Analysis Score analysis separates hard route legality from soft travel-time pressure.
  1. Hard constraints show whether the route plan is legal.
  2. Soft travel-time pressure remains visible for tradeoff review.
REST API REST endpoints expose the same retained route workflow for integration.
  1. Retained-job endpoints expose creation, status, snapshots, and analysis.
  2. Route and recommendation APIs keep repair workflows product-embeddable.