Why textile job-work tracking breaks in WhatsApp and Excel

The route a lot takes

A typical knit-garment order, simplified:

1. Sample and approval — the buyer approves a sample, a colour and a size mix.
2. Yarn to fabric — yarn issued in kilograms to a knitting unit; grey fabric returns in kilograms and rolls.
3. Processing — fabric sent for dyeing and compacting; it returns lighter, because processing loses weight.
4. Cutting — fabric in kilograms becomes cut panels in pieces.
5. Printing or embroidery — panels out to another unit and back, with some rejected.
6. Stitching, checking and packing — pieces become garments, then cartons, then a dispatch.

Every arrow in that list is a hand-off, often to a unit you do not own, and each one changes the unit of measure or the quantity. That is the part a chat thread cannot hold.

Where WhatsApp and Excel break

• The record is scattered. The delivery challan is a photo in one group, the return quantity is a voice note in another, and the rate is in the supervisor’s memory.
• Units change silently. A sheet that adds kilograms of yarn to kilograms of fabric to pieces of garments produces a total that means nothing.
• Process loss is never written down. Dyeing and cutting lose material legitimately. If the agreed loss is not recorded, every lot looks short, and a real shortage hides among the normal ones.
• Rejects and rework disappear. Pieces rejected at a printing unit are either sent back, re-done or written off, and each of those needs its own line.
• There are several versions of the truth. Two people edit two copies of the sheet, and nobody can say which one is current.

The minimum reliable record

Before any software, this is the structure that fixes most of the problem. It can be kept in a well-designed spreadsheet.

• One lot or order reference that every movement carries.
• An issue line for each movement out: date, unit, process, challan number, quantity and its unit of measure, expected return date.
• A receipt line for each return: quantity received, accepted, rejected, and the process loss agreed for that operation.
• A balance per unit per lot, calculated rather than typed, so what is still outside is always visible.
• Explicit conversions where kilograms become pieces, recorded once, with who confirmed them.
• One status per lot that anyone can read without asking.

When software is worth it

A disciplined spreadsheet is the right answer for a small number of units and one person entering data. Software earns its cost when several people enter records at the same time, when floor staff need simple screens in Tamil on a phone, when you need to control who sees rates, or when you need a history of who changed what. Those are the points where a spreadsheet stops being one record.

Start with the problem that costs you most. If missed dates are the issue, start with lot status and due dates; if material goes missing, start with issues and receipts. Add costing and buyer access later.

How job-work software differs from Tally

Tally is accounting and inventory software, and it does support job-work vouchers. The gap is usually operational rather than financial: which stage a lot is at, which unit has it, what came back short and why, entered by the people on the floor as it happens. Most businesses keep Tally for accounts and add an operations record that exports what the accountant needs, rather than replacing one with the other.

GST has its own rules for goods sent for job work, including separate reporting. Confirm the requirements for your business with your accountant before designing any export around them.