Why ERPNext fits a manufacturer, and where the build gets hard
A manufacturer needs one answer to three questions at the same time: what the plant made, what it consumed, and what that cost. Production, stock, costing and the general ledger have to agree, and the shop floor will expose every assumption made in the back office. ERPNext is a reasonable base for this work because it covers accounting, inventory, manufacturing and projects in one system built on the Frappe Framework. The core code is licensed under GPL-3.0, and the platform can be self-hosted inside your own cloud accounts, data centers or isolated networks, which keeps plant and cost data under your control. The licence and hosting choices are settled early and cost little to change later, so they should not take up the planning time.
The real work sits in how the plant is modeled. ERPNext ships with BOMs, work orders, workstations, operations and job cards, but the values that matter are the ones your process owners supply: the capacity and hourly rate of each workstation, the operation sequence for each product family, the scrap and rework allowances, and the point at which a job card records time and quantity. Batch and serial numbers are the hardest part to get right, because a missed scan at receipt, issue or completion breaks traceability for every downstream lot. Landed costs for freight, duty and inspection also feed valuation, so the costing method and its posting rules must be agreed with finance before go-live. Confirm these decisions with your plant managers, quality lead and controller, and check the current module behavior against the frappe/erpnext repository and your target version before you commit to a design.
Which industry requirements shape an ERPNext manufacturing build
This table maps each industry requirement in the topic facts to what it means for an ERPNext build. Read each row as a question to answer before design starts: which systems fall in scope, and what the ERP side must supply as evidence. The main takeaway is that ERPNext itself rarely carries the obligation, but the integrations, access model and data flows you design around it do.
| Requirement | What it means for the ERPNext build | Source |
|---|---|---|
| ISA/IEC 62443 series for industrial automation security | Decide whether ERPNext sits inside or outside the industrial control zone. Keep ERP, MES-style job card data and shop floor controllers in separate zones with defined conduits between them. | ISA, ISA/IEC 62443 Series of Standards |
| ANSI/ISA-62443-2-1-2024 security program requirements for asset owners | Assign owners for each ERPNext integration that touches production data, and document who approves changes to those interfaces and to shop floor access. | ISA, ISA/IEC 62443 Series of Standards |
| ANSI/ISA-62443-3-2-2020 security risk assessment for system design | Run a zone and conduit risk assessment before connecting ERPNext to production systems, and record which data flows cross each boundary. | ISA, ISA/IEC 62443 Series of Standards |
| NIST SP 800-82 Rev. 3 for OT security (September 2023) | Treat SCADA, DCS, PLCs and building systems as OT with their own performance and safety needs. Avoid designs where ERPNext jobs or scripts poll controllers directly. | NIST, SP 800-82 Rev. 3 |
| NIS2 Annex II listing manufacturing as a critical sector | Confirm with counsel whether your entity or its subsidiaries are in scope. If so, ERPNext logs, access records and incident data must support 24-hour early warning, 72-hour notification and one-month final reporting. | EUR-Lex, Directive (EU) 2022/2555 |
| Machinery Regulation essential requirement 1.1.9 (applies from 14 January 2027) | If you ship machinery with connected functions, the design must prevent a connected device from causing a hazardous state. ERPNext rarely controls this, but it shapes remote access and configuration pushes to products. | EUR-Lex, Regulation (EU) 2023/1230 |
| Cyber Resilience Act reporting duties (Article 14 from 11 September 2026) | Manufacturers of products with digital elements need a process to report actively exploited vulnerabilities and severe incidents. ERPNext should hold product, component and serial records so affected units can be traced quickly. | EUR-Lex, Regulation (EU) 2024/2847 |
| CMMC levels for defense contractors (32 CFR Part 170) | Level 1 covers federal contract information, Level 2 covers CUI under NIST SP 800-171 Rev. 2, and Level 3 adds selected NIST SP 800-172 requirements. Scope the ERPNext environment and its integrations to the level your contracts require, and confirm current phase timing with the contracting authority. | eCFR, 32 CFR Part 170 |
| LDAP or SSO access control for ERPNext users | Map directory groups to ERPNext roles and restrict shop floor users to the workstation and job card permissions they need. Review group mappings as part of each access review. | Frappe, ERPNext LDAP integration documentation |
Which ERPNext modules and settings a plant needs
A plant rarely needs every manufacturing feature on day one. These six components cover the planning, shop floor, supply, quality, traceability and cost settings that most ERPNext manufacturing rollouts configure, and each one depends on decisions the plant must make before anyone touches the system. Confirm the behavior of each setting against the documentation for your ERPNext version before you build.
Production planning and MRP
Production planning turns sales demand and stock levels into planned production orders and material requests, based on the bill of materials for each item. Before configuration, agree with the plant how far ahead demand is planned, which stock levels count as available, and whether planning runs on a fixed schedule or on demand. Confirm with the ERPNext documentation for your version how planning runs, which items it includes, and how it treats safety stock and in-transit material.
Workstations and job cards
Workstations describe where work happens, with capacity and hourly cost, and operations describe the steps of a routing. Job cards record the time and quantity each operation actually consumed on the shop floor. Decide with the plant which operations are tracked, how operators log time (terminal, tablet or supervisor entry), and how downtime is recorded. Confirm with the documentation how job cards feed costing for your version.
Subcontracting
Subcontracting covers work that an outside supplier performs on materials you send them, such as plating or machining. ERPNext models the supplied raw materials, the finished goods returned and the service charge. Decide with the plant which supplier operations are outsourced, who holds title to materials at the supplier site, and how returned quantities are reconciled against what was sent. Confirm the subcontracting flow and its accounting entries for your version.
Quality inspections
Quality inspections record checks against an item or a batch at receipt, during production or before delivery, with readings compared to accepted ranges. Before configuration, agree with quality staff which inspection points apply to which items, what readings and acceptance criteria are required, and who may accept or reject a lot. Confirm how inspection results affect stock movement in your ERPNext version.
Batch and serial traceability
Batch and serial numbers link stock movements, production and deliveries to specific lots or units, which is what recall and warranty work depends on. Decide with the plant which items need batch or serial tracking, how batch numbers are generated, what shelf-life rules apply, and whether the traceability report must show upstream and downstream movements. Confirm how these settings interact with stock entries and manufacturing for your version before loading master data.
Landed costs and costing
Landed cost vouchers add freight, duties and handling to the value of received stock, so that item valuation reflects the full cost of purchase. Costing also depends on the valuation method, the operating cost of each workstation and the rates used for raw materials. Decide with finance which costs are allocated to items, by quantity or by value, and when the costing run is performed. Confirm the valuation and landed cost behavior for your ERPNext version with your accountants.
Which shop floor integrations manufacturers ask for first
Shop floor requests often ask ERPNext to receive counts, status or scrap figures directly from machines and PLCs. The control network is usually a separate trust zone with its own safety and availability requirements, so ERPNext should not hold direct connections into it. A gateway or integration layer inside the plant should read from controllers, normalize the values and push only approved records into ERPNext through its API. The data flow is mostly machine to layer to ERPNext, and writes back to machines are a separate, higher-risk decision. The ISA/IEC 62443 series is a useful reference for how asset owners should group and protect these zones.
- Data direction: Mostly inbound, from controllers to the gateway and then to ERPNext as job card or stock entries.
- Trust boundary: The boundary between the operational network and the business network, which should be crossed through one controlled point.
- Controlled interface: A gateway that validates values, rate-limits writes and logs each transaction.
- Failure handling: Define what happens when the gateway or ERPNext is unavailable, so buffered counts are not lost or double-posted.
- Write-back: Treat any command from ERPNext to a machine as a separate design with its own approval and safety review.
Confirm with your automation vendor which protocols your controllers expose and who owns the gateway.
Manufacturing execution systems and historians often hold cycle times, downtime reasons and quality readings that ERPNext also needs for costing and planning. The cleanest pattern keeps the MES or historian as the source for high-volume process data and sends summarized results to ERPNext, such as completed quantities, labor time or variance by work order. Copying every sensor reading into ERPNext would strain the database and blur which system is authoritative for each figure.
- Data direction: Usually two way for work orders and completions, one way for historian summaries.
- Trust boundary: Between the MES or historian and ERPNext, often across a site or cloud boundary.
- Controlled interface: An integration service that maps identifiers, such as item codes and work order names, and rejects unmapped records.
- Ownership: Decide which system owns the work order status, the labor time and the scrap figure.
- Volume: ERPNext's Data Import tool is designed for a few thousand records at a time, so bulk history loads need a separate path.
Ask each vendor how it exposes its data and whether it supports retries and idempotent posting.
Label printing and barcode scanning look simple, but they touch serial numbers, batch numbers and lot traceability, so they affect quality records as well as warehouse movement. The usual design keeps label templates and print jobs close to the line, while ERPNext remains the source of item, batch and serial data. Printers and scanners on the shop floor should reach ERPNext through a print or scan service rather than through shared credentials typed into terminals.
- Data direction: Outbound for label data, inbound for scan events that create or move stock.
- Trust boundary: The shop floor network and any browser or kiosk used to scan.
- Controlled interface: A print service or scanning client with its own API key, scoped to the warehouse roles it needs.
- Traceability: Confirm which batch and serial fields must appear on labels for your quality process.
- Offline operation: Decide how scanning continues during a network outage and how records are reconciled afterward.
Review label requirements with your quality team before you fix the template.
Plant users often share workstations and move between shifts, so identity is a common weak point. ERPNext supports LDAP login against Active Directory or OpenLDAP through LDAP Settings, with SSL/TLS options and automatic mapping of LDAP groups to ERPNext roles at each login. Social Login Key lets users sign in through providers such as Google, Microsoft, GitHub, Facebook or Frappe and through custom OAuth or OpenID Connect endpoints. Use one identity source for plant users wherever possible, so that leaving the company removes access in one place.
- Data direction: Authentication requests flow from ERPNext to the directory or identity provider, and role attributes flow back.
- Trust boundary: Between the plant directory and ERPNext, and between ERPNext and any external identity provider.
- Controlled interface: LDAP over TLS or an OIDC provider you operate, with group-to-role mapping reviewed before go-live.
- Shared terminals: Plan session timeouts and kiosk logins, since group mapping alone does not handle shift sharing.
- Server Scripts: Server Scripts are disabled by default from version 15 and must be enabled with the
server_script_enabledsetting. Frappe Cloud public shared benches do not allow them, so custom login or role logic that depends on them needs a self-hosted or dedicated setup.
Confirm your directory group structure and the ERPNext version before you map roles.
Quality management and maintenance tools often run as separate products, or as Frappe apps alongside ERPNext. Inspection results, nonconformance records and equipment work orders all need to link back to the item, batch, work order or asset that ERPNext tracks. Decide whether the external tool or ERPNext owns each record type, then exchange identifiers and status rather than duplicating full records. Where regulated records are involved, such as electronic records under 21 CFR Part 11, the signature and audit trail design must be checked before any integration goes live.
- Data direction: Bidirectional for linked identifiers and status, one way for finished inspection results.
- Trust boundary: Between ERPNext and any separate quality, CMMS or document system, often with different administrators.
- Controlled interface: Documented APIs or scheduled exports with reconciliation checks, rather than direct database access.
- Ownership: Name one system of record for each inspection, nonconformance and maintenance order.
- Regulated records: Confirm whether 21 CFR Part 11 or a similar regime applies to the records you exchange.
Ask your quality and maintenance vendors how they handle identifiers, retries and audit logs before you commit to a data model.
How a manufacturing rollout is usually sequenced
The sequence moves from agreed process design to clean master data, then to a single production line, and only then to a full cutover, so that costing and traceability are proven before the whole plant depends on them. Each phase closes with a written check that the next phase can rely on.
Map BOMs, routings and workstations
The partner and your production, engineering and finance leads document how products are built today: bills of materials with their versions, operations in each routing, workstations with their capacity and cost rates, and where subcontracted operations leave the plant. Gaps are recorded as design decisions, such as whether a job card is closed per operation or per work order. The step is done when each finished product has one agreed BOM and routing, and the costing approach is signed off by finance.
Clean master data before importing
Item codes, units of measure, suppliers, customers, warehouses and opening stock are checked against the process map and duplicates are merged or retired. The Data Import tool accepts CSV or Excel files and downloadable templates, supports child table rows, and its documentation advises importing only a few thousand records at a time, so large sets are split into batches with a load log for each. The step is done when a test batch imports without errors, and the team can trace a sample of records back to the source file.
Import masters and opening balances in batches
Masters are loaded first, then transactional history or opening balances, in batches sized to the import guidance. After each batch, record counts and key totals are compared with the source system, and any rejected rows are corrected in the source file rather than edited ad hoc in the database. The output is a reconciliation sheet showing that item, BOM, stock and ledger totals match the source for each batch. Duration depends on data volume and scope, so the written plan from the partner should state the batch schedule and the people who sign off each batch.
Pilot on one production line
One production line or product family runs real work orders through ERPNext: planning, job cards at its workstations, material issue, quality inspection where required, and finished goods receipt. Shop floor users record time and scrap on the same screens they will use after go-live, and the team logs every workaround. The pilot is complete when a full set of work orders has closed with stock and cost postings that the production supervisor and the controller accept, and the open defect list is agreed for the next phase.
Run a parallel period with costing reconciliation
For a defined period, production runs on the existing system or spreadsheets while ERPNext carries the same orders in parallel. Finance reconciles material consumption, labor and overhead absorption, landed costs on purchases, and stock valuation between the two records and documents every difference with its cause. The step is done when the differences are explained, each explained difference has an owner and a fix or an accepted tolerance, and the controller signs the reconciliation. The length of this period is a decision for your finance team and should be fixed in the written plan.
Confirm traceability and quality controls
Before the cutover, the team tests batch and serial traceability from raw material receipt through production to shipment, including a mock recall or trace request. Quality inspection templates and the points where inspections block stock movement are confirmed with the quality lead. The output is a trace report that starts from a finished-goods serial or batch and reaches the supplier lots and work orders behind it, with any gaps logged as open items before go-live.
Go live with hypercare support
Production cuts over to ERPNext on a date agreed in advance, with the opening balances reconciled one final time and the old system set to read only. Super users sit on the floor for the first working days, and the partner works through a defined issue queue with priorities agreed in the plan. The step closes when open issues are either resolved or scheduled, the support model for after hypercare is in place, and the handover documents for configuration, scripts and integrations are accepted by your team.
Compliance obligations that touch a manufacturing ERP
A manufacturing ERP holds the records that regulators, customers and auditors ask for: production lots, serial numbers, supplier data and incident contacts. The obligations below apply to different parts of the business, so confirm which ones reach your plant, your products and your contracts before you design the ERP around them. DeployOpen prepares systems, controls and evidence for these reviews, but independent auditors and certification bodies issue any audit report, attestation or certification.
NIS2 incident reporting
Manufacturing is a critical sector under NIS2 Annex II, covering electrical equipment, machinery, motor vehicles and other transport equipment, among others. In-scope entities must send an early warning within 24 hours, an incident notification within 72 hours and a final report within one month. Important entities face fines of at least EUR 7 million or 1.4% of worldwide turnover. For ERPNext, check that incident contacts, asset lists and supplier records can be pulled quickly, and that the ERP's own backups and access logs can support a timeline.
Cyber Resilience Act reporting duties
The Cyber Resilience Act covers products with digital elements, which can include connected machines and embedded software your plant ships. Its main obligations apply from 11 December 2027, but manufacturers' Article 14 duties to report actively exploited vulnerabilities and severe incidents have applied since 11 September 2026. Ask which of your products fall in scope, who owns vulnerability intake, and whether your ERP records which component versions shipped to which customers so you can respond.
Machinery Regulation essential requirements
Regulation (EU) 2023/1230 applies from 14 January 2027 and requires that machinery be protected so that connecting another device or a remote device does not lead to a hazardous situation. This affects machine design and commissioning, but the ERP is involved where machine configuration, firmware versions and service records are tracked against serial numbers. Confirm with your notified body or compliance lead which technical file records must live in the ERP and which stay in engineering document control.
CMMC levels for defense contract data
If your plant handles federal contract information or controlled unclassified information for defense work, CMMC under 32 CFR Part 170 sets three levels. Level 1 covers the 15 safeguarding requirements of FAR 52.204-21, Level 2 covers the 110 requirements of NIST SP 800-171 Rev. 2, and Level 3 adds 24 selected NIST SP 800-172 requirements. Confirm your current contract clauses and the phase in effect, since the Department of War has suspended CMMC Phase II requirements. Ask whether quotes, drawings and part data sit in the ERP and who can see them.
21 CFR Part 11 for regulated product records
Only apply 21 CFR Part 11 if your manufacturing records support products regulated by the FDA and those records are electronic records or electronic signatures that replace paper. In that case, the ERP needs controlled access, audit trails, signature meaning and validation evidence for lot release and quality records. A plant making non-regulated goods does not need this card. Confirm scope with your quality team before configuring approvals or inspection sign-offs in ERPNext.
What manufacturers ask before hiring an ERPNext partner
What drives the cost of an ERPNext manufacturing implementation?
The cost is driven by how many plants, production processes and integrations the written scope covers, and by how much of the data and costing logic must be cleaned and agreed before go-live. Cost has two parts: the one-time build (configuration, scripts or custom apps, data migration, testing and training) and the recurring part (hosting, the Frappe Cloud plan if you choose it, and any support retainer). Self-hosting ERPNext is free under its GPL-3.0 license, so your infrastructure and staff time are the main running costs. DeployOpen does not publish a price list. Ask for a quote that lists each deliverable, the assumptions behind it, what the plant team must provide, and which items are one-time versus recurring.
How long does an ERPNext plant build take, and what makes it longer?
Duration depends on the scope agreed in writing, not on a general rule. The biggest drivers are the number of work centers and routings to model, whether subcontracting and quality inspections are in scope, the volume and cleanliness of item, BOM and stock history to migrate, and how many shop floor or accounting systems must integrate. Decision-making speed on costing rules also matters, because landed cost and valuation choices affect several modules at once. Ask any partner for a phased plan with milestones for design, build, data load, testing and go-live, and check which items depend on your own team's availability.
What must our plant team supply before an ERPNext build starts?
Your team must provide the approved item master, current bills of materials with revision rules, routings with operations and workstation capacity, and the costing rules your controller already uses for materials, labor, overhead and scrap. You also need the warehouse layout, serial and batch policies, quality inspection criteria, and a list of the shop floor machines or systems that will exchange data. Missing or inconsistent inputs are a common cause of rework, so ask the partner to confirm each input in the written scope and name the person who signs it off.
Can our internal IT team build ERPNext for manufacturing without a partner?
Yes, a capable internal team can build it, and ERPNext is free to self-host under GPL-3.0. The questions to answer honestly are whether your team already runs Linux, the bench command line tool or Docker-based deployments, can maintain a Python and JavaScript codebase, and has someone who knows manufacturing costing well enough to test it. Also consider the upgrade path, since each major version has its own support window. A partner is most useful when the scope is fixed, the timeline is tight, or the internal team needs to hand over documentation and tests. Compare the internal estimate with a written partner scope before deciding.
Do we need Server Scripts for manufacturing customizations, and what does Frappe Cloud allow?
Many manufacturing needs can be met with configuration, custom fields and standard print formats, and Server Scripts are needed only for logic that cannot be configured. From version 15, Server Scripts are disabled by default and must be enabled with the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so a plant that needs document-event logic should plan for a dedicated bench, a self-hosted deployment, or a custom app instead. Confirm this limit against the current Frappe documentation before you choose a hosting model.
Which ERPNext version should a manufacturer choose given the support dates?
Choose a version that is still supported for the whole period you plan to run it. According to Frappe's supported versions page, ERPNext and Frappe Framework version 14 reached end of life on January 31, 2026, version 15 is planned to be supported until the end of 2027, and version 16 until the end of 2029. A new plant build should normally start on version 16 unless a specific app or integration requires otherwise. Also confirm that the minor releases your team applies, such as those published on the ERPNext releases page, remain within the support window. Keep a dated upgrade plan from the start.
How are shop floor and machine integrations scoped in an ERPNext project?
Scope each integration as a separate item with its data direction, trigger, frequency, volume, owner and failure handling. Typical examples are work order and job card status from the shop floor, machine counts or downtime, quality results from test equipment, and barcode or label printing. ERPNext's Data Import tool handles CSV or Excel loads and advises importing only a few thousand records at a time, so bulk machine data needs a different pipeline. Ask the partner to name the protocol, the authentication method, the test environment and who maintains each interface after go-live. Industrial network security requirements, such as those in the ISA/IEC 62443 series, should be reviewed before connecting control systems.
What to confirm with the vendor and your plant before build
Before any build work, confirm the exact ERPNext version you will run and its support status. The supported versions page lists the end-of-life dates for each major release, so check that the version you pick will still receive fixes for the length of your planned operating period. Ask the vendor which Frappe Framework version pairs with it, and whether you need a matching Frappe Cloud support plan to keep warranty coverage. Do not assume that a manufacturing feature you saw in a demo exists in your chosen release. Ask for the release notes covering Work Order, Job Card, Subcontracting and Quality Inspection behavior on that version, and test each one against your own BOM structure before you commit to a design.
Next, confirm what your shop floor can actually send to ERPNext. Make a written inventory of every machine, PLC, scale, label printer, barcode reader and MES or SCADA system that must exchange data with the ERP, and record which of them can expose data by an interface you can reach from a server. For each one, identify the protocol, the owner who can change its configuration, and whether the vendor allows third-party connections without voiding support. Where a machine cannot connect, decide whether manual entry at a workstation is acceptable, and write that decision down. ERPNext can take data through its API and server-side logic, but the connection to the controller itself usually sits in a separate layer that your plant or integrator must own.
Finally, confirm your plant's own safety and operational technology requirements before the integration design is fixed. The ISA/IEC 62443 series governs security for industrial automation and control systems, and NIST SP 800-82 Rev. 3 covers operational technology security, including performance, reliability and safety. Ask your site engineering and safety teams which network zones and conduits they will allow between the ERP and the control network, who approves changes to those boundaries, and which systems must never accept writes from IT. Confirm any regulatory scope that applies to your products, such as the NIS2 manufacturing sector or the machinery requirements that apply from January 2027. These answers shape the integration architecture, so resolve them before the build plan is signed.
How DeployOpen works on this
DeployOpen plans, implements, customizes, integrates, documents and supports ERPNext inside your own infrastructure, including the cloud accounts, data centers or air-gapped networks you control. For manufacturers, the work starts with how your production, stock and accounting actually connect, before any configuration begins.
How we scope
- Map your BOM structure, routings, workstations and job card flow against how the shop floor really runs.
- Define which production, subcontracting, quality and traceability features are in the written scope and which are deferred.
- Agree integrations with shop floor equipment, MES or PLC data sources and name the owner of each data feed.
How we build
- Configure items, BOMs, workstations and operations, then test costing and landed cost against sample production runs.
- Design batch and serial numbering rules, quality inspection templates and the custom fields or scripts your processes need.
- Test with your own data sets, including data imports sized in small batches as the Data Import tool documentation advises.
How we hand over
- Deliver the configuration, customizations, integration designs and migration records as documented, versioned work products.
- Run user acceptance sessions with production planners, stock keepers and quality staff using scripted test cases.
- Train super users on job cards, stock entries and inspection workflows, and leave runbooks for deployment and rollback.
How we support
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- Ongoing support, version upgrades and continuous testing are available as a retainer after go-live.
- Ask for a written quote that lists each module, integration and migration item as a separate line.
