Map parties and sites separately
A supplier map should distinguish the business you contract with from the facility that performs a physical activity. A trader may arrange a sale without producing the goods. One company may operate several sites, and one site may process materials for several customers. Store these relationships explicitly rather than forcing every supplier into one address field.
Start with a stable internal party reference and a separate facility reference. Record the source of each relationship and the date or period when it applies. A facility address needs enough detail to distinguish the actual site from a registered office.
Suggested fields for a useful map
| Record | Suggested information |
|---|---|
| Legal entity | Legal name, aliases, registration reference where available, country and relationship owner |
| Facility | Site reference, address, operating entity, activity and applicable period |
| Material relationship | Input and output references, supplier tier, processor, dates and quantity basis |
| Evidence | Source, document reference, reviewer, limitations and unresolved questions |
Store the original spelling and script of names alongside any normalised search version. A change in a trading name should not erase the history of the relationship. Record uncertain matches for review rather than automatically merging them.
Follow the material, not just the contract tree
A tier-one supplier list is a starting point. To investigate an input, follow the material through the facilities that produced or transformed it. Include subcontractors and intermediate processors even if they are not parties to your purchase contract.
In a fictional example, an assembler buys a component from a distributor. The distributor identifies a manufacturer, which identifies a finishing site. The map needs all three relationships, plus the record linking the component lot to the relevant production run. A generic manufacturer name without that link leaves the actual product history uncertain.
Validate identity and preserve uncertainty
Compare supplier disclosures with the commercial and production records available to you. Resolve differing addresses, aliases and activities with the data owner. A registration entry can help identify a legal entity but does not establish which facility processed a specific batch.
When checking official lists, retain the source, date and search terms, then investigate potential matches. Do not equate a weak name match with a confirmed finding. Equally, do not treat a missing match as proof about all upstream material. The UFLPA guide explains the US-specific legal context.
Use one map with separate review records
Connect the map to material origins and custody events. Link sourcing concerns and evidence requests to particular sites and periods. Assign owners for incomplete disclosures and decide when a changed processor requires a new review.
Maintain distinct assessment records for the EU framework and US import enforcement. The map is shared operational infrastructure; its fields are not a universal statutory checklist. Use evidence management to preserve the basis and limits of each review.
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.
The data fields, review methods and fictional examples below are editorial implementation suggestions. They are not a universal legal evidence checklist, certification scheme or guarantee of admissibility. Evaluate legal requirements within the relevant framework.