ERPNext Manufacturing in Lebanon

Bulk, packed and scrap: BOM design for food and bottling lines

On a food or beverage line, the same batch of product often ends up in several pack sizes. In ERPNext the cleanest model is usually a BOM for the bulk intermediate, such as a syrup, a sauce or a dough, and separate BOMs for each packed item that consume it along with bottles, caps, labels, trays and film. That lets the plant record a bulk batch once, then pack it as orders require, while stock shows how much intermediate is waiting.

Points I agree with the plant lead:

• Process loss. Recent versions let a BOM carry an expected loss, so the yield gap is visible instead of buried in adjustments. I confirm how your version handles it.
• Scrap items. Rejected bottles, broken product or trimmings can be returned to stock as scrap with their own value, which matters where scrap is sold or reprocessed.
• Substitutes. When a label or cap supplier changes, alternative items let work orders use the replacement without rewriting every BOM.
• Pack size changes. A new pack is a new BOM version, with the old one kept for history.

Building materials follow the same logic with different words: a mix design as the intermediate, blocks or tiles as the finished items, broken pieces as scrap. The ERPNext Manufacturing page describes the module itself; here the aim is a structure your plant can keep accurate.

Workstation hour rates that reflect what a running line costs

ERPNext calculates conversion cost from operations. Each workstation has an hour rate, and ERPNext lets that rate be built from separate elements: labor, electricity, consumables and rent. A routing lists the operations for a product, the workstation for each and the time it takes, and the BOM then carries an operating cost alongside material cost.

For a Lebanese plant the electricity element deserves attention. Where part of the power comes from on-site generation, the cost per running hour can differ noticeably from grid power, and it can change. I ask finance to agree a method for the electricity rate, a named person to update it, and a review point when it moves, so product costs do not quietly drift away from reality.

Job cards record the actual time spent on each operation. They are where a supervisor logs start, stop and quantity produced, and where actual and planned time can be compared. I keep job cards only where the time data will actually be used; on a simple filling line, recording the work order and its completion may be enough, and asking operators for detail nobody reviews only produces poor data.

Downtime can be logged against a workstation with a reason, which shows how much capacity is lost to stoppages, changeovers or missing materials. That report is often more useful to an owner than any cost figure. The manufacturing page covers how production data feeds management reporting.

Outside processing: printing, filling and finishing by other workshops

Lebanese manufacturers often rely on outside workshops for a stage of the process: printing labels or cartons, filling under contract, galvanizing or coating metal parts, or cutting stone. ERPNext treats this as subcontracting. You send your own materials to the supplier, they return processed goods, and you pay for the service.

The way subcontracting is recorded has changed between ERPNext versions, with newer releases using a dedicated subcontracting order and receipt instead of options on the purchase order. I confirm which model your version uses before designing anything, because training material written for one does not fit the other.

The design questions I settle:

• Supplier warehouse. Materials sent out sit in a warehouse representing the supplier, so you always know what they hold.
• Consumption. Whether supplied materials are consumed by the BOM automatically on receipt, or adjusted to what the supplier reports.
• Service cost. The workshop's charge is added to the value of what comes back, so finished goods carry the full cost.
• Returns and rejects. Unused or rejected material coming back is recorded as such, not lost in an adjustment.

A monthly reconciliation of stock held by each workshop closes the loop. Hosting, regional apps and implementer choice are discussed on the Lebanese ERPNext page.

Batch records and inspection templates for buyers abroad

Lebanese food and cosmetics producers selling to distributors abroad are frequently asked to show where an ingredient came from and how a batch was checked. ERPNext supports this with batch numbers on items, expiry dates where shelf life matters, and quality inspections tied to stock transactions.

A quality inspection template lists the parameters to check, each either a measured value with an acceptable range or a visual pass or fail. Items can require an inspection at purchase receipt, before delivery, or during manufacture, and ERPNext can block the transaction until the inspection is completed. Results stay linked to the batch, so a buyer's question can be answered from the system instead of from a folder.

What I put in place with your quality lead:

• Batch naming that encodes enough to read on a label, agreed before the first production run.
• Inspection templates per item group, kept short enough that staff actually complete them.
• A tracing routine, rehearsed once, that walks from a finished batch back to raw material batches and forward to customers.
• Print formats for certificates of analysis or batch summaries, in the language each buyer needs, checked by native speakers on your side.

Where a buyer requires formal food safety or cosmetics certification, ERPNext holds evidence but does not replace the certification process. Your quality advisor decides what records are required.

Costing, support and where a specialist system fits better

Finished goods cost in ERPNext comes from raw material valuation plus operating cost. Valuation can be moving average or first in, first out, chosen per item or as a default; your accountant should decide which suits a business whose imported inputs are priced in dollars. BOM costs can be refreshed from valuation rates, last purchase prices or a price list. I agree which source is used and how often it is refreshed, so quotes are never priced from outdated material costs. Landed cost vouchers add freight and clearing to imported materials before they enter production.

ERPNext is a sound fit for discrete and light process plants that want production, stock and accounting in one open-source system. I would look at a specialist instead when:

• Formula management with regulated batch records is central, as in pharmaceutical production.
• Machine data must flow directly into production records in real time.
• Planning needs finite capacity scheduling across many constrained lines.

Then comes the question of who looks after the system. A developer on your payroll learns the plant quickly but creates a single point of failure; an implementer offers continuity only when the contract spells out duties. Either way, custom code sits in a separate app and is tested on staging before upgrades. The ERPNext vs Odoo manufacturing comparison and the ERP consultant for Lebanon page help with the wider choice.