ERPNext Manufacturing in Kenya

Grain milling and animal feeds: co-products and changing formulas

A maize or wheat mill does not make one product. Each tonne of grain produces flour or sifted meal plus bran, germ or pollard that is sold separately, often to feed makers. If the ERP treats those secondary outputs as zero-value scrap, the flour looks more expensive than it is and the bran looks like pure profit.

ERPNext lets a BOM list scrap or secondary items with a value, and records process loss on the work order. I agree with finance how secondary outputs are valued, whether at a fixed rate, a market price or a share of cost, and test that the main product cost comes out where they expect. How your version handles co-products is worth confirming with Frappe or the implementer, because this area has been developing.

Animal feed makers face a different problem: the formula changes when an ingredient becomes scarce or expensive. In ERPNext each formula is a BOM version. My recommended rules:

• A new version for every formula change, approved by the nutritionist or production manager before use.
• Work orders always referencing the active version, so each batch records exactly what went in.
• A report comparing planned and actual ingredient use per batch, which surfaces weighing errors and losses.
• Moisture and quality results at intake held on the batch of raw material, so yield problems can be traced back.

Product background is on ERPNext Manufacturing.

Dairy, juice and packaged foods: batches, release and standards

Plants producing milk, yoghurt, juice, water or packaged foods must be able to trace every finished lot to its inputs and its customers. Supermarket chains and institutional buyers may audit those records, and product standards and marks administered by the Kenya Bureau of Standards bring their own documentation. If your products are excisable, excise-related controls may also apply. Your quality and compliance staff confirm which rules bind you; I make ERPNext hold the evidence.

The design I test:

• Batch tracking on raw milk or fruit intake, ingredients, packaging and finished goods, with production and expiry dates.
• Quality inspection templates at intake, during processing and before release, with finished batches held in a quarantine warehouse until accepted.
• First-expiry-first-out picking for dispatch to distributors and supermarkets.
• A trace report run forward from a raw material batch and backward from a customer complaint, tested before go-live.
• Returns and destruction recorded with reasons, so expired stock collected from the market is written off properly.

ERPNext is not a laboratory system or a cold-chain monitoring tool. Plants that need instrument data, temperature logging or electronic batch records may run a specialist system beside it, which I record early through requirements gathering.

Steel coil, roofing sheets and plastics: getting units right

Kenyan roofing and steel processors buy coil by weight, run it through profiling or cut-to-length lines, and sell sheets by the piece or meter in different gauges and colors. Plastics and packaging converters buy resin by the bag or tonne and sell rolls, bags or crates. In both cases, a mismatch between buying, production and selling units is the fastest way to lose stock accuracy.

In ERPNext I set up:

• Unit conversions on each item, from kilos to meters to sheets, with conversion factors agreed per gauge and profile.
• Coils as batches, each carrying supplier, gauge, coating and actual weight, so the yield of every coil can be checked.
• Offcuts and scrap recorded on work orders, with usable offcuts returned to stock as their own items.
• Item variants for colors, gauges and profiles, so the catalog stays manageable.
• Made-to-length orders where customers specify sheet lengths, linked from sales order to work order.

Imported coil and resin carry freight, duties and clearing charges, which landed cost vouchers spread across the shipment in shillings before it is issued. Your accountant chooses moving average or FIFO valuation. For job and order costing patterns, see ERP for job costing.

Toll milling, contract packing and costing in shillings

Toll arrangements show up across Kenyan processing. Mills grind grain that belongs to traders or cooperatives for a fee. Contract packers fill and pack products for brand owners who supply ingredients and packaging. Getting ownership right in the ERP prevents stock and cost errors on both sides.

• For the toll processor, customer-provided items let you receive the client's grain or ingredients at zero value, consume them in work orders and invoice only the processing service. Losses and yields are reported back to the client from the same records.
• For the brand owner, a subcontracting order sends materials to the packer's warehouse and receives finished goods with the service charge added to their cost.

Costing then needs agreement with your finance lead:

• Workstation hour rates for milling, mixing, filling and packing lines, including power and the generator cost if you run one.
• How seasonal swings in raw material prices flow into product cost, and how often standard selling prices are reviewed.
• Dollar-priced inputs converted at the rate your accountant uses, with landed costs applied before issue.

A monthly comparison of planned and actual cost per product shows where yields or prices have moved. The Odoo approach to produce intake and grower records is covered on Odoo Manufacturing Kenya for comparison.

Where ERPNext stops, and who should support your plant

ERPNext Manufacturing is a strong fit for small and mid-sized Kenyan processors that need one record for production, stock, quality checks and the ledger, with no seat-based license cost. I recommend specialist tools beside it, or a different ERP, when:

• Farmer or outgrower payments with collection centers, deductions and mobile money payouts are central; dedicated agri-collection systems often handle that better and post totals to the ERP.
• Continuous process control at equipment level, such as large dairies or breweries with automated lines, needs SCADA or MES integration.
• Detailed shift scheduling across many lines is the main pain.
• A multinational parent mandates its own system.

Then decide who keeps the system healthy. The realistic arrangements are three: a developer on your payroll who knows the plant, an implementer on a retainer, or a hosted Frappe Cloud plan for the platform with an implementer covering the custom apps. Each can work when responsibilities, response times and source code rights are written down. Each fails when two parties assume the other will fix a broken report in the middle of peak intake. Factories and depots upcountry should also test speed on their own connections before rollout. Confirm with Frappe or the partner what each option includes for your version.

No provider pays me for a recommendation. For the wider platform picture read ERPNext Kenya; if Odoo is also on the shortlist, ERPNext vs Odoo for manufacturing sets the two side by side. The engagement runs in English, while Swahili training on the floor comes from your supervisors.