A number is not a record until it has context

A value such as “12.5” cannot be reviewed without knowing whether it is grams per component, grams per sellable unit, an estimated weight, or a measured average. It also needs a product identifier, packaging component, effective date, and source. If a supplier replaces a bottle, a later reviewer must be able to see which specification applied to the earlier sales period.

Keep the chain of evidence

For each important value, record the original file or supplier response, its date, who supplied it, the field it supports, and the reviewer who accepted it. Preserve the original rather than silently replacing it with a summary. When two sources disagree, record the conflict and the resolution. A source file is evidence; its existence alone does not establish that every value inside it is correct or applicable.

Version decisions as well as data

Track a proposed change separately from the currently approved specification. Capture the old value, new value, reason, requester, decision, and effective date. A rejected change should remain visible in the history instead of disappearing. Sales imports need the same discipline: retain the extract and record how unmatched SKUs, missing destinations, returns, and duplicate rows were resolved.

Make an exported total reproducible

A useful report snapshot names the product and packaging versions, sales input set, material mapping, reporting period, and rule version used. It should remain interpretable after today's master data changes. A spot check can pick one reported material total and trace it back through those layers. If any link is missing, the total may still be arithmetically correct, but its basis is harder to defend.

PackageReports connects original evidence, versioned specifications, review decisions, and calculation lineage in one workspace. See how to review a calculation and what leaves with a company export.