ERPNext Manufacturing in South Africa

Rebuilds, wear parts and customer-owned units for the mines

Mining customers send major components back for rebuild: slurry pumps, gearboxes, hydraulic cylinders, crusher parts. The unit belongs to the mine, carries its own serial number and history, and must come back with a report of what was replaced. Generic manufacturing setups treat everything as a new product built from a BOM, which is the wrong shape for this work.

ERPNext has no dedicated repair order, so I design the flow from existing pieces and test it with your foremen:

• Receipt. The unit arrives as a customer-provided item with its serial number, at zero value, so it never inflates your stock.
• Strip and assess. A quality inspection or custom checklist records condition, and the findings drive a quotation for the rebuild.
• Rebuild. A work order or project consumes new parts and labor against that unit, with job cards per operation.
• Return. The same serial goes back on a delivery note, with the parts used and the test record attached.

New-make wear parts, liners and fabricated items follow the normal BOM and work order route alongside it. Which approach suits your mix, work order or project-based, depends on how you quote and bill, and I test both before choosing. Product background is on ERPNext Manufacturing.

Material certificates, serial trace and what mines ask for

Mines and large plants may expect suppliers to prove what went into a part: steel grade and heat number, weld procedures, inspection results and test pressures. When those documents live in a filing cabinet or a shared drive, finding them for a warranty claim or an audit becomes a project in itself.

In ERPNext I attach evidence to the transaction it belongs to:

• Batches on plate, bar and pipe, with the supplier's material certificate attached to the purchase receipt and the heat number held on the batch.
• Serial numbers on assemblies such as rebuilt pumps or fabricated skids, linked to the work order that produced them.
• Quality inspection templates for dimensional checks, weld inspection and pressure or function tests, with results stored against the batch or serial.
• A data book report that pulls certificates, inspections and delivery details for one order into a single pack.

Your quality manager decides which standards and customer specifications apply. ERPNext stores the records; it does not replace a full quality management system for welding procedure qualification or calibration management, which may sit in a separate tool. That boundary is recorded early through requirements gathering.

Galvanizing, heat treatment and other outsourced steps

In many workshops, not every operation happens in-house. Fabricated steel goes out for hot-dip galvanizing, shafts for heat treatment or hard chroming, and some machining or coating is sent to specialist neighbors. Each trip creates three risks: material at a supplier that nobody tracks, a service invoice that never reaches the job cost, and a delivery date that slips without warning.

ERPNext's subcontracting flow handles this. A subcontracting order lists the service, the material sent and the item expected back. Stock moves to a supplier warehouse when the truck leaves and returns on a subcontracting receipt, which adds the supplier's charge to the value of the finished item. Practical rules I agree with the works manager:

• Which operations are always outsourced and which only when capacity is short, so routings reflect both.
• How weight-based charges, common with galvanizers, are captured on receipt.
• How rejects and rework at the supplier are recorded and charged back.
• Who chases overdue returns, with a report of material sitting at each supplier.

Transport between your works and the supplier can be added as a landed cost or a separate service line, depending on how finance prefers to see it. Costing patterns are covered on ERP for job costing.

Job cards, downtime and costing in rand

Load-shedding and unplanned outages mean some hours on the shop floor produce nothing. If those hours are absorbed silently into job costs, quotes drift and margins look worse without explanation. ERPNext has a downtime entry record linked to workstations, which lets supervisors log stops with a reason: grid outage, generator limit, breakdown, waiting for material. A monthly report then shows lost hours by cause.

On the cost side, I agree with your financial manager:

• Workstation hour rates covering labor, power, consumables and overheads, with a decision on whether generator diesel is part of the rate or tracked separately.
• Job card discipline on bottleneck machines and welding bays, and simple completion booking elsewhere, so data entry matches the value it adds.
• Landed costs on imported steel, bearings and seals, spreading freight, duties and clearing charges in rand before they are issued.
• Valuation method, moving average or FIFO, consistent with how your auditor has seen stock valued before.

When power fails mid-shift, job cards are often completed on paper and entered later. I design that fallback explicitly, with a supervisor responsible for backfilling the same day. The Odoo Manufacturing South Africa page covers capacity planning around outages for comparison.

Where ERPNext falls short, and who should support it

ERPNext Manufacturing is a good match for jobbing works, rebuild shops and small-to-mid converters that want production, stock and accounts in one place without per-user licensing. I suggest a specialist system, or one beside ERPNext, when:

• Detailed finite scheduling across many machines and shifts is the main problem, which usually calls for a dedicated scheduling or MES tool.
• Maintenance of the customer's assets on site, with service contracts and technicians, is the core business rather than workshop production.
• Continuous process plants need recipe control at equipment level and laboratory integration.
• A group standard requires a parent company's ERP.

Support is the other decision. A works with a capable in-house developer can own its custom apps, provided changes pass through version control and a staging site. Without that person, a South African implementer or a Frappe Cloud plan with defined response times is safer. Mixing both without written boundaries leads to disputes when something breaks. Confirm with Frappe or the partner what each plan covers for your version.

I am independent of all of them. The platform overview is on ERPNext South Africa, and the ERPNext vs Odoo manufacturing comparison helps if you are still choosing. The engagement runs in English, remotely.