How ERPNext fits process manufacturing batches and grades
A plant manager running batch-based output needs to know early whether ERPNext can record what the plant actually produced, not just what the recipe planned. In process manufacturing the finished grade is often confirmed only after QC sampling, so the system has to hold a batch that may end up as a different grade than the one ordered. ERPNext's manufacturing module covers the planning side through BOMs, work orders and job cards, and its stock module covers batch tracking through batch numbers on items. What the documentation supports is the general pattern: batch-tracked raw materials and outputs, stock entries for manufacture, and scrap items and scrap warehouses for loss. Whether a given grade change, co-product or yield split can be recorded without workarounds depends on the version you install, so confirm it against that version's manufacture and stock documentation before you commit to a design.
The decision to configure ERPNext rather than keep batch records in spreadsheets usually turns on traceability and cost. Once several batches feed one run, or one run yields more than one saleable grade, manual sheets make it hard to trace which input lots went into which output, to post scrap and process loss against the right warehouse, and to value each grade. A configured setup gives you batch numbers linked to stock movements, a documented place for scrap, and quality inspection tied to receipt or manufacture. Ask your implementation partner to walk through one real batch from raw material receipt to a graded finished lot, including the QC hold, the grade decision and the scrap entry, and to show which steps need custom fields or scripts. Those custom parts are where cost and risk concentrate, so they should be scoped in writing before build starts.
Which process plant patterns need which setup
Chemical batch plants make a defined quantity of product in discrete runs. A recipe is usually fixed for each grade, but yield varies slightly from run to run. The configuration centers on one batch per run, a BOM for each grade, and a clear record of what went in and what came out. Most of the setup is standard, and the custom work tends to sit in how the plant reports yield and losses.
- Batch numbers on finished and intermediate output: Enable batch tracking on items produced in runs, and confirm whether intermediates need their own batch series.
- Grade as an item or variant: Model each saleable grade as its own item, or as a variant if grades share one BOM and attributes. Confirm which option your costing and reporting need.
- Process loss on each run: Record the difference between input and output quantities in the manufacture entry, and decide which loss is normal shrinkage and which is scrap.
- Inspection before release: Hold batches in a non-issuable state until the lab result is entered, so stock cannot be sold before release.
- Custom need, batch recipes with tolerances: Concentration or pH ranges per step, and reactor-level sequencing, are usually outside the standard flow and need scoping.
Ask your process engineers how many runs they perform per day, how often recipes change, and which losses must be reported to customers or regulators before you agree the item and batch design.
Lot traceability in food and beverage plants has to answer two questions: which supplier lots went into which finished lots, and which customers received a given finished lot. The configuration decides how far back the trace goes and how quickly it runs. Shelf life and allergen data also need to reach the stock records and labels, not sit in a separate spreadsheet.
- Lot numbers on incoming raw materials: Batch-track purchased items at receipt, so each supplier lot is linked to its stock entry.
- Forward and backward trace: Confirm the trace reports you need, such as from a finished lot to its customers and from a supplier lot to every finished lot that used it.
- Expiry and shelf life: Set shelf-life fields on items with a fixed life, and confirm how expired stock is blocked from issue.
- Allergen and label data: Store allergen declarations on item master data or custom fields, and check that they appear correctly in print formats and labels.
- Custom need, line-side capture: Scale and barcode integrations at the line, and traceability through mixing and packing steps with several lot inputs, are often custom work.
Ask your quality lead to walk through one recall scenario using real lot numbers from a past run, then time how long the trace takes in a test system.
Some plants produce more than one saleable item from a single run, or find at QC that output meets a lower grade than planned. Recording these outcomes correctly protects costing and stock accuracy. ERPNext provides standard routes for scrap and multiple outputs, but how each is classified and valued is a design decision for the business.
- By-products as defined outputs: Add by-products to the BOM as secondary items so each run records them, rather than adjusting stock later by hand. Confirm that the ERPNext version you run supports the flow you intend.
- Scrap items and a scrap warehouse: Define scrap items in the BOM and a warehouse for them, so losses leave an audit trail.
- Regrading at QC: Agree a process that moves output from the planned grade item to a lower grade item through a stock entry linked to the inspection result, and name who approves it.
- Valuation of secondary output: Decide how cost is split between main and secondary output, and confirm the method with your accountant before go-live.
- Custom need, allocation rules: Cost allocation by weight, density or market value is usually outside the standard setup and needs scoping.
Before configuration starts, ask finance and production to document how each by-product and regrade is valued and who is permitted to post it.
Quality inspection gates decide when stock may move. A gate has to match where the plant actually tests, and the records have to meet the rules that apply to the products. Electronic record and signature requirements apply only where a regulator imposes them, so confirm that scope early instead of assuming it.
- Inspection at receipt, in process and at release: Map which tests happen at each point, and link each one to a Quality Inspection record.
- Blocking stock on failure: Confirm how a failed inspection holds stock, for example through a quarantine warehouse or a stock status, so it cannot be issued.
- Role-based release: Restrict batch release to named roles, and review the change log regularly.
- Regulated electronic records: If FDA rules apply to your products, check the requirements of 21 CFR Part 11 for electronic records and signatures with your quality team and validation specialist before relying on the system.
- Custom need, instrument and LIMS interfaces: Direct capture of results from lab instruments or a laboratory information system is usually a custom integration.
Confirm with your quality function which tests are release criteria and which regulations apply to your products before designing the gates.
Configuration options for batches, grades and by-products
This table compares the main ERPNext configuration choices for batch-tracked process output, off-grade product and scrap. Read each row against your product mix: the right option depends on how often grades change, how traceability is audited, and how scrap is valued. Confirm each setting in the ERPNext version you install before you lock the item master.
| Configuration option | When it fits | What it changes in stock and costing | What to confirm in your ERPNext version |
|---|---|---|---|
| Batch numbers on items | Output must be traceable to a production run, lot or recall scope | Batch-tracked items are issued and received by batch, so stock ledger entries carry batch numbers and reports can filter by batch | Whether batch tracking can be enabled on items already holding stock, and how batch expiry and batch selection behave in manufacture entries |
| Separate items for each grade | Grades have different specifications, prices or customer approvals and must be sold or reported separately | Each grade has its own item code, stock balance and valuation, so the grade must be fixed before the manufacture entry is posted | How item variants, item attributes and item groups will map to grades, and whether a grade can be reclassified later without a stock transfer |
| Item variants for grades | Grades differ by a small set of attributes such as purity or particle size and share one base specification | Variants inherit the template item and keep separate stock balances, but the attribute values drive item codes and reporting | Attribute value limits, naming rules for variants, and whether BOMs can be defined per variant for each grade |
| Scrap items in BOMs | Losses are predictable per run and should be planned and costed | Scrap quantities on the BOM are expected output, so the scrap item is recorded at manufacture and affects the cost of the finished goods | How scrap items are set on the BOM, whether scrap valuation rates are applied as you expect, and how scrap is shown in cost reports |
| Scrap warehouse and scrap in manufacture | Actual loss varies by run and must be counted at the point it occurs | Scrap posted in a manufacture entry moves to a scrap warehouse, which affects stock balances and the value left on finished goods | Scrap warehouse settings on the work order and stock entry, and how the scrap account is mapped in your chart of accounts |
| Quality inspection on receipts | Incoming raw materials need a result recorded before they can be used or accepted | Inspection results gate the receipt workflow and can hold stock until the result is recorded, but they do not change valuation | Whether quality inspection is required per item and per supplier, and how rejected quantities are handled on purchase receipts |
| Quality inspection on manufacture | Intermediate or finished output must be tested against a specification before it moves on | Results are tied to the manufacture or job card, so a failed test can prevent a finished grade from being recorded as the planned grade | Which quality inspection templates attach to operations or items, and whether a result can change the grade recorded on the stock entry |
| Recording a different finished grade | Output tests into a lower or higher grade than planned | Usually handled by a stock entry that moves the batch from the planned item to the actual grade item, which changes stock balances by item | Whether your team will use a repack or manufacture entry for regrading, and how the cost of the original batch carries into each grade |
Setup sequence from item master to first batch run
This sequence configures items, grades, BOMs, quality inspection and stock settings in the order ERPNext depends on them, so a test batch can be traced from raw material lot to finished grade. Each step ends with a check you can repeat in a test environment before go-live.
Define batch-tracked items and naming
In the item master, enable batch tracking for each raw material, intermediate and finished product that must be traced by lot, and set a batch naming rule that matches your lot coding. The process engineer decides which items need batches, and the ERP administrator configures them. Leave items that are not traced by lot untracked to keep stock entries simpler. Done means a test batch created from one item shows the correct item code and ID format in the batch list.
Model each grade as its own item
Create one item per saleable or stockable grade, with its own unit of measure, valuation settings and item group. A grade found at QC is then recorded as output of the grade item, so the stock and cost history stay accurate. Confirm with your quality team how grade codes map to item codes before loading data. Done means each grade appears in the stock balance report with the expected valuation method and unit of measure.
Set scrap, process loss and by-products in the BOM
Build the BOM for the main product with its raw materials, and add scrap items and any expected process loss percentage the process supports. Confirm in your ERPNext version how by-products are recorded, either in the BOM or on the manufacture entry, and test that choice before using it in production. The BOM costing and expected output quantity should reconcile with the process recipe. Done means a test manufacture against the BOM produces the expected main, scrap and by-product quantities.
Configure quality inspection templates
Create Item Quality Inspection Parameter records for each test your lab runs, such as appearance, purity or moisture, with the acceptance ranges from your specification. Link the templates to the relevant items and set the inspection requirement on items where it applies. Your QC lead signs off the parameters and ranges before they are used. Done means a draft quality inspection for a test item loads the expected parameters with the right acceptance limits.
Set quality gates in the transaction flow
Decide which steps must be blocked until inspection passes, usually goods receipt for incoming raw materials, in-process checks and finished goods release, and confirm which document types enforce the check in your version. Define who can approve a grade change or override a failed result. Document this as a short control note the QC and production leads both accept. Done means a test submission without a passing inspection is blocked, and a passing inspection allows it to proceed.
Run a test batch from issue to receipt
Create a test work order or manufacture stock entry, issue raw materials with their batch numbers, then record the output batch, the grade found at QC, and the scrap and by-product quantities. Use the same units and warehouses your production will use. Record any mismatch between expected and actual quantities as a finding. Done means the test batch closes with every input and output traceable to a batch number.
Review stock ledger and valuation after the test
After submitting the test manufacture, review the stock ledger entries, batch-wise stock balances and general ledger entries for work in progress and inventory. Check that scrap and by-products carry the valuation you expect and that the grade difference moved to the correct item. Your finance lead should confirm the valuation before the setup is approved. Repeat the test with a second batch that has a different grade result before go-live.
Trade-offs when a plant regrades output at QC
When QC finds that a batch belongs in a different grade than planned, the plant has to decide how the item master, stock entries, costs and lot records should reflect that. The five decisions below are connected: the item model sets how a regrade is recorded, and the recording method determines how yield, cost and traceability can be reported afterwards.
One item per grade or variants
Decide whether each grade is its own item code or a variant of one parent item. Separate items keep grade-specific prices, specifications and reorder points simple, but multiply item masters and BOMs. Variants share a template and reduce duplication, yet every grade still needs its own stock balance and quality specification. Ask the plant to list every grade it sells and every grade a single batch can become before choosing, and confirm how the chosen model appears in sales and purchase documents.
Regrade as transfer or manufacture
A regrade can be recorded as a stock transfer between items or as a new manufacture entry that consumes the original batch and produces the new grade. The transfer is faster and keeps the batch identity, but it may not carry the cost and yield logic the plant needs. A manufacture entry records consumption and output explicitly, which suits reprocessing, but it needs a BOM or a documented process. Test both with one real regrade scenario before committing to a standard.
Yield and loss reporting
Decide how expected yield, actual output and process loss are captured for each run. Scrap and process loss should be entered as separate lines, not netted into the finished quantity, so that yield trends by grade remain visible. Define who signs off a variance and at what threshold. Ask the plant which losses are measured by weight or volume, which are counted, and how evaporation or moisture loss is treated, because these choices change the reported yield percentage.
Cost allocation across grades and by-products
When one run yields several grades and by-products, the cost of the run must be split. Options include allocation by weight, by market value or by a fixed percentage agreed with finance. Each option changes the valuation of every output and the margin reported per grade. Confirm the allocation basis with the controller in writing, and check how the chosen method is applied when a regrade happens after the original cost has already been posted.
Traceability through splits and blends
A batch that is split into several lots or blended with another batch must still show which source batches went into each output. Decide whether lots keep their original batch number, receive a new one with a parent reference, or both. Blending breaks a simple one-to-one trace, so the plant needs a rule for recording multiple input batches on one output. Ask quality which trace reports a recall or customer complaint would need, and test that the chosen design produces them within the time quality requires.
What do plants ask before configuring ERPNext for process manufacturing?
What drives the cost of configuring ERPNext for process manufacturing?
The main driver is how many product structures, grades and quality rules the plant needs to model before the first batch runs. Software licensing is not the cost: ERPNext is free and open source under GPL-3.0, and self-hosting it is free according to the ERPNext pricing page. The remaining cost is labor: configuration of items, batch and grade rules, quality inspection templates and stock flows, plus testing with real plant data. Costs rise with the number of finished grades, by-products, sites, and the number of integrations with weighing, lab or equipment systems. If you hire a partner, ask for a fixed-scope quote with deliverables and timelines written out. Hosting is a separate, recurring cost: Frappe Cloud shared hosting starts at 5 US dollars per month according to the same pricing page, while self-hosting moves that cost to your own infrastructure.
How long does it take to get a working batch process in ERPNext?
The time depends on how settled the plant's product and quality rules already are, not on the software itself. A plant with documented recipes, clear grade definitions and written QC specifications can move faster than one that is still deciding how a by-product is classified. The sequence usually runs through item and batch design, a test environment with a small set of real batches, and then a parallel run against the existing paper or spreadsheet process. Ask any partner to show the phases and the decisions each one needs from your team, and confirm the timeline in the written scope rather than relying on a general estimate.
What must the plant supply before configuration starts?
Configuration goes faster and costs less when the plant prepares three inputs first:
Can our internal team configure ERPNext for process manufacturing alone?
Yes, a team with ERPNext experience can configure items, batches, stock entries and quality inspection templates without an outside partner, because the platform is open source and its documentation is public. The harder questions are about design: how a grade found at QC is recorded, how process loss is booked, and which records must be controlled for regulated products. Those decisions need someone who understands both the plant and the system, and they are easier to get wrong than to configure. Many plants keep ownership of day-to-day administration in-house and bring in outside help for the design and the first production cycles.
When is it worth bringing in a partner for ERPNext process manufacturing?
A partner is worth considering when the design decisions carry high risk or when internal staff cannot give the project enough time. Typical triggers include regulated products that need electronic records and signatures, several plants sharing one data model, integrations with equipment or laboratory systems, or a go-live date tied to a contract. DeployOpen plans, implements, customizes, integrates and supports self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope. Ask for a written scope that names the processes covered, the deliverables, who tests what, and what support follows go-live.
Does the choice of ERPNext version affect the configuration work?
Yes, the version determines which features are supported and how long you can expect security updates. According to Frappe's supported versions page, 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. Starting a new process manufacturing build on an unsupported version adds rework. Confirm the version choice with your partner or internal team before configuration begins, and check the supported versions page at the time of decision.
Does configuration need access to production data or custom code?
Configuration usually relies on standard ERPNext settings: items, batches, warehouses, quality inspection templates and manufacturing entries. Custom code becomes necessary only for specific rules the standard setup does not cover. Server Scripts, for example, are disabled by default from version 15 and must be enabled with the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them. Ask early whether your hosting option permits the scripting you need, because that answer changes both the design and the cost.
How DeployOpen scopes process manufacturing work
DeployOpen plans and implements self-hosted ERPNext inside your own infrastructure, whether that is your cloud accounts, your data centers or an air-gapped network. Most engagements run on a fixed scope agreed in writing before work starts, with deliverables and timelines listed explicitly. Ongoing support, upgrades and testing can follow as a retainer, so the one-time build and the recurring operating work are priced and agreed separately. A quote follows from that written scope, and DeployOpen does not publish a price list, so the scope document is what you compare across bidders.
The scoping inputs for a process plant are specific. Start with batch rules: which items are batch-tracked, how batch numbers are assigned and whether a batch can be split, merged or blended. Then document the grades: the finished grades a run can yield, the specification each grade must meet, and how a lower grade found at QC is recorded against the original work order. Next, map the QC gates: which inspections block a stock movement, who signs off, and which results must be kept for audit. Finally, define by-product and scrap rules, including expected yields, which items are valued, and which warehouse receives them. Each of these becomes a line item with an owner and an acceptance test.
Ask every bidder to show which of these inputs they reviewed before quoting, and to list what they assume about your side. Confirm whether your team will supply sample batch records, current yield data and QC specifications, and who will validate the test runs in your environment. Confirm too whether any work touches regulated records, such as the electronic signature controls described in 21 CFR Part 11 on eCFR, which would need to be named in the scope rather than assumed. DeployOpen can prepare systems and evidence for an assessment, but independent auditors issue any audit report or certification.
