Supplier Traceability Data Quality: Build an Owned Exception Queue

Define required fields and their business meanings for each activity. A generic spreadsheet column list may miss the requirements of the actual workflow.

Retain raw values alongside normalized ones. Cleaning a supplier name should not erase original identity or turn an ambiguous location into a falsely precise address.

Separate delivery, parsing, acceptance, correction, and review states. An imported flag should not represent both a readable file and complete operational evidence.

Classify missing fields, invalid formats, conflicting identities, and unresolved scope by the action needed. Each exception should name an owner and the evidence required to resolve it.

Use a file with every column populated but a source copied from the wrong supplier and a quantity in the wrong unit. Shape validation alone will pass; business validation should expose both conflicts.

Track exceptions by age and supplier. A shrinking queue is useful only if records were corrected rather than dismissed, and corrected files should not duplicate existing events.

FoodChainAPI suggests candidate Food Traceability List categories from product descriptions. Save the reviewed result beside the product specification; a category match does not establish exemptions, complete operational records, or certify compliance.