A CoC is one page that confirms goods match their specification. It carries no test data, no third-party signature and no guarantee — and yet for some buyers it is the document that releases payment or clears an internal audit. Knowing what it is worth, and what to ask for instead when it is not enough, saves a week of confusion at the wrong moment.
A certificate of conformance is a supplier's written declaration that the goods supplied meet the stated specification. It is self-declared, not independently tested, and it proves nothing on its own — its value is entirely in how specific the specification it references is, and in whether the supplier is someone you would believe. Ask for one when your own process requires a document on file, when customs or a tender requires it, or when you need a defined reference point for a future dispute. Ask for test data instead when you need to know how the batch actually behaved.
One page, four sentences, a lot of misunderstanding
A certificate of conformance — also called a certificate of conformity, and abbreviated CoC — is one of the most requested documents in B2B procurement and one of the least understood.
It is a supplier’s declaration. In its usual form it states that the goods supplied under a given order conform to a given specification, and it carries a signature and a company stamp. That is all it is. It is not a test result, not a third-party opinion, and not a guarantee.
That is not a criticism. A declaration has a real function. The problem is that buyers frequently ask for a CoC expecting test data, and suppliers frequently issue a CoC that appears to satisfy the request, and both parties discover the mismatch when someone in compliance reads it.
What it actually says
A useful CoC contains four elements:
- The specification it declares conformity to — named, ideally with a version or date.
- The order or batch it applies to.
- The quantity covered.
- A signatory with authority to make the declaration.
The first is what gives the document meaning. A CoC referencing a detailed specification is a statement you can check against something. A CoC referencing “flash memory products” is a statement that the supplier sells flash memory products.
The second and third make it applicable to your goods rather than to a product type. A generic certificate kept on file and reissued for every shipment is technically a CoC and practically useless, because it cannot be tied to what arrived.
What it does not say
It does not tell you that anything was measured. It does not tell you who tested what, at what conditions, or with what result. It does not come from an independent party. It does not survive the supplier going out of business.
None of this makes it worthless. It makes it a document, in the same category as an invoice: evidence that something was declared, useful in a dispute and useless as an assessment of quality.
When a CoC is genuinely the right ask
Three situations where it is exactly what you need.
Your process requires one. Many internal procurement systems will not release payment without a conformity document on file. In that case you need the document, and the quality of it matters less than its existence. Ask what format your finance or compliance team requires, and specify that rather than asking for “a CoC” and hoping.
Customs or a tender requires it. Some destinations and some public tenders list a certificate of conformity among the required documents. Again, the requirement is documentary. Get the version the authority asks for, in the language and format they specify.
You want a reference point for a future dispute. A batch-specific CoC that names a specification gives you something to point at later if the goods turn out differently. It is a weak lever but a real one, and it costs nothing to have.
When it is the wrong ask
When what you actually want to know is how the batch performed.
If you are trying to decide whether to accept a delivery, if you are qualifying a new supplier, or if the product carries a consequence when it fails, a CoC will not help. The document that helps is a test report — from the supplier’s own test with the method and conditions stated, or better, from a party you appointed.
The distinction matters because it changes what you ask for at enquiry. “Please provide a CoC” gets one page. “Please provide the test data for this batch: conditions, sample size, coverage and error counts” gets something you can reason about. What each test actually proves explains why the second request is harder to answer than it sounds, which is itself informative.
The documents that are often confused with it
| Document | What it is | Who issues it |
|---|---|---|
| Certificate of conformance | Declaration that goods match a specification | Supplier |
| CE declaration of conformity | Legal declaration under EU rules, defined content | Manufacturer |
| RoHS statement | Declaration on restricted substances | Manufacturer |
| Test report | Measured results for a sample | Laboratory |
| Material lot record | Traceability of components used | Supplier |
| Inspection report | Findings of an inspection, per criteria | Inspector, third party |
Buyers asking for “certification” often mean one of these and receive another. Naming the specific document is the fix, and it takes one sentence at enquiry.
How to ask for one that is worth having
Please issue a certificate of conformance for this order, referencing the specification version dated [date], the order number, the quantity and the batch, signed by a named person with authority to make the declaration. We also require [the specific compliance documents your process needs — CE DoC, RoHS statement, test report] separately.
Two things happen when you ask this way. You get a document that can be tied to your goods. And you find out whether the supplier can produce the other documents you need, which is the actual risk — a CoC is easy to issue; a verifiable test report is not.
What we issue, and what we do not
We will issue a batch-specific CoC against a stated specification, signed and stamped, and we will tell you honestly which of the other documents we can produce. Our position on certificates generally is stated plainly on the company record page — including what we have not published yet, which is a short list and worth reading before you build a compliance requirement around us.
We will not issue a CoC claiming conformity to a specification we have not been given. A certificate that declares conformity to something vague is worse than no certificate, because it creates a false record.
If your process needs specific documentation, send the requirement at enquiry stage — before quotation if possible, because a compliance requirement that surfaces after the order is placed is the single most common reason a shipment sits at a port. Cathy will confirm in writing what we can and cannot provide for your specific order.
Frequently asked questions
What is the difference between a CoC and a test report?
A CoC is a declaration; a test report is evidence. The CoC says 'these goods conform to specification X' and is signed by the supplier. A test report says 'sample Y was measured and gave these results' and comes from whoever ran the test — ideally a laboratory you can verify. They answer different questions: the CoC answers 'is there a document on file', the test report answers 'what did the goods do'. For most procurement processes you need the first. For a decision about whether to accept a batch, you need the second.
Is a CoC the same as a CE declaration or RoHS statement?
No, though they are often confused and sometimes bundled. A CE declaration of conformity is a specific legal document under EU rules with defined content and the manufacturer's responsibility behind it. A RoHS statement certifies restriction of certain substances. A CoC is generic — it confirms conformity to whatever specification the document names. When a buyer asks for 'a CoC' they sometimes mean one of the others, which is worth clarifying before documents are produced that turn out not to be what the compliance team wanted.
Can a CoC be issued for a specific batch?
It should be, and asking for batch-specific is the difference between a useful document and a decorative one. A generic CoC covers a product type in perpetuity; a batch-specific one references the order, the quantity, the date and the specification version. The second is what you want, because it can be tied to the goods you received. If a supplier offers a generic certificate for a specific shipment, ask for it issued against the order instead.
What should a CoC reference to be worth anything?
Four things: the specification it is declaring conformity to, ideally by version or date; the order or batch it applies to; the quantity covered; and a named signatory with authority to make the declaration. Without the first, it declares nothing. Without the second and third, it applies to nothing in particular. A CoC that names a product category rather than a specification is a piece of paper with a stamp on it.
Does a CoC replace an incoming inspection?
No. It is a declaration by the party whose goods you are checking, which is the least independent source available. It is useful as a document to hold, and useless as evidence of quality. If the batch matters — a first order, a launch, anything where a failure is expensive — inspect or test independently. The CoC then sits alongside the inspection as the paperwork, which is exactly the role it is suited to.