ERPNext for Manufacturing in India: BOM, Production & Subcontracting Explained

ERPNext manufacturing India implementations give small and mid-size factories a complete production system — Bill of Materials, Work Orders, Job Cards, subcontracting, and quality inspection — with native GST support, at zero licence cost. This guide walks through every key module so you know exactly what you are getting before you commit to an implementation.

Manufacturing is the one domain where ERPNext was clearly built for the real world, not bolted on as an afterthought. The full manufacturing module ships in every ERPNext installation. There are no add-on tiers or per-seat charges for production planning or subcontracting. For Indian manufacturers navigating GST on job work, e-invoicing, and multi-level BOMs across a mix of in-house and outsourced production, this matters more than most ERP vendors will tell you.

Key manufacturing DocTypes and what they do

Before walking through each area, here is a map of the ERPNext doctypes you will use every day in production.

---

Bill of Materials: the foundation of your production data

The BOM is where manufacturing in ERPNext begins. Every Work Order inherits its material list and routing from a BOM, so getting BOM structure right is the highest-leverage configuration task you will do.

Single-level vs multi-level BOMs

A single-level BOM lists the direct raw materials for one finished good. A multi-level BOM nests sub-assemblies — each sub-assembly has its own BOM, and ERPNext explodes all levels when you generate a material requirement. For an Indian engineering or auto-components manufacturer producing complex assemblies, this is non-negotiable.

In ERPNext, set a BOM as the default BOM for an item, and all production and procurement planning will reference it automatically. You can maintain multiple BOMs per item — useful for alternate formulations, seasonal packs, or customer-specific variants — and switch the active BOM without touching historical data.

Scrap, yield, and operation costs

Each BOM line can carry a scrap percentage, so ERPNext inflates the required quantity automatically when you create a Work Order. If your process consistently wastes 3 percent of a raw material, that loss is built in from the start rather than reconciled as a variance at month-end.

Operations on a BOM define the routing: which workstation, how long, at what hourly rate. The BOM cost rolls up raw-material cost plus operation cost, giving you a standard cost per finished unit before production begins.

---

Production Plan: from sales orders to a production schedule

The Production Plan DocType bridges demand and production. It pulls open Sales Orders or Material Requests, explodes the BOMs to calculate material requirements, checks stock, and raises either Work Orders or Purchase Orders for any shortfall.

How to use Production Plan in practice

1. Open a new Production Plan and select the time horizon — a week, a fortnight, or a month.
2. Pull in Sales Orders (or a forecast quantity) for the items you want to plan.
3. Click Get Items for Work Order — ERPNext explodes all selected BOMs and calculates the net requirement after deducting existing stock and open Purchase Orders.
4. Review the material plan. Any raw material below the required quantity can have a Purchase Order raised directly from this screen.
5. Click Make Work Orders — one Work Order per item-BOM combination is created, ready to schedule against workstations.

This flow turns what is otherwise a spreadsheet exercise — "do we have enough stock to run next week?" — into a two-minute system action. For Indian manufacturers with a mix of make-to-stock and make-to-order items, the Production Plan is usually where the most time-saving happens.

---

Work Orders and Job Cards: running the shop floor

A Work Order is the execution document for a production run. It carries the BOM, the planned quantity, the planned start and end dates, and the target warehouse for finished goods.

Work Order lifecycle

• Draft — Created from Production Plan or manually; not yet released to the floor.
• Not Started — Submitted; material can be transferred from stores to the production floor.
• In Process — At least one Job Card has been started.
• Completed — All operations done; finished goods posted to stock.
• Stopped / Cancelled — Production halted or aborted.

Job Cards for operator-level tracking

Each operation on the Work Order generates a Job Card for the assigned workstation. The operator opens the Job Card, clicks Start, works, and clicks Finish. ERPNext records actual time against planned time, operator identity, and any quantity produced or scrapped at that operation.

This is shop-floor visibility: you can see, in real time, which Work Orders are running on which machines, how long each operation is taking, and where a batch is sitting if a delivery is at risk.

---

Capacity planning and workstations

ERPNext capacity planning works through Workstations. Each Workstation has:

• Working hours per day (defined on the Holiday List and a Workstation schedule).
• An hourly operating cost (electricity, tooling, overhead).
• A capacity in hours — how many hours of productive work are available per shift.

When you schedule a Work Order, ERPNext checks the workstation's available hours and can flag over-loaded machines. The Production Analytics report shows planned vs actual hours per workstation over any period, so your planning team can see bottlenecks before they become missed delivery dates.

For Indian manufacturers running two or three shifts, configure multiple shifts on the Workstation to reflect true available capacity — ERPNext will plan across shifts when calculating expected completion dates.

---

Subcontracting: sending material out and bringing goods back

Subcontracting is one of the most India-specific workflows in ERPNext, and it is one of the most complete. The typical scenario: you send raw material or semi-finished goods to a job-work vendor, the vendor processes them, and you receive finished or semi-finished goods back — with the vendor raising a service invoice for the job-work charges.

How ERPNext handles the subcontracting cycle

1. Raise a Subcontracting Order for the item to be processed, referencing the BOM. ERPNext calculates the raw materials to be sent based on the BOM.
2. Create a Stock Entry (Send to Subcontractor) — this transfers the raw materials from your store to the vendor's location (ERPNext tracks this as stock at the vendor, not consumed from your books).
3. Receive the finished goods via a Subcontracting Receipt. ERPNext simultaneously posts the finished-goods receipt and the raw-material consumption.
4. Post the vendor's Purchase Invoice for the job-work service charges.

GST on job work

This is where Indian ERPNext implementations need careful setup. Under GST, sending goods to a job-worker is a supply on Form ITC-04. ERPNext supports the following:

• The Stock Entry for sending goods can be configured to generate an e-way bill if the value and distance threshold are met.
• The Subcontracting Order and Receipt track the quantity sent and returned, so you can generate ITC-04 data from ERPNext reports.
• The vendor's invoice for job-work charges attracts GST (typically 18 percent), and the input tax credit is claimable — ERPNext posts this as GST Input on purchase.

For manufacturers with significant outsourced processing, the Subcontracting module removes the need for a separate job-work register and aligns with the GST compliance requirement for goods sent outside your premises. See the Frappe framework solutions page for how we configure this during implementation.

---

Quality inspection at every stage

ERPNext Quality Inspection is not a separate module — it is a checkbox on Purchase Receipts, Delivery Notes, Work Orders, and Stock Entries. You configure a Quality Inspection Template per item or item group, listing the parameters to check (dimensions, colour, hardness, pH — anything) and the acceptance criteria.

Where inspections trigger

• Goods Receipt (Purchase) — Inspect incoming raw materials before accepting to stores.
• In Process — Inspect semi-finished goods at critical operations (triggered from a Job Card).
• Finished Goods (Manufacture) — Inspect finished goods before posting to saleable stock.
• Outgoing (Delivery) — Inspect before dispatch, triggered from the Delivery Note.

Each inspection records the reading against the criteria, a pass/fail status, and the inspector. Failed items can be quarantined in a Rejected warehouse automatically. The quality data is searchable and reportable — useful for supplier quality reviews and for internal process improvement under any ISO or BIS scheme.

---

Shop-floor visibility: reports that matter

ERPNext ships several manufacturing reports that experienced shop managers actually use.

• Production Analytics — Planned vs actual quantity and hours by Work Order, item, or workstation.
• Work Order Summary — Status of all Work Orders in a date range; filter by item, BOM, or warehouse.
• Job Card Summary — Time booked per operator and per workstation; good for payroll and productivity.
• BOM Stock Report — For a given BOM, how much stock do you have against what is required to produce a target quantity.
• Subcontracting Status — Materials sent, pending receipt, and overdue returns per vendor.

For Indian manufacturers exporting or serving large customers, these reports can be exported and shared as part of a delivery dashboard or customer-specific reporting pack without any custom development.

---

---

Frequently asked questions

Does ERPNext support multi-level BOM for complex assemblies?

Yes. ERPNext BOMs can be nested to any depth. Each sub-assembly item can have its own BOM, and the system explodes all levels when generating a Production Plan or material requirement. You can also run a BOM Comparison report to diff two versions before switching the default.

How does ERPNext handle GST on job-work subcontracting?

ERPNext tracks the quantity and value of goods sent to subcontractors separately from sold goods. The vendor's service invoice for job-work charges is a taxable purchase, and GST input credit is claimed normally. Goods sent and returned can be extracted for ITC-04 filing. For goods moving under e-way bill thresholds, the Stock Entry can trigger e-way-bill generation through the GSTN API.

Can ERPNext run on a factory floor with limited internet?

Yes, with some planning. ERPNext is a web application and requires a browser and network access. Most factory deployments run ERPNext on a local server inside the plant network so that internet outages do not affect production. Frappe Cloud (managed hosting) also works for plants with reliable broadband.

What is the difference between a Work Order and a Job Card?

A Work Order covers the full production run for a batch of finished goods — it references the BOM, planned quantity, and schedule. A Job Card is created for each operation within a Work Order at a specific workstation. The operator works against the Job Card; the Work Order tracks overall progress by aggregating all its Job Cards.

How long does an ERPNext manufacturing implementation take in India?

For a mid-size manufacturer with 20–50 users, BOM setup, Production Plan, Work Orders, and basic subcontracting, a focused implementation takes 6–10 weeks. BOM data migration and operator training are usually the longest tasks. See our manufacturing industry page for a typical project scope.

Is ERPNext manufacturing suitable for make-to-order and make-to-stock businesses?

Yes. ERPNext handles both modes. Make-to-order manufacturers pull Work Orders directly from Sales Orders via the Production Plan. Make-to-stock manufacturers use reorder-level triggers or a forecast to generate the Production Plan. Most Indian factories run a mix of both, and ERPNext lets you choose per-item which mode applies.