Constraint-aware route optimisation
Routes are solved against vehicles, capacities, shift windows, time windows — and a live constraint layer of closures, queues and access limits. Not a shortest-path line drawn over a map tile.
Core engineDispatch & route optimisation
Your dispatcher knows the roads. Now your software does too.
Darbline plans and re-plans delivery routes under the constraints your drivers actually hit — checkpoints, closures, unnamed streets, and addresses that are descriptions rather than coordinates.
Illustrative demo data — not live customer figures.
Treated as input, not exceptions
- Road closures
- Checkpoint queues
- Unnamed streets
- Landmark addresses
- Vehicle access limits
- Shift end times
- Cash on delivery
- Re-delivery attempts
01 The problem
Software that assumes an open road gets overridden by lunchtime.
Off-the-shelf routing engines are built for predictable networks. They hand the dispatcher a plan that is already wrong before the first van leaves the yard — so the dispatcher fixes it by hand, all day, until the software quietly gets switched off.
-
The network on the map is not the network outside
A junction that is clear on a map provider's tiles can be a closure, a queue, or a road nobody uses after four o'clock. The engine has no way of being told, so it keeps proposing it.
-
Addresses are descriptions, not coordinates
“Behind the mosque, second building, ask for the pharmacy” does not geocode. The driver phones the customer, finds it, delivers — and the next driver starts the search from zero.
-
Every override is thrown away
Dispatchers correct the plan continuously and none of it returns to the model. Tomorrow the software makes the same mistake, with the same confidence.
Dispatcher override log
Tue · 07:10 – 11:00
- 07:14 Moved stops 8–12 off the ring road — driver phoned in a closure. Manual
- 07:52 Split route C by hand, van too tall for the underpass. Manual
- 08:26 Called customer for stop 31 — address is a landmark, not a street. Phone
- 09:05 Re-sequenced route A around a checkpoint queue. Manual
- 10:41 Pushed 4 stops to tomorrow — shift ends before the plan does. Rollover
17 manual overrides before 11:00. Illustrative sample of a dispatcher's morning — the pattern the product was designed against.
02 The system
Constraints are input. Not exceptions to be worked around.
A driver reports a closure or a queue from the app in two taps. Every affected vehicle reoptimises within seconds, and the constraint stays in the model with a decay window — so tomorrow's plan already knows about it. Over weeks, your fleet builds a road graph no map provider has.
Before
Static plan · generic map routing
Distance118 km
Overrides17
Finish18:40
After
Darbline · constraint-aware
Distance91 km
Overrides2
Finish16:55
Both panels show the same 42-stop demo scenario. Figures are illustrative sample data used to explain the mechanism — not measured customer results. Measured before-and-after numbers will be published once pilot fleets agree to be named.
03 What you get
Eight parts, one operational loop.
Plan, drive, report, reconcile. Each piece feeds the next one — which is why the constraint layer gets better the longer your fleet runs on it.
Real-time driver reports
Closure, queue, blocked access, wrong address — two taps from the driver's phone. Every vehicle whose route depends on that segment is replanned immediately.
Field inputLandmark address book
Resolve “behind the mosque, second building” once. It becomes a pinned, reusable location with driver notes, entrance photos and a phone number attached.
Address dataDriver app with proof of delivery
Sequenced stop list, signature or photo capture, failure reasons, and cash collected per stop. Works on the phones your drivers already carry.
MobileLive customer tracking links
A link with a real position and a real ETA that moves when the route moves — instead of a four-hour window and a phone call to the shop.
RecipientFleet and cost-per-drop analytics
Cost per drop, drops per driver, failed-delivery reasons and constraint hotspots — per route, per vehicle, per day, exportable.
Ops reportingCash-on-delivery reconciliation
Cash expected against cash collected, per driver, per shift, with variances flagged at hand-in. Core to the product, not a paid add-on.
MoneyYour fleet's own road graph
Reports from your drivers accumulate into a private constraint layer for the roads you run. It is yours, it is exportable, and it does not depend on a map vendor modelling your streets.
Differentiator04 Inside the console
One board for the day. One card for every drop.
Dispatchers watch progress, not dots. Every completed stop closes with proof — signature or photo, timestamp, position, and the cash that came back with it.
| Driver | Route | Progress | Next stop | COD | Status |
|---|---|---|---|---|---|
| DRV-04 | A · 28 stops | Stop 17 — landmark pin | ₪1,240 | Rerouted | |
| DRV-07 | B · 22 stops | Stop 19 — Al-Bireh | ₪860 | On plan | |
| DRV-11 | C · 31 stops | Stop 15 — checkpoint | ₪2,015 | Queue +6 min | |
| DRV-15 | D · 19 stops | Stop 6 — retry | ₪430 | Access blocked | |
| DRV-22 | E · 24 stops | Return to depot | ₪1,690 | Closing |
Proof of delivery
Settled
Order#DB-4471
Stop17 · landmark pin
Delivered14:22 · DRV-07
Attempt1 of 1
Cash collected₪180 of ₪180
PositionMatched to pin · 8 m
Sample records from a demo tenant. No real customer or recipient data is shown.
05 How it works
Four steps, and none of them start with a rebuild.
Most fleets are running their first real routes inside a week. You keep your orders where they are; Darbline takes the day and gives it back sequenced.
-
STEP 01
Bring in the day
Upload the day's stops as CSV or push them from your shop, ERP or WhatsApp order flow. Addresses that will not geocode go to the landmark queue instead of failing silently.
-
STEP 02
Plan against reality
Darbline solves the routes against your vehicles, shifts and capacities plus the live constraint layer your own drivers have been building.
-
STEP 03
Drive and report
Drivers work the sequence, capture proof, take cash and flag anything blocking the road. Affected routes replan without the dispatcher touching anything.
-
STEP 04
Reconcile and review
Cash is reconciled per driver at hand-in. Cost per drop, failed reasons and constraint hotspots land on the ops dashboard the same evening.
06 Pricing
Per vehicle if you run a fleet. Per delivery if you don't.
One price, all features. The constraint engine, the driver app and cash reconciliation are not upsells — a fleet without them is the fleet you already have.
Merchant
Shops and e-commerce merchants running one or two of their own vans.
$0.15per completed delivery, from
- Driver app and proof of delivery
- Live customer tracking links
- Landmark address book
- Cash-on-delivery reconciliation
- CSV import
Billed on completed deliveries only. No monthly minimum during the pilot programme.
Fleet Most fleets
Courier companies, distributors, pharmacy and grocery operations running their own drivers.
$18per vehicle / month
- Everything in Merchant
- Constraint-aware route optimisation
- Dispatch console and live reroute
- Fleet and cost-per-drop analytics
- API access and your exportable road graph
Volume tiers begin at 10 vehicles. Trial runs on up to 5 vehicles with your real stops.
Enterprise
Fleets above 50 vehicles, multi-depot operations and 3PLs with integration requirements.
Custom50+ vehicles
- Everything in Fleet
- Multi-depot and sub-fleet route groups
- Onboarding with your dispatchers on site
- SSO and role-based access
- Integration support and uptime commitments
Quoted per operation. Tell us vehicle count, depots and daily drop volume.
Indicative launch pricing in USD, excluding tax. Volume tiers begin at 10 vehicles and fleets above 50 are quoted individually. Pricing is being validated with pilot operators and may change before general availability — anything quoted to you during the pilot is held for twelve months.
07 Credibility
We would rather show you the numbers than claim them.
Darbline is early. Rather than borrow logos or invent a metric, here is exactly what will occupy this section — and what is already true today.
Deliveries routed per month
Not yet published
Will be read from production and refreshed monthly once the first pilot fleets are live. It will not be a number from a slide.
Not yet published
Average drops per driver, change
Measurement in progress
Measured against each fleet's own four-week baseline from before they switched over, with the methodology published alongside it.
Measurement in progress
Named fleet customers
Awaiting operator consent
Logos, names and quotes appear only with written permission from the operator. Until then this space stays empty on purpose.
Awaiting consent
- Built alongside working dispatchers. The dispatch flow came out of ride-alongs and sitting in dispatch rooms through peak hours — not from a competitor's feature list.
- Optimisation done properly. The routing and scheduling models are grounded in the industrial-engineering work taught at An-Najah National University, where the team studied.
- Constraints are the whole reason we exist. Movement constraints are the defining operational problem of logistics here, and no global vendor models them.
- No borrowed proof. Nothing on this site is presented as a customer result until it is real, measured, and approved by the operator it came from.
08 Straight answers
The questions dispatchers ask in the first ten minutes.
Do we have to replace our whole dispatch process on day one?
No. Most fleets start with one route group and one dispatcher, keep the rest of the day on the existing process, and compare the two for a week. Orders can arrive by CSV the whole time — an integration is not a prerequisite.
What happens when a driver has no signal?
The driver app holds the sequence, the stop details and any proof captured on the device, and syncs when the connection returns. Dispatch sees the last known position with its timestamp rather than a dot that silently stops being true.
How does the landmark address book actually work?
An address that will not geocode goes into a queue instead of failing. The first driver who finds it drops a pin from the door, adds a note and an entrance photo, and the description is bound to that pin. Every later order to the same description routes straight to it.
Can we keep using our own map provider?
Yes. Darbline sits on top of a base map for geometry and travel times, and applies your fleet's constraint layer over it. The constraints and landmark pins your drivers create belong to you and can be exported at any time.
How is cash on delivery handled?
Every stop carries an expected amount. The driver records what was actually collected at the door, and at hand-in the shift reconciles expected against collected per driver, with variances and partial payments flagged for the supervisor. It is part of the core product, not a paid module.
Who owns the constraint data our drivers create?
You do. Closures, queue patterns and landmark pins reported by your drivers are your fleet's private layer by default, exportable in a documented format. Nothing is shared with another fleet unless you explicitly opt in to a shared road graph.