Record the customer’s required species, grade, finished dimensions and agreed measurement basis before translating the quote into a production plan. Separate nominal descriptions from the actual acceptance requirements. The handoff should also identify allowed tolerances and substitutions, so purchasing or processing does not treat a familiar trade name as a complete instruction for the order.
Understand the decision
A hypothetical customer orders a repeat timber product but expects a different finished dimension after machining. Available raw stock carries a similar nominal description, while the yield assumption came from the earlier product. The planner needs an approved specification and a revised material requirement before promising the same lead time.
Work through the requirements
- Confirm actual finished dimensions and acceptance criteria.
- Identify species, grade and approved alternatives.
- Review the raw-stock and yield basis for the order.
| Record or decision | Why it matters |
|---|---|
| Order specification | Define the accepted finished product. |
| Material assumption | State raw dimensions and planned recovery. |
| Approval reference | Preserve customer acceptance of requirements. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Nominal names are convenient shorthand but can conceal a costly dimensional mismatch. Keep the finished requirement and the raw-material assumption distinct, then confirm that both estimating and production use the same approved basis for the customer order.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Wood products manufacturing in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: manufacturing product configuration ↗Odoo 19: lot numbers ↗Odoo 19: quality control points ↗