Odoo implementation for manufacturers: planning the production-line rollout
An Odoo implementation for a manufacturer works when bills of materials, routings, work centres, component purchasing and stock, quality checks and maintenance all run from one system instead of a spreadsheet per department. Configure the manufacturing modules first, prove the pattern on one production line, then migrate and roll out the remaining lines with a rehearsed rollback.
Submit a project See the Odoo implementations recordReviewed by Huy Nguyen (David), CEO · Updated 19 Oct 2026 · 12 min read
OutsourcingVN is operated by Netbase JSC. Working with a local Odoo implementation partner, Netbase has consulted on and customised Odoo in Vietnam for manufacturers, among other clients that are not named; this guide turns that pattern into a production-line implementation plan, not a report on any one project's results.
Contents
- What does a manufacturing Odoo rollout need to cover?
- Which Odoo modules cover which part of manufacturing?
- How should the rollout be sequenced?
- Worked scenario: a five-line electronics assembler's pilot
- What has Netbase delivered on Odoo for manufacturers?
- Where does AI fit in a manufacturing Odoo rollout?
- What should you check before committing to the stack?
- What goes wrong in a manufacturing Odoo rollout?
- Which questions should you ask an Odoo implementation partner?
- How this guide is sourced and where it stops
- Common questions
- Plan your line-by-line Odoo rollout
What does a manufacturing Odoo rollout need to cover?
Whether Odoo is the right platform at all is decided on the Odoo platform page, and whether to configure Odoo, extend it or build a custom ERP instead is decided in Odoo vs custom ERP; this guide starts once Odoo has been chosen and covers planning the manufacturing-plant rollout itself. A retail chain's Odoo rollout centres on a different set of decisions, point of sale and store replenishment rather than a production line, and Odoo implementation for retail chains sequences that rollout instead.
A plant's rollout has to cover eight things working together: bills of materials and routings that describe how each product is built, manufacturing orders and work centres that run the production floor, component purchasing and stock that keep a line fed, quality checks at the points where a defect must be caught, maintenance that keeps equipment running, costing that feeds the finished-goods number into accounting, a shop-floor interface operators actually use, and the rollout sequence that proves the pattern on one line before it reaches the rest. The ERP and back-office operations solution maps the wider back-office workflow behind these decisions, and the ERP procurement and inventory guide defines the stock states and reconciliation points a manufacturing rollout still needs.
Which Odoo modules cover which part of manufacturing?
| Manufacturing operation | Odoo module or feature | What it usually replaces |
|---|---|---|
| Product structure | Bills of materials and routings | A paper routing sheet or a spreadsheet parts list |
| Production floor control | Manufacturing orders and work centres | A verbal work assignment or a paper traveller |
| Component purchasing and stock | Inventory reordering rules feeding Purchase | A manual reorder call or email to a supplier |
| Quality checkpoints | Quality control points and checks | A paper inspection sheet kept at the line |
| Equipment upkeep | Preventive and corrective maintenance requests | A maintenance logbook or an operator's memory |
| Production cost | Manufacturing order costs feeding Accounting | A spreadsheet cost estimate built after the fact |
| Shop-floor interface | Tablets on the production line | A paper work order carried station to station |
Netbase's own ERP consultancy and development experience covers Odoo consultancy and customization, cloud ERP platform development, and modules built for finance, inventory, sales, HR, CRM and project planning; the same experience is what plans the stock and accounting modules a manufacturing rollout sits on top of.
How should the rollout be sequenced?
-
Blueprint the rollout
Document the bills of materials, routings, work-centre assignments, purchasing approvals, quality checkpoints and maintenance schedules each line runs today, and map them onto Odoo's Manufacturing, Inventory, Purchase, Quality and Maintenance modules before any line goes live.
-
Pilot one production line
Configure and run the rollout on a single representative line first, including its bills of materials, work centres, quality checkpoints and shop-floor tablets, so the pattern is proven before it is repeated anywhere else.
-
Migrate component and routing data
Move item masters, bills of materials, routings, equipment records, supplier records and open purchase orders from the legacy systems, cleaned and reconciled against the pilot line's real numbers; the legacy data migration planning guide covers that reconciliation decision in full.
-
Rehearse the cutover and the rollback
Run the pilot line on Odoo alongside its old process for a full production cycle, and rehearse the rollback to the legacy process before anyone decides to proceed.
-
Decide go or no-go for the next wave
A named owner checks the pilot line's first-pass yield, quality-check pass rate and cost variance against the legacy baseline before authorising the remaining lines.
-
Roll out line by line
Repeat the configured pattern across the remaining lines in scheduled waves, verifying each line's bills of materials, quality checkpoints and maintenance schedule before the next wave starts.
-
Stabilise and hand over
Close out exceptions from the rollout, confirm costing and maintenance are running everywhere, and hand over the running system with training and support.
(opens the full-size diagram in a new tab)
Worked scenario: a five-line electronics assembler's pilot
A hypothetical electronics assembler runs five assembly lines from a shared parts store, with routings on paper and quality checks logged on a clipboard at final test. The blueprint stage maps each line's bill of materials, work-centre sequence and quality checkpoint onto Odoo's Manufacturing and Quality modules. The pilot line goes live first: its operators use shop-floor tablets for a full production week while component stock and maintenance records migrate in parallel, and a yield dip on day two is traced to a routing step mapped to the wrong work centre during migration, fixed before the next line is touched. The go or no-go review checks that the pilot line's first-pass yield matches the legacy baseline and that the cost roll-up from the bill of materials reconciles with the previous month's accounting figure; only then do the remaining four lines roll out in two scheduled waves.
What has Netbase delivered on Odoo for manufacturers?
Working with a local Odoo implementation partner, Netbase has consulted on and customised Odoo in Vietnam for manufacturers, among other clients that are not named; see the Odoo implementations record for the published summary. Separately, Netbase's own ERP consultancy and development experience covers Odoo consultancy and customization and cloud ERP platform development, the same practice a manufacturing rollout's stock, purchasing and accounting modules draw on.
Plan the next step for your project
Where does AI fit in a manufacturing Odoo rollout?
The categories that pay off first on a manufacturing Odoo rollout are demand and reorder-point forecasting from the purchasing and stock history Manufacturing and Inventory already hold, flagging an unusual pattern in quality-check results for a supervisor to review, and suggesting a maintenance schedule from equipment history rather than a fixed calendar interval. None of it replaces the bill-of-materials, routing and quality logic Odoo already owns; it reads from records that are more trustworthy once every line reports into one system instead of a clipboard each. Legacy application modernization is the usual route when an AI feature is added to a manufacturing Odoo rollout already running rather than a new implementation.
What should you check before committing to the stack?
Odoo's own Manufacturing documentation states that the app "helps manufacturers schedule, plan, and process manufacturing orders," built around bills of materials that document the components and quantities needed for each product and routings that sequence the work across work centres, and that a work-centre control panel can put "tablets on the shop floor to control work orders in real-time and allow workers to trigger maintenance operations, feedback loops, quality issues, etc." Its Quality documentation describes quality control points that trigger checks at set stages and quality alerts raised when a check fails, and its Maintenance documentation states the app "helps extend the effectiveness of equipment by keeping track of maintenance requirements" through both preventive and corrective requests. The documentation for Odoo 18.0 describes the Shop Floor module as installed alongside Manufacturing, and notes it can be installed in a workstation's Chrome browser to limit that screen's access to other Odoo applications. Confirm before scoping a build:
- Which bill-of-materials structure fits each product, a single-level bill for a simple assembly or a multilevel bill that nests sub-assemblies for a more complex one.
- Which workstations should run Shop Floor alone, since the documentation for Odoo 18.0 describes installing it in a workstation's browser so that screen cannot open other Odoo applications.
- Which work centres need shop-floor tablets, since the documentation describes assigning specific work centres to each workstation the first time Shop Floor opens there.
- Which maintenance workflow fits each piece of equipment, a scheduled preventive request on a calendar or a corrective request raised when something breaks.
What goes wrong in a manufacturing Odoo rollout?
- Rolling out every line at once. Skipping the pilot line means the first real mistake is made at full scale instead of on one line.
- Treating quality checkpoints as an afterthought. Adding checks after go-live, once a defect has already reached a customer, costs more than defining them during blueprinting.
- No rehearsed rollback. A plant that has never tested going back to its legacy process discovers the rollback does not actually work during a live cutover.
- Routing and bill-of-materials data not cleaned before migration. A routing step mapped to the wrong work centre or a bill of materials missing a component throws off costing and yield figures the moment the pilot line goes live.
Which questions should you ask an Odoo implementation partner?
- Which parts of this rollout are standard configuration, and which require a custom module for a workflow Odoo's modules do not already model?
- How is the pilot line chosen, and what does the go or no-go review check before the next wave is authorised?
- How is scope fixed? Most Netbase projects are agreed as fixed-scope contracts after discovery, with milestone-based arrangements also available.
- What does the delivery plan look like? Netbase's own delivery lifecycle runs from discovery and strategic alignment through team assembly and architecture planning, agile execution with outcome-based milestones, modular components and training and rollout to ongoing support; for this rollout, discovery closes once the pilot line's bills of materials, routings and quality checkpoints are signed off.
How this guide is sourced and where it stops
The rollout sequence and the manufacturing-operation table are editorial, built from how a manufacturing Odoo implementation is run in practice; Netbase's evidence covers Odoo consultancy and customisation for manufacturers with a local Odoo implementation partner, and the five-line electronics scenario is illustrative, not a delivered project.
Common questions
Yes, that is the pilot-line pattern this guide recommends: one line runs fully on Odoo while the rest continue as before, until the go or no-go review clears the next wave.
No. Each product keeps its own bill of materials and routing; what should be shared across lines is the configuration pattern, the work-centre naming, the quality checkpoint types and the maintenance workflow, so the second line is a repeat of a proven setup rather than a fresh design.
Move what the new process needs: current bills of materials, open purchase orders and active equipment records usually move, while closed historical work orders can stay in an archive.
Yes, and it usually should. Each wave's go or no-go review is a deliberate checkpoint, not a formality, and a plant can hold at any wave until the issues the pilot or a prior wave surfaced are resolved.
Yes. Operators need to run the shop-floor tablets, log quality checks and raise maintenance requests in Odoo before the pilot week starts, or the yield and quality figures the go or no-go review relies on will reflect unfamiliarity with the screen rather than the process.
The field service and inspection apps solution covers dispatch, inspection checklists and technician records for work that happens off the production line rather than at a fixed work centre.
Plan your line-by-line Odoo rollout
Bring your line count, current routing and maintenance records, and the quality checkpoints you already run to a scoping session, and a person will map them onto the sequence above. Manufacturing and field service covers the wider sector context, and legacy application modernization is the route when an existing plant system needs to be assessed before the rollout starts.
OutsourcingVN is Netbase's own outsourcing-services platform. Submit a project with your line count and current systems, and a person will reply with a sequence like the one above.
Work behind this guide
Working with a local Odoo implementation partner, Netbase has consulted on and customised Odoo in Vietnam for a range of organisations, none of which is named.
Keep ReadingRelated services and solutions
Legacy application modernization, one bounded capability at a time
The code is assessed first, then one bounded capability moves at a time, with a way back.
Learn More