ERPNext Manufacturing in Oman

Yield-driven production: seafood, flour and dates

Several of Oman's food processors buy a raw material by weight and sell several products from it. Whole fish becomes fillets, frozen portions and fishmeal. Wheat becomes flour of different grades and bran. Dates are sorted into grades, pitted, pasted or rejected. A simple BOM that says one input makes one output will report perfect yields that nobody on the floor believes.

In ERPNext Manufacturing I handle this in a few deliberate steps:

• Expected loss on the BOM: moisture, trimming and handling loss recorded as process loss, so planned quantities are realistic.
• Scrap and by-products: listed on the BOM with a value, so fishmeal or bran enters stock at an agreed rate instead of zero.
• Actual quantities on the manufacture entry: the supervisor records what was really consumed and produced, and yield variance becomes a report.
• Batches: each run carries a batch with production and expiry dates for traceability.

There is a limit worth knowing. ERPNext does not have a dedicated co-product costing engine, so splitting cost between several main products from one input needs a rule agreed with your accountant, usually by relative sales value or weight, applied through the entry design. Catch-weight selling, where each carton has its own weight, also needs careful testing. I prototype both with your own data before anyone commits, and the wider sector picture is on the Oman manufacturing ERP page.

Three decimals in the rial and the cost of a bottle cap

The rial carries three decimal places, which sounds generous until you cost small components. A preform, cap or label can cost a fraction of a baisa per piece. If the item is stocked and costed per piece, ERPNext rounds that rate according to its precision settings, and a multi-level BOM that multiplies thousands of pieces can drift from the real purchase cost.

The fixes are mostly about design, not code:

1. Choose sensible units: buy and stock granules, caps and labels per kilogram, per roll or per thousand, with conversion factors to the unit used in the BOM.
2. Check rate precision: agree with your implementer how many decimals rates and quantities carry, and test a full BOM cost rollup against a manual calculation.
3. Compare at the top: the finished product's cost should match the sum of purchase invoices for a sample run within rounding, not just look plausible.
4. Watch reports and exports: printed cost sheets, Excel exports and any custom report must show the same precision as the ledger.

Groups with a sister company in a two-decimal currency should also test how amounts display across both. The ERPNext consultant Oman page explains the system-level currency settings; here the concern is that every BOM, valuation and work order cost reflects them correctly.

Routings, job cards and shifts for extrusion and fabrication

Plastics, pipe, cable and steel fabrication plants in Oman's industrial estates tend to run long shifts on a few critical machines. Routing design should follow those machines, because that is where capacity and cost sit.

What I agree with plant managers:

• Workstation types and workstations: an extruder type with each physical line as a workstation, so plans can move work between similar lines.
• Hour rates: power, maintenance and direct labor per workstation, kept as simple as finance can support.
• Routings reused: one routing per product family rather than per item, so a new size does not need a new routing.
• Job cards by shift: start, stop and quantity logged per shift, with downtime reasons from a short fixed list.
• When to skip job cards: a product made in a single step needs no job card; finishing the work order is enough.

Fabrication shops add their own needs: cutting from bars or plate, welding and painting operations, and parts made for a specific customer order. Linking the work order to that order keeps margin visible per job. I document the routine supervisors will follow and train them in short remote sessions, supported by ERP training material they can revisit.

Subcontracting, VAT on inputs and inspection before dispatch

Omani manufacturers regularly send work outside: galvanizing for steel, machining for spare parts, printing for packaging films. ERPNext covers this with subcontracting orders, material held in a supplier warehouse and subcontracting receipts that bring the finished item back with the service charge. I settle who issues the delivery note, how short returns and rejects are recorded, and how often material at each workshop is reconciled.

VAT touches production cost through purchasing. Omani VAT falls under the Tax Authority, and the treatment for your purchases is your tax advisor's decision, not mine. My concern is the ledger: where input VAT is recoverable it should sit in the tax account, not in item valuation, while customs duty, freight and clearing belong in landed cost. Mixing them distorts unit cost quietly. The Tax Authority's e-invoicing program affects sales invoices more than production, so I keep that in the wider ERPNext plan.

Before dispatch, I set up:

• Inspection templates with measured parameters for incoming resin, steel or ingredients.
• In-process checks after critical steps such as welding or extrusion.
• Final inspection linked to the batch shipped, with certificates attached.

That gives sales a document trail for buyers in Oman and the wider GCC. The method behind it is my process mapping work.

Hosting, support and where ERPNext stops

An Omani plant has three realistic support models. Frappe Cloud runs the platform for you, so check its current regions against any customer expectations on data location. A self-hosted server in an Omani data center keeps records local but makes your IT team, or a contractor, answerable for patches, monitoring and backups. A local or regional implementer can bundle hosting with support, which is convenient if the contract names response times and who tests updates before they reach the plant.

ERPNext is a sound choice for many Omani factories, but not for these:

• Continuous process plants in petrochemicals, metals or fertilizers, where plant control systems and process ERP dominate.
• Strict pharmaceutical validation, where computerized systems need formal validation documentation from the vendor.
• Finite scheduling across many lines and changeovers, which needs a planning tool on top.
• No technical owner inside the business to keep the system current.

If your plant fits one of these, I compare alternatives using ERP evaluation and the neutral manufacturing ERP comparison. How I work across the country is set out on the Oman hub and my Oman ERP consultant page.