These stay put. Average matters most — every vehicle runs differently.
Nobody knows their servicing in rupees per kilometre. Put in the bill and how long it lasts; the per-km figure works itself out.
Lead is one way — the empty return is added. Days is door to door, including time standing at the gate.
Paste your destination, your km and your rate. You get the rate to negotiate on.
| Destination | Km | Rate ₹/T | Days | Cost/km | Ask ₹/T | Per trip | Verdict |
|---|
Insurance, fitness, PUC, permit. Put the dates in once and it tells you before they run out.
| Vehicle | Insurance | Fitness | PUC | Permit / tax |
|---|
Uses your phone's location to open the map at whatever you need.
Red is expired, amber is inside a month. Once this is on a server it will message you a month out and again a week before — that is the part that needs a backend.
Validity can only be extended from 8 hours before expiry to 8 hours after. Miss it and it is ₹10,000 or the tax evaded, whichever is higher — and the truck can be held.
| EWB | Vehicle | To | Expires | Left |
|---|
Typing these by hand defeats the point. The EWB number and its expiry are printed on the invoice handed over at loading — photograph that and every bill tracks itself. Extending still happens on the government portal — this gets you there with the number copied and the answers ready. Doing it inside the app needs licensed API access, which is a later build.
Photograph the DI, the invoice or your LR at the gate. It reads the trip out, prices it, and starts the e-way bill clock.
| From | To | Tonnes | Vehicle | Despatched | EWB expiry |
|---|
One photo fills everything the paper carries — origin, destination, tonnage, vehicle, dates and the e-way bill — and files it into the other tabs on its own. Distance is never printed on a DI, so you give it once per destination and it is remembered after that.
Wherever the truck is right now. Opens your maps app with directions.
Send the bill number and where the truck is. Someone extends it and messages you back.
This is a picture of the message, not a live one. Sending it needs a server holding your number and a WhatsApp or SMS channel — that is the first backend job after deployment.