How ERP Batch Sizing Optimization Cuts Fabric Waste and Costs

Fabric waste and overproduction are not inevitable

Most fabric plants run batches by habit: a fixed yardage per loom, a set number of rolls per dyehouse, or a standard carton size for stitching. The problem is that habits do not account for defects, machine downtime, or changes in buyer orders. Every extra yard cut from a flawed batch, every roll left sitting because the next order changed, and every shift spent reworking fabric that should have been scrapped earlier—these are costs that show up nowhere until the month-end spreadsheet. ERP batch sizing optimization fixes this by tying batch size directly to real data: defect rates, order lead times, and machine efficiency. It does not eliminate waste; it makes waste visible so you can act on it.

The payoff is not just less scrap. It is also less cash tied up in half-finished fabric, fewer rushed deliveries to meet deadlines, and a clearer picture of which fabrics are actually profitable at your plant’s scale.

Why fixed batch sizes hide more costs than they save

Fixed batch sizing—producing the same yardage or roll count regardless of order size or fabric quality—seems simple. In practice, it creates three silent cost drivers:

• Defects spread across batches. If 3% of your polyester is flawed but you run 5,000-yard batches, you either scrap 150 yards per batch or mix flawed fabric into good orders, forcing rework later.
• Storage space fills with “just in case” inventory. A buyer cancels an order, but you already dyed 2,000 yards of that shade. Now it sits until the next matching order—or until it spoils.
• Machine time is wasted on setups. Changing looms or dye vats for small batches burns hours that could go to higher-margin work.

These costs do not disappear if you track them in spreadsheets. They get buried in “overhead” or “unplanned waste,” making it hard to see which fabrics or processes are truly efficient.

Facteno’s batch sizing tool changes this by linking batch size to:

• Defect rates per fabric type (from your quality logs).
• Order lead times (from your sales and production schedules).
• Machine changeover times (from your production routing).

For example, your own scrap rate is 3% on cotton blends but 1% on polyester. A fixed 5,000-yard batch of cotton yields 4,850 good yards, while the same batch of polyester yields 4,950. The difference is 100 yards per batch, times every loom in the plant, times every month.

Facteno calculates this automatically when you set up batch rules. You define the defect rate per fabric, and the system suggests batch sizes that minimise waste. You can override it for rush orders, but the override becomes a data point: “We ran small batches here because the buyer changed the spec.” Over time, the system learns which overrides work and which do not.

How dynamic batch sizing cuts inventory holding costs

Inventory holding costs include:

• Financing charges on fabric tied up in WIP (work in progress).
• Insurance and taxes on stored rolls.
• Spoilage or obsolescence if fabric is unused within shelf life.
• Labour to move, rehandle, or recount batches that sit too long.

A fixed batch size forces inventory between stages. For example, if your dyehouse runs 10,000-yard batches but stitching needs 2,000-yard cuts, you either:

• Store 8,000 yards of dyed fabric (tying up cash and space), or
• Cut the 10,000-yard batch into smaller rolls, adding handling time and damage risk.

Illustration: Your stitching line cuts fabric in 1,500-yard lots. Facteno’s batch sizing tool suggests dyeing 1,500-yard batches directly, cutting handling by 85% and eliminating intermediate storage.

Dynamic batch sizing reduces labour, damage claims, and improves order flexibility. Smaller batches free dyehouse capacity for reallocation without waiting for full runs.

It requires real-time data on:

• Yardage needed for next cutting order (sales/production modules).
• Fabric defect rates (quality logs).
• Machine changeover times (production routing).

Facteno pulls this from existing data, preventing manual re-entry. It also flags inefficiently small batches (e.g., 500-yard orders with high loom changeover times), avoiding the ‘small order trap’ of increased scrap and rework.

When on-time delivery depends on batch size—and how to fix it

On-time delivery isn’t just about meeting ship dates—it’s about meeting them efficiently. Smaller batches often backfire:

• They increase setup time per yard, reducing total output.
• Defects go unnoticed until later, requiring costly last-minute rework.
• Inventory must be held between stages, delaying subsequent orders.

For example, a 2,000-yard batch may seem efficient, but if the buyer cancels half, you’re left with a 1,000-yard roll requiring storage or rework—delaying the next job. Facteno’s batch sizing tool mitigates this by:

• Cross-checking pending orders before recommending batch sizes.
• Flagging inefficient setups (e.g., “This 800-yard order adds 2 hours of setup; combine with the 1,200-yard order due next week”).
• Aligning batch sizes with lead times for reliable delivery promises.

Small batches aren’t banned—they’re optimized. For instance, a Friday rush order for 600 yards might run immediately if:

• The fabric has low defects (no rework risk).
• The loom is already set up (no extra changeover).
• The stitching line has Monday capacity (no delay risk).

If conditions fail, the system suggests waiting for a full batch or using an alternative loom. This reduces “fire drill” orders, stabilizes schedules, and lets sales teams provide accurate lead times—boosting buyer trust and cutting last-minute changes.

The hidden cost of mixing good and flawed fabric in one batch

Most plants sort fabric by quality after production, not before. This means a batch with 5% defects is either scrapped entirely (wasting good fabric) or mixed with good fabric, forcing later sorting and rework.

Facteno’s batch sizing tool reduces inefficiency by:

• Splitting batches by defect rate. For example, if 3% of polyester is flawed, the system suggests separate batches: one for good fabric and one for flawed, marked for rework or scrap.
• Linking defect rates to batch size. A fabric with a 1% defect rate can run in larger batches than one with a 5% rate.
• Flagging when a batch is too small to justify sorting, such as a 200-yard batch with 2% defects.

This requires accurate defect data, pulled from quality logs. If inspectors record defects per roll, the system adjusts batch sizes automatically. For example:

Illustration: Your quality logs show 4% of cotton blends have “tight weave” defects. Facteno’s tool suggests running cotton blend batches in 3,000-yard lots, with a 120-yard sub-batch (4%) set aside for rework, cutting sorting time by 60%.

The system ties batch sizes to actual defect patterns, adjusting if rates change due to new suppliers or machine issues. This prevents “surprise scrap” that harms margins.

How to spot the trade-offs in batch sizing—and avoid the wrong fixes

Batch sizing is a trade-off between four factors:

• Waste (scrap and rework).
• Setup time (loom or dyehouse changeovers).
• Inventory holding costs.
• Delivery speed.

Most plants focus on one or two of these and ignore the rest. For example:

• A plant might reduce setup time by increasing batch sizes, but this increases inventory and waste.
• Another might cut waste by running small batches, but this slows down delivery and raises setup costs.

Facteno’s batch sizing tool helps you see these trade-offs clearly. For instance:

To use this table, ask: “Which of these costs is hurting us most right now?” If your issue is high scrap rates, the tool will suggest smaller batches with stricter defect sorting. If your issue is slow delivery, it will recommend larger batches with buffer time for changes.

However, the tool cannot fix poor data. If your defect logs are incomplete or your lead times are guessed, the batch sizes will be wrong. Facteno’s batch sizing module requires:

• Accurate defect rates per fabric type (from your quality module).
• Real lead times per order (from your production scheduling).
• Actual setup times per machine (from your production routing).

If these are missing, the system will prompt you to fill them in—before suggesting batch sizes. This forces you to clean up your data, which is often the real bottleneck in “optimisation” projects.

What to do next week: Three practical steps

You do not need to overhaul your entire production process to start using batch sizing. Begin with these three steps:

1. Audit one fabric type. Pick the fabric with the highest scrap rate or most frequent order changes. Check your quality logs for defect patterns, your sales records for order sizes, and your production logs for setup times. Use this data to run a manual batch size calculation (or ask Facteno’s support team to show you how the tool works with your figures).
2. Test two batch sizes. For the next production run of that fabric, try two batch sizes: one based on your current habit, and one suggested by the data. Track the results—scrap rate, setup time, and delivery delay—and compare them to your usual output.
3. Adjust your approval rules. If dynamic batch sizing works for that fabric, update your production approval workflows to allow smaller or variable batch sizes. Use Facteno’s dynamic approvals to set limits (e.g., “Batches under 2,000 yards need manager approval”). This prevents operators from bypassing the new rules.

Do not try to apply this to every fabric at once. Start with one, prove the savings, then expand. The goal is not to eliminate all waste—it is to make waste visible so you can act on it.

Related reading: Optimize Fabric Batch Sizing with ERP to Cut Waste and Costs.