Assign the nesting tool responsibility for its cutting plan and explicitly decide where actual material consumption becomes authoritative. Exchange stable job, sheet and revision identifiers. Define how rejected nests, recuts and repeated messages are handled so a revised plan does not silently create a second issue of the same sheet.
Understand the decision
A hypothetical nesting application sends a planned sheet requirement before the operator cuts anything. Later it sends the actual result, including an extra sheet used after a machine interruption. The integration must distinguish planning demand from physical consumption and provide a review path for the difference.
Work through the requirements
- Separate planned and actual consumption messages.
- Map sheet and job identifiers explicitly.
- Test retries and a corrected cutting result.
| Record or decision | Why it matters |
|---|---|
| Interface map | Assign ownership of each quantity. |
| Cut result | Record actual sheet usage. |
| Failure queue | Expose rejected or repeated events. |
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
Importing every nest as a completed stock movement can consume material before cutting occurs. Require an explicit completion event and a recoverable error view, especially when operators revise a plan after the initial transfer.
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 Metal fabrication 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: vendor pricelists ↗