/industries
Odoo for manufacturing
Know what every product really costs to make.
- 1,300+ Active SKUs on the largest build
- 3 Export markets served
/where-it-breaks
Where it breaks, before anyone mentions software.
-
01
Your bill of materials is a catalogue, not a BOM.
Prints and fabric arrive from separate vendors, but nothing in the system connects either one to what a finished product really costs. A paper catalogue is fine for browsing and no use for costing. Ask what a product costs and the answer is to find the person who remembers. When a batch goes wrong, you cannot trace it back.
-
02
Work in progress lives on paper.
On a floor of 600+ people, cutting, printing, assembly and quality are all tracked on hard copy. To learn what is in progress right now, someone has to walk the floor and count.
-
03
Without a system of record, there are no KPIs you can trust.
Management cannot calculate a figure it believes. Production problems surface late, if they surface at all. Finance has no live view of what purchasing and production are doing.
-
04
Cost, quality and finance tell three different stories.
Finance is not linked to purchasing. Quality checks happen, but a failed batch has nowhere defined to go. The three functions that should describe one product describe it three different ways.
/configuration-choices
Five decisions we make early
- BOMs split at component level. Prints and fabric are tracked separately from intake, because that is how your vendors and your floor already work. See Manufacturing.
- A quality-fail location in the routing. A rejected batch has a defined place to go instead of disappearing into general stock. See Inventory and warehouse.
- Standard costing set before go-live. Day-one production carries a real cost, not an estimate. See Accounting and finance.
- Serial number tracking from raw material to shipped unit. When something goes wrong, you can follow it back to where it started.
- Quality results trigger the next manufacturing step. A pass does not sit waiting for someone to notice it.
/what-we-will-not-do
And five we argue against
- We will not force a wholesale data migration. Only finance data moved across, in one month. The rest stayed as historical record, so go-live was quicker and the new system started clean.
- We will not automate export paperwork before the basics work. Shipping documents come first, and full automation waits until they are solid.
- We will not impose a textbook BOM on a floor that thinks in prints and fabric. We configure Odoo to match how your work really happens, so your team recognises it on day one.
- We will not customise everywhere it is tempting. We built one automation, moving the order on after a quality pass, because that was the real bottleneck. Every line of custom code is a maintenance cost.
- We will not add multi-company complexity to a single-entity, single-site business. Multi-currency, yes. Multiple companies, no.
/next
Tell us what you are running today.
Twenty minutes, no slides. We will tell you straight if Odoo is not the answer.