How to Use ERP to Track and Cut Fabric Scrap Rates by Line

Scrap rates are not just material waste—they hide inefficiencies that eat margins

Every yard of fabric that ends up in the scrap bin carries more than its own cost. It includes the labour, utilities and machine time spent making it, plus the storage fees for the rejected rolls, the rework time if it’s salvaged, and the lost sales if the customer rejects the finished product. The problem is that most plants track scrap by total weight or value, not by where it happens. Without breaking it down by machine, operator and fabric type, you’re chasing symptoms, not causes.

Facteno’s production module lets you drill into scrap by the exact line, shift and batch where it occurred. That’s how you find whether a loom is misaligned, an operator is rushing through quality checks, or a particular dye batch is reacting poorly. The data doesn’t just show you the scrap—it shows you why it’s happening.

How to measure scrap by the real cost drivers, not just weight

Most plants measure scrap as a percentage of input material. That’s useful for suppliers, but it misses the second-order costs. For example:

• If a loom produces 10% more scrap when running at 90% speed, the extra waste isn’t just the fabric—it’s the extra labour and electricity used to push the machine that far.
• If an operator salvages scrap into lower-grade fabric, the cost isn’t just the material lost—it’s the rework time and the reduced sale price of the finished product.
• If a dye batch causes pilling in 5% of the rolls, the scrap is only part of the cost—the rest is the storage fees for the rejected rolls and the lost production time while the machine is cleaned and recalibrated.

Facteno’s costing module ties scrap to these hidden costs automatically. Instead of seeing ‘scrap = 8% of input,’ you see:

• Material cost of scrap: $X per batch
• Labour cost tied to the defective batch: Y hours at $Z/wage
• Machine downtime for rework or cleaning: A hours at $B/hour
• Storage fees for rejected rolls: C days at $D/day
• Lost sales from downgraded fabric: E units at $F/unit

Add these up, and the ‘8% scrap rate’ becomes a $1,200 hit per batch—not just a material loss. That’s the number that forces action.

Which machines and operators are the real scrap hotspots?

Not all scrap is equal. A tear in a single roll from a new loom is different from consistent edge fraying across three shifts on Machine 4. Facteno’s production analytics let you filter scrap by:

• Machine ID and model (e.g., ‘Loom 12 produces 30% more scrap than Loom 11’)
• Operator ID and shift (e.g., ‘Night shift operators salvage 15% of their scrap, day shift only 5%’)
• Fabric type and dye batch (e.g., ‘Polyester blend X always frays at the selvedge’)
• Time of day (e.g., ‘Scrap spikes at 3 AM when the air conditioning fails’)

For example, say your own scrap rate is 3% by weight, but Facteno shows:

Illustration: Scrap breakdown for a 5,000-yard batch of cotton poplin

• Material cost of scrap: 3% of $2,500 = $75

• Labour cost (operator + helper): 2 hours at $12/hour = $24

• Machine downtime (cleaning + recalibration): 1.5 hours at $80/hour = $120

• Storage fees (rejected rolls for 3 days): $40

• Lost sales (downgraded to lower grade): 50 yards at $1.50/yard = $75

Total cost per batch: $334 (not $75)

This is why you need per-line data. The loom with the highest scrap rate isn’t necessarily the problem—it’s the one where the scrap cost per batch exceeds your tolerance. Facteno flags these automatically.

How to spot when scrap is a process issue, not a one-off defect

Every plant has bad batches. The challenge is telling whether a defect is a random event or a sign of a failing process. Facteno’s defect capture module (part of Quality Control) lets you log defects by type, size and location on the roll. Combine this with production data, and you can answer:

• Is the defect clustered in one area of the roll (e.g., always near the selvedge)? If so, it’s likely a machine misalignment.
• Does the defect appear in every batch from a specific dye supplier? If so, it’s a material issue.
• Does the defect only happen when Operator 4 runs the loom? If so, it’s training or fatigue.
• Does the defect worsen over time (e.g., more pilling in later batches)? If so, it’s machine wear or a buildup of residue.

For instance, if you see ‘edge fraying’ logged on 80% of rolls from Loom 7 in the last week, but only 5% from other looms, you’ve got a process issue. If it’s just one roll out of 50, it’s likely a one-off. Facteno’s dashboards show these patterns in real time, so you don’t wait for the monthly report to act.

What are the trade-offs in reducing scrap—and how to balance them?

Cutting scrap isn’t always the cheapest fix. For example:

Facteno’s production module lets you model these trade-offs. For example, if slowing Loom 7 by 10% cuts scrap by 20%, but that costs you 500 yards of output per shift, you can compare:

• The scrap cost saved ($334 per batch × 20% = $668)
• The lost output cost (500 yards × $1.20/yard = $600)
• The extra labour cost (0.5 hours × $12 = $6 per batch)

In this case, the net gain is $62 per batch—but only if the scrap reduction holds. Facteno tracks whether the fix works or if the problem shifts elsewhere.

How to tie scrap data to financials before it hits the P&L

Scrap shows up in the accounts as a material cost, but its real impact is spread across labour, overheads and lost sales. Facteno’s Finance module posts scrap costs to the correct accounts automatically, so you see:

• Direct material waste (COGS)
• Labour tied to defective batches (payroll)
• Machine downtime (overheads)
• Storage and rework (WIP)
• Lost sales (revenue)

For example, if a dye defect causes 10% scrap in a $5,000 batch, the P&L might only show a $500 hit—but the actual cost is:

• $500 material
• $300 labour (operator + helper)
• $200 machine downtime
• $150 storage fees
• $400 lost sales (customer rejects downgraded fabric)
• Total: $1,550

Facteno’s costing module (Product Costing) builds this into the batch record, so you know the true cost before the invoice is raised. This is how you stop scrap from hiding in ‘other expenses’ or ‘unallocated overheads.’

What to do next week—without disrupting production

You don’t need to overhaul your system to start cutting scrap. Here’s what to do in the next seven days:

1. Pull a scrap report by machine and operator for the last month. Use Facteno’s Production module to filter by:
• Top 3 machines with the highest scrap cost per batch
• Top 3 operators with the most rework or salvage
• Top 3 fabric types with the worst defect patterns
2. Pick one hotspot and log defects for a week. Use the Quality Control module to record:
• Defect type (e.g., tear, pilling, stain)
• Location on the roll (edge, centre, random)
• Time of day it occurred
3. Compare scrap costs with your tolerance. Use the costing module to calculate the true cost of scrap per batch (material + labour + downtime + storage + lost sales). If it’s over your target, flag it for action.
4. Schedule a 30-minute review with your production and quality teams. Bring the data, not assumptions. Ask: ‘What’s the most likely cause of this pattern?’ and ‘What’s the quickest fix to test?’
5. Test one small change. For example:
• Adjust loom tension on the worst machine
• Add an extra quality check for the worst operator
• Switch to a different dye supplier for the worst fabric type
6. Measure the result in two weeks. Use the same report to see if the scrap cost per batch drops. If not, try the next fix.

This isn’t about eliminating scrap overnight—it’s about finding the leaks and plugging them one at a time. Facteno gives you the data to do it without guesswork.

Related reading: How ERP Stops Fabric Defects Before Cutting Starts.