There is a fundamental distinction in how production is scheduled: whether the schedule respects the real limits of resources, or assumes resources are unlimited. This piece explains finite versus infinite capacity scheduling and why it matters in Odoo.
The two approaches
Infinite capacity scheduling assumes a resource can do any amount of work in a period. It schedules work according to when it is due, without checking whether the resource can actually fit it. It is simple to compute, and it produces a schedule that lists what should happen without asking whether it can.
Finite capacity scheduling respects the real limit of each resource. It will not schedule more work into a work center's time than the work center can genuinely do. It produces a schedule that is constrained by reality: harder, because it has to fit work within real limits, but achievable.
The difference is whether the schedule treats capacity as a real constraint or ignores it.
Why it matters
The distinction matters because of what each kind of schedule is worth to a manufacturer. An infinite-capacity schedule can look fine on paper while being impossible on the floor: it can show a work center doing, in one day, three days of work, because it never checked. A manufacturer that plans against such a schedule is repeatedly surprised when the floor falls behind, because the plan assumed a capacity that does not exist. A finite-capacity schedule, by respecting real limits, produces a plan the floor can actually meet. It may be less comfortable, it shows honestly that the plant cannot do everything at once, but that honesty is exactly its value.
The role of capacity data
Finite capacity scheduling depends entirely on knowing the real capacity of resources, and in Odoo that comes from how work centers are set up. A work center carries its capacity and its working calendar. Finite scheduling uses those to know how much each work center can genuinely do and when. This means finite capacity scheduling is only as good as the work center capacity data: if a work center's capacity is set optimistically, the finite schedule built on it inherits that optimism and is not truly realistic. Honest work center capacity data is the foundation of meaningful finite scheduling.
What this means for an Odoo manufacturer
For a manufacturer using Odoo, the practical implication is to want, and to set up for, scheduling that respects real capacity. That means investing in honest work center setup, accurate capacity, accurate calendars, so that the scheduling has real limits to respect. A manufacturer that sets work centers up carelessly, or not at all, effectively gets scheduling that does not reflect real capacity, and a schedule that does not reflect real capacity is a schedule the floor cannot trust. The effort of setting work centers up realistically is what earns a manufacturer a schedule that is achievable.
Living with a finite schedule
One honest point about finite capacity scheduling: it tells uncomfortable truths. A finite schedule will show, plainly, that the plant cannot fit all the work into the time available, that something has to give, be delayed, be moved, be subcontracted, be reprioritised. That is not the scheduling failing; that is the scheduling being honest about a real constraint. A manufacturer should welcome that honesty, because the alternative, an infinite schedule that hides the constraint, does not remove the constraint; it just ensures the manufacturer meets it as a surprise on the floor instead of as a visible fact in the plan.
The takeaway
Finite capacity scheduling respects the real limits of resources and produces an achievable schedule; infinite capacity scheduling ignores those limits and can produce a schedule the floor cannot meet. For a manufacturer using Odoo, the realistic, finite approach depends on honest work center capacity and calendar data, so setting work centers up properly is what earns a trustworthy schedule. A finite schedule tells uncomfortable truths about constraints, and that honesty is its value. For how we approach Odoo for manufacturers, see our manufacturing work.