Buyers regularly ask for the wrong one of these two documents, in both directions. Some request a full third-party test for a decision a signed declaration would settle. Others accept a declaration where nothing but an accredited result will survive scrutiny. The cost of the first mistake is money; the cost of the second is a rejected shipment.
The two documents do different jobs, and the useful question is which job the current decision requires.
What each document actually is
A declaration
A statement by the manufacturer that the product conforms to a named standard or specification, signed by a person accountable for that statement. Its value is attribution: it fixes who is making the claim, and it is the document a customs officer or a retail compliance team reads first because it names a responsible party.
Its limit is equally clear: a declaration is an assertion, not a measurement. It carries no test data, and it cannot tell you whether the claim is true — only who says so.
A third-party test report
Results produced by an accredited laboratory on a described sample under a named method. Its value is evidence: an independent party measured something specific. Its limit is scope — it describes the sample tested, at the time it was tested, under the method used. It says nothing about the next production run.
A decision matrix
| Situation | Declaration | Third-party test |
|---|---|---|
| onboarding a supplier for a routine, established product | Sufficient to start | Worth having on file; not always required up front |
| Entering a market with a formal conformity regime | Usually mandatory | Usually mandatory alongside |
| Retail customer with its own technical requirement | Supporting | Almost always required, often from a named lab |
| Material or construction change on an existing SKU | Must be reissued | Must be re-run if the changed component drives the claim |
| Public tender or institutional purchase | Required | Required, with specified methods |
| Answering a performance question in negotiation | Not useful | The only useful answer |
The pattern: declarations handle who is accountable; tests handle what is true. Most decisions need the first, some need the second, and a few — formal regimes and retail technical requirements — need both.
Where declarations are quietly misused
Three patterns worth recognising:
- Declaration as substitute for data. A supplier responding to a performance question with a declaration has not answered the question. On an absorbency or rewet discussion, only results answer.
- Declaration with stale scope. Declarations name a standard and a product. When the product changes and the declaration does not, the document is describing something that is no longer made.
- Declaration without an accountable signatory. A declaration signed by a sales address rather than a named function is weaker evidence than it appears, and retail reviewers notice.
Where testing is over-specified
The opposite error is spending on tests that do not change a decision. Two questions prevent it: what would we do differently if this test failed? and does the customer's requirement name this test specifically? If the answer to the first is "nothing" and to the second is "no", the test is reassurance, not evidence — and reassurance is a legitimate reason to test, as long as it is a conscious one and not a line item nobody questioned.
Keeping both current
The failure mode for both documents is the same: they were valid at onboarding and nobody re-checked. A dated register per supplier, with the document type, the construction it covers, and a review interval, resolves it. When a material substitution is proposed, the register should be the trigger for reissuing the declaration and re-running any test that the changed component drives — not a note discovered during a shipment dispute.
Supplier-level evaluation is covered in the supplier directory and criteria; the production-side verification sequence is in the quality control framework. The full document set is listed under compliance documents to request, the classification question is covered in regulatory classification changes, and environmental claim wording is discussed in degradability claims.
The short version
Declarations assign responsibility; tests produce evidence. Ask which one the decision actually needs, reissue both when a material changes, and keep a dated register so the question never arrives during a shipment dispute. Neither document is stronger than the other — they answer different questions.