The shop floor does not wait for a clean demo.
What does industry-depth work actually mean?
Industry-depth manufacturing work means the system matches how the plant runs: multi-level BoMs, routing, quality, and the banking or field loops beside production. It is not a module checklist sold as a vertical.
Most manufacturing ERP conversations arrive as a feature list. The hard part is elsewhere. Child BoMs disagree with cost. Quality sits in a spreadsheet. Field loyalty or banking loops touch inventory the ERP does not see.
We build and sustain manufacturing estates on Odoo. When the path is delivery, we route to Odoo Implementation, Odoo Migration, or Integration Engineering. When the live plant is already failing users, start at Rescue & Stabilization.
Does any of this sound familiar?
BoMs and costing disagree, and finance trusts a parallel spreadsheet.
Routing and quality live outside the ERP, so the shop floor and the books never match.
A version upgrade keeps dying on custom modules nobody owns.
Banking or field-loyalty loops touch stock the warehouse screen does not show.
Multi-company manufacturing shares masters that were never designed to share.
You are comparing implementation quotes without a risk register for cutover on a live plant.
If you recognised three of these, you do not need a prettier MRP demo. You need an estate that can run while production continues.
What this looked like when it had to hold.
Cemseal · multi-company manufacturing that stays live
Construction-chemicals manufacturing across companies and states on Odoo: manufacturing orders, child-BOM cost visibility, ICICI banking, and a field loyalty loop (MAAN) that has to reconcile. The plant did not pause for the version path.
Cemseal case study → ICICI Banking →What an industry engagement covers, and what it does not.
In scope
- BoM, routing, quality, and inventory design that match how the plant runs.
- Multi-company manufacturing masters, access, and reporting leadership can trust.
- Integrations that touch money or stock, with reconciliation in scope.
- A written path for migrate vs rebuild vs stabilise-first when the estate is ageing.
- Post-go-live engineering so month-end and the shop floor do not drift apart.
Not in scope
The interesting engineering starts when the order is already in progress.
We implement manufacturing systems for plants that cannot freeze the floor for a clean cutover. Parallel run, reconciliation, and the integrations beside production are the job. How we work is on How we work. Engagement shapes are on Engagement models.
How an industry engagement runs.
-
01
Situation call
What breaks in operations, what cannot pause, and whether something is already failing users.
-
02
Estate map
Name the processes, systems, and conflict cases that define this vertical.
-
03
Options on paper
Implement, migrate, integrate, product, process-only, or rescue first. Each option carries what you give up.
-
04
Recommended path
One primary recommendation and the conditions under which we would change it.
-
05
Hand-off into Services or stop
You keep the write-up. Delivery lands on a named Service, Solution, or Product page — not a vague phase two.
Questions we get first.
Do you only implement Odoo for manufacturing?
Odoo is where most of our manufacturing depth sits. The same discipline applies when banking, field apps, or multi-company reporting sit around the plant.
Is this the same as Odoo Implementation?
No. Implementation is delivery. This page is manufacturing proof and vertical framing. When the path is build, go to Odoo Implementation.
Can you migrate a live plant?
Yes, with a written risk register. See Odoo Migration and ERP Modernization.
What if the system is already broken?
Start at Rescue & Stabilization.
What does this cost?
Scoped after the situation call, in writing, before work starts.
Get a manufacturing path that survives production.
Tell us what the plant cannot pause and which numbers disagree. We will say implement, migrate, integrate, or rescue first.