Odoo ERP Implementation Guide: Step-by-Step Process for Manufacturers
A structured deployment, not a software installation.
An Odoo ERP implementation for a mid-market manufacturer changes a company from its current operational state to running production, inventory, purchasing, accounting and warehouse operations in Odoo. Six phases, each with a sign-off gate before the next begins.
Book a Discovery CallAs featured in
What an Odoo ERP Implementation Involves
The implementation covers configuration (setting Odoo up to match your operations), data migration (moving the item master, BOMs, open orders, lot history and financial balances out of the legacy system), integration development (connecting Odoo to external systems that must stay, such as MES, EDI, PLM and compliance reporting), custom module development, user training and go-live support.
For the broader picture of what the platform includes, see Odoo ERP modules and the Odoo Community vs Enterprise decision.
What the implementation does not cover
“Odoo out of the box” is not what manufacturers go live on
Every implementation involves configuration, because Odoo's defaults are not set up for manufacturing. It needs BOM structures, routing steps, work centers, lot tracking rules, costing methods and warehouse location configuration before production can run.
Custom modules are separate from implementation configuration
FSMA 204 KDE capture, METRC integration, AS9100 serial genealogy and AI demand forecasting are custom development engagements, scoped apart from the base implementation.
Training is part of the implementation but not a substitute for it
Training on a poorly configured system teaches people to use a broken process correctly. Configuration and data migration must be complete before training begins.
What determines implementation complexity
- Module scope: how many modules go live (Manufacturing, Inventory, Purchasing, Accounting, Quality, WMS Barcode, PLM, Maintenance).
- Data volume: active items, BOMs, open production orders, lot records and historical transactions to migrate.
- Integration count: the number of external systems connected at go-live.
- Compliance requirements: FSMA 204, pharmaceutical Part 11 and GMP, AS9100, and cannabis METRC each add custom module work.
- User count and training complexity: how many departments go live together versus in phases.
Odoo Implementation Phases: Step by Step
GrayCyan's Odoo implementation for mid-market manufacturers follows a structured six-phase methodology. Each phase has defined deliverables and a gate before the next begins. The project does not advance to configuration until discovery is complete, and Odoo does not go live until user acceptance testing and the go-live checklist are signed off.
A general Odoo implementation methodology guide describes these phases in the abstract. What follows is what each phase looks like on a manufacturing floor.
Phase 1: Discovery and Requirements
Weeks 1 to 3
The objective is to document current operations, define Odoo scope, identify data migration requirements, surface integration needs and confirm compliance module scope before a line of configuration is written.
- What costing method is in use? Standard cost, average cost, or FIFO/FEFO actual cost. This determines how Odoo Inventory valuation is configured and how production order variance is calculated.
- How many BOM levels exist? Single-level discrete, multi-level assemblies, or formula-based process manufacturing with yield factors.
- What lot and serial tracking is required? Which items need lot tracking, which need serial tracking, and which are exempt. This drives both configuration and migration scope.
- What compliance documentation is required? FSMA 204, 21 CFR Part 11, AS9100, METRC and ISO 9001 each add custom module scope.
- What external systems must remain at go-live? MES, EDI, PLM, e-commerce, 3PL WMS. Each integration is scoped here.
- What historical data must migrate? Open production orders, WIP valuation, lot genealogy back to what date, and customer and vendor balance history.
A requirements document mapping operations to the Odoo implementation methodology, a data migration scope document (what migrates, from which system, at what date), an integration scope list, a compliance module scope decision, a go-live module sequence, and a project timeline with resource plan. Discovery also includes a data audit of the legacy system, so remediation needs surface before the timeline is committed.
Phase 2: Odoo Configuration
Weeks 3 to 8
The objective is to configure Odoo to match the operations documented in discovery. No custom code is written in this phase, only Odoo's built-in configuration options.
- Manufacturing: work centers, routing templates, single-level and multi-level BOM structures, scrap and by-product handling, and production scheduling parameters.
- Inventory: warehouse structure (locations, zones and bin positions), lot and serial tracking per item, FEFO rules per product category, reorder point rules, and the costing method. Set the costing method once; it cannot be changed after transactions exist.
- Quality: quality control points by operation and product category, quality alert routing, and CAPA workflow.
- WMS Barcode: receiving operations, putaway rules per zone, directed picking, and pack-and-ship confirmation.
- Accounting: chart of accounts mapped from legacy, manufacturing cost accounts (raw materials, WIP, finished goods, COGS, variance), and intercompany configuration for multi-entity manufacturers.
- Purchasing: vendor price lists, lead times, purchase order approval thresholds, and three-way matching.
Configuration review gate. Before migration begins, GrayCyan conducts a configuration review with your project team. Each configured workflow is walked through in Odoo, from receiving a purchase order through production to shipment confirmation. Issues found here are configuration changes, not custom development. The gate prevents loading data into a misconfigured system.
Phase 3: Custom Development
Weeks 4 to 12, parallel with Phase 2
The objective is to create the compliance modules, integration connectors and AI middleware identified in discovery. Development runs in parallel with configuration rather than after it, so custom modules are ready for testing when configuration finishes.
- Compliance modules: FSMA 204 KDE capture at CTE scan events (food and beverage), GMP batch record assembly from production order data and 21 CFR Part 11 electronic signatures (pharmaceutical), METRC API integration (cannabis operators), and AS9100 serial genealogy linking.
- Integration connectors: EDI transaction mapping (850, 855, 856, 810), MES machine data to Odoo work orders, PLM BOM sync to Odoo BOMs, e-commerce order import, and 3PL WMS inventory sync.
- AI middleware: machine-learning demand forecasting on sales order history, anomaly detection on production yield and inventory movements, agentic replenishment sequencing, and a batch record assembly agent.
- Custom reports: Certificate of Analysis from lot quality data, production batch record template, landed cost allocation report, and FSMA 204 KDE structured export.
All custom modules are delivered as Odoo add-ons with full Python source code and documentation. No proprietary module requires GrayCyan to maintain it, because you own the source.
Phase 4: Data Migration
Weeks 8 to 12
The objective is to migrate validated data from the legacy system into Odoo. Data migration is the phase manufacturers most often underestimate, and the most common cause of go-live delays.
- Item master: all active items with Odoo product attributes (UOM, tracking type, costing method, purchase and sales settings, and manufacturing lead times).
- Bills of material: all active BOMs, including routing steps, work center assignments, operation times and scrap factors. Multi-level BOMs are validated for correct parent-child structure.
- Open purchase and sales orders: all confirmed orders that will not complete before go-live, migrated with original quantities, confirmed prices and expected delivery dates.
- Open production orders: most manufacturers choose to complete open production orders before go-live rather than migrate current WIP, and that is our recommendation for first-time Odoo deployments.
- Lot records and genealogy: active lot numbers with expiration dates, on-hand quantities and, for regulated manufacturers, quality status. Historical genealogy is migrated back to the agreed cutoff date.
- Financial balances: general ledger opening balances as of go-live, accounts receivable and payable aging, and inventory valuation by location.
Validation. GrayCyan runs three migration cycles before go-live: a test migration into a staging Odoo instance, a parallel run in which the legacy system and Odoo operate side by side for two weeks, and the final cutover migration on the go-live weekend. Each cycle ends with a validation checklist covering item count, BOM count, open order count, lot count, and financial balance reconciliation against the legacy system.
Phase 5: User Acceptance Testing
Weeks 10 to 14
The objective is to confirm that Odoo, configured and loaded with real data, works for your actual workflows before users are trained and before go-live is confirmed.
- End-to-end production run: receive raw materials, issue a production order, complete production, receive finished goods and ship to the customer. Validate lot tracking, FEFO selection, COGS posting and inventory balance at every step.
- Quality control: test control points at receiving, production and shipping. Fail a check on purpose. Validate quality alert generation, lot hold and CAPA creation, and confirm the COA generates from lot data.
- Compliance scenario: for FSMA 204, complete a receiving scan and verify KDE capture in the FDA-required format. For pharmaceuticals, complete a production batch and verify GMP batch record assembly. For cannabis, complete a transfer and verify METRC manifest creation.
- Custom module scenarios: test each module against the acceptance criteria written in discovery. METRC API calls are logged and verified. EDI transactions are generated and validated against trading partner specifications.
- Financial posting: confirm that every inventory movement creates the correct GL entries. Receiving posts to raw materials at the right value, production completion posts COGS correctly, and the WIP balance clears when production completes.
UAT gate. Go-live is not confirmed until your operations lead, controller and IT lead sign off. Issues found in UAT are fixed in staging and re-tested before the go-live date is set.
Phase 6: Go-Live and Stabilization
Weeks 14 to 18
The objective is to execute the production cutover and stabilize operations over the first 30 days.
- Friday close: the final transaction is posted in the legacy system, which is then locked to new transactions. The final data extract is taken for cutover.
- Saturday: the cutover migration runs. Financial balances, open orders, inventory balances and lot records are loaded into the Odoo production instance, and the migration validation checklist is completed.
- Sunday: all integrations are verified and tested in production, compliance modules are verified, and GrayCyan and your project lead confirm go-live readiness.
- Monday: Odoo goes live. GrayCyan is on site or on call for the first week, supporting the first receipts, production orders and shipments.
Stabilization, days 1 to 30. Users are live, but volume and complexity rise progressively. During this period we provide same-day response to operational issues, daily check-in calls with the operations lead and controller, and a priority queue for configuration adjustments that surface in live operations.
For how custom work in Phase 3 is scoped, see Odoo customization and Odoo ERP development. For the AI middleware, see manufacturing AI solutions.
Odoo Implementation Timeline: By Module Scope and Company Size
Odoo implementation timelines differ by module scope, company size, integration count and compliance requirements. The ranges below come from GrayCyan's US mid-market manufacturing deployments: 50 to 500 employee manufacturers, 5 to 15 Odoo modules, and 1 to 4 external integrations. Pricing is a separate question, covered in the Odoo implementation cost guide.
Basic
14 to 18 weeks
Manufacturing, Inventory, Purchasing and Accounting, no compliance modules, no integrations.
Fits manufacturers with fewer than 500 active items, standard BOM structures, and no legacy WIP to migrate.
Standard
18 to 24 weeks
The above plus Odoo Quality, WMS Barcode, and one to two integrations.
Adds quality control configuration, scan-based warehouse setup, and integration development.
Complex
24 to 36 weeks
The above plus compliance modules, three or more integrations, and AI middleware.
Regulated manufacturers with FSMA 204, pharmaceutical or cannabis module development alongside a full integration set and AI layer.
The average Odoo ERP implementation timeline for a mid-market manufacturer therefore runs roughly 18 to 24 weeks, with regulated operations at the longer end.
What extends timelines, in order of frequency
- Data quality problems in the legacy system: items with missing attributes, BOMs with incorrect structures, and lot records without expiration dates. Discovery uncovers these, and remediation adds time before migration can proceed.
- Scope additions after discovery closes: adding modules or integrations once Phase 2 has begun extends both development and testing.
- Legacy extraction limits: manufacturers on Access databases, spreadsheet-based systems, or heavily customized legacy ERPs face longer extraction phases.
- Compliance module complexity: state-specific METRC configuration, Part 11 validation scope, and FSMA 204 KDE structured format requirements.
- User availability for UAT: testing needs operations and finance staff for two to three weeks of structured work. Teams that cannot dedicate that time consistently extend the phase.
Odoo Go-Live Checklist: By Department
GrayCyan's go-live checklist gates the production cutover. Odoo does not go live until every item is checked off by the responsible team. The checklist is signed by the operations lead, controller, warehouse manager and IT lead before the go-live weekend begins.
- All active items loaded with correct UOM, tracking type and costing method; count verified against the legacy system
- All active BOMs loaded and validated: component quantities, yield factors, routing steps and work center assignments verified by the production manager
- Work centers configured by capacity, with OEE targets and shift calendars confirmed
- Open production orders migrated, or confirmed closed in the legacy system before cutover
- Replenishment rules set for all stocked raw materials; reorder points confirmed by the production planner
- Custom compliance modules tested in production: FSMA 204 KDE capture verified, GMP batch record assembly confirmed, METRC API calls tested against the state system
- Shop floor operators trained on the Odoo work order interface, with sign-off per operator
- Physical inventory count completed and reconciled, so Odoo on-hand balances match the count at the go-live date
- Warehouse location structure configured, with all zones and bin positions created and putaway rules verified
- Lot records loaded for all active lot-tracked inventory, with lot numbers, quantities, expiration dates and quality status confirmed
- Odoo WMS Barcode tested with production hardware, with scanners connected and receiving and picking confirmed
- Cycle count schedule configured, with the first count window set
- Warehouse team trained on the barcode interface for receiving, putaway, picking and pack-and-ship
- Chart of accounts loaded and mapped from legacy, with controller approval on account structure
- Opening GL balances loaded as of the go-live date and reconciled to the legacy trial balance
- Accounts receivable open invoice aging migrated, with balance per invoice confirmed
- Accounts payable open bill aging migrated, with balance per bill confirmed
- Inventory valuation opening balance matches the legacy system as of the go-live date
- Costing method confirmed and locked (standard, average, or FIFO/FEFO actual). It cannot change after transactions begin
- Tax configuration verified for sales and purchase tax rates, and cannabis excise tax if applicable
- First payroll cycle confirmed, with Odoo Payroll or the external payroll integration tested
- All integrations tested in production, with EDI transactions confirmed with trading partners, MES data flowing to work orders, and e-commerce orders importing correctly
- User access reviewed for correct roles for all users, with no test accounts holding production access
- Backup and recovery confirmed, with backup schedule verified and recovery procedure tested
- Custom module source code delivered to your IT team in version control
- Odoo.sh or on-premises server configuration reviewed, with SSL, email and scheduled actions confirmed
Common Odoo Implementation Mistakes Manufacturers Make
Most Odoo implementation errors in manufacturing are not technology failures. They are project management failures, and the same mistakes appear again and again. GrayCyan has worked on several mid-implementation rescues for manufacturers who started with a different partner or attempted self-implementation.
These are the five Odoo ERP implementation best practices that the mistakes violate.
Starting configuration before discovery is complete
Configuring Odoo on assumptions about your operations produces a system that must be reconfigured when real requirements surface in UAT. Discovery must be signed off before configuration begins, not run in parallel with it.
Setting the wrong costing method
The method cannot be changed once inventory transactions exist. Manufacturers who pick standard cost without understanding variance accounting, or average cost without understanding how it behaves for lot-tracked items, spend their first quarter reconciling unexpected valuations.
Underestimating data migration effort
Item records with missing attributes, BOMs carrying uncorrected historical errors, and lot records without expiration dates must all be fixed before they can load. Teams that budget two weeks and discover eight weeks of remediation are the most common source of go-live delays.
Training before configuration is stable
Training on a system still being configured teaches operators the wrong workflows. Train on the final, UAT-validated system.
Going live on all modules simultaneously
For a broad module scope, a phased go-live (manufacturing and inventory first, accounting second, quality and WMS Barcode third) reduces risk at every stage. Seven modules going live at once multiplies the support load and the chance of cross-module issues surfacing together.
Frequently Asked Questions: Odoo ERP Implementation
Planning an Odoo ERP Implementation?
Tell us your manufacturing type, module scope, compliance requirements (FSMA 204, pharmaceutical, AS9100, cannabis), your current ERP or legacy system, and your target go-live window.
GrayCyan will give you an honest implementation timeline and scope estimate, with no offshore delivery and no discovery surprises. If you are not sure your data and processes are ready, start with an AI Readiness Assessment.
See Odoo implementation services or start with the AI Readiness Assessment →


Client


Partner
Member









