When a manufacturing order is created for a product with a routing, Odoo generates work orders, one per operation. Those work orders then have to be scheduled: placed against work centers and against time. This piece explains how work order scheduling works in Odoo.
What scheduling has to do
Scheduling work orders means deciding, for each work order, when it runs at its work center. A plant has many work orders, from many manufacturing orders, competing for a limited set of work centers. Scheduling places them: it works out a sequence and a timing so that the work centers do the work in a sensible order, and so that the manufacturing orders can be completed when they are needed. Without scheduling, work orders are just a list; with it, they are a plan the floor can run.
The inputs scheduling uses
Work order scheduling draws on the data set up earlier. It uses the routing: the operations of a manufacturing order run in their sequence, and where operation dependencies are defined, an operation waits for the operation it depends on. It uses the operation durations: how long each work order is expected to take. It uses the work centers: which work center each operation runs at, the work center's capacity, and its working calendar, so scheduling places work only when the resource is actually available. This is why setting up routings and work centers realistically matters; scheduling is only as good as those inputs.
How the schedule comes together
From those inputs, Odoo schedules the work orders: each operation is placed at its work center, in routing order, respecting dependencies, taking its expected duration, within the work center's available time. The result is a schedule that says when each work order should run. Because the schedule is built from the routing, the durations, and the work center calendars, it reflects the real shape of production rather than a wish.
Seeing and adjusting the schedule
Odoo presents the work order picture in ways that let a manufacturer see and manage it, including a view of work orders organised by work center, so it is clear what each work center has queued, ready, in progress, and behind. The schedule is not a fixed thing set once. As reality changes, an order is added, a priority shifts, a work center goes down, work orders can be rescheduled, and the picture updated. The value of work order scheduling in a connected system is exactly this: the schedule is live data that can be re-formed as conditions change, rather than a static plan that goes stale.
Capacity and the realistic schedule
A schedule is only useful if the floor can actually meet it, and that depends on scheduling respecting capacity. If scheduling is allowed to pile more work into a work center's time than the work center can do, the schedule is a fiction. Scheduling that respects each work center's real capacity and calendar produces a harder but achievable schedule. A manufacturer should want the realistic schedule, even though it shows the plant cannot do everything at once, because the realistic schedule is the one the floor can actually run to.
Scheduling and priority
Not all manufacturing orders are equal; some are more urgent. Odoo's scheduling takes account of priority, so that urgent work is placed ahead of less urgent work. This lets a manufacturer influence the schedule by marking what genuinely matters most, rather than every order being treated identically.
The takeaway
Work order scheduling in Odoo places each work order against its work center and against time, using the routing and its dependencies, the operation durations, and the work centers' capacity and calendars. The schedule is live data that can be re-formed as conditions change. It is only as good as the routing and work center setup behind it, and it is only useful if it respects real capacity, so it produces a schedule the floor can genuinely meet. For how we approach Odoo for manufacturers, see our manufacturing work.