An ERP that has been closing a real weaving company's books, without interruption, for over seven months.
LIVE · IN DAILY USE
BOOK.SHANTOTEXTILE.COM · STAFF LOGIN7+ months
Continuous production use
3,897
Stock entries recorded
175
Endpoints across 69 screens
SIGN-IN
THE PROBLEM
A vertically-integrated weaving operation ran on paper ledgers and spreadsheets. Weaving jobs were costed by hand, weavers were paid per unit against loans nobody could total quickly, and the month-end position was an argument rather than a number.
The constraint that shaped everything: the people entering the data are on a factory floor, not at a desk, and many of them do not type comfortably in English. A system that demanded fast accurate English keyboard entry would simply not be used, and an unused system is worse than the spreadsheets it replaced.
WHAT WE BUILT
SHAPE OF IT
A deliberate monolith — one application, one database, three worker processes behind a reverse proxy. For a single-tenant system used by a handful of staff on one site, splitting it into services would have added operational surface without buying anything. It is installable as a progressive web app so the factory floor can use it on a phone, including offline.
DECISIONS THAT MATTERED
The most-used feature is voice entry: a user speaks an expense in Bengali and it becomes a structured ledger entry, with the account and supplier lists supplied to the model as context so it resolves to real records rather than free text. Input is stripped of control characters and explicitly guarded against prompt injection before it reaches the model — an easy step to skip, and a costly one to skip in a system that writes to the books.
All monetary arithmetic uses decimal values with explicit half-up rounding. Floating point is fine until a trial balance is off by one paisa and nobody can say why, at which point it is the most expensive shortcut in the codebase.
Changing a posted record goes through a revision request and an approval, so there is always a record of what was changed, by whom, and who agreed to it. In a business where the same person often enters and approves, this is what makes the audit trail worth having.
Weaver loan balances are decremented by one database statement triggered on repayment insert, clamped at zero. Reading a balance, subtracting in application code and writing it back would double-decrement under concurrent repayments — which is exactly the kind of bug that surfaces as a weaver being told they owe money they have already paid.
Three worker processes start simultaneously and would otherwise race each other applying schema changes. An advisory lock means exactly one does the work and the others wait — a small fix for a failure mode that only appears under real deployment conditions.
Business dates are computed in Asia/Dhaka rather than taken from the server clock or the database's timezone. A report that silently shifts by six hours puts transactions in the wrong month, and month-end is precisely when nobody has the patience to debug it.
The people entering the data are on a factory floor, not at a desk. A system that demanded fast English typing would simply not be used.
WHERE IT LANDED