Odoo or ERPNext for the factory? The difference is where the licence starts.
Both systems cover the core of manufacturing. They differ in what sits behind a per-user licence, and in how far a specialist can build on them for process industries. Kawader has added process manufacturing and demand planning inside ERPNext.
Kawader Technology · 14-11-2026 · 4 min read
A factory looking for an open-source ERP today usually ends with two names: Odoo and ERPNext. Both handle bills of materials, production orders, work centres, subcontracting, batches and expiry dates. On the basics, neither is a wrong choice. The difference shows in two places: the licence, and the kind of factory you run.
Where the licence starts
Odoo comes in two editions. Community is open source and includes the core manufacturing app, with by-products and their share of the cost. Odoo's own comparison of editions places the shop-floor screens and scheduling, quality, product lifecycle management (PLM), barcode and the Studio customisation tool in Enterprise, which is licensed per user, per month. So a factory that starts on the free edition meets the licence at the moment it wants a screen in front of the operator or a quality check on the line.
ERPNext has one edition. Its publisher states plainly that no features are held behind a paywall, and its licence (GPL v3) does not count users. Job cards, quality inspection, downtime recording, the plant floor view, co-products and by-products (added in version 16) and a master production schedule are all in the same open code. You pay for hosting and for the people who implement it, not for each person who logs in.
Both were built for discrete factories first
If your factory assembles parts into a product, such as furniture, equipment or garments, both systems fit. Process industries are different: paints, chemicals, food, feed, plastics, detergents. There the recipe is a formula in percentages, not a list of parts. One batch gives more than one product. The strength of a raw material changes from lot to lot. And a batch can be in the warehouse without being released for use.
As of November 2026 we did not find, in the standard documentation of either product, formulas in percentages that rescale themselves, balancing a batch by the strength of its active ingredient, or demand planning that handles promotions and measures how accurate the forecast was. On forecasting each gives a starting point: Odoo's production schedule suggests figures from past sales averages for the planner to adjust by hand, and ERPNext has an exponential smoothing forecast report. What lies beyond that is what large licensed suites such as Microsoft Dynamics 365 and SAP are bought for in process industries.
What Kawader added inside ERPNext
Because ERPNext is one open edition, this layer can be built inside it, on the same items, batches, production orders and ledger. That is what Kawader has built:
- Formulas in percentages. Each formula has a batch size, a yield and validity dates. Change one ingredient and the others rescale. Some lines stay fixed per order, and some move in steps with the order size.
- Co-products and by-products with their cost. The cost of the batch is split between the main product and what comes out beside it, by the share you set.
- Potency and batch balancing. The laboratory reading is recorded on the batch. When an order starts, the system picks the batches of the active ingredient and recalculates quantities to reach the target strength.
- Batch status. A batch under test or rejected is blocked from production, transfer or delivery until quality releases it. Retest and best-before dates are calculated, and can pass from the ingredients to the finished batch.
- Demand planning. A baseline forecast from sales history, split down by territory and customer group, with promotions and the dip that follows them. Each planning cycle is published as a version, and its accuracy is measured against actual sales: the error, the bias, and whether the planner's changes improved on the baseline.
- Planning and scheduling. A time-phased run proposes purchase, production and transfer orders, shows which demand each one serves, and turns the approved ones into ERPNext documents. Purchases are grouped by supplier and rounded to whole packs. Operations are scheduled against the real capacity of each workstation.
What this means for the buyer
A process manufacturer no longer has to choose between an affordable system that stops at discrete manufacturing and a licensed suite priced by the user. ERPNext with this layer covers that ground, the code and the data stay open, and the fiftieth user costs nothing in licences.
Odoo is a capable and polished product, and for a discrete factory that is comfortable with Enterprise pricing it is a sound choice. Our point is narrower. If your factory mixes, cooks or blends, ask every vendor to show three things on the screen: the formula, the potency, and the accuracy of last month's forecast. Then ask what the fiftieth user will cost.
Checked against the public documentation of Odoo 20 and ERPNext 16 in November 2026.