Manufacturing training should help operators and planners explain what was required, what was consumed, what was completed and what remains unresolved. Use a representative product with an approved material list and a deliberate production exception. Verify the resulting records and responsibilities before judging readiness by how quickly a manufacturing order is closed.
Documented product basis: manufacturing configuration and tracking
Odoo 19 documentation describes configuring a manufactured product with a bill of materials. It also documents lot and serial tracking for manufacturing and requires a tracked output’s lot or serial identity before completion. These features are a starting point for checking the product setup that learners will use.
The exercises below are hypothetical training scenarios. Their production, quality and stock decisions must be mapped to your accepted configuration. Documentation does not establish that a particular rework, approval or inspection process is already available in your selected applications or that it matches your factory’s rules.
Separate operator tasks from planning and engineering decisions
List who may release work, confirm material identity, record consumption and decide the disposition of questionable output. An operator should know how to report a shortage without assuming authority to change the approved component. A planner should be able to distinguish a production observation from a revised promise to a customer.
Prepare sample products, units and material lists that the production owner can explain. Include the devices and role accounts the agreed process requires. If an exercise reveals an ambiguous unit or revision, resolve the underlying data decision rather than teaching users a private workaround that others cannot reproduce.
Hypothetical exercise: a run finishes below plan
Start with a sample run planned for ten units. The exercise reports eight accepted units, one rejected unit and one unit still awaiting work. Ask the learner to record actual consumption and output using the validated process, identify the unfinished obligation and explain the rejected quantity. The scenario does not assume that all three outcomes use the same record type.
Introduce a component-identity question before the remaining work continues. The learner must use the escalation route and leave the unresolved decision visible. A warehouse learner then identifies which output may proceed under the approved release rules. Where tracking is in scope, retrieve the relevant material and output identities.
- Planned quantity is distinguishable from accepted output.
- Consumption and remaining material reconcile to the exercise evidence.
- Rejected and unfinished quantities retain an owner and disposition.
- The warehouse receives an understandable, approved handoff.
Make the readiness review useful on the floor
Ask learners to explain the records without an instructor narrating each action. Keep a short aid near the task: the identity to check, the quantity to record, the decision that requires approval and the next person to notify. Include the approved correction route for a mistaken entry.
Review repeated issues with production, warehouse and system owners. An unsuitable screen, unclear policy and missing knowledge need different responses. Any further exercises or adoption review should be agreed in the training scope. A successful sample run demonstrates that case only; it does not establish readiness for every product family or exception.
Turn the guide into a training brief.
Choose your team’s roles and starting point. Build a practice checklist to review before training is scoped.
Plan my team’s trainingCommon questions
Should operators learn to change bills of materials?+
Only where that is an explicitly assigned responsibility. Most practice should teach users to recognize a mismatch and follow the approved engineering or process-owner decision path.
Can one production exercise cover the whole factory?+
No. Select representative families, work stages and exceptions, then agree which scenarios demonstrate the roles and first-release scope you need to validate.
Sources & further reading
Product capabilities depend on the Odoo version, edition, subscription and configuration. Source documentation supports product facts; project checklists and scenarios are editorial guidance. Confirm current details before purchase.
Odoo 19 documentation: manufacturing product configuration ↗Odoo 19 documentation: manufacture with lots and serial numbers ↗