Odoo Manufacturing Routing: The Operations Sequence Through Work Centers

What a Manufacturing Routing Actually Is

A manufacturing routing is the sequence of operations a product flows through during production, and the work centers those operations run on. It answers two questions that a Bill of Materials (BoM) alone cannot: in what order is this made, and where does each step happen?

In modern Odoo (including Odoo 19), the routing is not a standalone master-data object. It is the ordered list of operation lines on the Operations tab of a Bill of Materials. Each line names an operation (for example, Cut stock, Mill features, Inspect, Pack) and assigns it to a work center. When a Manufacturing Order is confirmed from that BoM, Odoo spawns one Work Order per operation and schedules each against its work center calendar, capacity, and efficiency settings.

This is what separates a routing from a flat parts list. A BoM says what components go into a product; a routing says how, where, and in what order those components are transformed into the finished good. The two stay linked through the Consumed in Operation field on each component line, which ties a raw material to the specific step that uses it so readiness checks know whether first-step parts are available before work begins. That same structure feeds [material requirements planning](/learn/mrp-guide): MRP nets demand and stock; routing turns the make plan into station-level work.

BoM and Routing in Odoo: What Each Controls

Search traffic for “bom and routing in odoo” usually means the same confusion: people expect a separate routing form the way older ERPs and Dynamics 365 provide. In Odoo the recipe and the process share one document — the BoM — with two tabs that must stay consistent.

The Components tab is the material recipe: product, quantity, and optional scrap rules. The Operations tab is the process recipe: sequence, work center, duration mode, and optional worksheets. When Work Orders is disabled, the Operations tab never appears and every Manufacturing Order behaves like a single black-box step with no work-center load or OEE. When Work Orders is enabled, confirming an MO explodes both tabs into component moves and work orders.

Linking materials to steps is optional but high-value. Without Consumed in Operation, Odoo tends to treat components as available at MO start. With it, steel is expected at Cut, packaging only at Pack, and Manufacturing Readiness can fail early on the right station instead of after the line is already blocked.

Routing vs Operations vs Work Centers vs BoM

Searchers who type “odoo manufacturing routing” or “bom and routing in odoo” often need vocabulary first, not a settings tour. Four labels show up in every partner guide and forum thread; they are related but not interchangeable. Get the map wrong and you will “fix capacity” on a BoM line or hunt for a Routing menu that no longer exists as master data.

Think of the stack bottom-up: the BoM is the product recipe document; the routing is the process view of that document (the ordered Operations tab); each operation is one step with duration and dependencies; each work center is the capacity resource that can host many operations across many products. Confirming an MO materializes work orders from those operation lines so the floor can start, stop, scrap, and reassign.

Enabling Work Orders and Work Centers

Odoo’s routing feature sits behind a single setting. Open the Manufacturing app, then Configuration, then Settings, and tick the Work Orders checkbox under Operations. That unlocks the Work Centers menu under Configuration and the Operations tab on every Bill of Materials. Without it, BoMs are flat component lists with no operation sequence and no work-order tracking.

For tablet-style execution, enable Shop Floor under the same Operations settings block. Work Orders alone creates work orders and Gantt planning; Shop Floor is what operators use to start/stop timers, log scrap, block a center, and — in Odoo 19 — run Modify Routing actions on a live job. Partner walkthroughs treat Shop Floor as the live capture layer that makes OEE and real duration history usable.

Work centers are where Manufacturing work orders are processed. Official Odoo 19 documentation describes them as the unit for tracking costs, building schedules, planning capacity, organizing equipment, and measuring efficiency. Specifying a work center is required when a work order is defined on the BoM Operations tab. A work center can represent a physical station (Assembly Station 1, CNC Mill 3), a certified team, or any unit of productive capacity. Each one carries working hours, cost per hour, time efficiency, capacity, OEE target, setup time, cleanup time, optional alternative work centers, and often an Equipment tab for linked maintenance assets.

Once Work Orders is on, the Operations tab becomes the heart of the routing. Each line added there is one step in the production sequence — and the ordered set of lines is the routing itself. Older Odoo versions and many third-party ERP screens taught a separate Routing menu; if you are following pre-v14 or generic MRP tutorials that still say “create a routing, then attach it to the product,” stop and use BoM Operations instead — that is the current Odoo model.

Work Center Fields That Drive MO Planning

Most weak Odoo schedules share the same root cause: work centers exist, but capacity, efficiency, and calendars still sit at defaults. Infinite-looking Gantt charts look clean until the shop floor has three jobs on one mill and an idle booth next door. The fields below are the ones that change planned duration, load, cost, and OEE targets on every Manufacturing Order that routes through the center.

Capacity is not a substitute for multiple machines. Odoo’s capacity field means parallel units on the same resource (for example a multi-fixture bench). Two independent CNC mills should be two work centers — often linked as alternatives — not capacity = 2 on one form. Wrong capacity inflates throughput in planning and hides real bottlenecks.

Configuring Operations on a Bill of Materials

1. 01
   Enable Work Orders

   Go to Manufacturing > Configuration > Settings and enable Work Orders. This exposes the Operations tab on BoMs and the Work Centers menu.

2. 02
   Create your work centers

   Under Configuration > Work Centers, define each station with Working Hours, Time Efficiency, Capacity (and Specific Capacities if products differ), OEE Target, Setup Time, Cleanup Time, Cost per hour, and any Alternative Workcenters.

3. 03
   Add operation lines to the BoM

   On the BoM’s Operations tab, click Add a line for each step in sequence. Name the operation, pick its Work Center, and choose a Duration Computation mode. The ordered operation lines are the routing.

4. 04
   Set duration and computation

   For each operation, choose Set duration manually and enter a Default Duration in minutes, or choose Compute based on tracked time so Odoo averages duration from recent completed work orders at that center.

5. 05
   Link components to operations (optional)

   On the Components tab, use the Consumed in Operation column to tie each raw material to the step that uses it. This drives Manufacturing Readiness checks before an order starts.

6. 06
   Add dependencies (optional)

   If Operation Dependencies is enabled in Settings (and ticked on the BoM’s Miscellaneous tab), use the Blocked By field on each operation so a downstream step waits until its predecessor finishes.

Multi-Step Routing Example: Cut → Mill → Inspect → Pack

A concrete routing makes the abstract model usable. Take a machined metal bracket built on four work centers. Operations stay sequential unless you deliberately leave dependencies off and allow parallel starts; with Operation Dependencies, Inspect cannot start until Mill is done.

Planned process time for one unit is 12 + 25 + 5 + 3 = 45 minutes of cycle time before setup, cleanup, and time-efficiency multipliers. If the CNC mill is at 90% time efficiency, the mill step alone schedules as roughly 25 × (100/90) ≈ 27.8 minutes. A Capacity of 1 on that mill means a 10-unit MO stacks ten cycles on the same resource unless you split MOs or reassign alternatives.

Sequential vs parallel: default order on the Operations tab is the intended flow. Operation Dependencies (Blocked By) hardens that order so Shop Floor cannot start Pack while Inspect is open. Parallel work is for true concurrent steps (for example paint and dry-cure on separate resources) — model them carefully, or planners will assume free float that the floor does not have.

End-to-End Flow: BoM → Operation → Work Center → Work Order → Shop Floor

Search queries like “how Odoo manufacturing handles work orders, routing, and production scheduling” are really asking for one pipeline. Routing is not a report you run later — it is the template that turns a confirmed Manufacturing Order into station work, Gantt load, and tablet actions.

Read the chain left to right: configuration lives on the BoM; execution lives on work orders and the Shop Floor. If any link is missing (Work Orders off, empty Operations tab, default infinite capacity calendars, or paper travelers instead of tablet start/stop), planners see a clean schedule while the floor queues three jobs on one mill.

Odoo Manufacturing Routing: Duration and Default Duration

Each operation line has a Duration Computation field with two practical families of modes. Set duration manually lets you type a Default Duration in minutes — Odoo’s estimated time to complete the operation, used for planning manufacturing orders and for determining work center availability. Compute based on tracked time replaces the manual figure with a rolling average from completed work orders (partner guides commonly describe last-N averages such as the last ten runs, or a broader historical average once the process is stable).

Implementation pattern that avoids the chicken-and-egg problem: start every new product on manual duration with a conservative buffer (many plants add roughly 20% until they have shop-floor history), run 20–30 real work orders with honest start/stop on the tablet, then switch mature operations to computed time so the routing self-corrects. Leaving every line on a year-old manual guess is the fastest way to ship optimistic Gantt charts.

Default Duration feeds directly into scheduling. When a Manufacturing Order is confirmed and planned, Odoo uses each operation’s duration, the work center’s Working Hours, Capacity, Setup/Cleanup, and Time Efficiency to place work orders on Planning by Workcenter and Planning by Production Gantt views. Time Efficiency is a percentage: at 50% every operation takes twice as long; at 100% it runs at the duration you typed; above 100% the center is modeled as faster than standard.

A frequent forum complaint is that planned times “ignore” the previous operation. That usually means either Operation Dependencies is off (so the next work order is not blocked and appears ready too early), calendars do not match real shifts, or people expect finite-capacity slot finding while Odoo still places work using duration math without fully rebalancing every queue. Dependencies fix sequence; realistic calendars and capacities fix load; advanced APS tools sit on top when you need multi-constraint optimization beyond ERP.

Alternative Work Centers, Time Off, and Load Balancing

Odoo 19 work center forms include Alternative Workcenters: stations where a work order should run if the primary center is not available. Official docs frame this as a backup assignment path; partner guides use the same field to balance load across identical or near-identical machines (CNC-01 with CNC-02 and CNC-03 as alternatives).

Configure alternatives on the work center that appears on the BoM operation, not as a second hidden routing. When CNC-01 is fully booked, under maintenance, or on time off, planners can reassign the work order to an alternative. Alternatives do not have to be identical: set Time Efficiency and Cost per hour per machine so a slower older mill correctly extends planned duration and cost when work spills over.

Work center time off is the planned unavailability path. Odoo’s official workflow: install Time Off, enable developer mode so the Time Off smart button appears on the work center’s Working Hours form, create a Resource Time Off entry with reason and date range, and ensure the primary work center lists at least one Alternative Workcenter with compatible equipment. On a confirmed MO, the Plan button can reassign work orders from the unavailable primary to the alternative while the time-off window is active. After the window ends, Plan no longer forces the alternative unless the primary is at capacity. Without an alternative configured, work orders simply pile on the dead station — the Plan button has nowhere to send them.

Practical rule: create one work center per independent resource, link peers as alternatives, and keep capacity as concurrent units on that resource only. Using capacity to fake multiple machines collapses OEE and load reporting into one fake station and breaks shift comparisons. Octura’s Odoo 19 capacity guidance is blunt: two independent CNCs are CNC-01 and CNC-02 as alternatives, not capacity = 2 on a single form.

OEE Tracking on Work Centers

Overall equipment effectiveness (OEE) in Odoo Manufacturing is the share of time a work center is fully productive relative to the time it is active. Official Odoo 19 docs define fully productive time as periods when the center is operational and processing work orders that have not exceeded their expected duration. OEE is shown as a percentage on the work center form smart buttons and under Manufacturing > Reporting > Overall Equipment Effectiveness.

For OEE to mean anything, Time Efficiency, Capacity, OEE Target, and Working Hours must match the real station. Odoo records losses such as reduced speed (work longer than expected duration), material availability (center free but components missing), and equipment failure (blocked for maintenance). Shop Floor start/stop and downtime logging supply the timestamps; batch-closing work orders at shift end destroys the metric.

Industry practice still uses the classic Availability × Performance × Quality framing when coaching plants; Odoo’s product OEE is the ERP’s productive-time ratio against available work, not a separate third-party MES formula. Set an honest OEE Target (for example 87.5% if you expect 7 productive hours in an 8-hour day) and treat the report as a coaching tool, not a punishment score — operators who fear the metric will game start/stop times.

How Routing, Work Orders, and Production Scheduling Fit Together

Routing configuration only pays off when the execution path is clear. Confirming a Manufacturing Order with Work Orders enabled creates one work order per BoM operation, copies duration and work center, and fills the MO’s Work Orders tab. Operators complete those work orders on the MO form or in the Shop Floor app; marking a step done advances the flow, especially when dependencies block the next operation until the predecessor finishes.

Scheduling is the planning layer on top: Manufacturing > Planning > Planning by Workcenter (and Planning by Production) shows Gantt load by station. By default, Odoo-style ERP scheduling is closer to infinite capacity than true finite slotting: it places work from durations, calendars, and lead times, but does not always rebalance every queue so that a fully booked mill automatically pushes later jobs to the next free window. Partner capacity guides are blunt about the failure mode — a beautiful Gantt that collapses on contact with three concurrent jobs on one machine. Honest Working Hours, Capacity, Time Efficiency, alternatives, and planner drag-and-drop are the first realism layer; custom finite slot-finding or an APS sits above that when the shop is highly constrained.

Multi-location and multi-warehouse manufacturing is another common pain: one BoM operation list does not magically move semi-finished stock between plants. If Cut runs in Warehouse A and Mill only exists in Warehouse B, model subassemblies with their own BoMs, stock routes, and inter-warehouse replenishment — not a single work center pretending to be two sites. Warehouse manufacture steps (1-step / 2-step / 3-step pick-manufacture-store) control component and FG stock moves; they complement routing, they do not replace it.

When is native Odoo routing enough? Stable discrete BOMs, a handful of work centers per step, honest durations, and Shop Floor discipline. When do teams bolt on external scheduling? High-mix job shops, finite capacity across many constrained resources, and complex changeovers — ERP still owns BOM, WO consumption, and cost; APS owns the slotting. Framing that split early avoids blaming “routing” for problems that are really infinite-capacity assumptions. For the broader manufacturing stack around BoMs, quality, and subcontracting, see the [Odoo manufacturing hub](/learn/manufacturing).

Shop Floor Execution and Modify Routing in Odoo 19

Configuration is useless if progress only reaches Odoo after someone updates a paper traveler. Practitioners keep repeating the same 2026 theme on X and partner blogs: paper is not live production data; if work-order progress arrives tomorrow, today’s schedule decision is already late. Shop Floor is Odoo’s answer — operators log in on a tablet, pick their work centers, start and stop operations, and keep the MO record synchronized with the floor.

Odoo 19 Shop Floor actions commonly available during an operation include Register Production / Serial, Add Components, Scrap, Add By-product, Update Instructions, Create a Quality Alert, Request Maintenance, Block, Open Manufacturing Order, and Modify Routing. Those actions are what turn a static routing into a living process when reality diverges from the BoM.

Modify Routing is the floor-level escape hatch. Partner documentation for Odoo 19 describes two paths: Move to work center (reassign the current operation to another station — often an alternative machine when the primary is down or overloaded) and Add Work Order (insert an unexpected step with title, work center, expected duration, and placement after a chosen operation). Use it for real process changes; do not use it as a substitute for fixing the BoM when every job needs the same extra deburr step.

Discipline still matters. Batch-closing work orders at shift end destroys OEE and computed durations. Allowed Employees on the work center can restrict who may run certified equipment. Block for true downtime reasons so loss categories stay clean. Greytrix and other partners pitch the same outcome: replace paper job cards with tablet updates so inventory, time, scrap, and cost stay accurate in the moment.

Practical Patterns: Quality, Scrap, Parallel Steps, Multi-Location, Subcontracting

Definition tables win the SERP; plant teams stay for patterns that survive go-live. The five cases below are the ones that show up in Odoo 18/19 forums, partner case studies, and shop-floor rollouts when a “simple” BoM Operations list meets a real factory.

Quality at a specific step. With the Quality app enabled, create a Quality Control Point (QCP) under Quality → Quality Control → Control Points. Set Operations to Manufacturing and, when the Work Order Operation field appears, pick the BoM operation name (for example Assembly or Inspect). Odoo 19 docs use the Coffee Table example: a QCP tied to the Assembly work order creates a check on that step only when an MO for that product is confirmed — not a vague end-of-MO inspection after the damage is already built in. Check types that fit stations include Pass–Fail, Measure (norm + tolerance), Instructions, Register Production, and Take a Picture. Pair QCPs with Operation Dependencies so Pack cannot start until Inspect has closed.

Scrap at the operation, not only at close. Official scrap workflow: from a Manufacturing Order use Actions → Scrap; from Shop Floor open the MO card actions and choose Scrap. Shop Floor is limited to scrapping components; finished goods are scrapped from the Manufacturing app once the MO is Done. Scrapped qty moves to Virtual Locations/Scrap for loss tracking without inventing a fake physical bin. Use Replenish Scrapped Quantities only when the warehouse runs two- or three-step manufacturing and you need a pick to replace the lost component. Routing design tip: put high-risk operations early and attach QCPs there so scrap hits before expensive downstream capacity is burned.

Parallel vs sequential operations. Sequence numbers alone are a suggested order. Hard sequence requires Work Order Dependencies (settings) + Operation Dependencies on the BoM Miscellaneous tab + Blocked By on each dependent line. Two operations that share no Blocked By relationship can be ready at the same time — use that only when the floor truly runs concurrent resources (for example powder-coat and hardware kitting on separate centers). If every step must wait on the previous station, set Blocked By end-to-end or operators will start Pack while Mill is still open.

Multi-location inside one MO. A common Odoo 18 thread: each operation happens in a different stock location with its own input/output, but the MO still looks like one plant job. Practitioners’ rule of thumb: treat Location ≈ Work Center — if the step crosses a hard location boundary that needs its own stock moves and traceability, model it as a separate operation (or a multi-level subassembly BoM), not one operation with magical multi-site stock. Warehouse manufacture steps (1/2/3-step) still own component pick and FG putaway; BoM Operations own the process sequence. Do not expect a single work center field to replace inter-warehouse routes in [inventory](/learn/inventory).

Subcontracting is not “one more operation on the internal routing.” Odoo models subcontracted products with subcontracting-type BoMs and purchase flows (basic subcontract, resupply components to the subcontractor, or dropship components to the subcontractor). Internal multi-step routing stays on Manufacture-type BoMs with work centers you own. Multi-tier subcontracting (vendor A feeds vendor B) needs separate BoMs, vendors, and stock routes — partner manufacturing case studies in 2026 treat that as an MRP + inventory design problem, not a single Operations-tab sequence. Keep the boundary clean so job costing does not mix your shop’s Cost per hour with a PO service line you never configured.

By-products and mid-job structure changes. Configure by-products on the BoM when a step yields a salable or reusable co-product; Shop Floor can also Add By-product during a live work order for one-off yields. Structural changes that every future MO needs belong on the BoM Operations tab; one-off inserts belong in Modify Routing. For quality program design beyond station checks, see the [Odoo quality](/learn/quality) guide.

How Routing Drives Cost

Routing is where manufacturing conversion cost accumulates. Odoo computes an operation’s cost from the hourly cost of operating the work center and the duration of the operation. Cost per hour on the work center has two parts — a per-workcenter figure for the machine and operating expense, and a per-employee figure for average labor.

The arithmetic is straightforward: cost equals the work center’s hourly rate multiplied by the operation’s duration. Official Odoo documentation walks through Assembly Station 1 at $30.00 per hour: a Cut felt operation with a 7-minute Default Duration costs $3.50, and an Attach pad to felt operation at 15 minutes costs $7.50. Sum those operation costs across the routing and add component costs, and you have the BoM’s estimated Manufacturing Order cost.

Odoo draws a deliberate line between this MO cost — the planned cost built from the BoM configuration — and the real cost recorded after production. Real cost uses each employee’s actual hourly rate and the durations actually logged on the shop floor. The two diverge whenever operations run longer than Default Duration, more components are consumed than planned, or component purchase prices shift. The routing is the structure that makes both numbers calculable.

Where Is Routing in Odoo? The Naming Trap

If you are searching “where is routing in Odoo,” the short answer for production is: Bill of Materials → Operations tab, after Work Orders is enabled. There is no modern Odoo 19 menu named Manufacturing → Routings that holds a reusable master like older versions and many competing ERPs. The technical model still uses operation lines (historically mrp.routing.workcenter records) but they hang off the BoM, not a separate routing header you attach to many products.

There is a second trap on the same form. The field literally labelled Routing on a BoM’s Miscellaneous tab is not the production routing. Official Odoo 19 BoM documentation defines it as a warehouse stock-routing concept — it selects which warehouse manufacturing operation type (pull rule) applies when a product is produced across multiple warehouses, defaulting to that warehouse’s Manufacturing operation type.

Mixing the two up leads to misconfigured production flows and stock rules that never fire. If you are configuring how a product is made, you work on the Operations tab. If you are configuring how stock moves between warehouse locations, you work on the Miscellaneous tab Routing field. They share a label and almost nothing else. Teams migrating from Dynamics 365 or legacy Odoo often look for a Routing No. on the product form — that pattern lives on Business Central, not on current Odoo manufacturing.

The Dynamics 365 Equivalent for SMEs

Dynamics 365 offers two routing models depending on the edition, and both model the same concept as Odoo’s Operations tab — a sequence of operations through work centers — but with one structural difference.

In Dynamics 365 Business Central, the SMB edition, a Routing is explicit master data assigned to a produced item via the Routing No. field. It has a Status (New, Under Development, or Certified), a Type (Serial, ordered by Operation No., or Parallel, ordered by Next Operation No.), and routing lines carrying Operation No., resource Type (Work Center or Machine Center), Routing Link Code, Run Time, Setup Time, and Concurrent Capacities. Setup time is calculated per production order, while run time is calculated per produced item. Duration follows the formula Run Time divided by Efficiency divided by Capacity — so 2 hours of run time at 80% efficiency takes 2.5 hours, and at 200% efficiency it takes 1 hour. BC defaults to infinite capacity scheduling, with optional finite-capacity scheduling on resources flagged as constrained.

In Dynamics 365 Supply Chain Management, the enterprise edition, Microsoft defines a route as the process for producing a product: it describes each step (operation) and the order they must be performed in, along with required resources, setup and run time, and how cost is calculated. A route definition has four elements — Route (order of operations), Operation (a reusable named step), Operation relation (setup/run time, cost categories, and resource requirements that vary by route, product, and site), and Route version (which route applies for a given product, by site, quantity, and date). F&O supports both simple sequential routes and route networks with parallel branches, primary and secondary parallel operations, resource-requirement-based scheduling where operations resolve to any capable resource rather than a fixed machine, and routes shared across sites.

The mapping is clean: an Odoo Work Center maps to a BC Work Center or an F&O Operations Resource; an Odoo operation line maps to a BC Routing Line or an F&O Operation plus Operation Relation; Odoo’s Default Duration maps to BC Run Time or F&O Run Time; Odoo’s Consumed in Operation maps to BC’s Routing Link Code. The key structural difference is that D365 separates the routing from the BoM as its own reusable master-data entity — one routing can serve many items — whereas Odoo binds the operation list directly to the BoM. Neither approach is universally better; Odoo’s is simpler to configure for a single product family, while D365’s reusable routing scales better across sites and shared processes. For a deeper Business Central production walkthrough, see [Business Central manufacturing](/learn/bc-manufacturing).

When It Makes Sense to Bring in Help

Configuring a routing sounds mechanical, but the decisions behind it — how granular your work centers should be, whether to use manual or tracked durations, how to split machine cost from labor cost, how to set alternatives and OEE targets, and whether to model parallel operations or keep the flow strictly serial — shape every cost number and every schedule the system produces afterwards. Getting the routing wrong at rollout means every Manufacturing Order cost, every lead time, and every capacity plan inherits the error.

That is where a dual-platform implementation partner earns its fee. Because Flectic implements both Odoo and Dynamics 365, the routing gets modelled against the right structural pattern for the platform you actually choose — not retrofitted from a template built for the other one. If you are weighing up an ERP move or reconfiguring an existing manufacturing setup, book an ERP Readiness Call and we will walk through your routing, work centers, and cost flow before any commitment.

Frequently asked questions