← All insights

ERPNext manufacturing implementation: from BOMs to a controlled factory cutover

A practical implementation guide for discrete manufacturers: agree the production records, choose the right settings and move unfinished work without counting materials or costs twice.

  1. 01Define
  2. 02Configure
  3. 03Reconcile
  4. 04Prove
  5. 05Cut over
Short answer

ERPNext manufacturing implementation means agreeing how approved product definitions, material movements, shop-floor work and production costs will be recorded, then configuring and proving that flow with your own data. Its manufacturing records provide a starting point, not a finished factory operating model. For a discrete manufacturer, the critical decisions are which bill of materials (BOM) each job uses, how materials and partial output are recorded, who can release stock, and how unfinished production and its value move into the new system.

Will production, stores and accounts agree on what exists on the first morning in ERPNext? A factory can have correct item codes and still go live with parts counted in two places, half-built jobs restarted from zero and rejected output available to ship. Start the implementation with those decisions, not a tour of the manufacturing screens.

Which factory problems should the implementation solve first?

This guide is for a discrete manufacturer: a business making countable products such as cabinets, brackets, equipment or component assemblies. It assumes ERPNext is shortlisted or chosen. The question is how to make it run the agreed production flow, not which ERP brand wins a feature comparison.

Choose a product family where disconnected records cause a visible problem. Purchasing buys parts already on the floor because stores still shows them elsewhere. A supervisor reports a job complete while inspection holds some units. Finance sees a healthy estimated margin but receives material and labour costs after dispatch. The costs are extra buying, missed promises, rework and a margin report nobody trusts—not merely time spent entering data.

ERPNext provides manufacturing records alongside stock and accounting. The business still has to decide when each record is created, who approves it and how exceptions are corrected. A Work Order is an instruction to make something; a material transfer records where parts moved; consumption records what was used; finished output records what was made. Treating those as one event hides unfinished work.

Use the current ERPNext manufacturing documentation as the product starting point. Agree the ERPNext and Frappe Framework versions in the project scope and check their release notes before configuration. The documentation includes version-specific changes; a feature described there is not proof that an older installation or a custom app behaves the same way.

What does ERPNext provide, and what must you configure?

A bill of materials, or BOM, lists the components and quantities needed to make a product. A routing lists the operations, such as cutting, assembly and inspection. ERPNext supports multi-level BOMs, so a stocked subassembly can have its own parts list. Its BOM documentation also distinguishes active and default BOMs and explains that a submitted BOM cannot simply be edited. That helps define the product; it does not replace an agreed engineering-change process.

Turn each factory symptom into a configuration decision and a remaining responsibility
Failure symptomERPNext supportImplementation decisionWhat remains to prove
Operators build from the wrong drawingBOMs with components and operations; selected BOM on the Work Order.Engineering approves the BOM and linked instructions; planner confirms which definition each open job retains.A new default must not silently change an already released job. Specialist design/version systems may need a connection.
The plan buys material already orderedProduction Plan can consider projected stock and create Material Requests and Work Orders.Choose demand sources, warehouses, consolidation and the skip-available settings; buyers approve new commitments.Incoming supply, usable stock and material assigned to other work must be interpreted correctly.
A completed operation is mistaken for saleable stockJob Cards record operation progress; Stock Entries record manufacturing movements and output.Agree who records progress, consumption, completion and inspection release.Partial work, rejected output and finished goods cannot all become available just because a timer stopped.
Outside processing disappears from the stock reportSubcontracting Orders, supplier warehouses and Subcontracting Receipts track supplied material and returned output.Model processed/unprocessed items, the service item, receipt quantities and consumption rules.Supplier communication, overdue receipts, losses and invoice differences still need owners.
A job appears profitable until month endBOM estimates, Work Order operating costs and Stock Entry valuation provide cost records.Finance agrees material consumption, time capture, overhead, outside work and correction rules.Missing time or duplicated service costs can still distort margin. A BOM estimate is not the actual result.

The Production Plan documentation explains how demand can come from Sales Orders or Material Requests and how projected quantities affect shortages. Projected stock can include incoming supply; it is not a count of inspected parts available now. The planner must check when supply will actually arrive before sales promises a date.

ERPNext documents scheduling using workstation availability, working hours and holidays in its Work Order and Workstation guides. That is not evidence that it will automatically optimise every machine, skill, tooling change and urgent order in your plant. Demonstrate the real bottleneck. If specialist scheduling or machine-data collection is necessary, scope that system and its connection separately.

Subcontracting needs its own design. ERPNext’s documented subcontracting flow separates the processing service, materials supplied to the contractor and the returned product. Ask finance to follow one receipt through material consumption, service cost and supplier invoice. A normal purchase of finished goods is not the same flow.

How should the shop floor record materials, time and rejected output?

Work in progress, or WIP, means production that is not yet finished. ERPNext can use a WIP warehouse to represent material on the production floor. A workstation identifies where an operation happens; it is not an inventory location. Decide which physical movements require a stock record and which operation updates only record progress.

Choose between recording material against the Work Order or individual Job Cards, and agree how consumption is calculated. ERPNext’s BOM settings distinguish consumption based on the BOM from consumption based on material transferred. Automatic consumption at completion is often called backflushing. It saves entry only when the assumed quantities match the process; it can conceal extra usage or unused material if nobody records the difference.

Job Cards hold operation time and completed quantities. The documentation describes a version 16 Pending Qty field to distinguish work still to do from process loss. Include partial completion in the demonstration on your actual version. Ten units still awaiting assembly must not become ten units of waste simply because the shift ended.

Quality Inspection supports incoming, outgoing and in-process checks, with templates and configurable document-submission requirements. See the official inspection guide. An inspection record is not, by itself, proof of a complete quarantine system. Design the holding location, who can release it and how every picking, transfer and connected sales channel excludes held stock. Test a failed inspection and an attempted dispatch, not just a successful inspection.

How do you move a half-finished order into ERPNext without doubling it?

Consider an illustrative mounting-assembly manufacturer switching systems between shifts. Customer order SO-240 needs 24 assemblies, none dispatched. Each assembly uses two plates and four bolts. Legacy job WO-240 received all 48 plates and 96 bolts. It has made 10 assemblies, consuming 20 plates and 40 bolts. Eight finished assemblies are released; two are held for rework. Fourteen assemblies remain to be made, with 28 plates and 56 bolts still on the floor. Assume no other usage or material loss.

This is a proposed migration proof, not a report of an ERPNext test or a client result. The implementation team must demonstrate the opening-record method in a rehearsal. The key is importing a defensible opening state, not replaying every historical movement on top of opening balances.

Illustrative opening-state handover for SO-240 and WO-240
Opening factOwner and ERPNext design to proveError to prevent
Customer demand remains 24 assembliesSales retains the legacy order reference and the outstanding commitment. Planner identifies 10 already made and 14 still requiring production.Creating a new job for all 24 because the old production history was not imported.
Eight assemblies are released; two await reworkWarehouse and quality load separately identifiable released and held stock with the agreed values and references.Loading all 10 as saleable, or treating the two physically completed units as another two new assemblies to build.
WIP holds 28 plates and 56 boltsStores counts the floor; the migration team establishes those quantities in the correct WIP location and links the residual production design.Leaving the same components in opening stores stock, then issuing them a second time.
Fourteen assemblies remain unfinishedProduction retains the original instructions, operation progress and legacy job link. Demonstrate a residual Work Order or another explicitly reconciled method.Resetting every operation or adding the already consumed 20 plates and 40 bolts to opening WIP.
Existing production carries material and conversion costFinance signs the opening finished-stock and WIP values, including the treatment of work already performed.Adding old labour or material cost again through recreated time logs or manufacturing entries.

ERPNext’s Stock Reconciliation tool supports opening quantities and valuation by item and warehouse at a specified time. Its Data Import tool supports structured record imports. Neither fact establishes a one-button conversion of partially completed legacy jobs. A WIP warehouse count does not carry operation progress or explain all accumulated labour. Agree how those values and references will survive, and retain the legacy detail needed to investigate them.

The first live movement must reconcile to the signed opening state
  1. 01
    Accept the opening stateProduction, stores, quality and finance

    Counted floor material, released and held units, residual work and signed values. If any disagree, hold cutover rather than force a balancing adjustment.

  2. 02
    Dispatch six released assembliesWarehouse, against the approved sales instruction

    Six dispatched leaves two released, two held and 18 still owed to the customer. If picking can use held stock, stop and correct the release control.

  3. 03
    Continue the remaining productionSupervisor and operators

    Consume only the remaining material through the agreed method. If completion posting fails, check for an existing Stock Entry before retrying.

  4. 04
    Rework and close with evidenceQuality with production; finance closes the values

    Record additional work and the release decision separately. Reconcile material, output and cost before closing the residual job.

Illustrative first-shift owners, triggers and failure handling

Give every imported open order and job a legacy reference and a named owner. When a migration row fails, reconcile what loaded before re-running it. When an external shop-floor connection times out, check whether ERPNext already accepted the completion before sending another. Preventing duplicate records is part of the migration or integration design, not a claim that any connector does it automatically.

If stock products and custom jobs compete for parts, add the separate mixed-mode manufacturing decision guide. That resolves priority and promise rules; the opening-state proof here resolves what production and value actually cross the cutover.

What implementation sequence produces a trustworthy first live day?

Start with one representative product family and its difficult exceptions. A pilot does not excuse leaving purchasing or finance out: the selected flow must still reach stock, dispatch and cost. Expand only after the records and responsibilities work together.

ERPNext manufacturing implementation stages and the evidence needed to move on
StageClient input and ownerExit evidence
1. Discover and bound the flowOperations maps demand, drawing approval, making, inspection, outside work and dispatch. Finance defines the cost questions.An agreed process map, exceptions, target versions and a list of what ERPNext will not own.
2. Clean the production dataEngineering owns items, units, BOM quantities, approved alternatives and instructions; production owns operations and realistic times.A sample build uses the correct component quantities and units. Duplicate codes and obsolete defaults are resolved before bulk loading.
3. Configure records and approvalsPlanner, warehouse, quality and finance agree demand sources, warehouses, consumption, inspection, costing and permissions.Each setting has an owner and a reason. Normal-role users can perform their work but cannot authorise their own restricted corrections.
4. Design migration and connectionsData owners inventory open sales, purchases, work, supplier-held stock and balances. Integration owners identify the source of each external update.Trial loads reconcile; unfinished production retains a reference and value; failed or repeated messages have a recovery path.
5. Prove the full flow and trainActual users run normal orders, partial output, scrap, rework, shortages, outside processing and reversals.Signed acceptance cases, reconciled quantities and values, and users completing their tasks without consultant narration.
6. Rehearse and execute cutoverProject lead freezes the relevant movements, coordinates counts, loads final balances and controls queued external updates.A timed rehearsal, agreed go/no-go criteria and a fallback before live transactions begin; final production, stock and finance sign-off.
7. Support the first shifts and closeNamed production and finance owners review exceptions with the support team.Daily open-job and stock/value checks, a defect queue, tested backups and an agreed support handover.

Use ERPNext’s role permissions to distinguish creating, submitting, cancelling and amending records. The exact approval design is implementation work. Test with an operator, a supervisor and a finance user—not only an administrator who can bypass ordinary restrictions.

Where traceability is needed, migrate the actual lot and serial references, not only total quantities. ERPNext documents transaction-specific Serial and Batch Bundles. Prove how a retained legacy lot connects to new production and dispatch records; loading an opening quantity does not recreate its entire historical genealogy.

A connected design must name the record owner. Engineering may retain drawings in a separate design system; a specialist shop-floor system may capture machine events; ERPNext may own stock and financial postings. Define which approved event crosses each boundary, who handles a rejection and how totals are reconciled. Scope that work through systems integration and automation, rather than assuming an unspecified connector is included.

Decide the fallback boundary before cutover. Restoring a backup after live shipments or invoices have been issued can erase records while the physical and financial events still exist. Before the first live posting, a return to the old process may be possible; after it, controlled correction or a separately reconciled recovery may be necessary.

Which acceptance tests should a manufacturer insist on?

Ask the implementer to run these with your configured ERPNext version, migrated sample data and ordinary user roles. They are proposed acceptance criteria, not claims that an unconfigured installation passes. Use the wider manufacturing ERP test framework for test ownership, defect tracking and go/no-go evidence.

Evidence to request before signing off ERPNext manufacturing
Buyer testPass evidenceInvestigate if
Approve a new BOM while an older job remains open.The planner can show the definition on each affected job and explain which work changes and which does not.Changing the default rewrites instructions or alters material requirements without review.
Produce part of an operation and stop for the shift.Completed, pending and lost quantities have the intended meaning on the installed version; outstanding work remains visible.Unfinished units become process loss or the whole job appears complete.
Issue extra parts, return unused parts and reject output.Work Order and Stock Entry records explain actual movement and consumption. Held units cannot be dispatched through any agreed route.The figures only reconcile after an unexplained stock adjustment or held stock reaches the picking list.
Send material for outside processing and receive only part back.The supplier-held balance, accepted output, losses and service cost reconcile to the documented subcontracting flow.Material vanishes at dispatch to the supplier or service cost enters valuation twice.
Run the opening-state example and first live dispatch.Sales, production, stores and finance reconcile to the signed snapshot, including the two held units and remaining WIP.The migration creates another full production requirement or repeats historical consumption.
Interrupt an external completion update, then retry it.The integration team demonstrates one accepted production event, a visible exception and a controlled recovery.Two completions, stock receipts or cost postings appear because a connection timed out.
Reconcile the job’s cost and correct a bad posting.Finance follows material, operation cost, outside work and agreed additional cost into stock and accounting, with authorised correction evidence.A BOM estimate is shown instead of the posted result, or cancelling a record leaves unexplained balances.

ERPNext’s Stock Entry documentation distinguishes material transfer, consumption and manufacture, and explains additional costs and ledger access. The implementation must prove the chosen sequence and accounting treatment together. A completed Work Order screen is not a substitute for the finance reconciliation.

When is ERPNext a sensible fit, and what drives the implementation cost?

ERPNext is worth evaluating when the factory’s discrete production can be represented through maintainable item structures, BOMs, operations, stock movements and documented exceptions, and the business can assign owners to those records. The case weakens if success depends on unproven specialist scheduling, deep machine integration, complex engineering configuration or regulated electronic records being available without additional systems or validation.

Quality records and lot tracking do not automatically establish regulatory compliance. Likewise, a manufacturing flow does not establish that US tax, UK VAT, payroll or every statutory reporting requirement is covered by the same installation. Have the appropriate finance or specialist adviser confirm the local scope and prove any required separate app or integration before committing.

Scope the work behind the quote rather than relying on a generic implementation fee
Cost driverWhat changes the effortWho must retain ownership
Product-data cleanupDuplicate parts, inconsistent units, multiple BOM levels, stale revisions and undocumented alternatives.Engineering and master-data owner.
Unfinished production migrationJobs at different operations, supplier-held material, quality holds and WIP value that includes work already performed.Production and finance jointly.
Connections and custom workDesign tools, shop-floor devices, warehouse systems or customer orders with unclear identifiers and unreliable failure recovery.An integration owner and a maintainer for any custom app.
Costing and reportingTime capture, overhead policy, outside services and the detail needed to explain estimated versus posted cost.Finance with production supervisors.
Training and ongoing operationShift coverage, usable devices, support availability, hosting, backups, upgrades and regression checks.Operations sponsor and a named technical/support provider.

Ask every proposal to separate standard ERPNext configuration, data preparation, migration, integrations, custom development and ongoing support. A small first phase may reduce risk, but excluding the stock and finance reconciliation only postpones it. Do not accept a fixed price or duration without a defined product family, data condition, connected-system scope and acceptance evidence.

For a useful starting discussion, bring an approved BOM and drawing, one open Work Order, a floor-stock count, a held-output example and the report finance uses to explain cost. Harmatiq’s ERP and manufacturing implementation service can help scope the operating flow, migration and connections. The first deliverable should be an agreed design and proof case—not a promise that installing ERPNext alone will fix the factory.

Find the handoff that needs fixing.

Bring one real order, the systems it crosses and the exceptions your team handles manually. We can turn that journey into an implementation scope.

Discuss your workflow