How ERP Tracks Fabric Rework Costs—and Cuts Them

Fabric rework costs do not appear on invoices. They hide in extra dyehouse runs, stitching rework, and the time operators spend sorting defective rolls. The only way to find them is to track defects from the moment they are logged to the moment they leave the factory—and ERP does that by tying defects to batches, not just to orders.

Most plants track defects in spreadsheets or on paper cards. That works until defects slip into finished goods, or until a supplier ships a bad batch that no one notices until the cutting table. ERP stops that by automating defect capture, linking defects to batches, and showing which machines, operators and suppliers cause the most rework.

Why Fabric Rework Costs Are Harder to Spot Than Scrap

Scrap is easy to measure: you weigh the bin at the end of the shift. Rework is not. A defective roll might get re-dyed, then re-stitched, then repacked—each step adding labour, chemicals and machine time. The cost does not appear in one ledger; it is spread across dyehouse logs, stitching tickets and packing slips.

ERP solves this by creating a rework chain: when a defect is logged, the system records the batch number, the defect type, and which stage it was found. If the same batch fails again after rework, the system flags it as a repeat. This is how you spot suppliers who send inconsistent dye lots, or machines that wear out yarn unevenly.

For example, say your own scrap rate is 3 per cent of input fabric. That is a known cost. But rework adds another 1.5 per cent of input fabric that gets reprocessed—once, twice, or three times—before it either passes inspection or ends up as scrap. The 1.5 per cent does not show up in your scrap bin; it shows up in:

• The extra dyehouse time logged against the batch.
• The stitching machine hours added to the order.
• The operator wages for sorting and respreading.
• The chemical usage from failed dye runs.

Without ERP, these costs sit in different logs. With it, they appear in a single cost report per batch.

How to Link Defects to Batches—Not Just to Orders

Most plants log defects against orders, not batches. That means if Order 456 uses Fabric Batch A and Fabric Batch B, and Batch B has defects, the system does not tell you which part of the order is affected. You only find out when the cutting table rejects pieces—and by then, the fabric is already cut.

ERP fixes this by attaching defect records to batch numbers, not order numbers. When a defect is logged at the inspection table, the system records:

• The batch number (e.g., DYE-2024-0542).
• The defect type (e.g., colour variation, yarn slub, seam pucker).
• The stage where it was found (e.g., after dyeing, after stitching).
• The quantity affected (e.g., 12 metres of a 50-metre roll).

This lets you run a report like “Show me all batches with more than 5 per cent defects in the last 30 days”. You then see which suppliers or machines are causing the most rework—and act before the next batch arrives.

For instance, if Supplier X’s dyehouse consistently produces batches with 8 per cent colour variation, you can renegotiate their contract or switch to Supplier Y before the next order. Without batch-level tracking, you only find this out when the fabric arrives—and by then, it is too late to avoid rework.

Automating Defect-to-Rework Tracking Saves Time—and Stops Defects Slipping Through

Manual defect logging is slow. Operators write defects on paper cards, then someone enters them into a spreadsheet. By the time the data reaches the production manager, the batch is already in stitching—or worse, it has been packed and shipped.

ERP automates this by letting operators log defects directly into the system from a tablet at the inspection table. The defect is linked to the batch, and the system:

• Flags the batch for rework if defects exceed a threshold (e.g., 3 per cent).
• Blocks the batch from moving to the next stage until rework is approved.
• Tracks how many times the same batch fails rework (a sign of poor quality control).

This stops defects from slipping into finished goods. For example, if a batch fails dyeing twice, the system can auto-reject it and send it back to the supplier—or route it to a different dyehouse. Without automation, this decision sits with a supervisor who may not notice the pattern until it is too late.

Facteno’s Quality Control module does this by tying defects to batches and stages. You set rules like “If more than 5 per cent of a batch has defects, require supervisor approval before release”. The system then enforces it.

How Production Planning Uses Rework Data to Reschedule Batches

Production planners schedule batches based on order deadlines, not defect history. That means a batch with a known rework problem gets mixed in with good batches—and when it fails, the whole line slows down.

ERP stops this by feeding rework data into the planning screen. When you pull up the production schedule, you see:

• Batches with high defect rates (coloured red).
• Batches that failed rework more than once (coloured orange).
• Batches from suppliers with poor quality records (flagged with a warning).

You can then reschedule these batches to run first, so if they fail, they do not hold up the rest of the line. For example, if Supplier Z’s fabric consistently has 7 per cent seam pucker, you might:

• Run their batches on the slowest stitching machine to minimise downtime.
• Assign extra quality inspectors to those batches.
• Hold their fabric in quarantine until defects are below 3 per cent.

Facteno’s Production module integrates with Quality Control, so the planning screen shows defect history alongside machine availability and operator shifts. This is how you stop rework from disrupting the schedule.

The Hidden Costs of Rework—and How ERP Exposes Them

Rework costs include:

• Extra dyehouse time (chemicals, water, labour).
• Extra stitching machine hours (thread, needles, operator time).
• Extra packing and labelling (if the batch is repacked).
• Storage costs for batches waiting for rework.
• Lost sales if the rework delays shipment.

These costs do not appear in one ledger. The dyehouse logs extra runs as “rework hours,” stitching logs them as “additional stitching,” and packing logs them as “repacked batches.” ERP combines them into a single cost per batch.

For example, say a 50-metre roll fails dyeing and requires a second run. The cost breakdown might look like this:

Facteno’s Product Costing module adds these up per batch, so you see the full cost of rework—not just the scrap bin weight.

Where Most Plants Go Wrong with Rework Tracking

Plants often track rework in one of two ways—and both fail:

• Spreadsheets. Operators log defects on paper, then someone enters them into Excel. By the time the data reaches management, it is outdated. Defects slip into finished goods, and the spreadsheet does not show which batches are at risk.
• Isolated QC software. Some plants use a standalone defect-tracking tool that does not link to production or finance. The QC team sees defects, but the production manager does not—and the cost still hides in different ledgers.

The fix is to use ERP, where:

• Defects are logged at the source (inspection table, cutting table, packing station).
• Defects are tied to batches, not just orders.
• Rework costs appear in the same reports as material and labour costs.
• Production planning uses defect history to reschedule batches.

Most plants start by tracking defects in one department—say, dyehouse or stitching—and then expand. Facteno’s implementation plan stages this by module, so you do not have to rip and replace everything at once.

What to Do Next Week—Without Waiting for ERP

You do not need ERP to start cutting rework costs. Here is what to do next week:

• Pick one machine or supplier with the highest defect rate. Log every defect for that batch on a whiteboard or tablet—even if you do it manually.
• Measure how many times that batch fails rework. If it fails twice, note the cost of the second run (chemicals, labour, machine time).
• Talk to the operator who handles that machine. Ask: “What changes would stop these defects?” (Often, it is machine maintenance or operator training.)
• Run a trial with the fix—say, adjusting tension on the stitching machine—and track defects again. If they drop, scale the fix to other machines.

This proves the method works before you invest in ERP. Once you see the cost of rework in real numbers, you can decide whether to automate it with Facteno’s Starter plan ($149 per month) or expand to full tracking.

Related reading: How to Track Fabric Defects with ERP Before Cutting Begins.