ERPNext Manufacturing in Iraq

High-volume lines: work orders, direct entries and backflushing

A water or soft drink line may run the same product for hours, and asking a supervisor to open a separate document for every pallet would be pointless. ERPNext offers more than one way to record that output, and the right choice depends on how much control the plant needs.

• Work order per shift or per day. The planner releases a work order for the expected quantity, materials are transferred to the line, and the shift posts what it actually finished. This gives a plan to compare against.
• Direct manufacture entry. A stock entry of the manufacture type can consume materials and add finished goods straight from a BOM, without a work order. It suits simple, steady lines.
• Sub-assemblies. Where preforms are blown in-house, they can be a separate BOM produced ahead of filling, with their own stock.

The material consumption method matters as much as the document. ERPNext can backflush raw materials based on the BOM, assuming standard usage, or on what was actually transferred to the line. Backflushing on the BOM is simpler, but hides waste; consuming what was transferred shows real usage, provided someone records returns of unused material.

I trial both methods with a few real shifts before deciding, and agree who reconciles output against the counted pallets each day. The ERPNext Manufacturing page describes the module in general; this is how it meets a fast Iraqi line.

Bags, tons and pallets: units and variants for building materials

Building materials plants buy, store, produce and sell in different units. Cement and aggregate may arrive by the ton, be consumed in kilograms per batch, while blocks are produced by the piece and sold by the pallet or truckload. Paint is mixed in liters and sold by the can or drum. If units are not designed carefully, stock figures stop meaning anything.

ERPNext lets each item have a stock unit plus conversion factors for purchase and sales units. I list every unit the plant uses, agree the factors with the plant manager, and test them on a purchase receipt, a production entry and a delivery note. Where the conversion genuinely varies, as with moisture in sand, I flag it so finance decides how differences are adjusted rather than letting them appear as unexplained losses.

Variants keep the item list under control. A block maker producing several sizes, a tile maker with finishes or a paint maker with many colors can define an item template with attributes and generate variants from it. Each variant keeps its own BOM, stock and price, while reports can still group them by template.

Quality matters too. Strength or density results from your lab can be recorded through quality inspections linked to the batch or production entry, with the lab report attached. Whether any standard requires particular tests is for your quality advisor to confirm. The construction industry page explains what buyers on the contracting side tend to need.

Machines, molds and generators: maintenance and downtime records

For many Iraqi plants, lost hours come from machine stoppages, worn molds and power interruptions more than from planning. ERPNext includes asset management features that can bring maintenance into the same system as production, though they are simpler than a dedicated maintenance package.

The setup I design with the plant manager:

• Assets. Filling machines, block presses, mixers, molds and generators registered as assets, with location and responsible person.
• Maintenance schedules. Recurring tasks assigned to a maintenance team, with reminders and a log of completed work.
• Repairs. Breakdowns recorded as asset repairs, with spare parts issued from stock and the cost captured.
• Downtime. Stoppages logged against a workstation with a reason from a fixed list, such as power, breakdown, changeover or missing material.

The downtime report is often more valuable than any cost figure. It shows the owner where capacity is lost, which machines need attention and whether power interruptions or material shortages are the bigger problem.

Spare parts deserve their own warehouse and reorder levels, because a missing part can stop a line for days when it has to be imported. I set reorder points with the maintenance lead for critical spares.

If maintenance becomes complex, with many technicians, condition monitoring or detailed work permits, a specialist maintenance system may fit better. The ERPNext in Iraq page covers the platform decision above this detail.

Imported inputs, landed cost and production cost in dinars

Iraqi manufacturers often import their key inputs: resin or preforms for bottles, pigments and binders for paint, additives, packaging film or machinery spares. These are usually priced in dollars, carry freight and clearing charges, and arrive in stages. If that full cost does not reach the raw material value, every finished product is undercosted.

ERPNext handles this through landed cost vouchers, which spread freight, insurance, clearing and other charges across the items on one or more purchase receipts, by quantity, value or a manual split. I agree the allocation basis with finance and test it with a real shipment, including one where charges arrive after the goods.

From there, production cost follows the BOM. Raw materials are valued by moving average or first in, first out, a choice your accountant should make. Operating cost comes from workstation hour rates. The BOM's material cost can be recalculated from current stock value, the most recent buying price or a nominated price list; I fix how often that happens so sales pricing does not lag behind input costs.

Reports I review with the plant and finance leads include the BOM stock report, work order summaries and stock ledger by item. Where the owner wants a margin view by product line or customer, I specify it as a report rather than a spreadsheet maintained outside the system. Exchange movements between purchase and payment fall to the accounting side, covered on the ERPNext Accounting in Iraq page.

Plant server, developer support and when a specialist fits

Plants depend on recording output even when the external connection drops. Some Iraqi manufacturers therefore prefer an ERPNext server on the plant's own network, which stays reachable internally during an outage; others accept cloud hosting with backup connections. Either way, a backup held elsewhere and a rehearsed restore are essential. The trade-offs are covered on the parent page; for production the key point is that shift entry must not stop because of a link failure.

Support is the other long-term choice. An employed developer is close to the line and quick to react, yet the plant then relies on a single individual. An outside firm brings continuity only if its agreement spells out response times, upgrade testing and who owns the custom app. Many plants combine the two. Custom code should sit in a separate app in a repository your company controls, and every upgrade should be tried on staging with real BOMs and work orders first.

ERPNext is a reasonable fit for discrete and light process production. A specialist system may serve better when:

• Line machines must feed counts and stoppages automatically in real time.
• Pharmaceutical or other regulated production needs formal batch records.
• Planning requires finite scheduling across many constrained lines.

I score the alternatives against your own production scenarios; see how ERPNext and Odoo compare for manufacturing, and the cross-platform view on the Iraq ERP consultant page.