Textile and garment manufacturing is a business decided in metres, lots and pieces. The price you quote for a garment is built on an average fabric consumption, a stitching rate and a few assumptions about wastage. The cost you actually incur depends on the marker the cutting master really used, the shrinkage the fabric lost at the dyer, the end bits left on every roll, the pieces that went missing between cutting and packing, and the sizes that stayed unsold because one colour ran short. When those two sets of numbers drift apart, the margin disappears quietly, and most Indian garment and textile units only see it when the season closes and the stock does not reconcile.
This guide is for owners, production heads and merchandisers in Indian textile and apparel units: knitwear and T-shirt exporters, woven garment makers, innerwear and kidswear brands, home textile and made-ups units, and fabric processors working with dyeing, printing, embroidery and washing job workers. It walks through the specific places where a textile or garment unit loses money, explains the mechanism behind each one, and shows how a manufacturing ERP built for Indian factories, such as ERPDrive, closes each gap. If you want the industry overview first, see our page on ERP for textile and garment manufacturers.
Deadline alert: If your aggregate turnover in the previous year was above INR 5 crore, the half-yearly Form GST ITC-04 for April to September 2026 is due on 25 October 2026. Units with turnover up to INR 5 crore file annually, by 25 April (ITC-04 frequency and due dates). For most garment units, that return covers every lot of fabric sent for dyeing, printing, embroidery or washing in the last six months.
Why Garment Margins Leak: The Cost per Piece Equation
Every garment carries three main costs: fabric, conversion and overheads. Fabric cost per piece is the metres consumed per piece multiplied by the landed rate of the fabric, including any dyeing, printing or processing charges paid to job workers, adjusted for the shrinkage and process loss the fabric suffered on the way. Conversion cost covers cutting, stitching, finishing, washing, embroidery and packing, whether done in house or by fabricators on piece rates. Trims, packing material and freight sit on top.
Look at what drives the fabric line: metres consumed per good piece. That one number depends on the marker for each size, the width and shrinkage of the actual lot that arrived, the end bits left on each roll, and how many cut pieces survive stitching and checking. A costing sheet built on one average consumption for the whole style hides the fact that XXL uses far more fabric than S, that a narrower lot from a different mill changes the marker, and that pieces rejected at checking still consumed fabric. Nothing on the floor looks broken. The cutting table is busy and the bundles move on. The loss only shows up if somebody compares planned metres per piece with actual metres per piece, size by size.
The same logic applies to every leak in this guide. Each one either raises the metres and rupees going in (consumption, process loss, rework, job work charges) or reduces the good, sellable pieces coming out (missing pieces, shade rejections, broken size sets), and each one is invisible unless your system records textile-specific data: style, size and colour, fabric lot and shade, marker consumption, challans at each job worker, and bundle movement by stage.
Key Takeaway: In garment manufacturing, cost per piece is a ratio of metres and rupees in to good pieces out. Profit leaks when consumption, process loss or job work charges creep up, or when good pieces fall, and neither change is visible in a system that only records fabric purchased and pieces invoiced.
8 Costly Problems Indian Textile and Garment Units Face
Problem 1: Costing on Average Consumption, Not the Marker
The Problem: Merchandisers usually cost a style on one average fabric consumption per piece, often taken from the sample or from a similar older style. Bulk production then runs on markers made by the cutting master for the actual size ratio of the order and the actual width of the fabric that arrived. If the order is heavy on bigger sizes, or the lot is narrower than the sample fabric, real consumption is higher than costed, and the extra metres are simply issued from stores. The difference is written off as "cutting wastage" at the end of the season instead of being caught on the first lay.
How ERPDrive Solves It: In ERPDrive's bill of materials, the cutting BOM defines fabric consumption in metres per piece for each size of the style, with fabric in metres and garments in pieces handled through dual units of measure. When the cutting room records a lay, it captures the marker and the actual fabric consumed against the theoretical consumption for that size ratio, so marker efficiency and cutting wastage are visible per style and per lot.
The Result: The merchandiser costs the next order on real consumption, the cutting master gets feedback on every marker, and the gap between issued and consumed fabric becomes a number you can investigate on the day it happens.
Problem 2: The Style-Size-Colour Matrix Nobody Can Track
The Problem: One style in six sizes and eight colours is 48 separate stock items. A season with dozens of styles quickly runs into thousands. Creating these by hand in Tally takes days, so many units keep stock at style level only, or in an Excel sheet that is out of date by the next morning. Without size and colour level stock, sales commits pieces that do not exist, production re-runs sizes that are already in the warehouse, and nobody can see which colours are moving.
How ERPDrive Solves It: ERPDrive generates the full style-size-colour matrix from one style definition: enter the size list and the colour list and every SKU is created with consistent coding. Inventory management then shows stock, work in progress and open orders at size and colour level, and every style can be tagged with its season and collection.
The Result: Item setup for a new season takes hours instead of weeks, sales promises only what is available, and planning produces the sizes and colours that are actually short.
Problem 3: Fabric and Cut Panels at Job Workers Without a Challan Trail
The Problem: Very few garment units do everything in house. Greige fabric goes to a dyeing or processing house, finished fabric or cut panels go to a printer or an embroiderer, stitched garments may go to a fabricator or a washing unit, and each movement comes back in parts and at different times. Under GST, inputs sent to a job worker must be received back within one year and capital goods within three years. If they are not, the goods are treated as supplied by the principal on the day they were sent out, and tax becomes payable on that deemed supply (job work rules and ITC-04, GST Council flyer on job work). Every movement must also be declared in Form GST ITC-04. When challans are handwritten and part receipts are matched in a notebook, nobody is sure how many metres or pieces are still lying at which job worker, and the ITC-04 is reconstructed in a hurry before the due date.
How ERPDrive Solves It: ERPDrive's job work tracking issues a GST job work challan, with an e-Way Bill where required, for every lot of fabric, cut panels or garments sent out for dyeing, printing, embroidery, stitching or washing. Part receipts are recorded against the original challan, a running balance is kept for every job worker, and the system flags challans approaching the one-year limit. The same transactions feed the ITC-04 working, so the return is prepared from records rather than memory. Our job work GST compliance guide covers the rules in detail.
The Result: You know at any moment what sits outside your factory, aged challans are chased before they become a tax liability, and ITC-04 filing becomes a report instead of a scramble.
Know Where Every Metre of Fabric Is
See how ERPDrive tracks fabric by lot and shade, issues job work challans to dyers, printers and embroiderers, and prepares your ITC-04 from transactions.
Book a Free DemoProblem 4: Process Loss at Dyeing and Washing Is Never Reconciled
The Problem: Fabric changes when it is processed. Greige fabric shrinks in length and width during dyeing and finishing, knitted fabric is often bought by weight and consumed by length, and washing changes garment measurements and weight. Some loss is normal. But if the unit sends 1,000 kg of greige to a dyer and receives finished fabric back without comparing the quantity against an agreed process loss norm, there is no way to tell normal shrinkage from careless processing or short return. Over a season, the difference can be large, and it is paid for as extra fabric purchases.
How ERPDrive Solves It: Because each lot goes out on a job work challan and comes back as a receipt against it, ERPDrive compares quantity sent with quantity received for every lot and every processor. Fabric can be held in metres or kilograms with conversion, so a knitted lot sent by weight and consumed by length is still traceable. Process loss by job worker and by fabric quality becomes a report, not a guess.
The Result: You can agree loss norms with each processor, question returns that fall outside them, and choose job workers on actual yield as well as rate.
Problem 5: Shade Lots Mixed Inside One Order
The Problem: The same colour dyed in two batches is rarely an identical shade. If panels from two dye lots end up in one garment, or two lots are mixed in the same carton, the shade variation is visible to the buyer and the shipment can be rejected or discounted. In many units the dye lot is written on the roll tag and nowhere else, so cutting picks whatever roll is nearest.
How ERPDrive Solves It: At goods receipt, ERPDrive records each fabric roll with its lot, GSM and shade along with quantity, using batch and lot tracking. When fabric is issued for a cutting order, the system suggests rolls from the same dye lot or matching shade band, and mixing lots requires an approval with a reason. Inspection results against each roll or lot are recorded in quality control, including buyer-specific fabric inspection where required.
The Result: Shade mixing becomes a deliberate, approved exception instead of an accident, and when a buyer complains you can trace exactly which lot went into which order.
Problem 6: Pieces Vanish Between Cutting and Packing
The Problem: A cutting order of 1,000 pieces rarely ships as 1,000 pieces. Some panels are damaged in cutting, some pieces are rejected at checking, some are sent for alteration and never come back, and some simply go missing between floors or fabricators. If the unit only records quantity cut and quantity packed, the gap is discovered at packing, when the order is already short, and nobody can say at which stage the pieces were lost.
How ERPDrive Solves It: ERPDrive moves cut pieces through job cards for cutting, stitching, finishing and packing, with bundle barcodes scanned at each stage. Work in progress is visible by stage, style, size and colour, so a shortfall is spotted at the stage where it happens. See our guide on WIP inventory tracking for the wider method.
The Result: Missing and rejected pieces are caught while there is still time to re-cut, and the cut-to-ship ratio becomes a weekly number the production head can act on.
Problem 7: Broken Size Sets and Dead Stock After the Season
The Problem: Garments sell in size sets. When one size of a colour runs out, the remaining sizes of that colour often stop selling as sets, and they sit in the warehouse as broken assortments. Fabric bought for a style that was cancelled, trims ordered for a buyer who reduced quantities, and last season's colours add to it. Because stock is tracked at style level or not at all, this cash blockage is invisible until the year-end stock count.
How ERPDrive Solves It: With stock held at size and colour level and every style tagged by season, the Cash Blocked in Inventory report shows which fabrics, trims and finished sizes are ageing and how much money they hold. End-of-season reporting shows sell-through and dead stock by style, so the next season's buying and production plans start from data. For the wider method, read our guide on inventory ageing and dead stock.
The Result: Broken sets are cleared or completed while they still have value, and fabric and trims are bought against real demand instead of last year's habit.
Problem 8: Orders Priced Right but Delivered Late or at a Loss
The Problem: Apparel orders run to fixed windows: a buyer's shipment date, a festive season, a retail launch. A delay at the dyer or a short-shipped size can push an order past its window and into a discount or air freight. At the same time, fabric and yarn prices move between costing and production, and job work rates change mid-season. Without a link between the costing sheet, purchase rates and actual production, some orders that look profitable on paper lose money in execution.
How ERPDrive Solves It: ERPDrive's production planning works back from the delivery date through cutting, job work and stitching, and the Dispatch Delays report highlights orders slipping against their promised dates while there is still time to act. The Purchase Cost Leakage report shows where fabric, yarn or job work is costing more than before, and the Low-Profit Orders report flags orders whose actual cost has eaten into their quoted margin. Dispatch runs with GST invoices, e-invoices and e-Way Bills, and accounts sync two ways with Tally.
The Result: Merchandisers see late orders early, sales knows which buyers and styles actually make money, and price revisions are discussed with evidence.
Manual Garment Unit vs Cloud ERP for Textiles and Apparel
| Area | Tally, Excel and Registers | ERPDrive Cloud ERP |
|---|---|---|
| Fabric costing | One average consumption per style | Metres per piece by size, actual vs marker |
| Item master | Style-level stock, SKUs created by hand | Size-colour matrix generated per style |
| Job work and ITC-04 | Handwritten challans, notebook matching | Challan-wise balances feeding ITC-04 |
| Process loss | Not compared lot by lot | Sent vs received per lot and processor |
| Shade lots | Lot written on the roll tag only | Lot and shade tracked, mixing needs approval |
| WIP | Cut and packed counts only | Bundle scans at each stage |
| Dead stock | Found at year-end count | Ageing by size, colour, fabric and trim |
| Order profitability | Costing sheet never revisited | Actual cost vs quoted margin per order |
Textile and Garment KPIs Every Production Head Should Track
You do not need dozens of metrics. These eight, reviewed weekly per style and per job worker, explain most of the margin movement in a garment or textile unit. Set your own targets from your current baseline once the data is being captured reliably.
| KPI | How It Is Calculated | What It Tells You |
|---|---|---|
| Actual vs costed consumption | Metres consumed per piece against the costing sheet, by size | Whether quotes reflect real fabric use |
| Marker efficiency | Fabric area used by panels divided by fabric area laid | How well each lay uses the fabric |
| Process loss by job worker | Quantity received divided by quantity sent, per lot | Which processors return less than the agreed norm |
| Ageing of job work challans | Days since dispatch for open challan balances | GST exposure and stuck material |
| Cut-to-ship ratio | Pieces shipped divided by pieces cut | Losses between cutting and packing |
| Rejection by defect and stage | Rejected pieces grouped by defect type and stage | Where quality effort should go |
| On-time delivery | Orders shipped by the promised date divided by orders due | Planning and job work reliability (see OTIF) |
| Sell-through and dead stock | Sold quantity and ageing stock by style, size and colour | What to buy and produce next season |
How ERPDrive Runs a Textile or Garment Unit End to End
Step 1: Set Up Styles, the Size-Colour Matrix and Cutting BOMs
Define each style with its size list, colour list, season and collection, and let ERPDrive generate the SKUs. Attach a cutting BOM with metres per piece for each size, plus trims and packing material.
Step 2: Receive Fabric by Roll, Lot and Shade
Record every roll at GRN with metres or kilograms, lot, GSM and shade. Purchase orders carry the latest negotiated rate so costing stays current.
Step 3: Plan, Cut and Track Bundles Through Every Stage
Sales orders become production orders. Cutting records markers and actual consumption, and bundle barcodes move cut pieces through stitching, finishing and packing with work in progress visible by stage.
Step 4: Send Job Work on Challans and Keep ITC-04 Ready
Fabric, panels and garments go to dyers, printers, embroiderers, fabricators and washers on GST job work challans. Receipts close each challan, process loss is measured per lot, and the ITC-04 working builds from these transactions.
Step 5: Dispatch, Invoice and Review Profitability
Orders ship with GST invoices, e-invoices and e-Way Bills. The Dispatch Delays, Low-Profit Orders, Purchase Cost Leakage and Cash Blocked in Inventory reports show where money is being lost, and accounts sync two ways with Tally.
How to Get Started: A Practical Rollout Sequence
- Clear your ITC-04 backlog first. List every open challan with every job worker and confirm balances with them, so the October return and the system start from the same numbers.
- Build the style master for the current season. Generate the size-colour matrix for running styles and enter metres per piece by size from your current markers.
- Receive fabric by lot. Start recording lot and shade on every new roll at GRN, and tag existing stock as you count it.
- Move all job work onto challans. Issue every outward movement on a job work challan and record part receipts against it.
- Start bundle tracking on one line. Scan bundles through stitching, finishing and packing on your highest volume line before extending it to others.
- Review the profit reports weekly. Go through dispatch delays, low-profit orders and blocked inventory with merchandising, production and purchase together.
For a wider view of ERP rollout in a factory, read our ERP implementation guide.
Frequently Asked Questions
When is ITC-04 due for a garment unit that sends fabric for job work?
It depends on turnover. Units with aggregate turnover above INR 5 crore file Form GST ITC-04 half-yearly, by 25 October for April to September and by 25 April for October to March. Units with turnover up to INR 5 crore file once a year, by 25 April. The return covers goods sent to and received back from job workers such as dyers, printers, embroiderers and fabricators.
What happens if fabric sent to a dyer or printer is not received back in time?
Inputs sent for job work must be received back within one year, and capital goods within three years. If they are not, the goods are treated as supplied by the principal on the date they were originally sent, and GST becomes payable on that deemed supply. Tracking challan ageing lets you chase returns before that happens.
How should a garment unit calculate fabric consumption per piece?
Calculate it per size from the marker, not as one average for the style. The marker for each lay shows how many metres were used for a given size ratio, and the actual fabric issued for that lay shows the real consumption. Comparing the two for every lot gives marker efficiency and cutting wastage, and costing future orders on the actual figure keeps quotes realistic.
Can an ERP handle fabric in metres or kilograms and garments in pieces?
Yes. ERPDrive supports dual units of measure: fabric is held in metres or kilograms with conversion, garments are held in pieces, and the cutting BOM links them through metres per piece for each size. Inventory views show both.
How does ERPDrive prevent shade variation within an order?
Each fabric roll is received with its dye lot and shade. When fabric is issued for a cutting order, ERPDrive suggests rolls from the same lot or matching shade band, and mixing lots needs an approval with a reason, so every order can be traced back to the lots it used.
Conclusion: Measure in Metres, Lots and Challans, Not Just in Pieces
A textile or garment unit that measures only fabric bought and pieces shipped cannot see where its margin goes. Marker consumption, the size-colour matrix, job work balances, process loss, shade lots, missing pieces, broken size sets and changing fabric prices each change the cost per piece, and each one needs textile-specific data to stay under control. Once production, stock and job work are recorded in metres per piece, lots and challans, the leaks become visible, and visible leaks get fixed. With the October ITC-04 deadline days away, job work is the best place to start.
ERPDrive gives Indian textile and garment manufacturers that visibility in one cloud ERP, from the style matrix and cutting BOM to lot and shade tracking, bundle-level WIP, job work challans and ITC-04, GST invoicing and profit reports. Book a free ERPDrive demo to see it on your own styles and job workers, or message us on WhatsApp to talk through your unit's setup.