Contact Info
ERPNext Manufacturing in Norway
Is ERPNext suitable for Norwegian maritime and aquaculture equipment makers?
ERPNext suits Norwegian equipment makers that build to order in modest volumes: winches, pumps, feeding systems, deck equipment and steel structures. Its BOMs, work orders, job cards, subcontracting, serial numbers and project costing cover the core. Engineering change control, heavy project planning and class documentation usually sit elsewhere. I assess that fit remotely and help decide between an in-house developer and a partner.
Last reviewed by Vikas Saroj
Norway's coast supports a dense network of equipment suppliers. Firms that build winches and deck machinery, pumps and valves, feeding and handling systems for fish farms, or steel structures for vessels and installations tend to work to order, in small series, against customer specifications and tight delivery windows. Every unit they ship is later serviced, repaired and supplied with spares for many years.
I work remotely with owners, production managers and finance leads in such firms who are considering ERPNext. I focus on the manufacturing side: how a customer order becomes a project, a set of work orders and a serialized unit, how cost is captured, and which parts need specialist tools or custom development.
What I Do
The scope follows a unit from the sales order through the workshop to its years of service at sea or on a farm.
Mapping how a won order becomes a project in ERPNext with its own work orders, purchases and time, so each delivered unit has one place where cost, progress and documents meet.
BOMs for standard modules and customer-specific variants, using item templates and variants where products repeat, and clear rules for when engineering creates a new BOM for a single order.
Serial numbers on finished equipment and critical components, so the unit history shows what went into it, when it shipped, where it was installed and which spares fit it.
Linking spare part lists and serial records to service orders, warranty claims and maintenance visits, which for many coastal suppliers is a steady revenue line worth designing properly.
Subcontracting orders for welding, machining, galvanizing or painting at partner yards and workshops, with material sent and returned, partial deliveries and supplier charges included in unit cost.
Weighing a staff developer against an ERPNext implementation partner contract, with a register of custom apps, upgrade tests and who answers when production is waiting on a fix.
How I Work
One real order end to end
Pick a recently delivered unit
Follow engineering, purchasing, production
Note where data was retyped
List after-sales needs
Pilot order in a test site
Build project, BOM and routing
Run subcontracting and receipts
Assign serial numbers
Compare cost with calculation
Live orders with support
Train planners and workshop
Load open orders and stock
Review first unit costs
Set upgrade and support routine
A Norwegian deck machinery or aquaculture equipment supplier rarely makes exactly the same thing twice. A customer orders a winch or a feeding system based on a standard design, then asks for a different motor, a longer drum, a specific coating or local control panels. Engineering adapts drawings, purchasing orders long-lead components, the workshop fabricates and assembles, and a subcontractor may galvanize or paint. The unit ships to a yard or a fish farm, often against a fixed date tied to a vessel or a season.
ERPNext covers that flow with standard documents:
What it does not provide is a full engineer-to-order suite. There is no deep engineering change management, no advanced project scheduling with resource leveling and no store for class or certification documentation beyond attachments. Many suppliers accept those limits and keep CAD, planning or document control in specialist tools. The decision depends on your volumes and how complex engineering is, which is why I start from real orders. The general method is on my ERPNext manufacturing page.
The hardest design choice for an equipment maker is how to represent products that are almost standard. ERPNext offers item templates with variants, where attributes such as drum size, motor type or coating create distinct items, and each variant can have its own BOM. That works well when options are finite and repeat. When every order carries unique engineering, a separate BOM per order, copied from a standard one and edited, is usually more honest.
I help you set rules that the engineering office and the workshop can both live with:
The handover from engineering to production is where data often breaks. A parts list from CAD is retyped into the ERP, or purchasing works from a spreadsheet the engineer sent by email. ERPNext can import BOMs through its data import tool, and some firms build an integration from their CAD or PDM system. Whether that integration pays for itself depends on how many BOMs you create in a typical month, and like any custom app it needs an owner.
Settling these rules before go-live avoids a long period of duplicated items and orphaned BOMs that nobody dares to delete.
For a coastal equipment supplier, delivery starts a long relationship. The unit will need spare parts, inspections and repairs, sometimes urgently when a vessel or a farm cannot operate. If nobody can tell which motor, gearbox or seal went into a particular unit, every service request begins with phone calls and old emails.
ERPNext can keep that history if serial numbers are designed in from the start. The finished unit receives a serial number when the work order completes, and critical components keep their own serial or batch numbers as they are consumed into it. The delivery note records which customer and installation received it. From there:
Some suppliers want a customer portal where owners look up their units and order spares. Frappe's portal features can support part of that, but expect custom work for anything polished. I scope it separately so it does not delay the manufacturing go-live, and so the portal's cost is weighed against the service revenue it supports.
Norwegian equipment makers buy in a lot of work: steel fabrication from a partner workshop, machining of shafts, hot-dip galvanizing, blasting and painting. ERPNext's subcontracting flow sends your material to the supplier's warehouse on a subcontracting order and receives the finished part with the service charge, so stock and cost stay complete. Partial returns, rework at the supplier and material the supplier provides themselves need agreed handling, and I test each case with real documents.
Cost per delivered unit then combines several sources:
ERPNext's project costing views and cost centers can bring those together, provided every document carries the project reference. That discipline becomes the main training topic for purchasing and the workshop.
Currency matters here too. Components may be bought in euros, the customer may pay in dollars and the books are kept in kroner. Finance sets how exchange differences are treated; I make sure the project report shows cost in kroner consistently. The ledger side is covered on the ERPNext accounting in Norway page.
A Norwegian manufacturer on ERPNext needs a clear support model, because experienced ERPNext people in Norway are few and production cannot wait for a slow reply. The realistic choices:
Whichever you choose, every custom app, report and integration goes into a register with its owner and a test that runs before each upgrade.
ERPNext is probably not the right system when engineering change control and multi-site project scheduling dominate, when customers demand formal configuration management for every delivered unit, or when you need a large local partner market. A specialist engineer-to-order system or Odoo Manufacturing in Norway could be the better home; the general trade-offs are laid out in the ERPNext vs Odoo manufacturing comparison.
I am independent of Frappe and every implementer and take no commissions. Work runs remotely, and a workshop visit happens only by arrangement. See also the ERPNext Norway page and the ERP consultant Norway page.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
It handles the core well: a project per order, customer-specific BOMs, work orders, subcontracting and costing against the project. It lacks deep engineering change management and advanced project scheduling, so firms with heavy engineering often keep those in specialist tools. I test the fit with one of your recent orders before you commit.
Assign a serial number to the finished unit when the work order completes, and keep serial or batch numbers on critical components consumed into it. The delivery note then records where the unit went. Warranty claims, maintenance visits and spare part sales can all link back to that serial number.
Yes, through subcontracting orders. Your material moves to the supplier's warehouse, finished parts come back on a receipt that consumes it, and the supplier's charge becomes part of cost. Partial deliveries, rework and supplier-provided material each need a rule, and I check every rule against real documents before go-live.
Usually a staff developer, an ERPNext implementation partner working remotely under contract, or a freelance developer alongside managed hosting. ERPNext specialists in Norway are few, so agree response times and code ownership in writing. Confirm what any partner offers directly with them; I help define the requirements but sell no support myself.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
