ERPNext Manufacturing, New Zealand

Turning recipes into BOMs that production will follow

A recipe kept in a spreadsheet may mix several things ERPNext keeps apart: ingredient quantities, the batch size the mixer or kettle holds, expected losses in cooking or trimming, packaging per finished unit and notes for the line. Getting it into ERPNext means splitting those cleanly.

• Two-level BOMs where they help: a bulk item such as a dough, sauce or brew made in batches, then a packing BOM that turns bulk into retail or foodservice units.
• Process loss recorded on the BOM, so material requirements allow for evaporation, trimming or cooking loss and actual yields can be compared with plan.
• Scrap items for trimmings or offcuts that have resale or reuse value, entered at an agreed value.
• Alternative ingredients handled as separate BOMs or permitted substitutions, depending on whether the swap changes allergens or labeling.
• Units of measure matching how you buy, in bags, drums or kilograms, and how you use them, with conversion factors checked.

Where by-products carry real value, such as whey, pulp or second-grade fruit, ERPNext's options for splitting cost between main product and by-products are limited, and the allocation may need custom work or an accounting adjustment. I settle that rule with your accountant early. Feature detail is on the ERPNext Manufacturing page, and the sector view on food and beverage ERP.

Batches, expiry dates and the recall rehearsal

Traceability in ERPNext rests on batch numbers. Each batched item can carry a manufacturing date and an expiry date calculated from the shelf life set on the item, and every receipt, transfer, production entry and delivery records which batch moved. When stock is picked, ERPNext can propose batches in order of expiry, though pickers still need to confirm the batch actually taken.

Design choices for a New Zealand food plant:

• Which items are batched. Ingredients and packaging that touch food generally are; low-risk consumables may not need to be. Your food safety plan, not habit, should decide.
• Batch numbering that matches the code printed on packs, so a complaint can be traced from the label alone.
• Supplier lot capture at receipt, with the supplier's own lot stored against your batch.
• Rework and partial batches recorded through stock entries, so a reworked batch links back to the batches it consumed.

The test that matters is the mock recall. Before go-live I pick a supplier lot and trace it forward to every customer delivery, then pick a customer delivery and trace it back to ingredient lots, using only ERPNext reports. Wherever the trail breaks, data capture gets fixed. Repeating that rehearsal on a schedule after go-live is worth more than any feature list. The testing and UAT page explains how such scenarios are scripted.

Food safety records and quality inspections

New Zealand food businesses generally operate under a food control plan or a national program, and some exporters and primary processors under a risk management program. The exact obligations depend on your products and markets, and should be confirmed with your verifier or MPI rather than inferred from software. ERPNext's job is narrower: to hold the records that tie inspections to the batches they concern.

Quality inspection templates list the parameters to check and their acceptable ranges, numeric or descriptive. They can be required:

• At receipt, for chilled ingredient temperatures, certificates of analysis and packaging condition.
• During production, linked to job cards, for cooking temperatures, metal detection checks or fill weights.
• Before release, so a batch cannot be delivered until its inspection is accepted.

Some records fit poorly in ERPNext: continuous temperature logging from probes, cleaning schedules, pest control visits, staff training and calibration. Those sit better in a food safety app or your current system, with ERPNext storing batch-level results. That boundary gets drawn while mapping the process, so the food safety system keeps its role and verifiers see one consistent story across both.

Allergen information belongs on the item and BOM through a custom field or attribute, with a check that alternative ingredients cannot quietly change the allergen profile.

Seasonal supply, planning and export orders

Food production in New Zealand can follow the seasons: fruit and vegetable intake peaks, honey flows, and demand that swings around summer and the holidays. ERPNext's production plan pulls demand from sales orders and forecasts, explodes BOMs into material requests and work orders, and shows what to buy and make. It does not optimize line schedules or sequence allergen changeovers, so planners still decide the order of runs.

Points to design:

• Forecasts entered for retail customers who send call-offs at short notice, so ingredients and packaging are ordered in time.
• Batch sizes set through BOM quantities and planning rules, checked against how the production plan rounds quantities in your version, so the plan never suggests half a kettle of sauce.
• Seasonal intake of produce received in bulk and processed or frozen for later use, with batches and expiry dates kept intact through freezing and storage.
• Export orders in AUD, USD or other currencies, with customer-specific labels, packing specifications and the documents each order needs.

Export certification and market access run through MPI and your exporter processes, not through ERPNext, but ERPNext can hold certificate references against the delivery and batch so they are easy to find later. Freight and customs systems can be connected through ERPNext's API if volume justifies it; the ERP integration page covers how I specify those links.

Costing, Xero and who supports the plant system

Food margins are thin, and a costing model that ignores yield and packaging waste will flatter them. ERPNext costs a batch from the ingredients and packaging actually consumed, at their valuation rate, plus operating cost from workstation hour rates on the routing. Your accountant and I settle three points early: the stock valuation method, how labor and overhead are built into hour rates, and the value placed on process loss and write-offs.

If Xero remains the ledger, stock valuation and production cost live in ERPNext and Xero receives summarized journals for cost of goods, stock movements and write-offs. That journal needs a clear mapping and a monthly check that stock in Xero matches ERPNext's stock value. The ERPNext Accounting in New Zealand page sets out that choice.

Where ERPNext is the wrong tool:

• high-volume continuous processing with recipe management, lab integration and line automation, where specialist process manufacturing software fits better;
• plants with nobody to own the system, since ERPNext needs an in-house developer, a contract Frappe developer or an implementation firm on a support agreement;
• teams wanting a wider catalog of ready modules, where Odoo Manufacturing in New Zealand is worth comparing.

I sell no support or hosting, so advice on ownership carries no hidden interest. Delivery is remote, with site visits by arrangement. See ERPNext in New Zealand and the New Zealand hub for the wider picture.