Every stop.
Every constraint.

Route planning for the team behind the deliveries.

Try the planning desk
Project
Forma Labs · Concept study
For
Small & medium 2PL / 3PL operations
Scope
Operational design · Interactive routing simulation

Independent concept with fictional data. This is a working planning simulation, not a client deployment or a claim of measured savings.

Forma Labs / Interactive planning study

Dispatch desk.

Simulation · 12 shipments · 1 depot
Available courier + vehicle

Standard morning plan. Fictional customer, courier, load and distance data.

Assigned shipments12 / 12
Vehicles in use3 / 3
Modelled distance91.7 km
Needs review0 shipments

Delivery area

Schematic · fictional locations
WEST DISTRICTEAST DISTRICTSOUTH DISTRICT 123456789101112 DDepot

Lines connect stops directly. Distances and ETAs are simulated, without road or traffic data.

Courier assignments

Select to inspect

V01 / Dimas / Box van

The load changes at every stop.

Depot load: 770 kg · 5.50 m³
08:00 departure · 11:24 depot return · 4 min waiting

Planned delivery sequence · windows include complete service
Stop / clientWindowArrival / serviceUnload / returnOnboard after stop
1Coffee roasteryS02 · Client B08:30–10:1508:28Service 08:30–08:45−90 / +20 kg15 min at stop700 kg5.00 m³
2Community kitchenS04 · Client B09:00–11:0008:58Service 09:00–09:20−130 / +0 kg20 min at stop570 kg4.10 m³
3Hotel suppliesS08 · Client A09:30–11:3009:41Service 09:41–10:01−210 / +40 kg20 min at stop400 kg2.80 m³
4North marketS01 · Client A09:00–10:3010:12Service 10:12–10:27−160 / +0 kg15 min at stop240 kg1.60 m³
5West groceryS06 · Client B09:30–11:3010:39Service 10:39–10:59−180 / +30 kg20 min at stop90 kg0.70 m³

All shipments fit this plan

Within the demo’s modelled constraints

Review the route sequence, available courier and vehicle load before approving a real dispatch.

How this simulation plans a route

A deterministic insertion heuristic considers orders with the fewest compatible vehicle types first, then the earliest delivery deadlines and chooses the feasible insertion with the least added distance. It checks weight, volume, vehicle compatibility, client allocation, stop limits, complete service windows and return within the courier’s shift. Early arrivals wait. Deliveries unload before return goods are collected at the same stop.

The model uses direct distances at a fixed 24 km/h, one depot, one morning trip per vehicle and pre-paired couriers. It does not guarantee a globally optimal plan; an unassigned order may become feasible with a different overall sequence. No live traffic, navigation, dispatch or customer messages are connected. Shifts: Dimas and Sari 08:00–13:00; Raka 08:00–12:00. Stop limits: 7, 6 and 5 respectively. Dedicated mode reserves V01/V03 for client A and V02 for client B; shared mode permits mixed loads. These are sample contract policies, not universal rules for 2PL or 3PL.

A short route can still
be the wrong route.

A van can be close to the next customer and still be the wrong choice: the receiving window has closed, the remaining cargo takes too much space, or the courier cannot return before their shift ends.

This concept explores a daily workspace for small and medium transport and logistics teams. The dispatcher needs to see which orders fit, who will carry them, what happens to the load and what still needs a decision.

The demo keeps the day deliberately small: 12 shipments, two fictional clients, three different vehicles and one depot. It makes the planning rules inspectable. It is not a benchmark for production fleet size.

Transport capacity.
A wider logistics service.

Know what the fleet can commit to.

A carrier plans transport against vehicle availability, customer appointments and contract commitments. This concept’s dedicated scenario reserves vehicles for specific clients.

Focus: shipment acceptance, suitable vehicles, driver assignment, dispatch manifests and transport costs.

Coordinate several clients in one operation.

A provider coordinates transport alongside services such as warehousing and fulfilment. This concept’s shared scenario allows different clients’ compatible shipments on the same vehicle.

Focus: client-level SLAs, warehouse readiness, consolidation, delivery evidence and billing separation.

Dedicated and shared capacity are configurable contract policies. Either business can use them; the labels do not impose a universal operating rule.

From the order book
to the last handoff.

A route planner needs the operational records around it. The study covers the full workflow, with the implemented simulation clearly identified below.

01

Orders & receiving windows

Record customer, delivery address, coordinates, client, priority, receiving window and service duration. Flag incomplete addresses or impossible windows before planning.

Demo: receiving windows, waiting and service duration.

02

Weight, volume & loading

Keep kilograms, cubic metres and vehicle compatibility on each shipment. Check depot departure load and load after every delivery or return pickup. Prepare a manifest and loading order.

Demo: kg / m³ capacity and returns at delivery stops.

03

Fleet & courier allocation

Match an available courier to a suitable vehicle. Account for shift hours, stop limits and the return to depot. Production planning also needs driver qualifications, breaks, vehicle downtime and working-hour policies.

Demo: paired couriers, mixed fleet, shifts and stop limits.

04

Client contracts & consolidation

A transport operator may reserve capacity for a customer; a logistics provider may consolidate shipments from several clients. Keep client ownership, service commitments and billing references on every order.

Demo: dedicated client allocation or shared capacity.

05

Dispatch & delivery execution

A dispatcher reviews the plan and approves a version. A courier receives a stop list with goods, contact details and handling notes. Record arrival, proof of delivery, discrepancies and failed attempts.

Product scope: approval, courier app, proof and status history.

06

Exceptions & replanning

Keep unassigned shipments visible. Explain which checks prevented placement, then let the dispatcher adjust capacity or appointments. During execution, freeze completed stops before planning remaining work again.

Demo: unassigned queue and scenario replanning.

07

Costs & service reporting

Separate planned distance and time from measured actuals. Track fuel assumptions, tolls, driver costs, carrier rates, cost per delivery, capacity use and on-time completion by client.

Product scope: costing, SLA reporting and invoice reconciliation.

08

Warehouses & integrations

Connect order intake, inventory availability and loading readiness. Add multi-depot planning, pickup-before-delivery pairs, reload trips, temperature needs and carrier handoffs when the operation requires them.

Product scope: WMS / ERP APIs, multi-depot and advanced constraints.

Plan. Check. Release.
Keep the exceptions visible.

  1. Prepare the work

    Validate orders, receiving hours, service time, weight and dimensions. Check warehouse readiness and available couriers.

  2. Build and inspect the plan

    Calculate assignments. Inspect stop sequence, arrival and waiting time, load at every stop and depot return. Resolve the unassigned queue.

  3. Approve and load

    In the proposed production workflow, a dispatcher approves a plan version. Warehouse staff check the manifest and load goods for the planned unloading sequence.

  4. Complete and reconcile

    Capture delivery evidence or a failure reason. Reconcile returns, discrepancies and actual costs. Replan remaining work with completed stops protected.

Make a feasible plan.
Show where it stops fitting.

Check each stop, including the way home.

The simulation calculates travel, waiting and service time. Its receiving window covers the whole service, so an arrival just before closing is not enough. The return leg must also fit the courier’s shift.

Weight and volume are separate limits. A delivery unloads first; return goods then add to the remaining load. A vehicle cannot accept an order simply because its total daily delivered weight looks reasonable.

Leave a difficult order visible.

Try the peak-load scenario, tighten all receiving windows or remove the box van. The planner retains shipments it cannot insert and lists the checks that blocked placement. Nothing is silently dropped or assigned beyond a modelled limit.

The browser demo uses a simple insertion heuristic. It finds feasible assignments, but does not prove the shortest possible route or that an unassigned shipment is impossible under every alternative plan.

Validate against the real operation before rollout.

A production version would need road-based travel times, customer address validation, the operator’s labour and handling rules, access controls, audit history and durable dispatch records. Pickup-and-delivery pairs, rest breaks, reloading, multiple depots and live replanning need their own scheduling rules.

A pilot should compare planned versus actual arrival times, unassigned orders, kilometres, overtime and loading exceptions using the same order set. No efficiency percentage or customer outcome is claimed in this concept.

Modelling references: time windows and capacity and routing parameters. The demo is implemented locally and does not call Google’s API.

← Back to all work