Choosing MRP software is easy. Choosing one your floor still uses in six months is not.
Every MRP demo shows the same factory: clean BOMs, one smooth routing, no rush orders, no rework. Your factory has partial batches, substituted materials and a customer who called this morning. The system worth buying is the one that survives that gap — and this page is about how to tell before you sign.
—— Sound familiar?
You know this problem by these symptoms.
Every vendor demo shows a spotless factory — one BOM level, no scrap, no rush orders — and none of it looks like your Tuesday.
Your planner builds the real schedule in Excel, then keys it into the old MRP afterwards so the record exists.
Work orders are printed at 8am and real progress lives on the whiteboard, because updating the system means walking to a PC in the office.
Anything with rework, a substituted material or a partial batch gets handled off the books, because the system only accepts the standard routing.
You are still paying for the last MRP nobody opens, which is exactly why signing for the next one feels dangerous.
MRP gets chosen in a meeting room, against a feature checklist, by people who will never clock onto a work order — and nearly every product passes the checklist. What the checklist never tests is the software's assumptions: that BOMs are always accurate, that every job follows the standard routing, and that operators will walk to a PC to record what they just did. When those assumptions meet a real shop floor, the floor does not argue — it quietly goes back to the whiteboard, and the MRP becomes a data-entry chore performed after the fact. That is not a training failure; it is a fit failure, and it was decided on the day of purchase.
—— The way out
How Odoo closes this gap.
Work orders live at the machine, not in the office
Odoo's shop floor interface runs on a tablet at each work centre. Operators start and pause work orders, register finished quantity and scrap, and flag blockers without leaving the machine — the schedule stays true because updating it is faster than the whiteboard. What the planner sees is what the floor just did, not what the office typed in at 5pm.
BOMs and routings that accept a real Tuesday
Odoo's BOMs go multi-level, carry by-products, and can be set to flexible consumption, so a substituted material or an off-standard quantity is recorded on the manufacturing order instead of hidden from it. Unbuild orders handle rework and disassembly, and when the drawing changes mid-job, an engineering change order in PLM versions the BOM rather than overwriting it.
Planning depth you can grow into
You do not have to run full MRP on day one. Reordering rules cover steady components, the replenishment report shows what actually needs buying, and the Master Production Schedule comes in when forecasts start to matter. Make-to-order and make-to-stock run side by side, set per product, so the plan matches how each item really moves.
Quality and maintenance on the same work order
Quality control points trigger checks at goods receipt or at a specific operation, and a failed check blocks the order instead of relying on someone remembering. Operators raise maintenance requests from the work centre they are standing at, and downtime is logged against that equipment — so the floor stops needing a parallel world of paper forms.
—— How we run it
The transition, managed properly.
One pilot line decides, not the demo
The first phase puts Odoo on one line or product family, with a fixed written scope and price agreed before it starts. The floor's verdict on that line — not a slide deck — is what gates the plant-wide rollout.
Scoped on your routings, trained on live orders
During scoping we model your actual BOMs and routings in a test database, so fit is proven on your own products before you commit. Training happens at the work centre on live orders, in Thai or English, with the same consultant from the first call through go-live.
The whiteboard retires on evidence
The whiteboard and the planner's spreadsheet keep running beside Odoo until the system's schedule has matched the floor for a full cycle. Old habits get switched off because they are proven redundant, not because a project plan says so.
—— FAQ
Questions teams ask about this problem.
We already bought an MRP the floor abandoned. Why would Odoo end differently?
Because the decision structure changes, not just the software. Fit is tested on a pilot line with your own BOMs and routings before any plant-wide commitment, operators record work at the machine instead of at an office PC, and the rollout only expands after the floor has kept the pilot line's data honest for a full cycle. Abandonment is a fit problem, and this sequence makes fit the first thing that gets tested.
Do we have to change how the factory runs to fit the software?
Some process change is healthy — most factories want fewer paper handovers, not more. But the tool bends first: flexible consumption, per-product routes and routings you define mean Odoo is configured around how your orders actually move. Where something genuinely does not fit, we say so during scoping, in writing, while walking away is still cheap.
What does MRP software cost with Odoo — and which edition do we need?
Core manufacturing — BOMs, manufacturing orders, inventory, reordering rules — runs on Odoo Community, a $0 licence. The shop-floor tablet view, Quality, PLM and the Master Production Schedule are Enterprise features; that licence is billed by Odoo directly and we never mark it up. Our implementation work is a fixed price per phase, agreed in writing before the phase starts.
How long before the pilot line is running on Odoo?
For one line covering BOMs, work orders and stock, typically eight to twelve weeks from scoping to first live orders — longer if quality checks or multi-level subassemblies join the first phase. You get the phased timeline in writing after scoping, and the plant-wide schedule is set after the pilot proves itself, not before.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.