製造向け ERPNext: BOM、作業指示書、および製造現場 — 2026 年完全ガイド

ERPNext ships a genuinely complete manufacturing suite at zero license cost: multi-level Bills of Materials with operations and costing, Work Orders that drive material issue and finished-goods receipt, Production Plans that run MRP-style material requirement explosions from sales orders or forecasts, Job Cards for shop-floor execution, workstations with capacity, subcontracting, batch and serial traceability, and quality inspections wired into receiving and production. For small and mid-size manufacturers — 5 to 250 people on the floor — it covers 90%+ of what proprietary MRP systems charge $50,000–$200,000 to deliver, and the missing 10% (finite-capacity scheduling, advanced APS) is missing from most mid-market competitors too.

This guide walks through the module the way an implementer actually configures it: items and BOMs first, then the work order lifecycle, then planning, then the shop floor — with honest notes on limits and a brief comparison against Odoo MRP, the other open-source contender.

Key Takeaways

• ERPNext Manufacturing is fully open source — BOMs, work orders, MRP, job cards, subcontracting, and quality at $0 license cost for unlimited users
• BOMs are versioned, multi-level, and carry both materials and operations — giving you cost rollups (material + labor + overhead) per finished item
• The Production Plan is ERPNext's MRP engine: it explodes demand from sales orders or forecast into work orders and purchase-material requests, netting against stock
• Job Cards bring execution to the floor: per-operation tracking with start/stop timing, completed quantities, and operator assignment on tablets or terminals
• Batch and serial tracking is native and flows through the whole chain — receiving, production, delivery — giving full forward/backward traceability for recalls
• Subcontracting is first-class: send raw materials to a vendor, receive finished goods, with material reconciliation handled by the system
• Honest limits: scheduling is infinite-capacity by default; finite-capacity APS and deep machine-data integration need customization or external tools
• Compared with Odoo MRP: ERPNext wins on license cost and simple customization; Odoo Enterprise wins on UI polish, integrated PLM/Quality apps, and ecosystem breadth

---

The Building Blocks: Items, Warehouses, UOMs

Manufacturing data quality starts below the BOM. Three foundations to get right on day one:

• Items carry the flags that drive everything: Is Stock Item, Has Batch No / Has Serial No, Default BOM, valuation method (FIFO or Moving Average), and lead times. Raw materials, sub-assemblies, and finished goods are all just items with different roles.
• Warehouses are tree-structured, and manufacturing leans on this: a Stores warehouse for raw material, a Work-in-Progress warehouse per line or plant, and Finished Goods. Work orders move stock Stores → WIP → Finished Goods, and the WIP warehouse is what makes shop-floor inventory visible in the balance sheet rather than vanishing into a black hole.
• UOM conversions handle purchase-in-tons, consume-in-kilograms realities. Define conversion factors on the item; every downstream document respects them.

Bills of Materials: Multi-Level, Versioned, Costed

The ERPNext BOM is the contract between engineering and the floor. Each BOM specifies:

Three behaviors worth knowing:

1. Multi-level explosion is native. A finished-good BOM referencing sub-assembly items (each with its own BOM) explodes correctly in planning and costing. The BOM Stock Report and Exploded BOM views show the full tree with availability.
2. BOMs are versioned and immutable once submitted. Engineering changes mean a new BOM version; the BOM Update Tool propagates a component replacement across every parent BOM that uses it — a genuinely excellent mass-change feature.
3. Costing rolls up live. Material rates pull from valuation or price lists; operation costs come from workstation hourly rates × operation time. You get a defensible standard cost per item before you make the first unit, and Stock Entries record actuals against it.

The Work Order Lifecycle

The Work Order is the execution document. The standard flow:

1. Create — from a Production Plan, a Sales Order, or manually: item, BOM, quantity, planned dates, source/WIP/target warehouses.
2. Material transfer — a Stock Entry of type Material Transfer for Manufacture moves required components Stores → WIP. Shortages are visible immediately; this is where reservation discipline lives.
3. Execute operations — each BOM operation spawns a Job Card: the shop-floor unit of work. Operators (on a terminal or tablet) start/stop the job, log completed and rejected quantities, and the system captures actual time per operation against planned.
4. Finish — a Manufacture Stock Entry consumes WIP components and receives finished goods (and scrap/by-products) into the target warehouse, posting actual material cost plus operation cost into the finished item's valuation.
5. Close — over/under-consumption is reconciled; the work order status drives WIP accounting cleanly to zero.

Partial completions, over-production allowances, batch/serial assignment at receipt, and process-loss percentages are all handled in standard configuration — not customization.

Job Cards deserve emphasis because they are what make ERPNext usable on an actual floor rather than just in the office. A $150 Android tablet at each workstation running the ERPNext interface gives operators their queue, drawings (attached files on the item/BOM), timer-based time capture, and quantity entry. Actual-vs-planned time per operation then feeds honest costing and capacity review — the data most small manufacturers have never had.

Production Planning: ERPNext's MRP

The Production Plan is the brain. Feed it demand — selected Sales Orders, Material Requests, or a manual forecast — and it:

1. Explodes finished-good demand through multi-level BOMs
2. Nets requirements against current stock, expected receipts (open POs), and existing work orders
3. Proposes Work Orders for items you make and Material Requests → Purchase Orders for items you buy
4. Respects sub-assembly strategies: manufacture them via their own work orders, or treat them as purchased

It is classic MRP-I logic: time-phased material requirement planning with infinite capacity assumed. (New to the concept? Our primer on what MRP is and how it works explains the netting and explosion logic in plain language.) For the majority of SMB manufacturers running weekly or daily planning cycles, this is exactly the right tool. What it is not — out of the box — is a finite-capacity scheduler: it will not automatically resequence 40 work orders across 6 machines to minimize lateness. Workstation calendars and capacity exist and Job Cards expose loading, but optimization-grade APS requires customization (a custom Frappe app embedding a scheduling library) or an external planning tool. Be honest with yourself about whether you actually run finite scheduling today — most shops claiming to need APS currently plan in Excel, and ERPNext's Production Plan is a large step up from that.

Traceability, Quality, and Subcontracting

Batch and serial tracking is native and end-to-end. Flag items as batch- or serial-tracked, and every movement — purchase receipt, material transfer, manufacture, delivery — records the identifiers. Forward and backward traceability (which customer received goods containing supplier batch X) is a report, not a project. For food, pharma, and electronics manufacturers, this is the feature that pays for the implementation by itself the first time a recall drill happens.

Quality inspections attach to purchase receipts, manufacture entries, and deliveries: define Quality Inspection Templates with parameters (numeric ranges or pass/fail), make them mandatory per item, and the system blocks receipt/delivery without an accepted inspection. Rejections route to a rejected warehouse for disposition.

Subcontracting handles the send-materials-out, receive-finished-goods-back pattern properly: a subcontracted PO tracks raw materials transferred to the vendor's (virtual) warehouse, reconciles consumption on receipt, and costs the finished item as materials + service charge. Shops that live on plating, heat-treatment, or assembly partners will find this far better developed than in most mid-market ERPs.

ERPNext vs Odoo MRP: The Short, Honest Version

Both are open-source ERPs with serious manufacturing. The differences that actually matter:

Our position as a firm that implements both: if per-user license cost matters and your processes fit MRP-I planning, ERPNext gives you more manufacturing per dollar than anything else on the market. If you want PLM-grade engineering change management, integrated maintenance, and the slickest operator UX — and will pay per seat for it — Odoo Enterprise earns its fee. We run this exact trade-off analysis with clients during platform selection rather than defaulting to either.

Implementation Notes From the Field

• Start with one product family. Configure items, BOMs, and routings for your highest-volume family, run it end-to-end for two weeks, then scale out. Big-bang BOM data entry for the whole catalog before validating the flow is the classic failure mode.
• BOM accuracy is the project. If your BOMs live in engineers' heads or stale spreadsheets, budget real time for capture and validation — a full implementation for a manufacturer is 30–40% BOM/routing data work.
• Decide WIP accounting policy early. Whether WIP value sits in a dedicated account, and how operation costs absorb, must match what your accountant expects before the first month-end close.
• Plan the customization line. Custom fields on Work Orders, a planning dashboard for your scheduler, label printing for the floor — these are quick wins via ERPNext customization on the Frappe framework, typically days not months each.
• Machine integration is possible, not free. Pulling counts from PLCs or connecting weighing scales/barcode hardware uses the Frappe REST API; it works well but is integration work — scope it explicitly via an integration engagement.

A realistic implementation for a 30–80 person manufacturer — accounting, inventory, purchasing, and manufacturing — runs 8–14 weeks and $12,000–$30,000 in services, with hosting at $50–$250/month and zero license line forever.

Talk to Our ERPNext Team

ECOSIRE implements ERPNext for manufacturers end to end: BOM and routing capture, work-order and shop-floor rollout with Job Cards on tablets, batch/serial traceability, subcontracting flows, and the costing setup your accountant will sign off on. We also implement Odoo, so the platform recommendation you get is based on your floor, not our margin.

Talk to our ERPNext manufacturing team →

Frequently Asked Questions

Is ERPNext good enough for a real manufacturing company?

Yes, for the overwhelming majority of small and mid-size manufacturers. Multi-level BOMs, work orders, MRP-style production planning, shop-floor job cards, subcontracting, batch/serial traceability, and quality inspections are all standard and free. The honest gaps are finite-capacity scheduling/APS and out-of-the-box machine connectivity — gaps shared by most mid-market ERPs and addressable through customization when genuinely needed.

Does ERPNext have MRP?

Yes — the Production Plan implements classic MRP: it explodes demand from sales orders or forecasts through multi-level BOMs, nets against stock and open orders, and generates work orders for manufactured items and material requests for purchased ones. It assumes infinite capacity (MRP-I); finite-capacity optimization requires customization or an external scheduling tool.

Can ERPNext handle multi-level BOMs and engineering changes?

Multi-level BOMs are native, with full explosion in planning, costing, and reporting. BOMs are versioned — submitted BOMs are immutable, changes create new versions — and the BOM Update Tool mass-propagates component replacements across all parent BOMs. Formal ECO workflow (approvals, effectivity dates) is light out of the box and is a common, inexpensive customization.

How does ERPNext manufacturing compare to Odoo MRP?

Feature coverage is broadly comparable for core MRP. ERPNext gives you everything — including quality and subcontracting — at $0 license cost; Odoo gates its best manufacturing features (PLM, Quality, Maintenance, polished shop-floor UI) behind Enterprise per-user pricing. Choose ERPNext for cost-efficiency and easy customization; choose Odoo for UX polish and ecosystem breadth with budget to match. We implement both and run this comparison per client.

Can shop-floor operators use ERPNext on tablets?

Yes. Job Cards are designed for floor terminals: operators see their operation queue, start/stop timers, log completed and rejected quantities, and view attached drawings. Inexpensive Android tablets or wall-mounted terminals per workstation are the standard deployment. Barcode scanning for material moves is supported; dedicated scanner hardware integrates via standard keyboard-wedge mode.

What does ERPNext manufacturing cost to implement?

The software is free. A focused implementation for a small shop (items, BOMs, work orders, basic planning) runs $8,000–$15,000 over 6–10 weeks. Mid-size manufacturers with subcontracting, traceability, quality, and integrations typically invest $15,000–$30,000 over 10–14 weeks. Hosting adds $50–$250/month. There is no per-user or per-module license line — which over five years is commonly a six-figure saving against proprietary MRP systems.