Batch Production

Batch production sits between one-off job production and continuous flow. A quantity of material is processed together as a unit, start to finish, and only then does the machine take the next quantity. A dye vat is the purest example: fabric goes in, a recipe runs for several hours, fabric comes out, the machine is cleaned, and the next batch begins.

The consequence that matters commercially is that a batch has a *fixed cost that does not shrink with the quantity in it*. The dyestuff scales with the fabric. The water, the steam, the electricity, the labour, the machine hours and the cleaning between batches largely do not. A half-empty vat costs nearly what a full vat costs.

Minimum batch size, and why small orders are expensive

Dyeing machines have a nominal capacity and a minimum practical load — usually expressed as a liquor ratio, the weight of water per unit weight of fabric. Load too little fabric into a large machine and the liquor ratio goes wrong: the dyestuff behaves differently, levelness suffers, and the shade you get is not the shade the recipe predicts. So there is a floor below which a given machine cannot dye reliably at all, and a range below which it can dye but uneconomically.

This is the whole explanation for something that mystifies buyers constantly: the re-order that costs more per metre than the original order. A buyer who ordered 3,000 metres and now wants 400 more of the same shade is not asking for a small job. They are asking for a full dye cycle — recipe, vat, water, steam, labour, cleaning, and a lab dip to match the original shade — carried out on 400 metres. The per-metre cost can be a multiple of the original, and the mill is not being opportunistic when it says so.

The planning response is batch consolidation: combining requirements for the same shade and quality from several orders into one batch. That is a genuine saving, and it is also how shade-continuity problems get created, because the consolidated batch now serves multiple customers and every one of them expects continuity within their own order. Consolidation without [lot traceability](/glossary/lot-traceability) is a way of trading a cost problem for a quality problem.

The batch is the unit of shade risk

Each dye batch produces one [dye lot](/glossary/dye-lot). Within it, shade is as consistent as the machine and the recipe allow. Across batches, it is not — even the same recipe on the same machine the next day drifts, because water chemistry, dyestuff batch and temperature profile all vary slightly.

This means the batch is the natural unit of shade risk, and batch size therefore has a quality dimension as well as a cost one. An order dyed in one batch is a single shade problem or no problem. The same order split across three batches is three lots that must be shade-banded, allocated to cutting in a controlled way, and reconciled if a lot falls outside tolerance. Every additional batch is another opportunity for a shade break.

So the ideal is that an order's fabric requirement fits a batch size cleanly. In practice it rarely does, and the planner's real job is deciding *where the batch boundary falls* — because if it has to fall somewhere, it should fall between two garments, not down the middle of one.

Batch scheduling: sequence is the whole game

Batch scheduling is not just about which orders go where. It is about the order in which batches run, because changeover cost between batches depends heavily on what ran before.

Dyeing a pale shade in a machine that just ran black requires a thorough clean; running black after pale requires almost none. So dye houses sequence batches light-to-dark within a machine and clean only at the wrap-around, which can substantially reduce total changeover time across a shift. The same principle applies to fibre type and to recipe class — grouping similar chemistry together avoids repeated machine preparation.

This is why batch scheduling cannot be solved by a first-come-first-served queue, and why it interacts directly with [capacity planning](/glossary/capacity-planning): the effective capacity of a dye house is not the sum of its vat volumes, it is the sum of its vat volumes minus whatever the sequencing decisions cost you in changeovers.

Batch records and what has to be captured

A batch record is the process history of a lot, and it is the document that quality investigation, shade dispute and compliance audit all fall back on. It should carry the recipe and its version, the machine and vat, the actual load weight, the greige rolls or yarn lots consumed, the process curve (temperature and time as actually run, not as planned), the chemicals and dyestuffs issued with their own supplier lots, the operator and shift, and the shade result measured against the standard.

The critical distinction is between the recipe as specified and the process as actually run. A batch that came out off-shade almost always did so because something in the actual differed from the specified — a temperature held too long, a chemical added late, a load weight that changed the liquor ratio. If only the specification is stored, that investigation cannot be conducted.

Vastra ERP treats the dye batch as a first-class production object with its own recipe version, machine, load, consumed lots and shade result, links it to the [rolls](/glossary/fabric-roll) it produced and the orders they were allocated to, and schedules batches against vat capacity and changeover sequence within [production planning](/features/production-planning).