Odoo manufacturing (MRP) implementation

The decision that shapes an Odoo manufacturing rollout is how the bill of materials, the routing and the work centers connect, because planning and product cost are both calculated from that chain. A bill of materials defines what goes into a finished item, a routing defines the operations that turn those components into the item and the work centers define where each operation runs and at what capacity. If any link is wrong, the master production schedule will promise dates the floor cannot meet and the cost of a manufactured product will not match what was actually spent. Before any test scripts are written, the team should agree on that chain in writing.

Start with product structure. Decide which items are purchased, which are manufactured in-house and which are intermediate subassemblies, and whether each manufactured item needs one bill of materials or several for different variants or recipes. Confirm with the process owner how many levels of subassembly exist, which components are interchangeable and how scrap is expected. Ask the implementation partner to show how each component will be sourced and whether any finished item will be made by a subcontractor. These answers determine how many bills of materials are needed and whether the structure is shallow enough for planners to read.

Next, define the operations. A routing lists the steps, their order and the work center where each step runs. Decide which steps are real production tasks that consume time and which are inspections, packing or waiting periods that belong in the schedule but not in cost. Confirm whether the plant needs one-step, two-step or three-step production flows, since that choice changes where stock is held between steps and therefore how inventory valuation and work-in-progress look. Ask the partner to walk through a sample order from raw material to finished goods, so the team can see every operation that will be recorded.

Then set capacity and cost rates for each work center. Work centers carry the efficiency, capacity and cost assumptions that the schedule and the costing both depend on. Agree on how many hours each center is available per day, how many parallel units it can run and which labor and overhead rates apply. Confirm with finance which rates are standard and which are actuals, and how overhead is allocated. These figures are usually the weakest data in a migration, so plan time to validate them against shop records. Note that the exact fields and menu locations for these settings should be confirmed against the Odoo version you will deploy.

Finally, decide who records completion, because cost is only as accurate as the shop-floor data. Name the people who confirm operation start and finish, record scrap, report consumed components and close manufacturing orders, and decide whether they will use a terminal, a tablet or a supervisor workstation. Test this with real operators before go-live, including a day with late changes and partial batches. Plan for the risk that operators skip steps under pressure, which leaves planned costs unchanged while actual costs drift. Assign an owner who reviews variances each period and reports them to the controller.

Manufacturing data is only as useful as the master records behind it. Before an Odoo Manufacturing go-live, the project team needs a signed-off set of products and variants, components, bills of materials, routings, work centers with their capacity, units of measure, suppliers and subcontractors, and the open orders that will be in flight on the cutover date. These records feed planning, costing, purchasing and shop floor execution, so an error in one of them shows up as a wrong order quantity, a wrong cost or a wrong schedule. Treat cleanup as a deliverable with an owner, not as a side task of the data load.

Start with products. Each finished good and component should exist once, with one internal reference scheme, one unit of measure and a clear classification of whether it is purchased, manufactured or both. Duplicate products are the most common failure point: the same part entered under two codes splits stock, breaks BOM lines and distorts costing. Variants need the same discipline. Decide which attributes create variants and which are notes, because changing this after BOMs reference variants is expensive. Map every legacy unit of measure to an Odoo unit of measure and confirm which conversions, such as case to each, are allowed in the product setup.

Bills of materials and routings need the most scrutiny because they are often the least maintained records in an older system. Ask production engineering to confirm each active BOM against the current drawing or recipe, remove obsolete versions, and confirm the operations, work centers and durations in each routing. Confirm whether a BOM is a kit or a standard manufacturing BOM, and whether any subcontracted operation should be modeled as a subcontracting step. Work centers need their capacity, working hours and efficiency values checked, since the master production schedule and shop floor timing depend on them. Run a sample of work orders through a test database to see whether the figures produce credible schedules.

Decide early what history migrates and what is archived. Open purchase orders, manufacturing orders, stock on hand and open sales commitments generally need to move so that the first day of production reflects reality. Closed orders and years of completed production are usually better kept in an archive that finance and quality can query, rather than loaded as operational records. Your decision should follow your traceability obligations, including any lot or serial history your customers or regulators require. Write the rule down per object type, because mixed rules are where reconciliation gaps appear.

Confirm import formats and migration tooling against the Odoo documentation for your exact version before you build any load file. Import templates, required fields, external identifiers and the order in which records must load vary between releases, and the Odoo versions this implementation targets have different support windows that affect when you must upgrade. Ask the implementer to show a reconciliation report for each object type, comparing counts and values between the source system and the test database, and to sign off that report before the final cutover. Ask whether any open order will be rebuilt by hand, because that work belongs in the plan and the quote.

Manufacturers should first establish which rules reach their plant and which do not, because the answer decides how much evidence the Odoo Manufacturing setup must produce. NIS2 Annex II lists manufacturing as a critical sector and covers NACE Rev. 2 divisions 26 to 30, which include computer and electronic products, electrical equipment, machinery, motor vehicles and other transport equipment. Entities in scope that are classed as essential or important must report significant incidents with an early warning within 24 hours, an incident notification within 72 hours and a final report within one month. Whether your company is in scope depends on its size, its sector and its member state's transposition, so confirm that with counsel before designing reports around these deadlines.

Industrial control and operational technology rules apply to the shop floor, not to the ERP itself. ISA/IEC 62443 sets requirements for securing industrial automation and control systems, and NIST SP 800-82 Rev. 3 (September 2023) covers SCADA, DCS, PLCs and related OT. Where your Odoo server or its Shop Floor terminals can reach PLCs, MES gateways or machine data collectors, those networks fall under these frameworks. The Machinery Regulation, Regulation (EU) 2023/1230, applies from 14 January 2027 and adds an essential requirement that connecting another or remote device must not lead to a hazardous situation. If you sell connected machinery, the design of any integration into Odoo is part of that conformity work.

For regulated products, the question is different. 21 CFR Part 11 sets requirements for electronic records and electronic signatures where FDA rules apply, which can reach Manufacturing when work orders, batch records or quality results are used as evidence. Odoo Manufacturing can hold records of who confirmed an operation and when, but whether those records meet Part 11 depends on controls such as unique user accounts, reason-for-change practices, audit trails, access reviews and validation of the configured system. Ask your quality function which records are GxP or regulated evidence before deciding which Odoo configuration needs validation documentation.

The Odoo setup supports these expectations in concrete ways. Plan separate user groups for planners, operators, quality and administrators, and restrict who can change bills of materials, routings and work center data after release. Use Odoo's documented authentication options, such as LDAP, OAuth sign-in and two-factor authentication, so access follows your identity provider. Keep the production database on infrastructure you control, confirm which Odoo edition supplies the features you need, and check that the chosen version is still in standard support, because security patches are provided only during that window. Document the configuration, the access model and the test evidence as you build, so the evidence exists when someone asks for it.

DeployOpen prepares systems, controls and evidence for assessments, but it does not issue audit reports, attestations or certifications. Independent auditors, certification bodies and your regulator decide whether requirements are met. Before scoping the work, confirm with counsel and the relevant body which of NIS2, the Cyber Resilience Act, the Machinery Regulation, IEC 62443 or 21 CFR Part 11 apply to your sites and products, and ask those parties what evidence they expect. That answer determines which controls, records and test results the Odoo project must deliver.