Problem
Vinod Rice Mill Pvt Ltd tracked orders across production, quality control and shipment using several apps and direct messages. Information was scattered, updates were late, and nobody could see an order's whole journey. A needs analysis with the client turned that into a brief: one system, with each department seeing only what it needs.
Method
A Flask web application with three roles. Administrators manage employees and oversee every order; employees in production, finance and shipment each get a dashboard to update their own stage; customers place orders and watch them move through the lifecycle. Every status change is stored, so the order history is auditable. Designed for phased rollout so the mill could pilot it alongside the old process. Alongside it, a public website for the business, its shopfront online.
Evaluation
The system was built to the director's brief and demonstrated in the mill. Where it met resistance was on the floor: employees used to the old channels didn't move across, and without their buy-in the rollout was eventually set aside. That is the real lesson of the project, and the one I carry into client work now: software adoption is decided by the people who have to use it every day, not by the person who commissions it.
The decision it drives
Who touches an order next, and whether it is late. For me, it set the pattern every later project follows: a real business, a real constraint, and change-management as part of the design.