Overview
A planner releases an achievable-looking order. Production then finds a wrong component quantity, missing operation and overloaded work centre. The completion date moves while purchasing places an urgent order. Odoo followed data that did not represent the factory.
Reliable Odoo MRP planning depends on connected product, BoM, operation, work-centre, inventory and lead-time records. Incomplete records create confident but unrealistic plans.
MRP data readiness means planning and execution information is defined, owned, tested and controlled. This guide maps the workflow then explains its data, controls, exceptions and KPIs.
The Current Pain: Planning Exists Outside the Manufacturing ERP
Manufacturers often have several production truths. Engineering keeps components in a spreadsheet. Supervisors know the sequence from experience. Purchasing keeps lead times in email while machine availability stays outside work-centre calendars.
Planners then check stock by phone, add large buffers and adjust exported schedules. Late operator reporting leaves inventory and capacity behind reality.
The deeper issue is ownership and lifecycle control. A correct BoM becomes wrong after an unmanaged change while work-centre duration drifts when nobody reviews actual time.
What MRP Data Readiness Includes
Odoo MRP readiness covers four connected planning structures:
Bills of materials: The products, components, quantities, units, by-products and applicability needed to make an item.
Routing operations: The ordered production steps, dependencies, instructions and work centres used to perform the work. In Odoo these are commonly configured as operations on the BoM rather than treated as a separate planning idea.
Work centres: The resources where operations occur with calendars, capacity, efficiency, setup or cleanup time and cost assumptions.
Lead times: The durations Odoo uses to schedule purchasing, manufacturing and delivery early enough to meet demand.
They depend on clean products, routes, units, supplier data, inventory and timely shop-floor transactions. Readiness is an operating condition rather than an import file.
A Realistic Use Case: A Multi-Step Assembly
Consider an industrial pump using a motor, housing, seal kit and fasteners. Production includes preparation, assembly, testing and packing. Motors have long supplier lead times while housings are subassemblies and testing has limited capacity.
The old spreadsheet assumes material availability and a fixed seven-day duration. It ignores the testing bottleneck and supplier variation while substitutions and actual time remain informal.
The target connects demand to material, capacity, execution and feedback without inventing client results.
End-to-End Odoo-Enabled MRP Workflow
1. Demand Creates a Planning Requirement
A sales order, forecast, reordering rule or master production schedule creates demand. Product and route determine the supply action while planning works backwards from the target date.
Odoo supports reordering rules, make-to-order and the master production schedule. Choose routes deliberately because the wrong route creates the wrong supply action.
2. Odoo Selects the Product and BoM
Product, company, quantity and variant determine the BoM. Odoo describes BoMs as manufacturing blueprints with components plus optional operations and instructions. Use an approved production structure rather than an engineering draft.
The pump BoM expands demand into components while the housing subassembly follows its own route and lead time.
3. Material Requirements Are Calculated
Odoo combines demand with component quantities and units then considers stock, reservations and receipts. Shortages create purchase or lower-level production needs.
Wrong units, duplicate products and late stock movements make this calculation unreliable.
4. Lead Times Position Supply and Production
Odoo uses lead times to calculate when supply begins. Its lead-time documentation places manufacturing lead time on the BoM and vendor lead time in supplier information. Customer and security lead times influence related dates.
Do not hide supplier unreliability in manufacturing duration or repeat one buffer at several levels. Base times on history and document deliberate protection.
5. Operations Become Work Orders
With work orders enabled BoM operations form the routing. Odoo creates preparation, assembly, test and packing work orders with a centre, duration and instruction.
Too few operations hide bottlenecks while too many increase reporting effort and encourage bypasses.
6. Work Centres Provide Capacity and Cost Context
Odoo work centres support scheduling, capacity and cost tracking. Testing may process one pump while packing handles several. Calendars determine available capacity.
A work centre represents a schedulable resource or similar group. One factory-wide centre hides constraints while one per tool may be impractical.
7. Shop-Floor Execution Records Actuals
Operators process work orders, quantities, scrap and blocked work. Components are consumed and output produced. Odoo Shop Floor supports execution but reporting still depends on timely updates.
Substitutions, rework and partial completion need defined transactions. Do not edit the BoM to hide actual variance.
8. Completion Feeds Planning Improvement
Compare planned components, time and dates with actuals. Repeated variance may reveal wrong standards, process loss, capacity limits or supplier delay.
Actuals should trigger governed review. One unusual order should not rewrite every future standard.
Required MRP Data and Ownership
The readiness register should identify every critical object, its owner and the operational consequence of poor data.
| Data object | Required information | Accountable owner | Risk when wrong |
|---|---|---|---|
| Manufactured product | Stable code, product type, UoM, route, company and tracking | Product-data owner | Wrong replenishment action or split demand |
| Bill of materials | Finished item, version or applicability, components, quantities, units and by-products | Engineering or manufacturing engineering | Shortages, excess consumption or incorrect cost |
| BoM operation | Sequence, work centre, duration, dependency and instruction | Process engineering | Missing work, hidden bottleneck or wrong schedule |
| Work centre | Calendar, capacity, efficiency, setup or cleanup time, cost and alternatives | Production operations | Impossible capacity plan or misleading cost |
| Supplier record | Vendor, product, purchase UoM, lead time, minimum quantity and price context | Procurement | Late material and emergency purchasing |
| Inventory record | Location, available quantity, reservation, lot or serial and status | Warehouse | False availability and weak traceability |
| Planning policy | Replenishment route, safety stock, order quantity and security lead time | Planning | Excess stock, shortages or unstable dates |
Accountability does not mean one person enters every value. The owner approves definitions, effective changes and quality thresholds. Process users remain responsible for accurate daily transactions.
Readiness Controls and Exception Paths
Controls should prevent high-risk errors while giving valid exceptions a visible route. A mandatory field is useful only when the business knows the correct value. Placeholder values make the record look complete while damaging planning.
| Control point | Preventive control | Exception path | Approval or owner |
|---|---|---|---|
| Product release | Required route, UoM and company before manufacturing use | Hold product from planning | Product-data owner |
| BoM activation | Component, unit, variant and operation validation | Draft remains unavailable for released production | Engineering approval |
| Engineering change | Effective-date rule and impact review for open orders | Decide whether open MOs keep or adopt the revision | Change board or manufacturing owner |
| Work-centre setup | Capacity, calendar and duration evidence required | Use approved alternative centre or reschedule | Production planning |
| Lead-time update | Compare actual history with the current standard | Temporary risk buffer documented separately | Planning and procurement |
| Component substitution | Approved alternative and traceability rule | Supervisor or quality review before use | Engineering or quality |
| Shop-floor delay | Reason code and expected recovery date | Escalate capacity, material or maintenance issue | Production supervisor |
| Data defect after release | Freeze unsafe processing and retain audit evidence | Correct master data then replan affected orders | Named data owner |
Access rights should limit who can change active BoMs, work centres and planning policies. Important changes need a reason, test and communication to planning and production. Periodic review should archive obsolete structures rather than leave several apparently valid choices.
Common Exceptions the Model Must Handle
Material shortage is not always a planning defect. A supplier may deliver late or quality may reject a batch. The exception should show the affected component, orders, required date, responsible buyer and recovery option. It should not silently push every order date without human review.
Capacity shortage may result from demand peaks, downtime or inaccurate duration. Planners need approved choices such as an alternative work centre, overtime, subcontracting, resequencing or a revised promise. The system should preserve the reason for the decision.
Production may consume more material, complete fewer units or create scrap. Record the actual transaction and reason. Review whether the cause is a one-time event, training gap, quality issue or incorrect standard. BoM correction and operational variance are different actions.
MRP Data Readiness Checklist
Use this checklist for one product family before scaling Odoo manufacturing.
| Checklist item | Evidence required |
|---|---|
| Manufactured products have approved codes, units and routes | Product-master review |
| One valid BoM is identifiable for each planned product and context | BoM applicability test |
| Multi-level components create the intended supply action | BoM explosion and replenishment test |
| Operations reflect the real sequence and control points | Shop-floor walkthrough and sign-off |
| Work centres have current calendars, capacity and alternatives | Capacity test with representative demand |
| Planned operation times have an evidence source | Time study or approved historical sample |
| Vendor and manufacturing lead times are separated | Lead-time register and calculation test |
| Inventory, reservations and units reconcile | Stock-count and UoM validation |
| Substitution, scrap, rework and partial completion are designed | Exception test cases |
| Users can record work and material movement on time | Role-based user acceptance test |
| Owners and approval rules are documented | Data ownership matrix |
| KPIs and review frequency are agreed | Operating dashboard and meeting calendar |
A product family is ready when the full process produces explainable material dates, work orders and outcomes under standard and exception scenarios. Field completion alone is not enough.
KPIs That Show Whether MRP Data Is Working
Track BoM accuracy through component variance and data defects found after release. Measure planned-versus-actual operation time, schedule adherence, manufacturing lead-time variance and work-centre load accuracy. Monitor orders delayed by missing material, emergency purchases, inventory differences, unrecorded shop-floor work and exception age.
Also measure user behaviour. Frequent spreadsheet rescheduling, manual date overrides or late bulk completion signals that the model does not match operations. Review KPIs by product family and work centre because one average can hide a serious bottleneck.
Set thresholds with named owners. A variance does not automatically mean the standard is wrong. The review should separate data defects from genuine operational variation then assign corrective action.
A Phased Implementation Approach
Begin with one representative product family that includes purchased parts, a manufactured subassembly and two or more operations. Clean the product and supplier masters then validate BoMs, operation sequences, work-centre capacity and lead times.
Run demand through the full planning flow in a test environment. Confirm procurement dates, material availability, manufacturing dates, work orders, reservations and expected completion. Test shortages, substitutions, downtime, partial quantities, scrap and rework. Reconcile planned and actual outcomes during a controlled pilot.
After stabilisation expand by product family or production line. Reuse standards but do not assume every process has the same routing depth or lead-time logic. An Odoo manufacturing services assessment should connect MRP data preparation with process design, Inventory, Purchase, Quality, Maintenance, migration, testing and user adoption.
Conclusion
Odoo MRP data readiness means more than importing products and BoMs. Demand must select the right product, replenishment route, BoM, operations, work centres and lead times. Shop-floor transactions must then return timely actuals so planning can improve.
Start with one product family and test the entire demand-to-completion flow. Give each critical object an owner, control active changes and design exception routes for real factory conditions. When material requirements, capacity dates and actual results are explainable the manufacturing ERP becomes a planning tool rather than another schedule to correct manually.
Frequently Asked Questions
1. What is Odoo MRP data readiness?
It is the condition in which products, BoMs, operations, work centres, lead times, inventory and planning policies are complete, owned and tested well enough to support reliable manufacturing planning and execution.
2. What is the difference between a BoM and routing in Odoo?
The BoM defines components and quantities. The practical routing is represented by ordered BoM operations assigned to work centres when work orders are enabled. Together they describe what is required and how production should proceed.
3. Where is manufacturing lead time configured in Odoo?
Odoo documentation places manufacturing lead time on the BoM. Supplier lead time is maintained with vendor information. Customer and security lead times serve different scheduling purposes and should not be combined without clear logic.
4. How detailed should Odoo manufacturing operations be?
Include steps needed for scheduling, capacity, quality, costing or operator control. Avoid unnecessary micro-steps that add reporting effort without improving a decision. Validate the level through a shop-floor walkthrough.
5. What work-centre data is most important?
Important fields include the working calendar, capacity, efficiency, setup or cleanup time, planned operation duration, cost and approved alternatives. The exact set depends on planning and costing needs.
6. Should actual production time automatically change planning standards?
Not without review. Actual history should trigger analysis but unusual orders, downtime or training can distort the result. The process owner should approve a standard change using a representative sample.
7. How can a manufacturer test MRP data before go-live?
Run representative demand through BoM selection, material planning, procurement, work-order scheduling, shop-floor execution and completion. Include shortages, substitutions, downtime, scrap, rework and partial quantities then reconcile expected and actual results.
