ERPNext Manufacturing in Germany

Standard machines, customer variants and order-linked BOMs

A German equipment builder rarely sells the same machine twice. A standard frame and drive get customer-specific options, a different control cabinet or a special tool. In ERPNext the core building blocks are items, multi-level bills of materials and work orders. The open question is how a customer variant is represented without breaking the standard.

Three patterns I compare with your engineering and order processing teams:

• Standard BOM plus options. Works when variants are a known set of assemblies. Item variants and attributes can describe them, and sales picks the combination.
• Copied BOM per sales order. Engineering copies the standard BOM, adjusts it for the order and links it to that sales order. Clear for assemble-to-order, but needs discipline so copies do not multiply into unmaintained versions.
• Project-driven build. For larger one-off machines, a project carries tasks, purchases and work orders together, so costs gather on the project as well as on the item.

The weak point is the connection to CAD and PDM. ERPNext has no built-in engineering change process of the kind a PDM system offers, and parts lists from CAD usually arrive through an import or a custom integration. I specify that interface, including what happens when engineering releases a change after material has been ordered. The general BOM approach is on my ERPNext Manufacturing consultant page.

Production plans, material requests and long lead times

For machine builders, late purchased parts cause more delays than the assembly itself. Drives, controls, bearings and castings can have long lead times, and a planner needs to see shortages while there is still time to act.

ERPNext's production plan takes sales orders or material requests, explodes the BOMs over all levels, nets available stock and open purchase orders and proposes work orders for made parts and material requests for bought parts. I configure it so the result is usable:

• Lead times on items that purchasing maintains, so required-by dates are realistic.
• Warehouses separating raw material, work in progress, assembly staging and finished machines, which also helps when ownership of stock must be clear for a customer down payment.
• Reorder levels for standard fasteners and consumables so they never appear on order-specific plans.
• Reserved stock for a specific order, where your version supports it, so a critical part is not taken by another job.

What ERPNext does not do is finite capacity scheduling with sequence optimization across many workstations. If your planners need a graphical plan board that respects capacity and changeover times, an advanced planning tool connected through the API may be justified. I describe the gap honestly before you decide whether to fill it.

Co-determination before the first job card

Each ERPNext job card captures an operation: who worked on which workstation, for how long, with what quantity and scrap. That data gives realistic hours for post-costing and future quotations. In Germany it also raises a question that must be answered early.

Where a works council exists, introducing a system that can record employee performance or behavior is generally subject to its co-determination rights, and a works agreement is often the result. Your HR lead and legal advisor decide what applies; my job is to make the discussion concrete and calm.

What I prepare for that discussion:

• the exact fields recorded on a job card and which are mandatory
• whether times are captured per person or per team or workstation
• who can see individual times, and which reports aggregate them
• retention periods and deletion of personal detail once costing is complete
• a statement of purposes, such as costing and capacity planning, and what the data will not be used for

ERPNext's role permissions and report design can support the agreed scope, for example by showing supervisors only aggregated times. I configure those limits and test that they hold. Leaving this step until the end puts the go-live date at risk. German shop floor screens rely on community translations, so a colleague whose first language is German checks the labels operators will see.

Serial numbers from assembly to after-sales service

A machine builder's relationship with a customer continues long after delivery. Service technicians need to know which control version, which motor and which spare parts went into a specific machine, and customers may ask for documentation tied to that serial number.

ERPNext tracks serial numbers on stock items through work orders, stock entries and deliveries. I design the policy with production and service:

• What gets a serial number. The finished machine, and key purchased or assembled components that matter for warranty and spare parts.
• Where the number is captured. At receipt for bought components, at work order completion for assemblies, with barcode labels where useful.
• Documentation. Test reports, declarations and manuals attached to the serial number or delivery, so they can be found years later. Which documents are legally required stays with your compliance lead.
• Service records. Warranty claims and maintenance visits linked to the serial number, so spare parts orders and service history sit in one place.

Incoming quality inspection on critical components uses ERPNext's inspection templates with measured readings. I run a trace test before go-live: start from a field complaint, find the component supplier and batch, and list every other machine that received parts from it. The ERPNext consultant Germany page covers the wider platform choice.

Costing, specialist systems and support

German manufacturers usually want both a pre-calculation for quoting and a post-calculation once the order is complete. ERPNext can give the first from BOM material cost plus routing times at workstation hourly rates, and the second from actual material consumed, job card hours and subcontracting charges on the work order. I agree with your controller how overheads sit in the hourly rates and how variances are reviewed.

Where ERPNext fits well: assemble-to-order equipment, component production with stable routings, outside processing and serial traceability, in one database from quotation to service. Where a specialist system tends to fit better:

• engineer-to-order projects with continuous design change and deep PDM integration
• finite scheduling across a large machine park
• direct machine data collection, which belongs in an MES
• industry-specific production systems that a German group already mandates

Support needs a decision before go-live. An in-house developer knows the plant; a German Frappe-focused service firm brings continuity and German-language support; a remote team needs strong specifications and review. Confirm with Frappe or your chosen firm what they will maintain. I do not resell services or take referral fees. If the fit is doubtful, compare Odoo Manufacturing in Germany and the options on my ERP consultant Germany page; the Germany hub explains remote working.