Going live, switching the manufacturing operation onto the new system, is a defined and significant moment. It should be reached deliberately, when the project is genuinely ready. This piece is a go-live checklist for an Odoo manufacturing implementation.
Why a go-live checklist
Go-live is the point of commitment: the moment the manufacturer starts genuinely running its operation on Odoo. Reaching it before the project is ready means going live on a system that is not right, which causes real disruption to production. A go-live checklist exists to make the decision to go live deliberate: a set of things to confirm, so that the manufacturer goes live because it is genuinely ready, not because a date arrived.
Confirm the data is right
The first and most important thing to confirm is the data. The products, the bills of materials, the routings, the work centers, the stock, the lead times, all the data the manufacturing system runs on, should be in Odoo, accurate, and verified. Bad data is one of the most common reasons a manufacturing implementation disappoints after go-live. Before going live, the manufacturer should genuinely confirm that the data is accurate, not assume it. The data being right is the foundation of everything else.
Confirm the system has been tested
Before go-live, the configured system should have been genuinely tested against the manufacturer's real processes: the actual ways the manufacturer produces, run through the system, including the awkward cases, not a clean script. Testing is where problems are found while they are still cheap to fix. The checklist item is that testing has genuinely been done and the problems it found have been addressed, so the manufacturer is not discovering them after go-live.
Confirm the people are ready
A manufacturing system is run by people, on the floor, in planning, in the office, and they have to be ready to use it from day one. Before go-live, the manufacturer should confirm that the people who will use Odoo have been genuinely prepared, trained, comfortable with how they will do their work in the system. A well-built system that the team is not ready to use will still falter at go-live. People readiness is a real checklist item.
Confirm the go-live plan
Go-live itself should be planned, not improvised. The manufacturer should confirm it has a clear plan for the cut-over: when it happens, how the switch is made, how the period immediately after is handled. And, importantly, it should confirm that support is in place for the period right after go-live, because that period, when the manufacturer is adjusting to the new system, is when support is most needed. A go-live plan, and support arranged for after, are checklist items.
Confirm scope and phasing
The manufacturer should confirm that what it is going live with is what it planned, and is a sensible scope. If the implementation was sensibly phased, the go-live is of the phase that was planned, a sound core, not an attempt to switch on everything at once. Confirming that the go-live scope is sensible, and that the manufacturer is not trying to do too much at once, is part of the checklist.
The honest principle: ready, not just due
The principle behind the whole checklist is this: go live because the project is genuinely ready, not because a date has come. It is far better to delay a go-live than to go live on a system whose data is not right, that has not been tested, or whose people are not prepared, because going live unready disrupts production and damages confidence in the system. The checklist is a way of making the go-live decision honestly: if the items are genuinely confirmed, go live; if they are not, the honest answer is to address them first.
The takeaway
A go-live checklist for an Odoo manufacturing implementation makes the decision to go live deliberate. Confirm the data is accurate and verified, confirm the system has been genuinely tested against real processes, confirm the people are prepared, confirm there is a go-live plan with support arranged for after, and confirm the go-live scope is sensible and not too much at once. The principle is to go live because the project is genuinely ready, not because a date arrived. For how we approach Odoo manufacturing implementations, see our ERP practice.