WebSoftOS
Transport & Logistics ERP · Illustrative scenario
How a 45-truck transporter runs LR, trips and driver settlement from one screen
Shivalik Roadlines (fictional) · Ludhiana, Punjab. A regional transporter with 45 owned and attached trucks, two branch offices and daily part-load and full-load trips.
Illustrative scenario. The company in this story is fictional. It shows how a business of this profile would typically set up and use WebSoftOS. It is not a customer testimonial and it does not report measured results.
The starting point
- LRs (bilty) were written by hand and re-typed into Tally by the branch accountant.
- Fuel, toll and driver advances were settled weeks after the trip, so per-trip profit was a guess.
- Proof of delivery photos lived in WhatsApp and were chased for every freight invoice.
How WebSoftOS would be set up
- Vehicle master with documents, tyres and maintenance schedules.
- LR creation per consignment, trip sheets with fuel, toll and driver advance entries.
- Driver settlement at trip close; freight invoicing with POD attached.
- Two branches as separate hubs sharing one customer and vehicle master.
Before and after
| Step | Before | With WebSoftOS |
|---|---|---|
| Booking | Handwritten LR | LR created in the system with consignor, consignee and freight |
| Trip expenses | Slips collected at month end | Fuel, toll and advances logged against the trip |
| Driver settlement | Calculated in Excel | Settled at trip close from logged entries |
| Freight bill | POD chased by phone | Invoice raised with POD attached |
What the team can do afterwards
- Trip-level profit is visible shortly after the trip closes.
- Freight invoices go out with proof of delivery already attached.
- Tyre and maintenance due dates are tracked per vehicle.
Rollout
Typical rollout: 2–3 weeks, starting with vehicle and customer masters and a one-branch pilot.