Stock leaves the warehouse and stops being counted
The loaded quantity is on a paper slip. What returns, what was sold and what was damaged end up as three numbers nobody reconciles.
Services
The route is planned on paper at seven in the morning, the driver calls twice to say a shop is closed, and the cash he collected is counted at eight in the evening. A delivery operation is manageable when three answers are current at every moment: what is in the van, what has been delivered, and what has been collected. We build the system that keeps those three current.
The loaded quantity is on a paper slip. What returns, what was sold and what was damaged end up as three numbers nobody reconciles.
A signature on a slip that gets wet, a photo in a chat thread, and a dispute three weeks later with nothing that settles it.
The driver's total and the office total differ by an amount that cannot be traced to a customer, an invoice or a day.
Orders grouped by wilaya and commune, ordered in a sequence the driver can follow, printed for the morning and downloaded to a phone for the road.
A signature or a photo on the phone, a reason code when the customer refuses, and the invoice marked delivered the moment it is saved — or when the phone reconnects.
A transfer moves quantity from the warehouse to the van; the evening return closes the difference and asks for a reason for every missing unit.
Each stop records the amount collected against its invoice. The day closes when the driver's cash equals the stops marked paid.
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
A morning at the loading bay and one run with a driver. The sequence written in the office is rarely the sequence the driver uses.
If the route sheet is wrong, software makes it wrong faster. Stop order, refusal rules and rates are agreed before the build.
The reconciliation is built before the dispatch screen, because it is the report that tells you whether the rest is working.
Drivers learn the app where they already stand at seven in the morning, with the printed sheet in hand as a fallback.
FAQ
What owners usually ask before requesting a quote for it.
Yes — an Android phone with a camera and enough storage for a day of photos. If a driver does not have one, the route runs on a printed sheet and the office enters the returns. That works, but the proof arrives the next morning.
Stops, signatures, photos and collected amounts are stored on the phone and sent when it finds a connection. Two drivers editing the same order is the case we design against: the last save wins and the earlier one is kept in the history.
No. Closures, market days and a driver who knows which street is one-way matter more than a routing algorithm here. We build the order of stops you decide, and record what actually happened at each one.
The variance is recorded with a reason and stays visible until someone closes it. The system does not accuse a driver and it does not absorb a difference; it keeps the difference in front of the person you name.
Start a project
Send the brief. It comes back as a written scope and a fixed quote before anything is built.