For an Odoo business in Belgium or France, a scheduled manufacturing order is only useful when the shop floor can actually execute it. In Odoo Enterprise, work centers provide capacity, calendars, costs and operation tracking; dependencies stop a step from starting before its prerequisite. These settings should represent the real flow, not simply reproduce the factory organisation chart.
Start with bottlenecks and measurable operations
Create a work center when a resource has capacity, a calendar, a cost or a planning constraint to manage: a shared machine, welding cell, paint booth or final inspection point. A bill-of-material operation then uses that work center. Do not create one center per operator when crews rotate; instead, model the stable resource whose availability supervisors can maintain.
Target durations are used for planning and cost estimates. Review them after representative production runs, without turning every exception into a new standard. A manufacturing order’s planned cost and actual cost remain two measures that should be read together.
Block only genuinely mandatory sequences
Work-order dependencies help when one operation must be completed before another can begin: machining before dimensional inspection, or assembly before testing. In Odoo 19, they are enabled after work orders, then configured on bill-of-material operations. A blocked step becomes available when its prerequisite is completed.
Avoid chaining every routing step by default. If two operations can safely take place in parallel, blocking them unnecessarily reduces displayed capacity. The goal is to make the constraint that protects the product visible, not to freeze the schedule.
Design for exceptions before the shop floor
A dependency can be unblocked to process an exception; that action breaks the link between the steps. Reserve it for an authorised, traceable case, such as an alternative quality approval or a rework operation. Define who may do it, what evidence is required and how the production manager is notified.
The work-center calendar deserves the same care: scheduled maintenance, team leave and machine downtime need to be recorded before planning. Otherwise, an apparently feasible plan promises a date that the workshop cannot meet.
Test a full flow, a saturated capacity and a waiver
Fictional Underside scenario: a manufacturer assembles a module, tests it, then packages it. Testing cannot start before assembly; packaging can run in parallel for another item. The team creates two close manufacturing orders, plans their operations, makes the test bench unavailable for half a day, then checks revised dates and blocked statuses.
- Verify that a manufacturing order creates the expected operations from the bill of materials.
- Test a parallel operation and a mandatory dependency.
- Compare the schedule before and after a work-center unavailability.
- Record time on a real run and review target durations where needed.
- Test an authorised dependency override with justification and manager review.
- Check the effects on planned cost, actual cost and the promised date.
Track the gap between plan and reality
Track late operations, overloaded centers, overridden dependencies and differences between expected and recorded time. A recurring gap can reveal an incomplete bill of materials, poorly modelled capacity or a missing shop-floor instruction. Pair this work with Odoo quality control points and a review of production and inventory valuation.
Official source and scope
References: Odoo 19 documentation on work centers and work-order dependencies. Check the modules and permissions available in your environment. The governance, acceptance scenarios and metrics are Underside’s analysis.
Frame your Odoo work centers with Underside, connecting workshop capacity, quality and customer promise dates.