How to Cut Fabric Rejections with ERP Data

Fabric rejections cost more than scrap

Rejected fabric is not just a pile of waste. It ties up storage space, delays orders and forces rework that eats margins. The real cost is not the material—it is the lost production time, the extra labour and the customers who cancel when deliveries slip. Most plants track scrap rates but ignore the hidden costs of rework and storage. ERP systems like Facteno change that by linking quality data to production and finance.

The first step is to stop treating rejections as an accounting problem. They are a production problem. If your QC team logs defects on paper or in a spreadsheet, you are already losing control. Defects spread between batches, operators switch machines without updating records, and by the time the accountant reconciles the stock ledger, the fabric has already been reworked—or worse, sold as seconds.

How to track defects before they become rejections

Defects start long before the final inspection. A warp break in weaving, a dye lot mismatch in finishing or a stitching fault in the cutting room all increase the chance of rejection. The key is to capture these defects in the ERP at the point they happen, not after the fact. Facteno’s quality control module lets you log defects by machine, shift and operator, with photos attached to each entry. This is not just a record—it is a warning.

For example, say your own scrap rate is 3 per cent, but your rework rate is twice that. That means for every metre of fabric you scrap, two metres are sent back for fixing. If your fabric costs $4 per metre to produce (including labour and overheads), then every 1 per cent of rework costs $80 per thousand metres in extra labour and machine time. The ERP does not just tell you the rejection rate—it shows you where the money is leaking.

To set this up, start with one critical process—perhaps dyeing or weaving—and log every defect for a week. Use the ERP to flag batches that exceed your target defect rate before they move to the next stage. This is not guesswork. It is data-driven triage.

What happens when you ignore defect tracking

Without defect tracking, rejections become a black hole. Fabric moves between departments, operators forget which batches had issues, and by the time QC catches a problem, it has already cost you. Here is what goes wrong:

• Defective batches are mixed with good ones in storage, increasing the chance of further damage or contamination.
• Rework orders are logged late, so the machine schedule fills with unplanned jobs and delays other orders.
• Customers receive fabric that does not match their samples, leading to complaints or returns.
• The accountant reconciles the stock ledger against production records and finds a discrepancy that takes a week to resolve.

Facteno stops this by linking quality data to the production schedule. If a batch fails inspection, the system blocks it from being issued to cutting or packing until it is either reworked or scrapped. This is not just a quality check—it is a production rule.

How to use batch-level costing to find the real cost of rejections

Most plants calculate scrap as a percentage of material cost. That is too late. By the time you know the fabric is rejected, you have already spent money on labour, utilities and machine time. Batch-level costing in Facteno shows the full cost of a rejection, including:

• The material cost of the fabric (yarn, dyes, finishes).
• The labour cost of the operators who worked on it.
• The machine cost per hour, including energy and maintenance.
• The overhead cost of floor space, storage and QC time.

Illustration: Say your own fabric batch costs $12 per metre to produce (including all overheads). If a 500-metre batch is rejected, the scrap cost is not just the material—it is $6,000 in lost production. If that batch had been caught earlier, the cost might have been $2,000 in rework instead. The ERP does not just tell you the rejection rate—it shows you the cost per metre of fixing it at each stage.

Use this data to set rejection thresholds. For example, if rework costs more than 30 per cent of the batch value, scrap it and log the defect as a process failure. This is not a rule you invent—it is a number you calculate from your own data.

How real-time alerts stop defective batches before cutting

Most quality checks happen at the end of the line. By then, the fabric has already been cut, packed and shipped—or worse, sold as seconds. Real-time alerts in Facteno stop this by flagging defects as they happen. For example:

• If a weaving machine logs more than two warp breaks per shift, the ERP sends an alert to the production manager before the batch is rolled.
• If a dye lot does not match the target shade, the system blocks the batch from being released to finishing.
• If a stitching fault rate exceeds 0.5 per cent in cutting, the batch is held for re-inspection.

These alerts are not manual—they are triggered by the ERP when the defect rate crosses your own threshold. The system also logs who acknowledged the alert and what action was taken. This creates a paper trail that ties quality to accountability.

To set this up, start with one machine or process where defects are costly. For example, if your own cutting room loses 1.5 per cent of fabric to stitching faults, set an alert at 1 per cent. When the ERP flags the batch, investigate whether it is a machine issue, an operator error or a material problem. The goal is not to punish the operator—it is to stop the defect before it spreads.

What to do when the ERP shows a defect trend

ERP data does not just flag individual defects—it shows trends. For example:

If the ERP shows a rising trend in warp breaks on Machine 4, the issue is not just the machine—it is the thread tension, the operator training or the yarn quality. Dig into the data to find the root cause. For example:

• Check the maintenance log for Machine 4 to see if tensioners were adjusted recently.
• Review the operator’s last three shifts to see if warp breaks cluster at the start or end of their shift.
• Compare the yarn batch used in the defective rolls against previous batches to see if the supplier changed the twist.

Facteno’s quality control module lets you attach notes, photos and supplier data to each defect. This turns a rejection into a lesson, not just a cost.

How to integrate quality data with production scheduling

Quality data is useless if it does not change what you produce. Facteno links defect rates to the production schedule so you can adjust batch sizes and priorities in real time. For example:

• If the ERP shows that 15 per cent of your dye batches fail shade matching, reduce the batch size for new colours until the process is stable.
• If stitching faults rise when a new operator takes over, assign them a mentor or reduce their workload until their defect rate drops below the threshold.
• If a supplier’s yarn consistently causes warp breaks, switch to a different supplier for the next production run.

The key is to use the ERP to reschedule work before defects become rejections. For example, if your own target defect rate is 0.3 per cent but Machine 3 has a 0.8 per cent rate this week, move the next batch to Machine 1 until the issue is fixed. This is not guesswork—it is data-driven scheduling.

To set this up, start with one process where defects directly affect yield. For example, if your own finishing room loses 2 per cent of fabric to shrinkage defects, use the ERP to track which operators and machines have the highest rates. Then adjust the schedule to balance the workload.

What to do next week

Start small. Pick one machine or process where defects are costly—perhaps dyeing or weaving—and log every defect for a week. Use the ERP to:

• Set a defect threshold (e.g., no more than two warp breaks per shift).
• Flag batches that exceed the threshold before they move to the next stage.
• Calculate the cost of rework for those batches (labour, machine time, storage).
• Adjust the schedule to avoid sending defective batches to cutting or packing.

Do not try to fix everything at once. The goal is to prove that the data works before you expand it to other processes. If the ERP catches three avoidable rejections in the first week, you have already saved enough to justify the cost.

Next, review the defect trends with your production manager and QC team. Ask:

• Which defects cost the most to fix?
• Which machines or operators have the highest rates?
• What changes would stop these defects before they happen?

Facteno’s quality control module and production planning features are designed to answer these questions with data, not guesses. [See how it works in a live demo](https://facteno.com/live-demo).

Related reading: How to Cut Fabric Rejections with ERP Data: A Plant Manager’s Guide.