“Will the order be ready on Friday?” If answering takes five phone calls, your factory needs better visibility. Here’s where ERPNext manufacturing makes a difference.
A customer calls to ask whether their order will be ready on Friday.
Sales checks with production. Production checks with stores. Stores checks with purchase. Somewhere between these conversations, the team discovers that one material is short, another job is occupying the machine, and part of the order is still waiting for inspection.
Everyone is working hard. Yet answering a simple question takes several phone calls.
This is where an ERP system earns its place: connecting the people, materials, operations and costs behind every delivery commitment.
At Wahni, we have implemented ERPNext for businesses in extraction, aluminium and polymer extrusion, furniture, medical kits, precision tooling, spices, breakfast products and other food manufacturing. Their production methods differ, but the questions owners need answered are often the same.
What should we produce? Do we have the materials? Where is the order now? How much did it cost?
The ERPNext manufacturing module provides a foundation for answering those questions. Version 16 strengthens that foundation with improvements in material planning, production tracking and subcontracting.
Imagine a food manufacturer receiving an order for packaged spice powder.
Before production begins, the team needs to know the ingredients, packaging materials and operations required. Grinding the product is only part of the job. Pouches, labels and cartons also determine whether the order can be completed.
In ERPNext, the Bill of Materials, or BOM, defines the materials and operations needed for a specified output quantity. Multi-level BOMs allow intermediate products and subassemblies to have their own manufacturing structures.
A furniture manufacturer might define a frame, an upholstered assembly and the finished chair separately. A food manufacturer might separate bulk processing from retail packing. The same standard structure supports both.
This gives production, purchase and costing a shared reference. It also brings an important implementation decision into focus: which stages need separate stock tracking, and which can remain operations within one production process.
Getting this structure right helps the business understand material requirements and production costs more clearly.
Once demand is known, the next question is whether the factory can fulfil it.
ERPNext’s Production Plan brings together requirements from Sales Orders or Material Requests. It identifies subassemblies, supports planning for their manufacture or purchase, and calculates material requirements while considering projected availability.
For the spice manufacturer, this can reveal a packaging shortage before processing begins. For a furniture business, it can show that enough timber is available but a required fitting is missing.
ERPNext Version 16 adds a dedicated Material Requirements Planning, or MRP, workflow. Its Master Production Schedule brings together demand from sales orders, material requests, forecasts and delivery schedules.
MRP calculates material quantities and requirement dates using procurement and manufacturing lead times. Forecast figures still need to come from the business; the system does not automatically predict sales.
The benefit is earlier visibility. Purchase can act on upcoming requirements, while production makes decisions with a clearer view of material readiness.
A production plan becomes actionable through Work Orders.
The Work Order identifies the product, quantity, BOM and production requirements. Operations and workstations provide the basis for scheduling, while Job Cards record execution at individual stages.
Those stages could be grinding and packing, cutting and assembly, or machining and finishing.
Job Cards capture time, employee details and completed quantities. As the team updates them, production managers can follow operation progress against the Work Order.
Version 16 improves partial-production handling with a Pending Quantity field, helping distinguish unfinished work from process loss.
A customer update then becomes easier to explain: processing is complete and the order is in packing, or machining is done and inspection is pending.
This visibility depends on timely recording. A system cannot show today’s production accurately if the team enters everything at the end of the week.
Issuing material to production and consuming it are different events.
ERPNext supports transferring materials into a Work in Progress warehouse, recording manufacturing consumption and receiving finished goods.
Work Orders show required, transferred and consumed quantities. They also support partial completion and returns of unused components.
For example, a furniture factory may issue materials for an entire production run but finish only part of it during the day. Recording the material movement and completed output helps distinguish finished stock from work still in progress.
ERPNext also shows planned and actual operating costs, with actual operation information coming from Job Cards. This gives the business a basis for investigating why a run used more material or took longer than expected.
The resulting cost is only as reliable as the underlying records. Material valuation, consumption, operation times and the treatment of additional costs all need to be configured and maintained properly.
Finishing production does not automatically mean a product is ready for dispatch.
ERPNext supports incoming, in-process and outgoing Quality Inspections. Templates can define numeric, non-numeric or formula-based acceptance criteria.
In-process inspections can be linked to Job Cards, allowing businesses to record checks such as dimensions, moisture readings, appearance or packing completeness according to their quality procedures.
Serial and batch tracking add another layer of control. With correctly recorded stock transactions, businesses can follow identified items or lots through inventory movements and manage relevant expiry information.
These are useful foundations for food products and medical kits. Specialised regulatory records, validation requirements and controlled release procedures still need a separate assessment during implementation.
Many factories send materials outside for part of the manufacturing process.
ERPNext’s standard subcontracting workflow supports materials supplied to a vendor and the receipt of processed goods. This is useful when a business outsources stages such as machining, coating or component processing.
Version 16 adds improvements such as reserving materials for subcontracting and creating multiple Subcontracting Orders against one Purchase Order.
The reverse arrangement also matters. A customer may supply materials and ask your factory to process them.
Version 16’s Subcontracting Inward workflow supports this journey, including customer-provided materials, production, delivery and service billing.
Choosing the correct workflow helps the business distinguish its own materials from customer-provided materials and maintain clearer production records.
Manufacturing does not always produce a single finished item.
A production run may also generate recoverable scrap, a by-product or another saleable output.
ERPNext’s Secondary Items functionality supports scrap, co-products, by-products and additional finished goods, with percentage-based raw-material cost allocation.
This provides a standard starting point for businesses that recover usable material or produce secondary outputs.
Where output quantities or cost allocation depend on specialised factors—such as moisture, purity or recovery rates—the process needs a more detailed assessment.
Our approach at Wahni is to map the business process against standard ERPNext capabilities first.
A different product does not automatically require custom software. Many requirements can be addressed through BOM structures, operations, warehouses, quality templates, permissions and workflows.
Customization becomes relevant when the business needs a calculation, integration or control beyond those capabilities.
The examples below illustrate how we assess that boundary. They are possible requirements, rather than features every business in that sector needs.
| Manufacturing sector | Standard ERPNext foundation | Requirements that may need extensions |
| Extraction | Material consumption, production output, batches and secondary outputs | Yield calculations linked to moisture, purity or recovery characteristics |
| Aluminium and polymer extrusion | BOMs, operations, Work Orders, material usage and scrap recording | Die-life tracking, profile-specific calculations, cutting optimization or machine data integration |
| Furniture | Multi-level BOMs, subassemblies, operations and subcontracting | Dimension-driven BOM generation, panel nesting or automated cutting lists |
| Medical kits | Component BOMs, assembly, batches and inspection records | Specialised sterilisation records, regulatory documentation or component-expiry controls |
| Precision tooling | Manufacturing operations, time recording, inspection and subcontracting | Drawing-revision controls, tool-life tracking or machine-specific data capture |
| Spices and breakfast products | Recipes represented as BOMs, processing, packing, batches and quality checks | Potency-based formulation adjustments, variable-yield calculations or packing-line integration |
Standard scheduling provides a starting point for allocating work to workstations.
More complex needs—such as sequencing jobs to minimise die changes, combining orders to meet minimum run quantities, or automatically replanning after a breakdown—require a detailed fit assessment.
The aim is to identify the smallest useful extension while keeping purchasing, inventory, production and accounting connected.
A successful ERPNext manufacturing implementation starts with understanding what happens between receiving an order and delivering the product.
How are materials identified? How is production planned? Where does stock change hands? Who records consumption and output? How are quality and costs reviewed?
These decisions shape the implementation.
For example, separating bulk processing and packing into different BOMs can be useful when a business stores bulk output before packing it into several retail sizes. When production and packing happen together without a separately managed intermediate stock, a simpler structure may be more suitable.
At Wahni, we work through these choices with the client, configure the standard workflows, validate them against representative production scenarios and identify the gaps that justify customization.
That distinction helps clients understand what ERPNext already provides, what their team needs to maintain and what additional development will solve.
For a growing manufacturer, the result should be practical: fewer calls to find an order’s status, earlier awareness of shortages, clearer production records and better information for reviewing costs.
When the customer asks whether the order will be ready on Friday, the answer should come from a connected production process.
Planning ERPNext for your manufacturing business? Talk to Wahni about your workflow, the standard capabilities that fit and the extensions your operations may need.