ERPNext Manufacturing in Sweden

Swedish subcontract manufacturing and where ERPNext fits

A typical Swedish subcontract manufacturer makes parts to someone else's design. The customer sends a drawing, agrees a price per batch size, then calls off quantities week by week. Margins depend on setup times, scrap, material prices and how well the shop loads its machines. Many such firms run an older production system or a mix of spreadsheets and an accounting package, and the person who knows how it all fits together may be close to retirement.

ERPNext covers much of what that business needs in one database:

• BOMs and routings: multi-level, with operations, workstations and scrap items.
• Work orders and job cards: material transfer, operation time logging and completion.
• Subcontracting: sending material to a partner shop and receiving finished parts.
• Stock: batches, serial numbers and perpetual valuation posted to the ledger.
• Quality inspection: templates with readings and acceptance criteria.

It is weaker on the specifics of supplying large OEMs: rolling delivery schedules, automotive-style EDI, label standards and finite scheduling across many constrained machines. Those need a custom app, an integration with a specialist tool or a decision that the shop is better served by another system. I make that call with you on the evidence of your own orders, following the method on my ERPNext manufacturing page.

Drawings, revisions and customer call-offs

The two areas I examine first for a Swedish supplier are revision control and delivery schedules, because both are easy to underestimate.

Revisions. ERPNext lets you attach files to items and BOMs and keep several BOMs per item, with one marked as default. It is not a PLM system: it does not manage drawing approval workflows or engineering change orders in depth. For a machine shop that is often acceptable if the rules are clear. I help you decide whether a revision change creates a new item code, a new BOM on the same item or just a new attachment, and how the shop floor sees which revision a job card is for. If you run a CAD-linked document system, we define which system is the master.

Call-offs. Vehicle and machinery customers often send forecasts and firm call-offs through EDI or a supplier portal. ERPNext has no built-in handling for rolling schedules. The options are a scheduled import that updates sales orders, a blanket order with releases against it, or a custom app that keeps forecast and firm demand apart for the production plan. Each carries a build cost and a maintenance owner, and the right one depends on how many customers send schedules and in which formats.

Both decisions go into the fit-gap list before configuration starts, because changing them after go-live means reworking item and order history.

Outside processing, inspection and serial traceability

Few Swedish machine shops do everything in-house. Hardening, plating, painting, laser cutting or a special machining step often goes to a partner nearby. ERPNext models this with subcontracting: a service item for the outside operation, a subcontracting BOM, a subcontracting order to the supplier, a transfer of your material to their warehouse and a receipt that consumes it and books the finished part with the supplier's charge.

That flow needs care in a few places:

• Partial returns: suppliers send parts back in several deliveries, so receipts must handle partial quantities and leftover material.
• Scrap at the supplier: agree how rejected pieces are recorded and who pays for them.
• Stock visibility: material at the supplier sits in its own warehouse rather than vanishing from the books.

Quality inspection templates can be required on purchase receipts, on manufacture entries and before delivery. Readings are stored against the inspection and the batch or serial number. When a part later fails at the customer, you can trace it back to the job card, the raw material batch and the material certificate attached to the receipt.

Customer quality systems sometimes demand reports or layouts beyond what standard ERPNext prints. Those are usually solved with custom print formats or reports, which belong on the same ownership register as any other custom code.

Costing a job against its quotation

A subcontractor's results depend on whether the actual cost of a batch matches what was quoted. ERPNext values stock perpetually, so every material issue, job card and finished goods entry posts to the ledger, and the work order can show planned against actual material and operating cost. That only helps if the inputs are honest.

The decisions I work through with your production and finance leads:

• Workstation hour rates: machine, labor and overhead elements per workstation, reviewed when wages or energy costs move.
• Setup time: how setup is recorded on job cards so short batches carry their true cost.
• Material price basis: valuation rate or last purchase price in the BOM, and how often BOM costs are refreshed.
• Scrap and rework: how scrap items and rework operations affect cost and stock.
• Currency: steel or components bought in euros and sold in kronor, with exchange differences posted as your accountant decides.

Once these are settled, a simple report comparing quoted cost per part with actual cost per completed work order gives the owner a view that many shops rebuild in a spreadsheet each month. It also gives sales a firmer basis for the next price discussion with the OEM, and it shows which parts are quietly losing money.

In-house developer, partner or a specialist system

ERPNext rewards companies that accept ownership of their system. For a Swedish manufacturer the realistic support models are:

• In-house developer: someone on staff who knows Python and the Frappe framework, maintains custom apps and runs upgrades on a test copy first. Fast and close to the shop floor, but a single point of failure unless the work is documented.
• Implementation partner: a firm specializing in ERPNext, in Sweden or elsewhere in Europe, providing development and support under contract. Confirm their manufacturing experience, response times and who owns the code they write.
• Frappe Cloud plus freelance help: managed hosting with a contracted developer for changes, which can suit smaller shops.

ERPNext is likely the wrong platform if your business depends on advanced finite scheduling across many machines, heavy OEM EDI with label and packaging standards, or validated processes demanded by aerospace or medical customers. A manufacturing system with an established Swedish user base, or Odoo Manufacturing in Sweden, may then fit better. The ERPNext vs Odoo manufacturing comparison sets out the general trade-offs.

I am not a Frappe partner and sell no development or hosting, so the recommendation follows your requirements. Workshops run remotely, with a shop-floor visit only by arrangement. More context sits on the ERPNext Sweden page and the ERP consultant Sweden page.