Discrete manufacturing Bill of materials and routing Serial and batch tracing

Custom discrete manufacturing ERP

Discrete manufacturing makes countable products from components: assembly to a fixed bill of materials, operations in a fixed routing, and batches with a changeover beforehand. The product is fixed before the order arrives, so the question is not what you are going to make but how many, when and in which batch. Appfront builds ERP software for companies that produce this way: metalworking, equipment manufacturing, electronics assembly and contract supply.

What makes discrete manufacturing different

Manufacturing comes in three flavours, and each one needs a different system. Process manufacturing works with recipes and batches, with a yield in kilos or litres. Engineer-to-order makes something new for each order, so the design is part of the lead time. Discrete manufacturing sits in between: the product already exists, is made up of countable components and is repeated in batches. That repetition is what makes planning, cost pricing and improvement possible in the first place.

Is this the right page for you? This page is about repeatable manufacturing with a bill of materials that is already in place. If the design only starts after the order has been signed and the bill of materials grows as you go, you belong with building an ETO ERP. If you run bills of materials and recipes side by side, with batch tracking alongside serial numbers, you belong with ERP for mixed-mode manufacturing.

The product already exists when the order comes in

Item number, bill of materials and routing are fixed. The order only selects the quantity and delivery date.

Batches, changeover time and sequence

Changeovers take time that produces nothing. Batch size and the sequence on the machine are therefore cost items.

Everything can be counted

Stock, rejects and work in progress are all counted in units. Any discrepancy can therefore always be traced back to an action.

The bill of materials and the routing are the heart of the system

Everything a manufacturing ERP does afterwards relies on these two sets of data. The bill of materials says what a product consists of, and the routing says how it is made. If they are right, material requirements calculation, the capacity overview, cost pricing and post-calculation all follow from them. If they are wrong, the system amplifies the error in every place at once.

A usable bill of materials is more than a list of components. It is multi-level, with semi-finished products that have a bill of materials of their own, it includes alternatives for when the first choice is not available, and it records for each line how much is needed and how much scrap is allowed for. A few per cent of rejects on a component four levels deep has a heavy knock-on effect on purchasing requirements. It also has revisions with an effective date, so you know which version is in work order 4471 and when the old stock can be used up.

The routing sets out the operations in sequence, with a workstation, a changeover time and a time per unit for each operation, plus the waiting and transport time in between. Those times determine the lead time that planning works with and the cost price that sales uses for quoting. Subcontracted work belongs in the same routing as an operation, otherwise planning loses track as soon as an order leaves the building for surface treatment.

Changeover time, batch size and the sequence on the machine

Changeover time is the reason discrete manufacturing works in batches. Larger batches spread that time over more units, but tie up money in stock and lengthen the lead time. A system that only knows a fixed batch size per item does not help your planner make that trade-off.

The changeover time that depends on the sequence is trickier. Spraying from light to dark costs almost nothing, while the other way round requires a clean, and the same goes for tool changes and material types. A schedule that ignores this looks neat on paper and produces changeover time on the shop floor that nobody budgeted for. See also building production planning software.

Change management: revisions, effective dates and orders that are already running

A bill of materials is never finished. A supplier discontinues a component, engineering improves a detail, purchasing finds a different material, a customer asks for a variant that then stays in the range. Every change raises two questions your system must be able to answer: from when does the new version apply, and what happens to everything already in progress?

The effective-date condition is rarely just a date. Sometimes a change applies from a certain serial number, sometimes only once the old stock has run out, sometimes only for one customer. If the system only knows "from now", people work around it with a new item number, and the item master fills up with variants nobody can maintain any more.

What happens to open orders is the second half of the work. There are released work orders with material reserved against the old revision, purchase orders running on a part that is being phased out, and semi-finished goods in stock that no longer fit the new drawing. For every affected order, the system should show where it stands, so someone can decide: let it run, rework it or write it off.

Routing changes are forgotten more often than BOM changes, even though they have just as much impact. An extra operation or a different machine changes the lead time the planning works with and the cost price sales uses for quoting. If only the new routing is saved, open orders stay on the old times and the post-calculation explains nothing afterwards.

Service depends on this too. Does the new part fit products delivered earlier, or can it only be fitted from a certain version onwards? Without a recorded replacement relationship, the service desk will sooner or later send the wrong part to a customer whose equipment is standing idle.

A lightweight procedure belongs around this: a status that moves from draft to released to obsolete, someone who releases who is not the same person who signs off, and a trail of who changed what and when. That trail is not bureaucracy but the prerequisite for traceability: if you later want to know which version is in a delivered unit, the revision must be linked to the work order and not only to the item.

A change has only been implemented once its consequences have been made visible. Which orders does it affect, which stock becomes obsolete as a result, which documentation has to follow, and does the price to the customer change? Systems that do not give that overview move the work to a meeting where everyone tries to reconstruct from memory what is still outstanding.

From bill of materials and routing to cost price

The cost price is not a field someone fills in, but a calculation from those same two data sets. Material comes from the BOM at a price you choose, labour and machine time come from the routing at a rate per work centre, and setup time is spread over the batch size. That last point immediately explains why the same product has a different cost price in a small batch than in a large one.

That pricing choice is a decision with consequences. If you calculate with the latest purchase price, the cost price moves with the market and your margin per order fluctuates. If you calculate with a fixed standard price, the cost price stays stable and the difference lands in a price variance account that someone has to deal with. Both are defensible. What doesn't work is when sales doesn't know which of the two underlies the quote.

Machine time deserves its own rate as soon as the machine costs more than the person operating it. A machining centre running unattended costs time without labour hours, while an assembly station costs hours without machine costs. Lumping both into one hourly rate makes automated work artificially expensive and manual work artificially cheap, and steers investment decisions in the wrong direction.

With multi-level BOMs, the cost price accumulates from the bottom up. If a component four levels down changes, all the levels above it have to be recalculated. If that only happens periodically, sales meanwhile quotes on outdated figures. With variants, you also don't want to maintain a thousand cost prices, but a calculation model that derives the price per configuration.

Overheads are where cost prices quietly become unusable. A fixed overhead percentage applied to materials makes orders with expensive purchased parts look unfairly unattractive, while labour-intensive orders look too cheap. The question is not which allocation key is the only right one, but whether everyone knows which one is used and what it hides.

The most important requirement comes back later on this page: the estimated costing must have the same structure as the actual costing. The same lines, the same operations, the same cost types. Without that mirroring, you can establish that an order became more expensive, but not where that happened.

What an ERP for discrete manufacturing needs to do

These components are interdependent: a requirements calculation without reliable stock is worthless number-crunching, and traceability without feedback from the shop floor is a register that lags behind.

Multi-level bill of materials with revisions

Semi-finished products, alternatives, scrap per line and an effective date per revision.

Routing with setup and unit times

Operations in sequence, with workstation, capacity and subcontracted work as a separate step.

Requirements planning you can follow

Net requirements from stock, open orders and lead time, with the reason given for each recommendation.

Work orders and sequence planning

Release with a material check, and rescheduling when a machine fails or an order jumps the queue.

Shop-floor reporting

Quantities, rejects, hours and material consumption in a single action, at the place where the work is done.

Serial and batch registration

Record what is in what, from receipt to delivery, without an extra round of data entry.

Where the ERP stops and an MES begins

This question comes up in every manufacturing project, usually when someone wants to integrate machine data. The ERP thinks in orders, days and money: what needs to be made, from what, when and what it costs. An MES thinks in operations, minutes and settings: what is running now on which machine, with which program and with which measured values.

The overlap is large and growing. Manufacturing packages come with shop-floor terminals and suppliers of shop-floor systems build planning features. As a result, you can end up buying the same function twice and then maintaining two versions of the truth about the status of the same work order. That is the most expensive outcome of this discussion, and the most common one.

The practical boundary lies in the granularity of recording and the speed of the response. If you report back per operation at start and finish, with quantities, rejects and reasons, that works perfectly well in the ERP. If you want to capture process data every second to prove quality or analyse machine behaviour, that stream does not belong in ERP tables. It calls for storage built for that purpose, with a summary per order fed back to the ERP.

For the integration itself, the direction of the data is what matters. Work order, bill of materials, drawing and possibly the machine program go to the floor. Quantities, hours, rejects with reasons and serial numbers come back. Machines with a controller can supply quantities and downtime themselves, via an industrial protocol or the machine's counter, after which the operator only confirms what a human needs to assess.

One rule prevents most of the misery: one owner per data item. If both the ERP and the shop-floor system keep track of the work order status, you get a daily argument about which screen is right. Agree which system is the source and let the other read that status instead of determining it itself.

So start with the question you want to be able to answer. If you want to know whether an order will be on time and what it will yield, that is a job for the ERP. If you want to know why a machine runs more slowly on the night shift, you need machine data and the ERP is the wrong tool for it. In a custom project, this is usually the first cut that gets made: what belongs in the core, what belongs on the shop-floor side, and what does not need to be recorded at all.

Material requirements planning is only as good as your stock levels

The requirements calculation does something simple: it takes sales orders and forecast, explodes them through the bill of materials into gross requirements, subtracts stock and open orders, and shifts the remainder back by the lead time to an order date. On paper, that is irrefutable. In practice, it stands or falls on three inputs: stock levels, lead times and safety stock.

If the stock level is wrong, the same behaviour follows everywhere. The planner double-checks the recommendations in the warehouse, raises the safety stocks, and at some point the requirements calculation gets switched off and the spreadsheet comes out. The cause rarely lies in the calculation module and almost always in the actions around it: a cupboard where someone takes items without booking them out, scrap that is quietly remade, a remainder that goes back on the shelf without a location.

Reporting back from the shop floor without double work

This is where most implementations fail. If the operator fills in a list afterwards that the work planner retypes the next morning, you pay twice for data that is already out of date, and nobody trusts it. Hours, quantities and material usage should be captured in the same action: the operator scans the work order, reports good and rejected parts with a reason, and the system books out the consumption according to the bill of materials.

That places demands on the front end: buttons that can be operated with gloves on, a screen that stays legible in a noisy hall, and the ability to keep working during a network outage with synchronisation afterwards. If machines have counters or a control system, the quantities come from there and the operator only confirms the reject reason. Hours serve two purposes, post-calculation and time accounting, so don't have them reconciled twice. See also software for the manufacturing industry.

  • Book at the moment of the action, not afterwards
  • Cycle counts per article class, not an annual stocktake
  • Book scrap and remainders, even when it hurts
  • Lead times from measured reality, not from the article file
  • One action for hours, quantities and consumption
  • Being able to report deviating consumption alongside automatic booking out

Capacity alongside material: finite scheduling on the bottleneck

A requirements calculation calculates material, not people and machines. In its classic form it plans with infinite capacity: it shifts orders by lead times as if a free machine were always standing by. The result is a neat list of work orders that together require more hours than the week has, after which the planner sets the sequence by hand anyway.

There are two answers to this. The first is to make the capacity requirement visible: per workstation and per week, the hours needed next to the hours available, so that a person can see where it is tight and adjust things themselves. The second is finite scheduling, where the system places the operations in time itself within the available capacity and takes sequence-dependent setup time into account.

Finite scheduling sounds more attractive than it often is in practice. It requires operation times that are accurate, up-to-date availability including shifts, maintenance and leave, and discipline on the shop floor to actually follow the proposed sequence. If any one of those three is missing, the schedule is out of date within half a day and the planner goes back to the whiteboard, with an expensive system alongside that nobody opens any more.

In most workshops, a single machine or a single department determines the flow. That is where you schedule tightly, paying attention to the sequence, and let the rest follow. That is less ambitious than a complete finite schedule and often delivers more, because the attention goes to the place where hours are genuinely scarce.

Capacity is also more than a machine. Without tooling, a die or an operator trained for that operation, the machine is not capacity. Models that only know machine groups schedule work at moments when nobody is there who is allowed to run it, and you only notice that difference when the order is already late.

Then there is rescheduling. A breakdown, a rush order or a late delivery changes the sequence. The system should recalculate quickly and show what shifts and who is affected, including the delivery dates that no longer hold. A schedule that only recalculates overnight lags behind the facts during the day.

The most useful application is often at the start of the process: a capacity check at the moment sales wants to commit to a delivery date. The question is then not about the perfect schedule, but whether the promise is feasible given what is already planned.

Purchasing: lead times, minimum order quantities and the pushback on planning

Recommendations from the requirements calculation only become orders once purchasing has converted them, and that is where the calculation model collides with the reality of suppliers. There are minimum order quantities, packaging units, price tiers and lead times that differ per period. Each of these constraints pushes back on the plan that produced the recommendation.

Lead time is the data point that is wrong most often. Usually it is a number in the item master that was filled in when the item was created and has not been looked at since. It is better to measure: the difference between order date, confirmed date and receipt date, per supplier and per item. Only then can you see that a component structurally arrives later in peak season, and plan for that instead of hoping for the best.

Minimum order quantities and packaging units turn a requirement of forty pieces into an order of a hundred. That is not an error, but it does change the next calculation and the stock value. Make visible which part of an order comes from genuine demand and which from a minimum quantity, otherwise nobody will later know why there is so much on the shelf.

A purchase proposal should carry its own justification: which order or forecast is it for, what happens if it arrives late, and which alternative component is permitted. With those three pieces of information, a buyer can decide without first opening three screens and calling a colleague.

Subcontracted work deserves the same attention as purchased material. Material leaves the building that remains yours, the operation has a lead time that belongs in the routing, and what comes back has to be inspected and booked in. As long as this happens outside the system, your stock is wrong and your planning is wrong too.

Finally, the second source. A system that knows alternative components and multiple suppliers gives the planner room to save an order without falsifying the bill of materials. That may seem like a detail, but it is exactly the point at which people otherwise invent a local workaround that the system never gets to see.

Post-calculation: why the pre-calculation is rarely right

Post-calculation is the only place where you find out whether your model matches reality. Hours come from the progress reporting, material from the warehouse bookings, machine time from the operation and subcontracted work from the purchase invoice. The condition is that this data lands on the same order and in the same structure as the calculation, otherwise you are comparing two lists that are not about the same thing.

The deviations you find are rarely random. Changeovers take longer than the standard, because the standard contains the good changeover and not the one from Monday morning. Rework does not appear in the calculation at all. And the first batch of a new product costs more than the tenth, simply because people still have to learn it. If you do not make these three visible separately, you only see a disappointing margin and raise your rate instead of correcting your standard.

On the material side, you compare theoretical consumption from the bill of materials with actual consumption from the bookings. The difference is scrap, remnants, or a cupboard someone emptied without booking it. These three causes call for different measures, so it pays to be able to tell them apart rather than reduce them to a single percentage.

Post-costing only becomes useful when something is done with it. Measured times should be able to flow back into the routing, with a person in between who judges whether a deviation is structural, because one order is not a norm. Without that loop, you keep calculating with times that a work planner once estimated and that nobody dares to adjust any more.

What you should not use post-costing for is holding individual operators to account. It is the fastest way to ruin the quality of the reporting, and with it the basis of your entire cost price. The figures are there to improve the process, not to catch anyone out.

Also look at the outcome by product group and by customer, not just per order. This is how companies regularly discover that part of their range consistently loses money, hidden behind an average that still looks acceptable overall.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Traceability, serial numbers and the recall

Traceability works in two directions. Backwards: which component batches, which BOM revision and which operations went into this one serial number. Forwards: which products contain a supplier batch that has been declared suspect, where are they now and to whom were they delivered. Your service engineer asks the first question; the second cannot be answered in a spreadsheet.

Choose the level deliberately: it is a trade-off between the burden of registration and the damage. A serial number per unit belongs with products that have a file, a warranty or a maintenance history. A batch number per production run is enough for components you make by the thousand. Choose too coarse a level and, when in doubt, you end up recalling months of production instead of two runs.

The number must be created where the product is created, linked to the work order and not added to a list afterwards. Test results, the revision used and the documents delivered all hang off that same number, so the file fills itself rather than someone compiling it after the fact.

For consumer products, the General Product Safety Regulation (EU) 2023/988, applicable since 13 December 2024, imposes additional requirements on recalls: direct contact with the customers concerned, a standardised recall notice and a free remedy. If you build machinery, the Machinery Regulation (EU) 2023/1230 becomes mandatory from 20 January 2027, replacing the Machinery Directive 2006/42/EC. Both ask for the same thing: knowing which unit ended up where.

Inspection, rejection and rework in the flow

In discrete manufacturing, quality is not a separate administration but a step in the flow: incoming inspection on receipt, inspection during or after an operation, and a final check before delivery. Each of these moments changes something in your inventory, your planning or both, which is why they belong in the same system as everything else.

On receipt, it is about blocking. Approved material goes into free stock; material that still has to be inspected should not. If your system only knows "in stock", requirements planning counts boxes that are in quarantine, and the planner promises a date based on material that has not yet been released.

During production, it is about the reason and the place. Six rejected pieces tell you nothing. Six pieces rejected after the third operation because of a dimensional deviation tells you where to look. If you only record quantities, you get a percentage without a story, which is exactly the number nobody does anything with in practice.

Rework is the case where most systems break down. A product that is rejected and goes through an operation again costs hours that are not in the routing and sometimes material that is not in the BOM. If the system only knows good or rejected, those hours disappear into a residual item and the order looks cheaper than it was. A separate rework order that stays linked to the original order keeps the costs where they belong.

Next comes the question of what happens to the shortfall. If a hundred pieces were ordered and six were rejected, the difference has to be made up: is the material still available, does it fit the schedule, and is a customer order waiting on it? This is where quality and planning meet, and where a system either proves its worth or doesn't.

The final step is release. Some products may only ship after approval, sometimes with a measurement report or a declaration that goes to the customer. Link those documents to the serial number or batch, so the file builds up while the work is being done. Complaints and returns close the loop: a return that you can trace back to the batch, work order and supplier turns an incident into data you can use to find the cause.

Multi-level bill of materials Routing with changeover time Requirements planning Work order control Barcode scanning Serial and batch registration Post-calculation per work order Recall file

When an off-the-shelf package is the better choice

Discrete manufacturing is the best-served part of the ERP market. The logic of bill of materials, routing, requirements planning and work orders is decades old and is built into almost every manufacturing package, including serial number tracking and shop-floor terminals. For some readers, such a package is the wiser route, and we would rather say so now than halfway through a quoting process.

Custom software pays off in fewer situations than vendors suggest. The strongest case is your own configuration or costing logic: a calculation model that derives the variants, the bill of materials and the price from a customer specification. The second is production that falls just outside the model, such as a matrix item in sizes and colours that becomes unworkable as a thousand separate item numbers. The third lies on the shop-floor side, where integrations with machines or a customer portal make the difference.

The downside comes with it: when you build it yourself, keeping up with changing regulations and integrations is your own organisation's responsibility. The middle route is often the best answer, with a package as the administrative core and custom software at the edge that sets your business apart. You can read how we weigh this up under a custom ERP system.

For metalworking companies that want to manage bills of materials from CAD with revisions and release, there is our software for bill of materials management of metal products.

  • Package if your process follows the standard pattern
  • Package if BOM discipline still needs to develop
  • Custom if you have your own configuration or calculation logic
  • Custom for variants that are unworkable as item numbers
  • Middle route: package as the core, custom on the shop floor

Frequently asked questions about discrete manufacturing ERP

Discrete manufacturing makes countable units from components, according to a bill of materials and a routing that already exist before the order comes in. Process manufacturing works with recipes, batches and yields in kilos or litres. With engineer-to-order, the design only starts after the order and the bill of materials takes shape along the way. This page is about the first situation: repeatable production of a product that is defined in advance.

A serial number belongs to a single unit and makes sense for products with a file, a warranty or a maintenance history. A batch number belongs to a production run and is sufficient for components you make by the thousand. The level determines the scope of a recall: too coarse means pulling back months of production, too fine makes registration unworkable.

Only if the system makes posting easier than working around it. A requirements calculation works with the levels it contains, so unreliable stock produces a plan that nobody trusts. Scanning at the moment of the action, counting in cycles per item class and actually booking rejects do more for reliability than any calculation module.

By having hours, quantities and material consumption arise in a single action, at the place where the work happens. The operator scans the work order, reports good and rejected units with a reason, and the system deducts consumption according to the bill of materials; only deviations require input. Forms that are retyped later produce data that is already out of date.

Two answers, fast. Which part batches went into this serial number, and which products contain a suspect supplier batch and to whom were they delivered. That requires watertight registration from receipt to delivery and a link between serial number and customer. The General Product Safety Regulation (EU) 2023/988, which has applied since 13 December 2024, also calls for direct customer contact and standardised recall notices.

Often, yes. Discrete manufacturing is the best-served part of the ERP market: BOMs, routings, requirements planning and work orders are found in virtually every manufacturing package. If your process follows that pattern, you buy it off the shelf. Custom becomes interesting when you have your own configuration or costing logic, or when the connection to machines and the shop floor is what sets you apart.

Related services

Building an ETO ERP

If the design only starts after the order and the BOM grows along the way, you belong with ETO ERP, with project structure and phased release.

ERP for mixed-mode manufacturing

If you run BOMs and recipes side by side, with batch registration alongside serial numbers, see ERP for mixed-mode manufacturing.

Custom ERP system

If the question goes beyond manufacturing, covering purchasing, sales, service and administration, then a custom ERP system is the broader starting point.

Your production under the microscope

Tell us how your BOMs and routings are set up, how reliable your stock levels are and what currently happens when a customer asks for the origin of a single serial number. Those answers usually show whether a package, custom software or a combination fits.

Edit content