ERPNext Manufacturing, Netherlands

Machine builders: project BOMs and engineering changes

A Dutch machine builder rarely makes the same thing twice. Each order starts with engineering, produces a bill of materials that may run several levels deep, and changes while parts are already being bought. ERPNext can follow this if the structure is designed deliberately. A sales order can be linked to a project, a project-specific BOM can be created for the machine, and work orders and material requests raised from it carry the project reference so purchasing and costs stay attached to the right order.

Long-lead items are the first test. Purchasing often has to order motors, controls or castings before the full design is released, so I plan how a partial BOM or a material request against the project handles early buying without creating duplicate demand later. The second test is change. ERPNext keeps several BOMs per item and lets you mark one as default; I agree who may release a new version, how the change reaches open work orders and how engineering signals it.

CAD and PDM systems usually hold the design master. Pushing released BOMs from those tools into ERPNext is a frequent request, but it is custom work with an owner, not a standard connector. I specify what moves, in which direction and who resolves conflicts. Production features are covered generally on ERPNext Manufacturing, and the engineering industry page discusses project-driven production.

Job cards, time registration and the works council

Job cards are how ERPNext learns what happened on the floor: who started an operation, how long it took, how many good and rejected parts came out. That information drives costing and capacity, but it is also data about employees. In the Netherlands, a works council generally has a say when a company introduces or changes systems that can monitor staff performance or attendance, and GDPR applies in any case. Your employment advisor confirms what applies to you; my part is to make sure the design can be explained and defended.

Practically, I start with the question of what management actually needs. Often the answer is time per operation and per order, not a ranking of individual operators. Job cards can then record the workstation and the employee where needed for traceability, with reports built on operations and orders rather than people. Only roles with a genuine need can open person-level records, and retention is agreed with HR.

I prepare a short description of the recording design in plain language: what is captured, who can see it, how long it is kept and what it is used for. Your HR lead and works council can review it before training starts, which is far easier than reworking a live system. Dutch screen labels and floor instructions come from Dutch-speaking staff, who review them before go-live. The process mapping page explains how I document floor processes.

Subcontracted machining, coating and assembly

Dutch supply chains rely heavily on specialist suppliers for machining, sheet metal, surface treatment and sub-assemblies, sometimes across the border in Belgium or Germany. ERPNext handles this through subcontracting orders: you list the materials you supply and the item you expect back, the supplied stock moves to a warehouse representing the supplier, and the subcontracting receipt consumes it and adds the service charge to the cost of the finished item.

I design the flow around what you really send. Some suppliers receive raw bar or sheet and return finished parts; others receive your machined parts and return them coated; a few hold consignment stock for repeated orders. Each pattern needs its own setup, and transport costs to and from the supplier can be added through landed cost vouchers so the item value reflects them.

Visibility is the part manufacturers often lack. Once material leaves your building, it is easy to lose track of how much sits at which supplier. I set up a report of stock per subcontractor warehouse and a routine reconciliation with each supplier. For cross-border movements, VAT and transport documents follow your advisor's instructions, and ERPNext stores the data needed to print them. For integration with supplier portals or EDI, see ERP integration; a comparison with a packaged alternative is on Odoo Manufacturing in the Netherlands.

Food and agri processing: batches, quality and where ERPNext stops

Dutch food and agri processors need batch tracking, expiry dates, quality checks and recall readiness. ERPNext covers the core: items can require batch numbers on every movement, batches carry manufacturing and expiry dates, quality inspection templates define checks at receipt, during production and before release, and the stock ledger can trace a batch forward to customers and back to suppliers. I prove this with a mock recall on a test copy before go-live.

There are also limits to name early. Products sold by variable weight, where each case weighs something different but is ordered by count, are not handled natively in the way specialist food systems handle catch weight. Yield variation across raw material batches, by-products and co-products can be modeled with scrap items and process loss, but complex recipe scaling or nutritional calculation usually means custom work. Label printing with batch and date data often goes through a separate labeling tool integrated with ERPNext.

None of this is a reason to dismiss ERPNext. It is a reason to test your three hardest products before selection, not after. If those tests show heavy customization, a specialist food ERP may cost less over the system's life. The food and beverage ERP page sets out typical workflows, and an ERP evaluation runs your own products through each candidate.

Costing, support and the limits of open-source manufacturing

ERPNext calculates production cost from consumed materials at their valuation rate, workstation operating costs from recorded time and hour rates, plus extra costs added to the manufacture stock entry. For engineer-to-order work, the project view then gathers material, labor and purchased services per machine. I agree the valuation method and hour rate structure with your controller or accountant, and compare planned and actual costs on a sample of completed orders before go-live.

Support needs a plan. The Frappe developer community serving Dutch manufacturers is smaller than for the large commercial platforms, and good developers may sit in other countries. Some manufacturers keep a developer on staff who also maintains integrations; others contract a partner with clear response expectations. Either way, every customization is listed with an owner, and a test copy is used to rehearse each upgrade. Hosting on Frappe Cloud or a European server is part of the same choice; the platform-level view is on ERPNext for Dutch companies.

Where ERPNext is weaker, I say so: detailed finite scheduling across bottleneck machines, advanced standard cost variance analysis and deep product lifecycle management are better served by specialist tools or larger suites. If those matter most, it is better to know before selection. The ERPNext vs Odoo manufacturing comparison, my ERP consultant page for the Netherlands and the Netherlands hub give the wider picture.