Define which approved design fields may create or change panels, fittings and job instructions. Preserve project and revision identifiers, and separate exported demand from actual cutting results. A rejected or repeated file should have a visible outcome, with review before a change replaces material already purchased or cut.
Understand the decision
A design application exports a revised kitchen after a customer changes a drawer stack. Some original panels are already machined. The interface needs to identify the difference and its disposition instead of deleting the previous demand and presenting the entire new layout as untouched work.
Work through the requirements
- Map approved panel and hardware fields explicitly.
- Compare revisions before replacing released requirements.
- Test duplicate files and partially completed jobs.
| Record or decision | Why it matters |
|---|---|
| Export manifest | Identify source project and revision. |
| Revision difference | List affected operational components. |
| Import decision | Record accepted or rejected changes. |
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
Blindly overwriting a job with the latest export can remove the evidence of material already used. Keep revision differences reviewable and decide how completed work is preserved before allowing a design interface to change operational demand.
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 Cabinetry 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: vendor pricelists ↗Odoo 19: quality control points ↗