Industries · PPC & MRP 15 min read

Process & batch manufacturing planning

A practical guide for planners in chemicals, food, pharma, paints and rubber — planning whole batches to a recipe or formula, netting ingredients against stock, releasing batch process sheets, and scheduling runs against real capacity and seasonal demand.

15 min read Vidya Kathare · July 18, 2026 Industry guide
The batch plan-to-make cycle
01
Demand plan
Sales/production plan, incl. seasonal peak
Captured
02
Explode recipe
Ingredients & packing from the formula BOM
Exploded
03
Net & size batches
Less stock; round to whole practical batches
Netted
04
Buy + make
PRs for ingredients, WOs for batch runs
Split
05
Schedule & book
Sequence runs; consume & complete vs plan
Made

What process & batch planning means

Process and batch manufacturing planning is material requirements planning (MRP) and production planning and control (PPC) for makers of chemicals, food, pharmaceuticals, paints, adhesives, rubber compounds and similar products that manufacture in batches to a recipe or formula. It takes demand as a sales or production plan, explodes each product through its recipe bill of materials to gross ingredient and packing-material requirements, nets those against stock and open supply, and turns the shortfall into purchase requisitions for raw material and work orders for batch runs. It then schedules those batches — each carrying a batch process sheet — and tracks completion and consumption back against stock.

The defining idea is the batch. You do not make one piece; you make a reactor-load, a mixer-load or a kettle-load of a given size, to a formula of ingredients in ratio, measured in kilograms and litres rather than counts. So planning works in whole batches against real ingredient stock and finite process capacity, not piece by piece. This guide sits alongside the process & batch manufacturing planning software product page, which shows the screens; here we explain the method.

The heart of it
A batch plan is a recipe scaled to demand: take the month's orders, work out how many whole batches of each product that means, check you have the ingredients in stock, and buy only what is short — then book what each batch actually consumed.
Get the recipe and the batch size right and the buying and the make plan fall out cleanly; get them wrong and you either over-buy ingredients that expire or run a batch short of one component.

How batch planning differs from discrete

Discrete manufacturing counts individual pieces assembled from components; batch manufacturing mixes or processes quantities of material to a recipe. The differences are practical and they all touch planning.

AspectDiscrete manufacturingProcess / batch manufacturing
BOM isA list of parts assembledA recipe / formula of ingredients in ratio
Output isA count of finished piecesA batch of a given size (kg / litres)
Units areEach / numberWeight, volume, sometimes with yield loss
Run sizingAny quantityRounded to whole, practical batch sizes
ConstraintsMachine / assembly capacityProcess capacity, plus packing on the other side
Netting still appliesYes — explode demand, net against stock and open supply, split into buy and make; it just operates on batches and recipes instead of parts and assemblies

The through-line is important: the MRP discipline is the same. Fast Planning serves discrete and process manufacturers on one engine, because explode-net-split-schedule works whether the BOM is a parts list or a formula. What changes is that the plan thinks in batches and ingredient quantities, and that packing material — bottles, cartons, labels — is netted and bought alongside the ingredients, because a batch you cannot pack is not a batch you can ship. See the foundations in what is production planning software?

Recipe / formula BOMs and batch sizing

In Fast Planning the recipe or formula is held as a bill of materials, and MRP explodes each product's batch demand through it to derive gross ingredient and packing requirements. Because the recipe is the BOM, a change to the formula — a reformulation, a substituted ingredient, a revised ratio — flows straight into the next planning run, exactly as an engineering change would in a discrete plant. The netting, the purchase requisitions and the batch work orders update from the recipe in force.

The distinctive planning judgement is batch sizing. A net requirement rarely lands on a whole batch, so the plan rounds it up to a practical run size — the reactor or mixer's working volume, or a minimum economic batch. That rounding decision ripples: it sets how much ingredient you actually consume, how much finished product you hold afterwards, and whether short-shelf-life stock will be used before it ages. Planning the number of whole batches, rather than an abstract quantity, is what keeps a process plan grounded in what the plant can actually run.

Ingredients (buy)

Raw chemicals, actives, base materials short of stock become purchase requisitions — netted on the recipe, with lead time in view.

→ Purchase Requisition

Batch runs (make)

Each whole batch becomes a work order carrying a batch process sheet, consumed and completed back against stock.

→ Work Order

Packing (buy)

Bottles, cartons, labels and packing material are netted and bought alongside ingredients, so a batch can actually ship.

→ Purchase Requisition

The batch plan-to-make cycle

Whatever the product, a disciplined batch planning run moves through the same stages:

01
Demand plan
Sales/production plan for the horizon
02
Explode recipe
Ingredients and packing from the formula
03
Net vs stock
Less stock, open POs, open WOs, reserved
04
Size & split
Round to batches; PRs and batch WOs
05
Schedule runs
Sequence batches by priority on a Gantt
06
Book & complete
Consume, complete, plan vs actual

The instruction at the centre is the batch work order: an order to make one batch of a product, carrying a batch process sheet — the recipe quantities and the processing steps. Batch work orders are generated from the netted plan, printed individually or in batch, sequenced by priority, and tracked to completion as the floor books what each run consumed. On the buy side, the same run raises the purchase requisitions for ingredients and packing that flow to purchasing.

Planning batches and ingredient buying on spreadsheets?

We can show you a live plan — your demand exploded through your recipes, netted against ingredient stock, rounded to whole batches, and split into batch work orders and purchase requisitions — in 30 minutes, on your own products.

Get a demo

Netting ingredients and packing against stock

The MRP engine runs the same single calculation, applied to every ingredient and packing item as the recipe explodes:

The netting formula
Net requirement = Gross batch demand − Stock on hand − Open supply (open POs + open work orders + reserved stock)
Whatever is still short becomes a purchase requisition for an ingredient or packing item, or a batch work order for what you make in-house.

Every term is a live number. Gross batch demand is the ingredient and packing quantity implied by the whole batches you plan to run. Stock on hand is current free inventory of each ingredient and packing item. Open supply is everything already coming — purchase orders not yet received, batch work orders not yet completed, and stock reserved against another plan so it is not double-counted. Because netting reads live stock and each item's planning parameters, notably lead time for imported or long-lead actives, it decides not just how much to buy but when to raise the requisition so the ingredient lands before the batch is scheduled.

Between formal runs, a live reorder-level dashboard keeps watching free stock against each ingredient's reorder point and proposes a purchase requisition the moment it dips below — the day-to-day safety net that stops a fast-moving base chemical from silently running out mid-month. Stock can be reserved to a plan so two products do not both count on the same drum of solvent. See MRP — BOM Explosion & Netting and what is MRP software?

Batch process sheets and scheduling runs

Each batch work order carries a batch process sheet — the recipe quantities to charge and the processing steps to follow, printed as a job card so the shop floor makes the batch to the same formula every time. That is the process side of the plan; the control side is scheduling the runs. Because process plants have finite capacity — a fixed number of reactors, mixers or lines, each able to run one batch at a time — the batches have to be sequenced sensibly.

Fast Planning sets and re-sequences order and resource priority and lays the batch work orders out on a DayPilot Gantt board, while finite loading shows which line or vessel is the constraint and when it will next be free. Sequenced well, batches of similar products or colours can be grouped to reduce cleaning and changeover between runs — the process-industry equivalent of setup reduction. As each batch runs, the floor books consumption and completion, feeding plan versus actual: the planned batch against what was really produced and consumed, including yield. Barcode and machine-data capture make booking practical on the floor — see IoT / Industry 4.0 machine data, Scheduling & Priority (Gantt) and the production scheduling guide.

Seasonal and festival demand

Many process and batch products — foods, confectionery, beverages, paints, personal-care and FMCG lines — swing hard with the season and the festival calendar. Demand for a paint or a sweet builds ahead of Diwali; a cold drink peaks in summer; a gifting line spikes for a few weeks and then collapses. Planning has to ramp the plant up the slope and back down without either stocking out at the peak or leaving short-shelf-life stock unsold afterwards.

In Fast Planning a seasonal build is planned the same way as any demand — a sales or production plan for the horizon, netted against stock (the WSTK "with stock" sub-type). Because the plan is netted with stock in view, a planner can pre-build to stock ahead of a festival peak, running extra whole batches into inventory while the reorder dashboard keeps proposing ingredient and packing purchase requisitions as stock draws down. Planning the ramp on batches and on ingredient lead times — long for imported actives, tight for perishable inputs — is what turns a festival surge from a scramble into a schedule. See the wider chain in make-to-order planning for the confirmed-order side of mixed plants.

Illustrative — specialty chemical / coatings maker

Why recipe netting and batch scheduling belong in one system

Consider a coatings maker planning a pre-Diwali build across a dozen products, each to its own formula. The month's plan explodes through the recipes to gross ingredient and packing needs; netting against solvent, resin and pigment stock and open purchase orders turns shortfalls into purchase requisitions — with long-lead imported additives flagged early by lead time — while each product's demand rounds up to whole reactor batches that become work orders with batch process sheets. The batches are sequenced on the Gantt so similar colours run back-to-back to cut cleaning, and reserved pigment stops two products fighting over the same lot. As runs complete, consumption and yield book back for plan-vs-actual. Because recipe, netting, batch work orders and the schedule ride one engine reading the same stock, the plan holds the seasonal ramp without over-buying perishable input.

12
products, one batch plan
2
buy streams — ingredients & packing
1
shared recipe & stock engine

How Fast Planning implements it

Fast Planning Software for process & batch manufacturing is a working implementation of everything above, built by Improsys in Pune under the Fast Technology brand, deployable cloud or on-premise. Mapping the cycle to the product:

1
Capture demand. Enter the sales or production plan for the horizon — including a seasonal build — netted against stock (the WSTK "with stock" plan).
2
Explode the recipe. The MRP engine explodes each product's batch demand through its recipe / formula BOM to gross ingredient and packing requirements.
3
Net and reserve. Every ingredient and packing item is netted against stock, open POs, open work orders and reserved stock, with reservation so two products never double-count the same lot.
4
Size and split. Net requirements round up to whole practical batches; ingredient and packing shortfalls become purchase requisitions, and each batch becomes a work order carrying a batch process sheet.
5
Schedule, book and measure. Sequence batch runs by priority on a DayPilot Gantt against finite line capacity, book consumption and completion, and read plan-vs-actual and yield — with Dhruv AI adding insight summaries and plain-English questions over your planning data.

Because it runs on the shared platform, the same deployment hands batch work orders to Fast Production, reads and reserves ingredient stock in Fast Inventory, and feeds purchase requisitions into purchasing — with no interface and no re-keying. Plan releases and reorder warnings can push to the shop and to suppliers over WhatsApp, email and SMS.

Deployment, India context and pricing

Process and batch manufacturers are one of the core profiles Fast Planning is built for, alongside discrete make-to-order and component makers — the chemical, coatings, food, rubber and allied units of the Gujarat, Maharashtra and southern industrial belts. It is designed for small-to-mid Indian units running a single plant or a few plants, deploys cloud or on-premise on IIS and SQL Server, and is licensed as a branded single-tenant copy, so your recipes, batch sizes and ingredient stock stay in your own database.

Two India realities shape the plan. First, demand is seasonal: festival and weather-driven peaks mean the ability to pre-build to stock against a netted plan and a live reorder dashboard is central, not a nicety. Second, ingredient lead times vary widely — imported actives run long, perishable inputs run short — so netting that raises the requisition at the right time protects both the peak and the shelf life. Any GST classification and input-credit questions on your raw materials should be confirmed with your CA. Pricing is indicative in Indian Rupees and scales with users and modules; the practical step is a quote against your product and recipe count, and a short demo on your own data. See planning software pricing or talk to us.

Keep going — the production planning library
The pillar guide, sibling industry guides, and the product pages that show how Fast Planning implements each part.

Frequently asked questions

What is process and batch manufacturing planning software?

It is MRP and production planning and control (PPC) for makers of chemicals, food, pharma, paints, rubber and similar products that manufacture in batches to a recipe or formula. It takes demand as a sales or production plan, explodes each product through its recipe BOM to gross ingredient and packing requirements, nets those against stock and open supply, and turns the shortfall into purchase requisitions for raw material and work orders for batch runs. It then schedules the batches, carrying a batch process sheet, and tracks completion and consumption back against stock. The goal is to plan whole batches against real ingredient stock and finite process capacity, not piece by piece.

How does batch planning differ from discrete manufacturing planning?

Discrete manufacturing counts individual pieces assembled from components; batch manufacturing mixes or processes quantities of material to a recipe, so the bill of materials is a formula of ingredients in ratio, output is a batch of a given size, and quantities are weights or volumes rather than counts. Planning therefore works in batch sizes — you round a net requirement up to a whole practical batch — and cares about ingredient availability, minimum run sizes and process capacity. Netting, work orders and scheduling still apply, but they operate on batches and recipes instead of parts and assemblies.

Can it plan against a recipe or formula BOM?

Yes. In Fast Planning the recipe or formula is held as a bill of materials, and MRP explodes each product's batch demand through it to derive gross ingredient and packing-material requirements. Those are netted against current stock and open supply, so what is short becomes a purchase requisition for ingredients and packing, and the batch itself becomes a work order carrying a batch process sheet. Because the recipe is the BOM, a change to the formula flows straight into the next planning run.

How does the software handle seasonal and festival demand?

Seasonal and festival demand is planned the same way as any demand — as a sales or production plan for the horizon that is netted against stock. Because the plan is netted with stock in view (the WSTK sub-type), a planner can pre-build to stock ahead of a festival peak, and the live reorder-level dashboard keeps proposing purchase requisitions for ingredients as stock is drawn down, so a rising plan does not silently run the store empty. Planning the ramp on batches and ingredient lead times is what keeps a seasonal peak from becoming a shortage.

Does Fast Planning suit process manufacturers in India?

Yes. Process and batch manufacturers are one of the core profiles Fast Planning is built for, alongside discrete make-to-order and component makers. It is designed for small-to-mid Indian units running a single plant or a few plants, plans batches against recipe BOMs and real ingredient stock, and deploys cloud or on-premise on the shared platform that Fast Production and Fast Inventory use. Pricing is indicative in Indian Rupees and scales with users and modules; confirm any GST treatment with your CA.

Ready to plan batches against real ingredient stock?

A 30-minute Fast Planning Software demo covers demand entry, recipe explosion and netting, batch sizing, purchase requisitions and batch work orders, process sheets, scheduling and plan-vs-actual — live, on your own data.

Get a demo
No commitment. No slides. Your plan on screen.