A busy day, a courier off sick, a campaign that lands all at once. On Kovan the bag a branch cannot cover opens to drivers on the network — and when that bag changes hands, the chain does not break.
Bags are split to the vehicle’s parcel and volume capacity. A bag you assign to your own courier is withdrawn from the board; take it back and it reopens the same day.
A parcel only changes hands after the identity is verified and the seal is scanned. A hand-off done around the app is the one thing this product exists to prevent.
When the “it says delivered but I never got it” call arrives, the door photo, the distance to the door and the delivery code are on one screen. A file is opened, a decision is made, and the driver keeps the right to appeal.
Courier branch
As long as your own couriers are enough, there is no problem. On the day they are not, a bag stays at the branch and rolls over to tomorrow. Kovan opens that bag to suitable drivers on the network without a single recipient address leaving the server.
The panel is desktop-first and falls to a single column on a narrow screen. Every role is checked on the server; permissions are never merely hidden in the interface.
Example screen · sample data. The pilot has not published a performance figure yet.
The five steps below are a branch’s daily work; the right-hand column is what gets written into the chain of events at that step.
Branch, day, time window, districts and neighbourhoods, vehicle type, and pay per parcel or per route. A job cannot open before its parcel list is uploaded.
The opening of the job and the parcel barcodes; the recipient’s name, phone and address are stored encrypted and the panel shows only a masked name.
Each parcel is scanned into its bag; a parcel that cannot be found counts as out of the bag and is marked.
Which parcel went into which bag, what was missing, and the seal number.
The moment the job opens, any bag nobody has taken becomes visible to the network; assigning it to your own courier withdraws it.
The bag going on the board and being withdrawn; recipient details are never shown on the board.
The progress of drivers on an open shift, the stops they skipped, and the reasons and photos for parcels that could not be delivered.
For every delivery attempt: distance to the door, GPS accuracy, and whether the location was mocked.
An admin closes the driver pay statement; Kovan closes the platform fee. If a bag is still unsettled the month cannot close and an alert is raised.
The closed month’s lines and their signature; anything counted later becomes a correction line in the next month.
Role checks happen on the server for every request. Panel roles and phone roles never mix in one person.
Kovan charges the company a platform fee per counted delivery. A counted delivery is a delivery attempt the server accepted and nobody rejected: either it never needed a review, or the review approved it. Pending, rejected and undelivered attempts never count. Even if a parcel goes out twice, it is billed at most once.
The driver’s pay is a separate statement and flows from the company to the driver; the money never passes through Kovan. On per-parcel jobs each counted delivery is a line; on per-route jobs each bag whose shift has closed is a line.
Unit prices are set in the contract and defined as a tariff per company — there is no price fixed inside the software. Months close in order; a closed month never changes again, and late records become correction lines in the next one.
If you run a courier company in İstanbul, or you drive your own vehicle, leave an application and our operations team will call you.