Getting evidence out of suppliers, and what silence is worth

The short answer

There is no statutory right for a brand to demand information from its own supplier. One route is written down and it is narrower than the problem: where an article contains a candidate list substance above the threshold, information about that substance is owed to whoever receives the article on supply, and a separate right to ask belongs to a consumer. What the route dependably produces is a record of having asked.

That is less than most people expect and more useful than it sounds. A request produces an artefact that has an author, a recipient, a subject and a date. The artefact is worth something whether or not a reply arrives. A reply is worth more. How often one arrives is not something anybody has measured, and this page publishes no figure for it.

The route that is written down, and its two unequal limbs

The supplier information article of the chemicals regulation has two paragraphs, and they are not one duty pointing in two directions. The first is owed to whoever receives the article in the course of business, and it operates on supply: no request is needed, no period is stated and no price term is stated. The second belongs to a consumer who asks, and it carries both a period and a guarantee that the answer is free. Neither is a mechanism a brand can point at its own supplier.

The asymmetry catches people out in one particular way. A brand writing to its supplier is not a consumer and cannot start the consumer clock, so a letter drafted from that paragraph cites a period that does not apply to the person sending it. Where the brand is itself the recipient of the article, what it is owed was owed already, and the paragraph that owes it describes no request procedure, no period and no remedy the brand operates. The practical position is that you are recording a duty rather than exercising a power.

Two neighbouring provisions are worth knowing and neither closes the gap. One runs the other way, obliging an actor to pass new hazard information up the chain rather than to answer questions coming down it. The other gives a business a safety data sheet for certain mixtures, which is a different object from an article.

Why supplier silence is a category rather than a compliance failure

Both limbs are capped by the same phrase. The information owed is the information available to the supplier, so neither limb creates a duty to generate information the supplier does not hold. It is the most useful sentence on this page and it is worth reading in the direction that hurts.

A supplier who was never told what is in the material cannot tell you, and is not in breach for failing to invent it. An unanswered request is therefore not automatically anybody's failure. It is also not a blank: it is an absence with an author, a date and a reason attached, which is a thing the estate has a vocabulary for and treats as an answer in its own right. That vocabulary, and the rule that not found by us never becomes there is none, is set out in how we know.

The regulator's own words, and the half that gets left out

A regulator's statutory review of this duty is the strongest authority available for any of it, and it is worth more than a vendor's account of the same problem. Where no information was received, the review records, it is not possible to see the reason: it could be non-compliance, or it could be that the substance is not there. That is a regulator declining to convert silence into a finding.

It is also half of what the review says. The other half is what happened where suppliers did respond, and responses did come in. Both halves belong to the same document, and publishing one without the other turns a balanced finding into an argument. We hold the review at the level of its findings rather than its underlying data, so we restate neither half as a rate.

A counter-example, because supplier evidence is not uniformly unobtainable

One merchant wrote to a number of suppliers about the substances in what they were selling and had no reply at all. Another picked up the telephone to a manufacturer and had an independent certification in hand within minutes. Those two accounts sit beside each other in the material behind this page, and a page that publishes the first without the second is telling half the story.

The provenance of that material is worth stating plainly. Nine items of genuine practitioner voice were reached across the whole programme, four of the nine carry no date that could be established, and they reached us as researcher-reported summaries rather than at their own source. We use them for existence statements and for nothing that resembles a rate.

There is no average supplier

The same practitioner recorded two suppliers on the same problem. One did not answer for seven months, against documents that practitioner described as years out of date. Another answered in ten minutes. We publish that pair as an existence statement and take it no further, because the shape of the population between those two points is not something anybody has measured.

What follows is narrow and worth having anyway. Suppliers on this evidence are bimodal rather than slow, so a plan built around speeding up the average supplier is optimising a distribution that does not exist. The work that survives either outcome is triage. Sort by what each supplier actually did, put the effort where movement is visible and record the rest.

One consequence is unglamorous. Where the information was never created upstream, no ladder, no portal and no letter will produce it, and the work that would produce it is a testing programme or a different supplier rather than a chase.

Why the supplier does not answer, and who is helping them

That suppliers do not answer is where most pages stop. The causal step is that your request is not the only one on the desk. A supplier of any size receives near-identical questions from every customer it has, each in a different template, each asking for the same substances information in a different shape and each carrying its own deadline. Answering them one at a time is a job nobody is funded to do.

Retailers noticed this before brands did and moved on it. The direction of travel described in the accounts reached for this page is retailers unifying onto shared questionnaires, so that a supplier answers one form rather than forty. That is a fix for the supplier and a fix for the retailer. It is not a fix for you.

There is an asymmetry underneath that which is worth saying out loud. Retailers buy supplier data onboarding as a product and brands generally do not. That is why the reader of this page finds vendors selling into the other side of the conversation and nobody selling into the position they are actually in.

What works is contractual before it is technical

The leverage that produces documents is leverage that was written into the relationship before anybody needed it. Where the contract is silent the request is a favour, and a favour has no escalation path. Practitioners describe this as a legal workflow problem wearing the costume of a data workflow problem, which is a better description than most software gives it.

The rungs below are the part that gets skipped, because vendor pages start at the software. Each rung is a decision rather than a message, and none of them carries a promise about what it will produce.

1. Put the obligation in the contract. A named list of information, a named format and a named period, agreed at the point where you still have something the supplier wants. Draft the wording once and reuse it, because a clause written afresh per supplier is a clause nobody can audit.
2. Repeat it as a purchase order condition. A term in a master agreement that no purchase order references is a term nobody reads at the moment it matters.
3. Attach it to a payment step. This is the rung practitioners describe as the point at which the request stops being optional, and it is reachable only if the first two rungs exist. We make no claim about what it produces in any particular relationship.
4. Send a sequence, not a message. A first request. A reminder that restates the question in the same words. A final one that says what happens next. Rewriting the question between attempts is how two different answers arrive and neither can be compared with the other.
5. Decide in advance what you will accept. Ask for a listing by component and you may well receive a blanket statement about everything the supplier makes. Decide before you send whether that answers your question, because deciding afterwards is deciding under pressure.
6. Record the request either way. The log is the deliverable, and the last two sections are about why.

What a regulator expects of the chain, in both directions

None of the ladder is a legal right, and one regulator's supply chain guidance is the closest thing to an external expectation this page can point at. It describes how businesses are expected to conduct themselves before they advertise, rather than creating a right one business holds over another. It runs in both directions and it has to be read in both, or it says something it does not say.

The half that usually gets quoted is the hard one: taking all reasonable precautions is not a defence and an innocent breach is still a breach. Quoted alone it makes a compliance programme look worthless, and it is the sentence a vendor reaches for. The same guidance says genuine compliance efforts may be treated as a mitigating factor when a penalty is calculated, which is the half that makes the record you keep worth keeping.

The artefact worth building is the log

Ask practitioners what they built to survive this problem and the answer is a request log rather than an evidence library. The library is what they wanted. The log is what the work produced, and it is the object that holds its value when the evidence never arrives.

A row holds seven things and none of them is sophisticated. It is a spreadsheet before it is anything else, and a spreadsheet that is honest about its last column already beats most systems. The drawing is the row, because this page has described it for a long time without showing it.

Two things become possible that a folder of attachments cannot do. You can say what you did about an attribute that never resolved, in words a customer or an authority can check. Somebody else can audit that account without reconstructing it from your inbox.

There is a third, reported to us rather than established by us. The account recorded for this page is that a documented record of asking, chasing and escalating can move an audit finding from a non-conformance to an observation. We publish it as reported, because what any auditor does with it turns on the scheme and on the auditor.

The last column is where the value sits. Silence with an author and a timestamp is a record: it says who asked, when, under which limb and what came back, which was nothing. A blank field is not a record, and what to write when nobody answers is a question with a published answer rather than a matter of taste.

What this page does not promise, and what we did not find

Four refusals, stated plainly, because a page about getting evidence is exactly the page that tempts an author into a guarantee.

We publish no response rate. There is no figure here for how often suppliers answer, how quickly they answer or how that varies by supplier type, and no percentage is attached to silence anywhere on this page. We hold no measurement of it and we have not found one published anywhere we looked. Four separate research streams reached that same absence, which is why it is stated rather than hedged.

We do not say the route obtains evidence. It obtains a record of having asked, and where the information exists upstream it often obtains that too, which is a different sentence from a promise.

We promise nothing about escalation. Each rung is a step that practitioners describe as changing the conversation, and not one of them is a step this page claims will produce a document.

On a wider right to demand, we looked and came up short. The two narrow routes described above are what exists, and neither of them is a right for a brand to require information from its own supplier. Beyond them, a general statutory right of that kind was not found by us. We searched the substances regulation, where the two narrow routes live, and we tried to read the ecodesign framework's article on supply chain actors, which is the most likely place a wider right would sit. Every route to that article's text failed, so we do not say what it contains and we do not say it contains nothing.

Sources

• REACH Regulation (EC) No 1907/2006, Articles 3(33) and 33
  Arts. 31(3), 33(1), 33(2), 34CELEX 02006R1907-20250422In forceRelevant provisions reviewed

  The spine of this page, and the source of the correction it now carries. Article 33 was read in full at the consolidated text, both paragraphs, together with Article 31(3) on safety data sheets and Article 34 on information passed upstream. The read is what establishes that one paragraph is a push duty owed to the recipient of an article, that the other is a request right belonging to a consumer, and that the same capping phrase sits on both. It does not support any right for a brand to require information from its own supplier, and this page says so.

  View official source

• Statutory review of the supplier information duty on substances in articles
  Regulator publicationRelevant provisions reviewed

  The strongest authority on this page for the proposition that silence cannot be read, and it comes from a regulator rather than from anybody selling a remedy. Two halves are taken from it and they travel together: that where no information was received it is not possible to see the reason, and what happened where suppliers did respond. Neither half is restated here as a rate, because the review is held at the level of its findings rather than its underlying data.

• Regulator guidance on supply chain evidence and environmental claims
  Regulator guidanceRelevant provisions reviewed

  Declared for one passage that has to be quoted whole. It sets an expectation on retailers to seek evidence ahead of advertising and on brands to provide assurance and share the evidence underneath it, it says that taking all reasonable precautions is not a defence, and it says genuine compliance efforts may be treated as a mitigating factor in a penalty calculation. Quoting the middle sentence alone makes a compliance programme look worthless. It is guidance about conduct and it creates no right one business holds over another.

• Ecodesign for Sustainable Products Regulation (EU) 2024/1781, consolidated text
  Art. 38In forceOfficial source confirmed, detailed review pending

  Declared for an absence rather than for a proposition. The framework carries an article whose heading concerns supply chain actors, and it is the most likely place a wider right to demand information would sit. Its number and heading reached us through a secondary aggregator and every route to its text failed, so this page says only that we could not read it.

  View official source