Make responsibility explicit
Traceability data crosses procurement, production, logistics, quality and information systems. Define who owns each data element and who resolves a failed relationship. Shared data does not remove the need for a responsible owner.
Separate ownership of the process from ownership of the software. An integration team may move a supplier file correctly while a quality team decides whether the evidence supports an origin claim.
Validate identity and meaning
Check that required identifiers are present, that referenced objects exist and that units and timestamps are interpretable. Look for duplicate events, impossible quantities and links to unknown facilities. Treat these checks as an ongoing operational process.
A schema check can confirm structure. It cannot confirm that the record describes the physical world correctly. Use sample reconciliation and source review to assess that second question.
Represent evidence status accurately
Useful states include reported, supporting document linked, reviewed and disputed. Define what each state means and who can change it. Avoid a single “verified” badge that hides whether verification was a format check or an independent review.
An event may be valid while its supporting evidence remains pending. Display the event status and evidence status separately, as the example journey on this site does.
Retain corrections and access history
Record the reason, source and timing of corrections. Preserve enough history for another investigator to reproduce the result. Set access rules around commercial sensitivity and personal information rather than making every supplier record public.
Choose retention periods from your operational needs and applicable rules. This site does not prescribe a universal retention duration. Also plan retrieval: a retained file that cannot be found during an incident offers limited practical value.
Review data quality over time
Track unresolved relationships, late records and recurring identifier collisions. Use these measures to find specific process weaknesses, not just to create an aggregate score. Review a small sample of complete traces regularly.
Include supplier changes, software changes and production exceptions in the review. Connect the results to your implementation checklist and partner agreements so corrective work has an owner.
Frequently asked questions
What does verified mean?
Define the check precisely. Format validation, document review and independent assurance establish different things. A badge should identify which check occurred and whose responsibility it was, rather than implying universal certainty.
How long should records be kept?
Determine retention from your applicable rules, contracts, product lifecycle and investigation needs. There is no single duration prescribed here. Include access and retrieval testing so retained evidence is available when required.
Sources and scope
Primary references checked on 4 October 2026. The process examples and implementation suggestions are editorial guidance. Formal standards are distinct from legal requirements.