A distribution group running on nineteen custom modules
Dispatch, field sales, collections, finance and reporting on one system — built module by module over four years.
The problem
A clerk wrote the load sheet each morning, the driver took it out, and somebody reconciled the cash that evening. It was usually late, and there was usually a discrepancy nobody could explain. The cash position was known about three days after the fact.
Credit limits existed on paper, but an order outside them was approved by a phone call nobody recorded.
What we built
Nineteen modules, built one at a time, starting with whatever was hurting most that quarter.
- Dispatch runs with a driver portal, structured no-payment reasons, and an end-of-day tally that goes to an approval queue before anything posts to the ledger
- Field invoicing with batch and expiry tracking, stock reserved the moment an order is placed
- Per-rep credit profiles that route an out-of-limit order to an approver instead of a phone call
- GPS visit detection, so a customer visit is logged on arrival rather than from memory
- Staff advances, company loans and leases, with amortisation that reconciles
- Twenty-plus management reports, and an AI layer that writes the daily position in plain language
Built under real constraints
Every module installs through cPanel File Manager with no server access and no downtime beyond a few minutes. That constraint shaped the architecture from the start, and it is why a system this size runs on ordinary shared hosting rather than a managed server nobody wants to pay for.
Staff were trained in Sinhala. The driver portal had to work for people who had never used a business system, which is why collections are recorded by choosing from a list rather than typing.
Still going
Current work covers a customer ordering portal, an audit log across every screen, and the migration of a legacy database going back to the 1990s.
Where it stands
Have a process that works like this one used to?
Send us a photo of the sheet you fill in by hand.
