
The chain, in five steps
Identity names the unit. Events record what happened. Custody names who held it. Evidence supports the claim. Governance keeps the file honest.
Open a file
How this file works
Three rules. First, no invented numbers and no clearance promises: figures come from official sources, are attributed, and carry the date they were checked; worked examples use labelled illustrations, never real shipments. Second, frameworks are never blended: Regulation (EU) 2024/3015 is not Section 307, and the UFLPA presumption is not an EU ban, and each guide says which system it is describing. Third, corrections are published, not buried: the corrections page records what changed and why.
This site does not recommend a platform, supplier, auditor, or service, and it does not generate leads. It explains the record so a reader can judge a supplier claim, an import file, or a professional's advice well, and routes product-specific decisions to the official sources and to qualified advisers in the relevant jurisdiction.
Try the worked record in the traceability lab, or work through the implementation checklist for one product family.
How a trace is filed
- Define the unit of trace first, and read its record, not a summary of another product's record.
- Record events as they happen, with place, time, custodian, and quantity.
- Confirm every handover on both sides, so custody has no silent gap.
- Keep supplier evidence current, and treat an expired or inconsistent document as a gap, not a filing delay.
- Re-check before relying on a record, because a supplier, a facility, or a framework can change between shipments.