ERPNext

Most manufacturing SMEs run their operations across a patchwork of spreadsheets, standalone inventory tools, and maybe a legacy MRP system that nobody fully trusts. ERPNext replaces that patchwork with a single GPL-licensed application that handles everything from multi-level BOMs to financial reporting, without charging per seat. It has been in active development since 2011 and is maintained by Frappe Technologies in Mumbai, with 897 contributors on GitHub.

Key features

• Multi-level BOM management with versioning, cost rollups, and support for sub-assemblies. You can define operations, routing sequences, and auxiliary materials (lubricants, consumables) within each BOM.
• Production planning and MRP that generates work orders from sales orders, demand forecasts, or manual plans. Considers material availability, machine capacity, and lead times.
• Work orders and job cards for shop floor execution. Job cards break work orders into per-workstation tasks, tracking time, materials consumed, and scrap.
• Plant floor interface (v15+) gives operators a simplified view for starting/stopping jobs, logging downtime, and recording output without navigating the full ERP UI.
• Quality inspection tied to manufacturing stages. Define inspection templates with numeric and pass/fail criteria, attach them to BOMs or purchase receipts.
• Inventory with batch and serial tracking, multiple warehouses, reorder levels, and landed cost calculations.
• Integrated accounting with real-time cost of goods sold, standard vs. actual costing, and multi-currency support.

What ERPNext does

ERPNext is built on the Frappe framework, a full-stack Python/JavaScript web framework that provides the ORM, REST API, role-based permissions, workflow engine, and report builder. The manufacturing module sits alongside 12+ other modules (accounting, HR, CRM, procurement, asset management, helpdesk) that all share the same database. This means a work order automatically updates inventory, triggers purchase requisitions for short materials, and flows through to cost accounting without any integration middleware.

The manufacturing workflow follows a standard path: define items and BOMs, create production plans (manually or from sales orders via MRP), generate work orders, issue materials to the shop floor, record production via job cards, and backflush finished goods into inventory. For process manufacturing, ERPNext supports batch tracking and formula-based BOMs where input quantities scale with batch size.

ERPNext's data model maps loosely to ISA-95 Level 3/4 (MES/ERP boundary). It handles production scheduling and material management well but does not extend down to real-time machine control or SCADA integration natively. For shop floor connectivity, most implementations pair ERPNext with Node-RED or a custom Frappe app that polls PLCs or IoT gateways and writes back to ERPNext via its REST API.

Why choose ERPNext

No per-user fees. The software is GPL-3.0. Frappe Cloud hosting for 50 users costs under $50/month. Self-hosting on a 4-vCPU/8GB VM handles small-to-mid production environments. The total cost of ownership is a fraction of Odoo Enterprise or SAP Business One for equivalent functionality.

Everything in one database. Manufacturing, inventory, purchasing, accounting, HR, and CRM share one schema. No ETL pipelines between systems, no data reconciliation scripts. When a work order completes, cost of goods flows straight to the general ledger.

Active open-source community. 32,600+ GitHub stars, 10,800+ forks, and a Frappe Forum with years of manufacturing-specific threads. If you get stuck on BOM configuration or MRP logic, someone has likely posted about it.

Customizable without forking. Frappe's "Custom Field" and "Client Script" features let you extend doctypes and add business logic from the UI. For deeper changes, custom Frappe apps install alongside ERPNext as separate Python packages.

Getting started

Self-hosting via Docker is the most common path. The frappe/frappe_docker repository provides production-ready compose files. Requirements: Ubuntu 20.04+, 4 vCPUs, 8GB RAM, MariaDB 10.6+, Redis, Node.js 18+. A basic instance takes 1-2 hours to stand up if you're comfortable with Docker.

Frappe Cloud offers managed hosting starting at roughly $5/month for a small shared instance, scaling to dedicated servers for production loads. There is a 14-day free trial but no permanent free tier.

The learning curve is real. ERPNext's interface looks simple, but configuring manufacturing workflows (BOMs, workstations, operations, routing) correctly takes a week or two of focused effort for someone new to ERP systems. The official documentation is extensive but uneven; community guides and YouTube walkthroughs often fill the gaps. Budget 2-4 weeks for a basic manufacturing setup, longer if you need custom workflows or integrations.

Technical specs

• Languages: Python (backend, Frappe framework), JavaScript (frontend, client scripts)
• Database: MariaDB 10.6+ (primary), experimental PostgreSQL support
• Architecture: Frappe framework (Python/Node.js web framework), Gunicorn WSGI server, Redis for caching/queuing, Nginx reverse proxy
• API: REST API with token and OAuth authentication, plus a Python SDK. RPC-style calls for custom whitelisted methods.
• Deployment: Docker (official frappe_docker), manual bench install, or Frappe Cloud (managed)
• Minimum hardware (self-hosted): 4 vCPUs, 8GB RAM, 50GB storage for a production instance serving 20-50 users

Limitations

• Not suited for large-scale manufacturing. Users with 4+ plants and hundreds of concurrent operators report performance degradation. ERPNext's single-process Gunicorn architecture and MariaDB backend aren't built for the transaction volume of a large discrete manufacturer. Multiple reviews confirm that companies outgrow it and migrate to larger ERPs.

• No native shop floor connectivity. ERPNext doesn't speak OPC-UA, MQTT, or any industrial protocol. Getting machine data into ERPNext requires a middleware layer, typically Node-RED, a custom Frappe app, or an IoT gateway writing to the REST API. This is a fundamental gap for plants wanting automated production tracking.

• Limited third-party integrations. Compared to Odoo or SAP, the integration ecosystem is smaller. Connectors for Shopify, WooCommerce, and a few payment gateways exist, but industrial integrations (PLCs, SCADA, MES) are essentially DIY projects.

• Reporting needs work. Built-in reports cover the basics, but complex manufacturing analytics (OEE breakdowns, multi-plant comparisons, yield analysis across batches) require either custom Script Reports or exporting to an external BI tool like Metabase or Grafana.

• Silent failures in production. Several production users report that ERPNext doesn't always fail loudly. Background jobs can stall, scheduled tasks can skip, and data inconsistencies can accumulate without clear alerts. Monitoring and regular audits are essential for production deployments.