Deep-Tier Supply Chain Traceability

Almost every difficult passport attribute has the same shape: the information exists, and it exists several tiers upstream from anybody you have a contract with.

Substance concentrations, material origins, recycled content and upstream emissions all originate at material production rather than at component assembly, which is where most brands’ visibility stops.

Why the gap exists

Supply chains are not designed for transparency. They are designed for cost, resilience and flexibility, and each of those pushes against knowing exactly where material comes from.

The third row is the one most often dismissed as obstruction. It is not. A supplier’s source list is genuinely valuable commercial information, and a customer asking for it is asking them to reduce their own negotiating position.

Approach one: cascading requirements

The standard approach requires tier one to impose the same requirement on tier two, and so on. It is contractually clean and it propagates slowly.

Propagation depends on each tier carrying commercial weight with the next. A brand with substantial volume can require a great deal of a component maker; that component maker may be a small customer of the chemical producer above them and carry no weight at all.

Approach two: buy at depth

Some brands contract directly with material producers while still buying finished components from an intermediate supplier, which is sometimes called nominating a source.

It gives genuine visibility because you have a direct relationship with the party holding the data. It also costs flexibility — the component maker can no longer switch sources for cost or availability — and it requires enough volume for a material producer to want the relationship.

This works well for a small number of critical materials and does not scale to a whole bill of materials. Used selectively on the attributes that matter most, it is frequently the fastest route to defensible data.

Approach three: industry schemes

Sector schemes certify upstream actors once, and downstream buyers rely on that certification rather than each establishing their own visibility.

The third node is the limitation that matters for passports. A scheme can tell you your material came from a certified producer; a passport attribute asking for the specific origin needs something a scheme does not always provide.

What actually gets responses

Across all three approaches, some practices reliably improve response rates and others reliably do not, and the difference is mostly about the burden being asked for.

• Ask for what you need, not everything possible — a short specific request outperforms a comprehensive questionnaire every time.
• Explain what it is for — a supplier who understands the regulation behind a request treats it differently from an unexplained form.
• Accept the data in their format first — translation is your problem, and insisting on your template loses responses.
• Make it contractual at renewal — the only moment when a new obligation is genuinely negotiable.
• Offer confidentiality that means something — permissioned access is precisely the mechanism that lets a supplier disclose safely.

The last point deserves emphasis because it is what a passport uniquely enables. A supplier reluctant to publish their source can accept a record where a regulator or a recycler sees it and a competitor does not.

When to accept an approximation

Perfect deep-tier visibility is not achievable across a full bill of materials, and a programme that treats it as a prerequisite will not ship.

The workable position is to be precise about data quality rather than to pretend to a precision you do not have. An attribute recorded as a sector average, with its provenance stating that plainly, is honest and useful. The same figure presented as supplier-specific is neither.

This is why provenance in the data model matters so much. It is what allows a programme to publish incomplete knowledge accurately, rather than choosing between waiting indefinitely and overstating what it knows.