Implementation · Manufacturing
The Odoo MRP implementation checklist: 12 steps from BOM cleanup to go-live
Twelve steps in the order they should happen, from the decisions to make before anyone opens Odoo to the parallel run before cutover. Each step ends with a test you can check off.
Key takeaways
- Check every BOM against what the floor actually uses before you import it.
- Work-center capacity comes from your plant lead, not from defaults.
- Set make-to-order or make-to-stock by product family, then a reorder rule for every raw material.
- Lock the costing method with your controller before any production data exists.
- Quality points and Shop Floor tablets are Enterprise, so decide the edition first.
- Run in parallel for one to two weeks and compare the plans before you cut over.
An Odoo MRP project rarely fails on the software. It fails when the data behind the schedule is wrong: BOMs that do not match the floor, work centers left without real capacity, raw materials with no reorder rule. Planners get a schedule they cannot trust, and within a few weeks they are back in the spreadsheet.
This checklist puts the work in order. Each step ends with a "done when" test you can hand to the person who owns it. It assumes you know how Odoo's manufacturing apps fit together; if not, start with our Odoo MRP guide for manufacturers.
Before you configure anything
1. Name the owners and decide the edition
Every step below needs someone from your side who knows the answer: a plant or production manager for routings and capacity, a planner for replenishment, your controller for costing, and a quality lead for inspections. Name them before kickoff and block their time for workshops and testing.
Decide the edition at the same point. BOMs, work centers, routings, work orders, reordering rules and lot tracking all run in Odoo Community. Shop Floor, Quality, PLM, the Master Production Schedule and the Barcode app are Enterprise. Steps 9 and 10 depend on that choice, so make it during scoping, not during testing. Our Community vs Enterprise comparison covers the trade-off.
Done when: each step has a named owner, and the edition is written into the scope.
Master data: BOMs, work centers and routings
2. Clean up every bill of materials
Export every BOM from wherever it lives today and check it against what the floor actually consumes. Fix component quantities, add realistic scrap allowances, and confirm units of measure: bar stock bought in 12-foot lengths and consumed in inches needs a conversion Odoo can use.
Give each BOM the right type. Use a standard manufacturing BOM for items you build and stock, a kit for sub-assemblies you build but never stock, and a subcontracting BOM for work done by an outside vendor. Record by-products where your process makes them, and set the consumption rule on each BOM (allowed, allowed with a warning, or blocked) so over-consumption is either visible or stopped.
Done when: a sample of BOMs has been checked line by line against real production, and every BOM has a type and an owner.
3. Model work centers from real capacity
A work center is anything that limits throughput: a machine, an assembly cell, an inspection bench or a pool of skilled labor. For each one, set the working hours from your shift calendar, the time efficiency, setup and cleanup times, and a cost per hour so operation time flows into product cost.
Get these numbers from your production lead, not from Odoo's defaults. A work center without a real calendar and capacity lets the schedule book more hours than the shop has, and planners stop reading it.
Done when: your plant lead has signed off the hours, efficiency and cost of every work center.
4. Build routings as operations on the BOM
In current Odoo versions, a routing is the list of operations on the BOM, available once the Work Orders setting is on. Add each operation in the order the shop runs it, link it to a work center, and set its duration from measured times or recent history rather than estimates. Where an operation applies only to some variants of a product, limit it to those variants instead of copying the BOM.
Done when: test manufacturing orders for five representative products give durations and dates your floor agrees with.
Planning logic: routes, replenishment and costing
5. Choose make-to-order or make-to-stock by product family
Custom jobs should be built against a sales order; standard items can be built to stock. In Odoo that comes down to routes: the Manufacture route, plus the make-to-order route for items built against demand, set on the product or on its product category so the rule covers a whole family at once.
At the same step, decide how many warehouse steps manufacturing takes: consume components straight from stock, pick them to the line first, or pick them, build, and then move finished goods to storage. Each extra step adds a transfer someone has to process, so add it only where the floor really works that way.
Done when: every product family has a written strategy and matching routes, tested with one sales order of each type.
6. Set reordering rules and lead times
The scheduler only plans what it knows about. A raw material with no reordering rule and no demand from a confirmed order can run out without warning. Give every purchased component a rule with a minimum, a maximum and a multiple that matches the vendor's pack size, and base the minimum on real usage history rather than habit.
Then check the lead times the rules depend on: the vendor lead time on each supplier line and the manufacturing lead time for items you build. Decide whether each rule triggers automatically or waits for a planner in the replenishment report, and who reviews the proposals each morning.
Done when: every raw material has a rule or a written reason not to, and a test scheduler run produces purchase proposals your buyer agrees with.
7. Lock the costing method with your controller
Choose standard cost, FIFO or average cost (AVCO) for each group of products, and decide whether inventory valuation posts to accounting automatically. AVCO suits most discrete manufacturers with steady material prices, FIFO suits lot-driven work such as food, and standard cost suits high-volume shops that want to see variances against a set standard.
Confirm the accounts production cost will flow through, and check the rolled-up cost of a few products in the BOM overview. Changing the method after production has posted means revaluing inventory, so this decision belongs in scoping.
Done when: your controller has approved the method and the accounts in writing, and test manufacturing orders post the journal entries finance expects.
Traceability, quality and the shop floor
8. Decide what you track by lot or serial number
Turn on lots and serial numbers if a customer, an auditor or a recall could ever ask where a component went. Decide product by product: lots for batches of material, serial numbers for individual units, and no tracking for cheap consumables where scanning adds work without adding value. If materials expire, turn on expiration dates too. Settle this before data migration, because opening stock for tracked products has to be loaded with its lot or serial numbers.
Done when: the traceability report on a test finished good shows every tracked component lot behind it.
9. Define quality control points (Enterprise)
Odoo's Quality app places control points at receipt, at a specific operation in a work order, or before shipment. Each one can be a pass/fail check, a measurement with a tolerance, a photo or an instruction, and it can run every time, on a random share, or periodically.
Map each gate in your current process before you configure it: what is checked, what passes, who signs off, and what a failure triggers (quarantine, rework or scrap). On Community, inspections stay outside Odoo, so decide where those records will live before go-live.
Done when: each control point exists and has been failed on purpose in testing, so everyone has seen what happens next.
10. Set up shop-floor tablets (Enterprise)
The Shop Floor app gives each work center a tablet queue where operators start and finish work orders, log time, record scrap and complete quality checks. Decide which stations get a tablet, how operators identify themselves, and whether they scan lots with the Barcode app.
Test on the actual hardware at the actual station: a screen that is easy to read in the office can be hard to use next to a press brake. Keep what operators must enter to a minimum, because every extra field is a reason to go back to paper.
Done when: an operator from each shift has run a full work order on the tablet without help.
Migration, parallel run and go-live
11. Migrate the data and test against real orders
Load master data first: products, BOMs, work centers, vendors and reordering rules. Opening stock goes in through an inventory count, with lots and serials where tracked, and its value has to reconcile with the inventory balance in your general ledger. Bring open sales and purchase orders across. For manufacturing orders already in progress, it is usually simpler to finish them in the old system where you can and recreate only those still open at cutover.
Rehearse the full load at least once before the final run. Then test with last month's real orders, not demo data: run the scheduler, compare its proposals with what your planner actually did, and work through every difference. For the wider set of checks before cutover, use our pre-go-live checklist.
Done when: a full rehearsal load reconciles, and your planner agrees with the scheduler's proposals for a real week of orders.
12. Run in parallel, train by role, then cut over
A parallel run means entering production in both the old process and Odoo for a short period and comparing the results. It costs double entry, so keep it short and focused: one to two weeks, a written list of what you are comparing (the plan, material shortages and stock levels), and a go/no-go decision at the end.
Train by role before the parallel run starts, so the floor, the planners and the buyers each learn their own screens. Cut over in a low-volume week, count stock at the cutover point, and stop transactions in the old system once Odoo is live. Keep the implementation team on hand through the first production cycle.
Done when: the parallel run's differences are explained, the go/no-go decision is signed, and the old system is read-only.
What this looks like on a real project
Our Odoo MRP case study follows the same broad order. A custom-parts manufacturer with 85 staff and one facility moved 340 BOMs and 12 work centers off QuickBooks, spreadsheets and a separate Access database into Odoo in 14 weeks, including a two-week parallel run. Planning went from a three-day cycle to same-day scheduling, and production stockouts fell 68% in the first 90 days.
If you want help with the planning side on its own, that is what our Odoo manufacturing consulting covers. Our page on Odoo for manufacturing shows the full build, and if you would rather talk it through, book a discovery call.
Odoo MRP implementation questions
How long does an Odoo MRP implementation take?
It depends mostly on how many BOMs and work centers you have and how clean the data is. In our MRP case study, an 85-person manufacturer went live in 14 weeks with 340 BOMs and 12 work centers, including a two-week parallel run. We use AI across configuration, development and testing to shorten delivery.
Can we run Odoo MRP on Community?
Yes, for the core. BOMs, work centers, routings, work orders, reordering rules and lot tracking run on Community. Shop Floor tablets, Quality control points, the Master Production Schedule and PLM need Enterprise.
Do we need a parallel run?
For MRP, usually yes, but keep it to one to two weeks. Entering production in both systems shows whether the plan, shortages and stock levels match before you rely on Odoo alone.
Scoping an MRP project?
30 minutes on your BOMs, your work centers, and a realistic path to go-live.
Book a discovery callKeep going
Related services and articles
MRP your planners trust
BOMs, routings, work centers, make-to-order and make-to-stock, and costing, set up the way your shop runs.
Odoo manufacturing consultingOdoo on the shop floor
The Odoo apps we configure for discrete manufacturers, the problems they fix, and the delivery plan.
Odoo for manufacturing Industry · ManufacturingOdoo MRP for manufacturing: a 2026 practical guide
How BOMs, work centers, shop floor, quality and subcontracting fit together in Odoo.
ImplementationThe 12-point pre-go-live checklist we run on every Odoo project
What we check before any Odoo database goes into production.
Planning an Odoo MRP rollout?
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751