Job-Work and Subcontracting in a Garment ERP

Job-work is the reality of the Indian garment industry. A single style might be cut in-house, stitched at one unit, printed at another, embroidered at a third and washed at a fourth before it comes back to be packed. Each hand-off is a moment where pieces can go missing, quantities can drift and margins can quietly leak. Yet most factories run this on delivery challans in a drawer and trust built over years.

A capable garment ERP lets you keep that trusted network and add control on top. Pixel ERP is a ready, AI-native garment ERP product that treats job-work as a first-class part of production — not an afterthought — so outsourced work is as visible as anything on your own floor. And because it is a configured product rather than a from-scratch build, that control arrives fast.

Job-work starts with an issue. In Pixel ERP you issue fabric, cut bundles or semi-finished pieces to a job-worker against a job-work challan. The system records what went out — quantity by size and colour, the process to be done, the rate agreed and the expected return date — and generates the GST-compliant job-work challan and e-way bill where required.

What gets captured at issue

• The job-worker and the process — stitching, printing, embroidery, washing, finishing.
• Quantity issued across the size-colour grid, tied back to the order.
• The agreed job-work rate, so cost accrues as work is done.
• Expected return date, so delays surface instead of hiding.

Once material is out, Pixel ERP tracks it there. At any moment you can see how much of an order sits at each job-worker, in which process, and how long it has been there. Pieces pending at a stitching unit, garments away for washing, panels out for embroidery — all of it shows on the same cut-to-ship view as your in-house work, so a single order stays one continuous thread even when five parties touch it.

This is exactly the visibility that a spreadsheet cannot give you. It also feeds the AI: Pixel ERP can flag a job-worker holding pieces past the expected return date or an order at risk of missing its ship window because a subcontracted leg is running late — while there is still time to react.

Reconciliation is where job-work control is won or lost. When finished or semi-finished pieces come back, they are received against the original challan, and Pixel ERP reconciles issued-versus-returned quantities by size and colour. Shortfalls, excess, rejects and process losses are recorded, so you know precisely what each job-worker returned against what they were given.

The job-work reconciliation checklist

• Received quantity matched to the issue challan, cell by cell.
• Shortfall and excess flagged against agreed tolerances.
• Rejects and process loss recorded, keeping good-stock honest.
• Job-work charges accrued at the agreed rate for the returned quantity.
• Pending balance kept open until the job-worker returns it.

Job-work has its own compliance and accounting. Pixel ERP posts job-work charges automatically from received quantities at agreed rates, keeps the GST job-work documentation and challan trail intact, and reflects the cost in the order’s style costing. So the price of every outsourced process — printing, embroidery, washing, CMT — flows into the true, actual cost of the style rather than being reconstructed by hand at season-end.

That closes the loop between production and finance. The same job-work cost that appears on the shop-floor view appears in the margin calculation and in Pixel ERP’s accounting, with no double entry. For how this outsourced cost combines with fabric and trim consumption to give a full style cost, see our post on style BOM and the size-colour matrix.

Job-work is never isolated — it is one leg of the journey from fabric to finished carton. In Pixel ERP the outsourced steps sit inside the same flow as cutting, in-house stitching, finishing, packing and dispatch, so an order moves seamlessly between your floor and your network. To see the whole journey, read how Pixel ERP runs a garment factory from PO to dispatch, and for how the product fits the wider sector, the textiles & apparel page and the pillar garment ERP overview.

Every apparel house has a different job-work chain — different processes, rate structures, challan formats and tolerances. Pixel ERP absorbs those through no-code configuration rather than a bespoke build, so your specific processes, rates and documents are set up as settings. And because delivery is phased into clearly priced steps, you pay on milestones we meet — often starting with job-work itself, since it is where so many factories lose the most.

Most losses in outsourced production are not dramatic thefts — they are small, repeated leaks that add up over a season. A hundred pieces short here, a rate paid on issued rather than returned quantity there, a bundle that never came back and was never chased. On paper each is tiny; across a year they quietly eat a real slice of margin. A garment ERP closes these gaps not by distrusting your network but by making every hand-off measurable.

Leaks Pixel ERP is designed to stop

• Paying job-work charges on issued quantity instead of what was actually returned and accepted.
• Pieces that leave for a process and are never reconciled back, so the shortfall never surfaces.
• Rejects and process loss absorbed silently into good-stock figures.
• Orders slipping their ship date because an outsourced leg ran late and nobody was watching the clock.
• Job-work cost reconstructed by hand at season-end, too late to influence pricing.

Because every issue, return and reconciliation is captured, the numbers are there when you need them — for a payment dispute, a margin review or simply deciding which job-workers to give more work to next season.