An Odoo manufacturing rollout starts with a question the production team can answer: can we follow one order from approved materials to finished stock, including what happens when the plan changes? A demonstration with perfect data is useful, but it does not establish that your own process is ready.
Use this checklist to prepare a small, representative pilot. The product references below use Odoo 19 documentation; confirm the installed version, applications and permissions before applying a configuration.
1. Choose one production flow to prove
Select a product that reflects everyday work: more than one component, a meaningful assembly step and a realistic exception. Avoid choosing either the easiest item in the catalogue or the most unusual engineered order. Write down where demand begins, who releases production, who records consumption and who accepts the finished goods.
Odoo Manufacturing covers manufacturing orders, work orders and several production workflows. Its manufacturing documentation separates basic setup from advanced features such as subcontracting and multilevel bills of materials. Treat those as scope decisions. You do not need every feature in the first pilot.
Set a clear boundary around the pilot: one product family, one production area and named users. Record which steps remain outside the system during testing so a successful demonstration is not mistaken for a complete business rollout.
2. Prepare the records production will depend on
A bill of materials (BoM) identifies components and their quantities. Odoo can also associate operations with a BoM; using operations requires the Work Orders setting. Check the official BoM setup guide before configuring these records.
| Decision | Prepare before configuration | Acceptance check |
|---|---|---|
| Product identity | One agreed code for every finished item and component | Store and production teams choose the same item without guessing |
| Units and quantities | Approved quantities per output unit or batch | A sample order expands to the expected component demand |
| Operations | Sequence, instructions and responsible work area | An operator can complete the pilot using the agreed instructions |
| Traceability | Which items need lot or serial identification, and why | The team can trace a sample finished item to the required records |
| Changes | A named owner for approving recipe or component changes | No one silently edits the production specification during the trial |
Odoo supports lot or serial tracking for manufactured products when configured on the product. The manufacturing product guide explains how this relates to production records. Agree the business requirement first: tracking every low-value component individually can create work without answering a useful operational question.
3. Make the physical handoffs explicit
Walk the route from receiving to storage, production and finished goods. Write the same names on the process map and the test data. If materials can be waiting for inspection, being assembled or ready for dispatch, explain how staff distinguish those states.
Odoo distinguishes warehouses from locations within them, and uses location types for different stock movements. See its inventory structure guidance. Your implementation decisions should reflect who controls each handoff; creating a location for every desk rarely solves an unclear responsibility.
Decide when staff will record work. If operators finish on paper and someone enters the data later, test that delay explicitly. A live screen can only reflect recorded transactions, so supervisors need to understand when information is current.
4. Run a worked order with an exception
Illustrative example, not a customer case: a fictional workshop assembles 20 desk lamps. Each lamp requires one base, one shade and two fasteners. The planned demand is therefore 20 bases, 20 shades and 40 fasteners. The team first checks that the order produces these quantities.
During the trial, one shade is damaged before assembly. The tester records what happened using the agreed process, identifies who can approve replacement material, and checks that the remaining stock agrees with the physical position. The acceptance criterion is a reconciled explanation of the extra component, not simply an order marked complete.
Repeat the exercise with a shortage and with only part of the planned quantity completed. Ask an operator to explain what remains to be done without help from the implementation team. Keep the actual result, expected result, owner and unresolved issue together in a short test log.
5. Set the release conditions
- Normal order: component demand, actual use and finished quantity reconcile.
- Wrong input: users know how to identify and correct an accidental entry.
- Shortage: the planner can see the missing item and the next responsible person.
- Access: an operator and supervisor can perform their jobs with their intended permissions.
- Handover: a trained employee completes the workflow without the project team driving the screen.
Before release, agree the opening-stock cut-off, unresolved issues that block production, and the contact for first-day problems. Expand to another product family only after the first flow is understood and repeatable. This keeps the next phase grounded in observed work.
For a broader discussion of production workflows, explore our manufacturing systems page. To scope a pilot, review Lava’s Odoo services or send an enquiry with your product family, current process and main exception.
For a related planning step, use the inventory setup checklist.