ERPNext Manufacturing in Italy

Conto lavoro: outside processors in ERPNext

Sending material to a terzista for machining, heat treatment, plating, dyeing or assembly is routine in Italian industrial districts. ERPNext models it with subcontracting: an order for the service, the list of material you supply, a transfer to the supplier's warehouse and a receipt that consumes the supplied material and brings the processed item back. The exact documents have changed between releases, so the screens depend on the version you run.

What I test with your production planner:

• A warehouse per processor, so you can see how much of your material sits at each terzista at any moment.
• Returns with scrap or process loss, and how any shortfall is valued.
• Partial returns spread over several deliveries against one order.
• Chains where material travels from one processor to the next without returning to you first.
• The processing charge flowing into product cost alongside your own operations.

Goods leaving for a processor travel with a transport document. What it must contain is a question for your advisor, and whether the ERPNext delivery note, a custom print format or an Italian app produces it is something I check with your partner. A native Italian speaker in your company drafts or proofreads the wording on those prints. Product-level features are on the ERPNext Manufacturing page.

Special machines: order BOMs, projects and serial numbers

Builders of packaging, food processing or woodworking machines rarely make the same machine twice. The order defines a configuration, the technical office releases the bill of materials in stages, and long-lead parts are bought before the design is finished. ERPNext can follow this with multi-level BOMs, a project linked to the sales order, and production plans that raise material requests for the levels already released.

The design points I work through:

• Standard modules kept as reusable sub-assembly BOMs, with only the order-specific level created for each machine.
• How drawings from CAD or PDM reach the BOM, whether by import, integration or manual release, and who owns each step.
• Project costing that gathers material, internal hours and outside processing against the machine, so the controller sees margin before the final invoice.
• A serial number on every delivered machine, so spare parts and service visits later attach to the right unit.

ERPNext does not include a rules-based product configurator. If quoting depends on one, that is custom work or a separate tool, and I scope it openly. Engineering change control is also light, so I agree a simple release discipline with the technical office rather than promise a full PLM workflow. The manufacturing industry page gives the wider context.

Food producers: batches, shelf life and inspections

Pasta makers, dairies, cured meat plants and confectioners must answer a recall question fast: which customer received which batch, made from which incoming lots. ERPNext supports batch numbers with manufacturing and expiry dates, batch-wise stock and trace reports across purchasing, production and delivery. That covers the core of the question, provided every movement is recorded.

Where I spend design time:

• Batch creation rules: whether batches come from supplier labels, the production date or your own numbering, and how labels get printed.
• Shelf life at dispatch: picking by earliest expiry, and blocking batches below the remaining life a customer contract demands.
• Quality inspection: templates for incoming milk, flour or meat and for finished goods, with readings the quality manager reviews.
• Yields: recording variable yields and process loss so ingredient consumption and cost stay truthful.

Food safety plans, laboratory systems and the audit files retail buyers request usually stay in specialist tools; ERPNext holds the transaction trail they point to. Large retail customers may also expect EDI or portal ordering, which means an integration project through ERP integration work rather than a standard feature. See ERP for food and beverage for the general picture.

Costing the way the controller and the commercialista expect

ERPNext values stock perpetually: each material transfer, consumption and finished goods receipt posts to the ledger at the valuation method set for the item, such as moving average or FIFO. In an Italian manufacturer two audiences must accept the result. The controller wants margin by order and by line. The commercialista needs year-end inventory valued on a basis they can defend.

I settle these points before configuration starts:

• The valuation method per item group, and whether it matches the basis your advisor uses for year-end inventory.
• Workstation hour rates that include labor and overhead in a way the controller can explain line by line.
• How subcontracting charges, scrap and process loss enter product cost.
• Where work in progress is parked, in stock and in the ledger, and the month-end look at open work orders.
• How often BOM costs are updated, so a quotation never relies on last season's purchase prices.

During testing I reconcile the stock ledger value with the general ledger and run a sample month through both the controller's model and ERPNext. Every gap gets an explanation while still in staging, not at the first closing. If the ledger is also in scope, the ERPNext Accounting in Italy page covers that side.

Limits on the shop floor, and who keeps ERPNext running

Plenty of small and mid-sized Italian plants can run on ERPNext, yet it remains a general ERP with manufacturing features, not a dedicated production suite. I raise these limits in the first workshops:

• Finite scheduling across many constrained machines usually needs an advanced planning tool or custom work.
• Machine connectivity, operator terminals and real-time efficiency data sit outside the core product. If machines must exchange data with the management system for a scheme your advisor identifies, that interface needs its own specification and owner.
• Process lines with several co-products need careful modeling and sometimes compromises.

Then comes the question of support. A developer on your payroll brings speed and knowledge of your plant, but also a single point of failure. A Frappe specialist firm offers a team and continuity at a different cost profile. A freelance developer sits in between. I help you choose, write upgrade testing into the arrangement and insist that custom features live in a separate app. Because I sell no support plans, that advice has no commercial angle. If another platform fits better, read the ERPNext vs Odoo manufacturing comparison and Odoo Manufacturing in Italy. Delivery is remote, with plant visits by arrangement.