Define whether each external system owns a raw observation, a reviewed result or a release decision. Map batch identities and units explicitly, and preserve correction history. An integration should route missing references, invalid measurements and repeated events for controlled handling rather than turning every received value into an approved inventory movement or technical release.
Understand the decision
In a hypothetical workflow, a scale sends an operator-corrected weight after an earlier reading, while the laboratory issues a reviewed result later. Both relate to the same batch but serve different purposes. The interface must preserve the sequence and authority without mistaking a corrected observation for an additional quantity or release.
Work through the requirements
- Map batch identifiers, units and event types.
- Define correction and supersession rules for observations.
- Separate measurement import from authorized release decisions.
| Record or decision | Why it matters |
|---|---|
| Raw observation | Preserve source value and timestamp. |
| Reviewed result | Identify accepted evidence and reviewer. |
| Integration receipt | Record event identity, correction and outcome. |
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
Data arriving automatically does not make it approved. Preserve who or what produced a value and which authority accepts it, especially when equipment readings, laboratory reviews and operational stock records are updated at different times during the batch.
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 Chemical blending 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 ↗