Project
The job, its phases and tasks, and the analytic account every cost tags to. This is where engineer-to-order profitability actually lives.
Engineering companies sell a promise and then discover what it cost. Design hours, bought-out items, fabrication and site work all land in different places, and project margin is a number assembled after the fact.
Odoo connects projects, BOMs, timesheets, procurement and quality so engineering cost accumulates against the job while it is still running.
Businesses running Odoo with OdooBots
Odoo ERP for engineering connects engineer-to-order projects with the BOMs, labour and procurement that deliver them. Projects carry the job and its analytic account, PLM controls drawing and BOM revisions, timesheets post design and fabrication hours to the project, purchase handles bought-out items against it, and quality gates the operations that need signing off.
In engineer-to-order work the hardest question is not technical. It is whether a job is a project, a manufacturing order, or both — and the answer determines where cost accumulates and what your margin report can tell you.
Odoo connects the applications an engineering business runs on: Project for the job and its cost structure, PLM for drawing and BOM revisions, Manufacturing for fabrication and assembly, Timesheets for design and shop hours, Purchase for bought-out items, and Quality for sign-off.
The job, its phases and tasks, and the analytic account every cost tags to. This is where engineer-to-order profitability actually lives.
Drawing and BOM revision control through engineering change orders with named approvers and full version history.
Fabrication and assembly against the job BOM, with work orders and work centers reflecting the real shop sequence.
Design, drawing and shop hours booked to project tasks and approved, turning engineering effort into a cost figure.
Bought-out items and subcontracted operations raised against the project, with vendor lead times that drive the schedule.
Inspection and test points on fabrication operations, with measurement capture and sign-off before despatch.
A won order opens a project with its analytic account. Design hours, bought-out purchases and manufacturing costs all tag to it, so project profitability is a live report rather than a reconstruction at closure.
These are the configuration decisions that are cheap to make now and structural to change later. We walk through each one before a single record is migrated.
For each job type, where cost accumulates. Running both without deciding which is primary is how engineering businesses end up with two different margin numbers.
Per job, per phase, or per cost head. Everything downstream tags to this, and changing it later means re-posting history.
Purchased to the project or into stock then issued. The first is simpler and the second gives real consumption; the choice has accounting consequences.
Per task or per project. Fine granularity gives better costing and is abandoned by engineers under deadline. We set what your team will sustain.
When a drawing changes mid-job, whether open manufacturing orders follow it. This needs deciding before it happens, not during.
What carries from the won quotation into the project: BOM, budget, milestones. Re-keying here is where estimates and actuals stop being comparable.
Advance, progress and retention terms configured deliberately rather than invoiced manually each time.
The right configuration depends on how your business actually operates, not on your sector label. Two companies with the same description on paper often need different warehouse steps, different approval chains and different reports.
We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a bolt-on, or tell you Odoo is the wrong tool.
Odoo does not read native CAD files or pull BOMs from a PDM system without an integration. It can be built, and it is development.
Odoo Planning schedules resources; dependency networks with float analysis belong in Primavera or MS Project.
Rule-driven configurable products that generate their own BOM and routing need custom development beyond Odoo variants.
Detailed estimating with labour and material rate libraries usually stays in a specialist tool feeding Odoo.
EVM metrics such as CPI and SPI are not native and need custom reporting on top of the analytic data.
Commissioning, punch lists and client sign-off at site need Field Service plus configuration, and sometimes more.
Implementing Odoo for engineering needs more than installing the applications. Your ERP should reflect how your operations actually run.
Understand your job types, where design ends and fabrication begins, how bought-out items are handled, your billing milestones and how hours are recorded today.
Map quotation to project to despatch onto Odoo, and settle the project-versus-manufacturing-order question before anything is configured.
Configure the applications above around your requirements rather than installing them at their defaults.
Prepare and migrate masters, open items and opening balances. Data cleaning is scoped explicitly, because it is usually the largest single task. See Odoo migration.
Connect the systems you are keeping and build only what configuration genuinely cannot reach. See integration and customization.
Your own team runs real transactions in a test database before go-live. Role-based training for the people who key them daily. See Odoo training.
Cutover planning, opening balance freeze, hypercare in the first weeks, then ongoing support and AMC.
We do not publish one implementation price, because the same application list costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.
Engineer-to-order costing comes down to one decision made in week one: whether the job is a project or a manufacturing order. We settle that in writing before configuring anything, which is why our engineering clients get one margin number rather than two.
Product capabilities stated on this page are documented by Odoo. The configuration advice and limitations come from our own implementations.
Tell us whether your jobs are designed before they are made, and how you bill. Those two answers decide the configuration, and the diagnosis call is free.