For open-source material requirements planning (MRP) software with a dated requirements report and purchase-draft action in the core application, evaluate ERPNext v16.60.0 first. Odoo Community 20.0 is a candidate when the team already uses its inventory, manufacturing and purchasing workflows and can reconcile forecast dates with procurement proposals. Test receipt, reservation and order behaviour in your setup. Planning evidence.
This comparison draws on official documentation and pinned source. The reproducible exercise gives expected quantities for a future trial with two gripper variants and a supplier delay.
Which versions, modules and licences are included?
MRP is the dated component-planning function within a manufacturing workflow. Enterprise resource planning (ERP) connects that work with wider operations records. Confirm the edition for each module you plan to use.
We inspected Odoo Community 20.0 at commit 4cf3c24cd9de, and ERPNext v16.60.0, released on 17 November 2026. The sources were reviewed on 20 November. Odoo uses the GNU Lesser General Public License (LGPL) version 3 for the core modules reviewed here. Table 1 fixes the comparison boundary.
| Candidate | Core workflow included | Open-source grant | Deployment to verify |
|---|---|---|---|
| Odoo Community 20.0 | mrp, stock, purchase, purchase_stock and purchase_mrp. The last links Manufacturing with Purchase Stock |
LGPL version 3 in each reviewed module and the core licence. | Community source or supported packages with PostgreSQL. |
| ERPNext v16.60.0 | Manufacturing, Stock and Buying, including the Master Production Schedule and Material Requirements Planning Report. | GNU General Public License version 3 for ERPNext. | Official Frappe Docker or documented manual deployment. |
Both grants permit commercial operation under their conditions. LGPL and GPL obligations differ when code is modified or distributed. Check the licences for the installed dependencies and add-ons too. Hosting and support terms are separate buying decisions.
ERPNext's pinned dependency declaration requests Frappe >=16.60.0,<17.0.0. Frappe v16.60.2, released on 18 November, falls within that range and uses the MIT licence. It is a compatible candidate for the trial, with no installation result claimed. ERPNext and Frappe version evidence.
Keep Odoo Enterprise features outside the Community baseline — Odoo's editions page includes Manufacturing, Inventory and Purchase in Community. It places PLM and the Shopfloor, Control Panel and Scheduling bundle in Enterprise. The public Community code inspected here does not include mrp_mps. Odoo's official Enterprise change record identifies that module. Do not use the Master Production Schedule documentation to infer its inclusion in this Community setup. Odoo edition evidence.
The open-source PLM guide evaluates OdooPLM add-ons on Odoo Community 19.0. That is a separate version and module selection. Interoperability with this 20.0 planning evaluation remains to be verified.
How this comparison was made
The audience is a low-volume robotics manufacturer that needs parts for a released product, possibly across in-house and contract assembly. Odoo Community and ERPNext were selected because the buyer question names them and both have identifiable core manufacturing, stock and purchasing code.
The criteria cover nested make/buy structure, usable stock, reservations, dated receipts, shortage visibility, lead-time actions and the response to a changed supplier date. Official documentation, licence declarations and pinned source were inspected on 20 November 2026. The trial will need to verify interface behaviour, configured permissions, exports and automatic rescheduling.
Arc is a software vendor with a commercial interest in software evaluations. Use the existing methodology to record comparable evidence against the criteria. Buyer-guide methodology
Set up one robot batch before testing either system
WP-200 is a fictional warehouse picking robot. Batch B-2412 needs twelve WP-200-J jaw robots and eight WP-200-V vacuum robots, with material issue on 14 December 2026. Planning starts on 20 November.
REL-WP-01 was approved on 30 October. Five earlier jaw robots, WP-001–WP-005, were built on 6 November with GR-J210 A, ACT-410 A, ENC-510 A and FW-310 1.4.0. VAC A was qualified in that release. Actuator availability prompts ECO-027, approved on 18 November. REL-WP-02 is issued on 19 November for the new batch. Earlier serials keep their as-built release, with no retrofit.
| New demand line | Quantity and serials | Selected physical structure | Installation reference |
|---|---|---|---|
| WP-200-J, BOM-JAW B / CFG-JAW B | 12, WP-006–WP-017 | One CH-110 A, one bought-complete CTL-310 B and one made GR-J210 B. Each gripper uses ACT-420 A and ENC-520 A | FW-310 1.5.0 on CTL-310 B |
| WP-200-V, BOM-VAC A / CFG-VAC A | 8, WP-018–WP-025 | One CH-110 A, one bought-complete CTL-310 B and one made GR-V220 A. Each gripper uses one PMP-430 A pump | FW-310 1.4.0 on CTL-310 B. No jaw encoder |
Keep DW-GR-J210 B and fictional TV-027 with the exact approved JAW B stack. TV-027 covers fit, encoder counts and direction, and encoder-fault response. Firmware remains an installation reference with zero purchased-stock demand. Eight legacy ACT-410 A are visible but unavailable as substitutes for this new jaw release. The BOM guide explains the accepted structure.
Create a distinct application record for each controlled item revision where needed, and retain its mapping to these engineering IDs. Record REL-WP-02 on the target planning records and manifest. Do not allow a default BOM to silently select the earlier gripper definition.
Table 2 is the supply input. All quantities are pieces, with unit purchase multiples, zero safety stock and no prebuilt grippers. Other approved physical inputs are sufficient. The fixture has zero extra operation, staging and inspection time. Supplier lead time runs from order confirmation to usable receipt in calendar days.
| Item | Physical / usable stock | Open receipt 1 | Open receipt 2 | Standard lead |
|---|---|---|---|---|
| CTL-310 B | 12 / 10. Two reserved elsewhere | 6 on 8 December | 5 on 17 December | 14 days |
| ACT-420 A | 4 / 3. One quarantined | 4 on 9 December | 3 on 18 December | 28 days |
Use one build warehouse. Put the quarantined actuator in an Odoo location outside the forecast scope or an ERPNext quarantine warehouse outside the report's selected warehouse scope. Reserve two controllers to an unrelated job and check that the report accounts for the reservation once, whether it appears as a reservation or outgoing demand. Keep all four existing receipts open in the build warehouse.
The independent baseline is twenty controllers and twelve replacement actuators. On 14 December it covers sixteen controllers and seven actuators, leaving gaps of four and five. The broad MRP calculation gives the arithmetic and purchase/rescheduling ledger.
Compare the two documented planning paths
Table 3 identifies what to evaluate in the actual modules. Purchasing actions can create a request for quotation (RFQ) or a purchase order (PO), depending on the workflow. Missing execution evidence remains an unresolved question.
| Planning job | Odoo Community 20.0 evidence | ERPNext v16.60.0 evidence |
|---|---|---|
| Nested assemblies | Made subassemblies have their own BOMs and procurement routes. Reordering rules and make-to-order routes have different demand links. | Multi-level BOMs and Production Plan can generate separate subassembly work orders. |
| Reservation | Methods are configured by operation type, including manufacturing. Test the exact source location and job allocation. | Production Plan and Work Order stock reservations are configurable. The MRP report subtracts reserved stock categories. |
| Dated shortage | Forecast lists receipts, demand and dates. Manufacturing source distinguishes available, expected and late components. | MPS-driven report applies receipts only when their dates can cover the demand. |
| Purchase proposal | Buy reordering creates an RFQ. Forecast horizons, routes and lead times influence the proposal. | Detailed MRP report action creates purchase/work drafts with default supplier and required dates. Production Plan can separately create Material Requests. |
| Lead-time source | Vendor, manufacturing and security lead settings plus purchase preparation/horizon settings. | This report reads the Item Lead Time document, including purchase time and buffer. |
In Odoo, compare the forecast date with the reorder proposal — Odoo's Buy route can create or update a draft procurement order. The forecast documentation treats RFQs as proposed procurement and includes POs as confirmed incoming supply.
Record the date and horizon used by reordering, because its suggested quantity can differ from the gap at 14 December. The pinned orderpoint code uses lead and horizon settings. Reproduce the due-date audit from the individual forecast rows, then explain any difference in the RFQ quantity before approving an action. Odoo planning sources.
In ERPNext, select the dated MRP report deliberately — ERPNext's Material Requirements Planning Report uses a Master Production Schedule (MPS), component relationships, free stock and dated PO receipts. It offsets the required delivery date by lead time. Set the report's Item Lead Time records to fourteen and twenty-eight purchase days, with zero buffer for this fixture. An Item-master field alone does not establish that this report will read that lead time.
Production Plan's optional netting uses an aggregate projected quantity. That quantity includes ordered supply and can include the later receipts. It needs the separate date check for this buyer question. The MPS-to-MRP report is the dated path under review. ERPNext dated-planning evidence.
The detailed report's “Make Purchase / Work Order” action requires permissions and default suppliers. Source shows it creates a draft PO with the calculated order date and required-by date. A past planned order date is information about lateness. It is not evidence that an order was placed then or that a supplier can meet the deadline. ERPNext lead-time and order evidence.
Move one receipt and check the effect
Change only the existing receipt of four ACT-420 A from 9 December to 16 December. Keep its quantity and PO identity, the three due on 18 December and every other input unchanged. This is an illustrative delay, with no additional order.
| Expected result at 14 December | Original plan | Same four-actuator receipt moved to 16 December |
|---|---|---|
| Controllers covered / short | 16 / 4 | 16 / 4 |
| ACT-420 A covered / short | 7 / 5 | 3 / 9 |
| Material-complete kits, eight VAC prioritised | 8 VAC + 7 JAW = 15 | 8 VAC + 3 JAW = 11 |
| Additional actuator quantity after all existing receipts | 2 | 2 |
The issue shortage increases by four because that receipt is now late. Eventual actuator supply stays ten, so the genuine extra quantity remains two. Record the effect on forecast rows, component readiness, purchase proposals and planner decisions. Automatic propagation of a date change or rescheduling is something to demonstrate in the intended setup.
Inspect issue-date purchase drafts against the full PO ledger. A proposal for four controllers and nine actuators may describe uncovered demand at issue, while later orders already provide supply. Requesting earlier delivery, reconciling a bridge purchase and ordering two additional actuators need separate review. Keep the existing orders visible through the exercise.
Run the test in each tool
Use isolated synthetic copies with supplier communication disabled. Record versions, installed modules, permissions, BOM mappings and warehouse scope. Run as at 20 November 2026, or shift the simulated clock and every case date by the same interval. Explicitly retain the 14 December material date and the zero-operation-time assumption.
Prepare the Odoo Community copy
- Install only the Community modules in Table 1 and their required core dependencies. Enter the robot, gripper and bought-part records with the accepted revision mapping. Make regular BOMs for GR-J210 B and GR-V220 A, then include one in each robot BOM. Keep CTL-310 B bought complete.
- Enter the physical stock and unrelated reservation in Table 2. Exclude the quarantine location from the selected source scope. Enter the four existing confirmed PO receipt lines with their specified usable dates.
- Create two manufacturing orders for twelve JAW and eight VAC robots with the selected BOMs and 14 December start/material date. Use zero manufacturing, preparation and security offsets for the fixture. Confirm them once. Configure grippers with the documented make-to-order and Manufacture routes, or record a tested alternative that generates their child demand once.
- Set purchased component lead times and record Buy reordering rules, minimum/maximum zero, unit multiples and the chosen forecast horizon. Open each product forecast and manufacturing component view. Reconcile the receipt rows to the 4/5 issue gaps. Record all generated subassembly orders, reservations and RFQ proposals before repeating any replenishment action.
- Move the existing four-actuator receipt to 16 December. Refresh the same views and record the 4/9 issue gaps, late status and any proposed actions. Observe which dates update automatically and which require the planner to reschedule. Keep any draft RFQ unsent.
These steps follow the documented subassembly routes, forecast, reservation and reordering model. The exact resulting Community UI and generated order links remain to be recorded in the trial. Odoo workflow sources.
Prepare the ERPNext copy
- Use v16.60.0 with a recorded compatible Frappe version. Enter the same item/revision mapping and submitted multi-level BOMs, preserving REL-WP-02 and the gripper make/buy boundaries. Enter stock, the unrelated reservation and the four confirmed PO lines in the chosen build warehouse.
- Create a synthetic Manufacture Material Request with two finished-item lines, twelve WP-200-J and eight WP-200-V, required on 14 December. Save and submit it within the isolated copy. Create an MPS covering 20 November through at least 18 December, select that request and use its demand to populate the MPS. Check the two quantities, dates and BOM selections.
- Create Item Lead Time records with purchase time fourteen days for CTL-310 B and twenty-eight for ACT-420 A. Set buffer and made-item operation times to zero. Select the MPS and build warehouse in the Material Requirements Planning Report. Disable added safety stock for the fixture and begin in detailed view.
- Reconcile each row's demand, stock, eligible PO quantity, required date and release date. Expect 4/5 issue gaps and 30 November/16 November standard order dates. Inspect draft creation on a separate copy only after retaining that baseline. Do not also enter manual child demands already generated from the BOM.
- Move the same four-actuator PO schedule to 16 December, rerun the report and record 4/9 gaps. Keep the Production Plan aggregate net as a separate diagnostic. Test draft order actions with an authorised purchasing role and default supplier. Inspect required-by dates, quantity, warehouse and existing PO overlap before any approval.
Record the generated document IDs, operator actions and any manual steps. Repeat the report after creating a draft to verify how the tool treats unconfirmed supply and whether the action can produce a duplicate.
Test a split build after the delay — In a fresh copy of the delayed plan, keep eight VAC and three JAW kits at 14 December and move the remaining nine JAW kits to 18 December. Preserve the serial assignments and the link to REL-WP-02. Change the underlying manufacturing orders or planning demand, then regenerate the dated supply view and check which dependent dates follow. Check that each issue appears once with the intended quantity.
The first issue consumes eleven controllers and three actuators. The five covered controllers left at that point plus the five due on 17 December cover the nine remaining robots. Four actuators due on 16 December plus three on 18 December leave two still needed. On another trial copy, enter two additional ACT-420 A as a confirmed receipt for 18 December. The revised material plan should then cover all twenty kits if the receipts are usable by issue. Record any manual order amendments and check assembly capacity before confirming completion dates.
For both tools, export the accepted input and result ledger. Another planner should be able to reproduce the shortage and identify which action is a receipt pull-in, which is additional quantity and who approved a build-date change. Confirm forecasted supply and physical reservation separately.
Account for operating the deployment
Self-hosting gives the team responsibility for application versions, database, file storage, authentication, permissions, workers and recovery. Odoo documents Community source and package routes with PostgreSQL. Frappe documents container and manual routes for ERPNext. Pin the actual application and deployment versions, retain the database and attachments/filestore, and rehearse recovery in a separate environment.
Include permission checks and an upgrade replay of the same plan. A supported deployment needs an owner who can restore its data and explain a changed planning result. Hosted support, commercial integrations and additional modules require their own scope and terms.
Decide from the dated evidence
ERPNext's core dated MRP report and order-draft path make it the stronger candidate to try when those are the required outputs. Odoo Community merits the first trial when an existing operations stack and an explicit forecast/procurement reconciliation are acceptable. Neither conclusion proves the fixture in a running instance.
Choose after the original plan and delay are both explained, the accepted robot revisions are retained, and the purchase ledger closes without duplicate supply. Keep the operating owner and any manual planning steps part of that decision.