Agree which identity and movement records are needed to support the business’s reviewed traceability requirements, then test their relationships before cutover. Preserve original references and distinguish verified history from incomplete legacy information. Operational and quality owners should approve any limitation rather than allowing a successful import count to stand in for traceability evidence.
Understand the decision
The source system records serials in delivery notes but not consistently in its product export. Some attachments are stored in a shared folder. Migration must demonstrate that a representative identity can be followed through the required records and that missing links remain visible for an authorized decision.
Work through the requirements
- Inventory required identity and movement evidence
- Map stable references across records and documents
- Rehearse retrieval with responsible reviewers
| Record or decision | Why it matters |
|---|---|
| Identity crosswalk | Links original and target references |
| Movement evidence register | Lists required historical relationships |
| Migration limitation log | Records gaps and approved treatment |
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
Do not manufacture historical certainty by assigning new identities to ambiguous stock or documents. Preserve the limits of the source evidence, and have the responsible owners decide whether the proposed opening state is acceptable for their requirements.
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 Medical supplies distribution 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.
Lot numbers ↗Serial numbers ↗Expiration dates ↗