Odoo 19 Enterprise for a cookware and pressure-cooker manufacturer
Two earlier ERPs were bought, started and abandoned. The third stuck, because the master data was cleaned before go-live and the team was trained to run the system themselves.
Pressure cookers & houseware
Distribution, modern trade & D2C
India
Project snapshot
Odoo modules in scope
What made the difference
- Master data cleaned in a test environment for a full month before the live database was opened
- The spreadsheet kept as an input, not an enemy: counts and price lists are prepared in a sheet and imported by the client’s own staff
- Warehouse mapped to the building: units, rooms and rack-level locations, raw material, work in progress and dispatch, with putaway assigning racks on receipt
- Mobile barcode operations for receipt, transfer, picking and delivery
- Packaging configured to how the plant packs, in packs of 6, 8 and 12 with master cartons, and a GS1-aligned label set
- Bills of material with by-products, scrap and subcontracted work tracked as stock, not gaps
- A helpdesk with an SLA clock, and the client trained to maintain their own master data
The starting position
This manufacturer makes pressure cookers and houseware, ships to distributors, dealers and modern trade, and sells online. Stock sits across several units and rooms, down to rack level, plus raw material above the shop floor and work in progress moving between operations. None of that was in a system. It was in Google Sheets.
The sheets could not say where stock actually was, could not survive multiple units and an inter-company entity, could not hold a clean item master free of duplicates and missing HSN codes, and could not connect stock to sales, manufacturing or accounts. The team knew all of this. That was not the problem.
The real problem: two ERPs already dropped
Before this engagement, the company had gone down the ERP path twice. Both times the software was bought. Both times it was abandoned. The stated reason each time was that the system was not user friendly. Underneath sat something more specific.
No bridge from the sheets
The systems demanded the team change how they worked on day one, with no path from the spreadsheets they trusted.
Dirty data loaded early
Data went in before it was clean, so the system produced numbers that did not match the floor. Catch an ERP being wrong twice and the team goes back to the sheet and never leaves.
No internal owner
Nobody on the client side was trained to maintain the system, so every change needed a vendor call, and changes stopped being made.
Nowhere for problems to go
Issues scattered across chat and died there. A team that has abandoned two ERPs is waiting for the third to fail.
What Ochre did differently
Data workstream
The single biggest decision, and it cost time on purpose. The whole of one month ran on test data. Ochre defined one consolidated master sheet with mandatory fields, hunted duplicates using the system’s own export as the check, and agreed a category taxonomy so reporting rolls up without manual grouping. Only then did anything go live, so the team’s first experience of the system was numbers that matched the building.
Adoption
Physical counts are done the way the warehouse already does them, then imported against the full location path. Price lists and master updates are prepared in a sheet and imported by the client’s staff. The spreadsheet became the loading dock, not the system of record, which is a much smaller ask than stop using sheets.
Inventory · Barcode
Locations mirror physical reality: units, rooms and racks, raw material, work in progress by operation, finished goods and dispatch. Putaway assigns racks on receipt, and barcode operations run on mobile: scan the location, scan the product, confirm the move. The operator does what he already does physically, and the system records it.
Inventory
Packaging was configured to how the plant packs, in packs of 6, 8 and 12 with master carton weights and dimensions. Item barcode labels, shelf labels and master carton labels were built to size, with item coding aligned to GS1 so it holds up with modern trade and marketplaces.
Manufacturing · Sales
Bills of material consume raw material through the manufacturing order rather than informal issue and later reconciliation, with by-products, scrap and subcontracted body-circle work all tracked as stock. Availability is visible at quotation, and the first full review surfaced 51 pending deliveries no spreadsheet had flagged.
Helpdesk · Training
Dedicated sessions on master creation, imports and price lists, plus a helpdesk with an SLA clock so complaints and system issues stopped moving over chat with no record. A client who cannot maintain their own master data has an ERP that dies in eighteen months.
The result
The live database opened in August 2026, with warehouse, purchase, sales and accounts transacting on it. Manufacturing setup and the online storefront connection are in the current hardening window, with training running so the client’s team can operate both without standing support. The measure that matters is not the go-live date, it is whether the sheets come back. Monthly physical counts, a master data procedure owned by the client’s own staff, and a ticket channel that closes issues are the three things holding that line.
On your second or third ERP attempt?
The last two failures were probably not the software. They were dirty data loaded too early and no internal owner. Ochre cleans the data first, keeps your spreadsheet as an input, and trains your team to run it.
