A Sourcemap supplier map is not food lot genealogy
Sourcemap presents multi-tier supply-chain mapping, supplier discovery, due-diligence records, chain-of-custody documents, and traceability capabilities. A network map can reveal where materials and suppliers may connect, but food incident scope still depends on event-level records that show which lots actually moved, transformed, commingled, or were reworked.
Editorial figure by Food Traceability Ledger. Source context: Sourcemap.
Network possibility and lot movement are different evidence
Sourcemap's current website presents multi-tier supply-chain mapping and traceability, including sub-supplier discovery, supplier due diligence, chain-of-custody records, parts and material relationships, and data pipelines. A map can help a food business understand possible upstream dependencies, identify facilities, and ask where an ingredient or risk may originate. That is valuable network intelligence.
Lot genealogy answers a narrower operational question: which identified quantity of a food or ingredient was received, created, transformed, split, combined, reworked, packed, shipped, or otherwise handled in a recorded event? A supplier-to-site relationship does not prove that a particular lot traveled along that edge. Treating every possible connection as actual movement can overstate incident scope, while treating a partial map as complete can miss affected product.
Link master data to event evidence without merging them
The network layer should retain legal and operating entities, facility identifiers, addresses, roles, approved relationships, materials, products, certifications or due-diligence documents, relationship sources, confidence, validity periods, disclosures, inferred connections, reviewer decisions, and coverage gaps. An inferred or supplier-declared tier should be labeled distinctly from a relationship corroborated by transaction or audit evidence.
The genealogy layer needs lot, batch, serial, or other traceability identifiers; item and version; quantity and unit; event type; date and time; location; sender and receiver; shipping and receiving references; input and output links; process step; transformation, commingling, split, repack, relabel, hold, release, destruction, return, and rework records; plus corrections and responsible parties. Master-data updates should not alter events already captured.
Show completeness boundaries during an investigation
When a hazard, complaint, test result, or supplier notice identifies a suspect input, the investigation should use the network map to identify plausible paths and the genealogy records to confirm actual affected movements. Missing event data, unmatched identifiers, quantity imbalances, undisclosed sub-suppliers, manual transfers, and unintegrated facilities should appear as explicit uncertainty. The system should not silently convert unknown into unaffected.
Scope may change as evidence arrives. A defensible case preserves the initial hypothesis, search criteria, source data versions, confirmed and possible lots, excluded lots with reasons, quantity reconciliation, locations, customers, hold or withdrawal actions, notifications, approvals, and each superseding scope decision. Supplier-map corrections and incident-scope corrections need separate audit trails, because a newly discovered relationship can be important even when no affected lot used it.
Test a commingled ingredient with an incomplete tier
A representative evaluation should map two farms through a processor and broker to a food manufacturer, then record a commingled ingredient lot used across two production runs. Leave one sub-supplier relationship undisclosed, introduce a corrected receiving record, split finished goods among distribution sites, and initiate an incident. Reviewers should distinguish possible from confirmed paths, reconcile quantities, expand and narrow scope with attributable evidence, and retain every prior map and genealogy state.
Sourcemap's official site supports the described mapping, sub-supplier, due-diligence, chain-of-custody, material-relationship, traceability, and data-pipeline positioning, but no customer's food, supplier network, facility, lot, event, quantity, genealogy, investigation, recall, configuration, implementation, or outcome was independently tested here. Food businesses and qualified food-safety, quality, supply-chain, operations, regulatory, compliance, and legal owners retain their decisions.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.