Most tailoring software is written for a shop that sells finished garments off a rail.
An Indian tailor shop does the opposite: the customer arrives with cloth, or picks it in
the shop, and everything after that is made to one person’s measurements against a
date that was promised out loud at the counter. Software that cannot hold a measurement,
a delivery date and a part payment against the same name is not managing the work —
it is only billing it.
The garment list matters more than vendors admit. A saree blouse, a salwar suit, a
lehenga, a sherwani and a school uniform are five different measurement sets, five
different fitting habits and five different seasons. A tool built around shirts and
trousers will make you record all of them in a notes field, and a notes field cannot be
searched, compared or reused for the next order. Juvee keeps them as
proper measurement records, one profile per
customer, with the history of how those numbers changed.
Then there is how the shop actually talks to people. Almost nobody rings back to ask
whether the blouse is ready; they send a message, and they expect one when it is done.
The same goes for the karigar who wants to know what is cut and waiting for him. A system
that lives only on a desktop in the corner gets used for the first week and abandoned in
the second, which is why the whole of Juvee also runs as a
tailor app on the phone, on the kind of connection a first-floor
shop in a market actually has.
And the words have to be the ones the shop uses. Juvee is built around naap, karigar,
udhaar and bahi-khata rather than translations of them — the same product reads as a
silai app or a darzi app depending on who
is holding the phone, because that is what the person searching for it calls it.