What a discrete manufacturing ERP is
A discrete manufacturing ERP runs businesses that make countable, individual things — fabricated structures, machined components, assemblies — where every item has a bill of materials, a process route and work orders. Its job is to connect a confirmed sales order to everything the order causes: a BOM explosion, a material plan, purchase requisitions for the shortages, work orders through the route, WIP bookings, a finished-goods transfer, inspection, dispatch and a GST invoice — on one database, so the whole chain reads as one record. That is precisely the shape of Fast ERP's discrete manufacturing profile.
"Discrete" is the operative word. Unlike process industries that blend and batch continuous material, a discrete manufacturer's world is structured: parts, sub-assemblies, operations, machines. That structure is exactly what an ERP encodes — the multi-level BOM says what the item is made of, the bill of resources says what makes it, and the released order says why it is being made now. The pillar guide covers the two commercial spines around this; this guide goes deep on the make cycle in the middle.
Job shop, batch, assembly — why the mode matters
Discrete manufacturers run in different modes, and the mode decides which parts of the ERP carry the load.
Job shop
Every order is different — a BOM against the specific order, a route built for it, costing per job. The order-to-BOM link is everything.
Order-drivenBatch
Repeating items in runs — standard BOMs, reorder levels, lot tracking and batch-wise inspection carry the weight.
Run-drivenAssembly
Deep multi-level BOMs and sub-assemblies — kitting, component plans and level-wise costing dominate.
Structure-drivenMost real plants are a mix — a fabricator repeats some weldments and quotes new ones every week. That is why the useful test of a discrete ERP is not "does it support my mode" but whether the same system can hold a BOM against a specific order for the job work and a standard BOM with reorder levels for the repeaters, without two databases and two truths. Fast ERP does both: BOM-against-OA for order-driven work, and item-level reorder planning for the standards.
BOM, BOR and engineering change
The bill of materials is the spine of everything discrete. In Fast ERP it is multi-level — sub-assemblies under assemblies under the finished item — with a BOM tree view, level reports and BOM costing that rolls material cost up the structure, so a quotation can be priced from the structure rather than from memory. Beside it sits the bill of resources (BOR): the machines, labour and tooling each operation needs, drawn from a resource master grouped by category.
The pairing answers the two questions a released order raises at once: what must be bought or issued (BOM) and which resources must be loaded (BOR). And because designs change, the structure is governed by engineering change (ECN) — changes are raised, approved and released through change management, with a change dashboard showing what is in flight. A drawing revision that never reaches the shop floor, or reaches it before approval, is precisely the class of error ECN control exists to kill.
Process routes, work orders and WIP
The route describes how the item moves through the shop: operations in sequence, each with its process sheet and specifications — including process sheets against the specific order for job work. Work orders then carry the quantity through that route, and this is where a discrete ERP either tells the truth about the floor or does not:
- Material issues post against the work order through the store engine, so consumption is recorded where it happened, not estimated at month-end.
- Good and reject quantities are booked per process, so line rejection is visible at the operation that produced it — the input to any serious scrap-reduction effort.
- Rework is a tracked flow — rework process reports and rework-to-FG transfer — not an untracked pile beside the machine.
- WIP-to-FG transfer closes the route: finished goods move to lot-tracked stock, ready for pre-dispatch inspection and the delivery challan.
In-process inspection records against the route as quantities move (the automotive ERP guide covers the full quality stack for regulated work), and process cost reports read actual cost off the same bookings — because the bookings are the record, costing is a report, not a project.
Running a job shop or batch plant on spreadsheets and registers?
See the discrete manufacturing profile of Fast ERP — BOM against your own orders, MRP, work orders, WIP and rejection tracking — live in 30 minutes.
MRP, plans and machine loading
MRP — material requirements planning — is the arithmetic that turns structure into action. Take the demand (released orders and sales plans), explode it through the multi-level BOM, net it against stock on hand and open purchase orders, and what remains is the shortage list: what to buy, what to make, how much, by when.
In Fast ERP the outputs are working documents, not a printout. Shortages become purchase requisitions — including PR-against-BOM and PR-against-stock — which flow through checking and approval to purchase orders and goods receipts. Raw-material and component plan reports show the netted position per item. Reorder levels on the item master cover the standard items between planning runs, generating requisitions when stock dips. And on the capacity side, Gantt-based scheduling and machine-loading MIS show which resources the plan actually fits onto — the difference between a plan and a wish.
One stock ledger under everything
Everything above stands on the store engine. Receipts from purchase, issues to work orders, WIP bookings, finished-goods transfers, kitting, reservations, returns and dispatches all post through one stock ledger, with lot and bin tracking underneath and GRN/item barcode labels for physical identification on the floor.
The consequence is that stock is never an opinion. On-hand reflects every movement as it happened; ABC analysis and slow/non-moving reports read off real consumption; and valuation agrees with accounts because both are built from the same transactions. For a discrete manufacturer, this is also what makes traceability real — which supplier receipt fed which work order, which lot went to which customer — a chain of linked documents rather than a reconstruction.
The India layer: GST, Tally and barcodes
An Indian job shop or batch manufacturer carries statutory and practical needs that generic ERP guides skip. Fast ERP treats them as first-class:
Spreadsheets and registers vs a discrete ERP
Most plants arrive at this question from a working system of spreadsheets, registers and one accounting package. The comparison worth making is not feature-by-feature but failure-by-failure — what breaks first as volume grows.
| Question | Spreadsheets + registers | Discrete manufacturing ERP |
|---|---|---|
| What does this order need? | Someone re-derives the BOM from the last similar job | Exploded from the multi-level BOM against the order |
| What should we buy? | Walk the stores, ask the supervisor | MRP shortage list → PR → PO → GRN, linked |
| Where is the job now? | Phone the floor | Work-order and process status on screen |
| How much did we scrap, and where? | Unknown until stock-take | Good/reject booked per process, rejection MIS |
| Does stock match the books? | Monthly argument | One ledger feeds both, valuation agrees |
| What did this job actually cost? | Estimated, later, roughly | Read off the same bookings — BOM costing and process cost reports |
How Fast ERP implements it
Fast ERP for discrete manufacturing is the full platform with the make cycle at the centre — the same engine proven in real fabrication, machining and assembly deployments. In practice:
Because the platform is modular by licence, a smaller shop can start with a slice — inventory and purchase, or production and planning — and grow into the full ERP with no migration. If that describes you, the SME manufacturing ERP guide walks the Tally-plus-spreadsheets decision in detail; if your work is project-shaped — site fabrication, EPC, long jobs billed by stage — read the construction and project ERP guide instead. Pricing is per-deployment, cloud or on-premise.
Frequently asked questions
What is a discrete manufacturing ERP?
A discrete manufacturing ERP runs businesses that make countable, individual things — fabricated parts, machined components, assemblies — where every item has a bill of materials, a process route and work orders. It connects the confirmed sales order to a BOM explosion, a material plan, purchase for the shortages, work orders through the route, WIP and finished-goods transfer, inspection, dispatch and a GST invoice, all on one database, so the order can be traced from enquiry to payment.
What is the difference between a BOM and a BOR?
A BOM — bill of materials — lists the materials and components a finished item consumes, usually in multiple levels for sub-assemblies. A BOR — bill of resources — lists the machines, labour and tooling the item needs at each operation. Together they let an ERP answer both questions a released order raises: what must be bought or issued, and which resources must be loaded. Fast ERP holds both, with BOM trees, level reports and costing built on them.
How does MRP work in a job-shop ERP?
MRP takes demand — released orders and plans — explodes it through the multi-level BOM, nets it against current stock and open purchase orders, and produces the shortages: what to buy and what to make, in what quantity, by when. In Fast ERP those shortages become purchase requisitions on the procure-to-pay spine and work orders on the shop floor, with raw-material and component plan reports showing the position, and reorder levels covering standard items between runs.
How does an ERP track WIP and rework?
Every stage movement posts through one store engine: material issues to the work order, WIP bookings as operations complete, and a WIP-to-finished-goods transfer when the route ends. Good and reject quantities are booked per process, so line rejection is visible where it happened, and rework runs as its own tracked flow — rework process reports and rework-to-FG transfer — rather than disappearing into a corner of the shop until month-end.
Can a small job shop start with only a few modules?
Yes. Fast ERP is one platform in which every module is a switch — the other Fast products are profiles of the same codebase. A job shop can start with, say, inventory and purchase, or production and planning, and expand into the full ERP by enabling more modules later. Because there was only ever one database, growing does not mean migrating; the items, parties and history stay where they are.