ERPNext Manufacturing in Nigeria

From bulk batch to shipper carton: BOM design

An FMCG product in Nigeria is usually made twice: once as a bulk batch in a mixer, tank or kettle, and again as packed units on a filling or packing line. Treating these as one BOM hides the information planners and accountants need. In ERPNext I separate them:

• Bulk item BOM with raw materials and the expected process loss, so yield variance is visible.
• Packed unit BOM consuming the bulk item plus bottles, sachets, labels, caps or wrappers.
• Shipper carton BOM where the carton is what distributors order and what the warehouse counts.

Sachet, single-unit and family packs from one bulk batch then share the same parent item, and a production plan can explode demand from distributor orders down to bulk requirements. Scrap items, such as rejected bottles or film waste, are recorded on the BOM so their value is not lost.

Imported inputs such as resins, flavors, concentrates and packaging films are the other complication. Their cost moves with the exchange rate and with clearing charges. Landed cost vouchers bring freight, duty and clearing into stock value, and BOM costs can be refreshed from current valuation rates so product cost reflects what the plant actually paid. The global ERPNext Manufacturing page explains BOM features in general.

Generators, outages and downtime on the shop floor

Where grid power is unreliable, production time is lost in ways a standard setup never records. A line stops, the generator starts, the batch is held, and the job card shows a long operation with no explanation. ERPNext has a downtime entry document that records the workstation, the period and a reason. I set up reason codes your supervisors agree with, such as grid failure, generator changeover, fuel shortage, mechanical fault and material shortage.

The workstation hour rate in ERPNext has separate components for electricity, consumables, rent and wages. Finance decides what goes into each: a share of diesel and generator maintenance in the power component, for example, recalculated when fuel costs change. Operating cost on work orders then reflects the plant's real energy situation instead of a grid tariff nobody pays in full.

Two practical points follow. Job cards must still be captured when the network is down, so I check whether supervisors will enter them live on tablets, at the end of a shift from paper, or through a simple screen near the line. And the hosting choice matters: a plant that cannot reach a cloud system during an outage needs a plan for catching up entries, which the ERPNext consultant Nigeria page discusses for hosting overall.

Batch records, quality inspection and regulator expectations

Food, beverage, cosmetics and household products sold in Nigeria are regulated, and NAFDAC registration and inspection set expectations for traceability and records. What exactly applies to your products is for your regulatory staff to confirm. ERPNext can support the operational side:

• Batch numbers on raw materials at receipt, with supplier batch references and expiry dates.
• Quality inspection templates with parameters and acceptance criteria for incoming materials, in-process checks and finished goods.
• Quarantine and released warehouses so stock awaiting a result cannot be issued or sold.
• Batch-wise stock and traceability reports following a finished batch back to its inputs and forward to each distributor delivery.

Before go-live I run a mock recall: choose a finished batch, list every customer that received it, then trace every raw material lot that went into it. If any step needs a spreadsheet, the design is not finished. ERPNext is not a laboratory system, so detailed test results, certificates of analysis and stability studies may stay in a separate tool or document control process, linked by batch number. The food and beverage industry page covers sector requirements more broadly.

Contract packers, toll manufacturing and distributor demand

Many Nigerian brands do not produce everything in their own plant. Some products are packed by a third party, some ingredients are processed by a toll manufacturer, and some plants pack for other brands. ERPNext's subcontracting flow handles the common case: a subcontracting order lists the finished item and the materials you send, stock moves to a supplier warehouse, and the subcontracting receipt brings the finished goods back with the contractor's service charge added to cost. Check how this flow works in your version, because it was reworked in recent releases.

Where you pack for another brand using their materials, ERPNext can mark items as customer provided, so they come into stock without a purchase cost. I design the warehouses, the documents the contractor or customer signs and the reconciliation of materials sent against materials consumed, since shortages at contractors otherwise go unnoticed until stock is counted.

Planning ties back to distribution. Production plans can be generated from sales orders or a forecast by depot, and material requests raised for shortages. I agree with the planning team which pack sizes are made to stock and which are made to order. Related designs for trade selling appear on the ERPNext CRM Nigeria page.

Where ERPNext fits, where it does not, and who supports it

ERPNext suits discrete and batch production with clear BOMs, which covers a good deal of packaged goods manufacturing. It is a weaker fit for:

• Continuous process plants such as flour milling, sugar refining or large breweries, where process control, recipes with variable ingredients and plant-level data dominate.
• Finite capacity scheduling across many lines with complex changeover rules; ERPNext's capacity planning is basic.
• Machine data capture from PLCs and sensors, which needs an MES or an integration layer.

In those cases ERPNext may still run finance, stock and procurement alongside a specialist system. The ERPNext vs Odoo manufacturing comparison and my Odoo Manufacturing Nigeria page help if you are still choosing.

Support is the other decision. An in-house developer knows the plant and responds quickly, but becomes a single point of failure. A partner brings a team but may take longer to understand production. Combining the two is a workable pattern. Either way, custom apps stay under version control and upgrades are tested on a copy before the plant depends on them; confirm support scope with Frappe or the partner directly. I am an independent ERPNext consultant, not a Frappe partner, and take no commissions from any provider. More on my approach is on the ERP consultant Nigeria page.