The Certificate of Analysis says one thing. The technical data sheet says another. The label on the bag says a third. All three describe the same ingredient — and reconciling them is the difference between a clean audit and a withdrawn product.
Every imported ingredient arrives with a stack of documents: a Certificate of Analysis (CoA), a Technical Data Sheet (TDS), a Safety Data Sheet (SDS), sometimes a specification sheet and a GRAS or regulatory statement. To an untrained eye they are interchangeable paperwork. To anyone who has been burned, they are three different instruments that must agree — and frequently do not.
Documentation discrepancies are among the most common and least visible problems in international sourcing. They rarely cause an immediate failure. Instead they surface months later, in an audit, a customs hold, or a customer challenge, when the gap between what one document says and what another says becomes someone's expensive problem.
What each document is actually for
- The CoA reports the measured results for a specific batch: assay, moisture, particle size, microbial counts. It is a snapshot of one lot, signed and dated.
- The TDS describes the ingredient in general: typical specifications, recommended use, storage, functionality. It is a description of the product line, not a given lot.
- The SDS covers safe handling: hazards, first aid, storage, disposal. It speaks to worker safety, not product performance.
The trouble begins when a parameter appears on more than one document with different values or different methods. Three real patterns:
- The assay mismatch. The TDS lists a typical purity of 98%. The CoA for the delivered batch reports 95%. Both may be acceptable — but if the formulation was modeled on 98%, the finished product is under-dosed and a claim may fail.
- The method gap. The CoA reports a result by one analytical method; the customer's own lab uses another. The numbers do not match, not because the ingredient is wrong, but because the methods are not comparable. Without method transparency, this looks like fraud when it is only physics.
- The label-document divergence. The name printed on the bag does not exactly match the name on the CoA — a trade name versus a chemical name, or a different grade designation. Customs and auditors treat this as a red flag until it is reconciled in writing.
A simple discipline prevents most of these failures: never model a formulation on the TDS typical value. Model it on the CoA minimum, with margin — because the typical value is a marketing description and the CoA is the contract.
Warning signs in a document set
- The CoA has no batch number or date — it is a generic template, not a real measurement.
- A key parameter appears on the TDS but is absent from the CoA, or vice versa.
- Analytical methods are not stated, making any number impossible to reproduce or compare.
- The name or grade differs across the bag, the CoA, and the invoice.
- The documents come from different legal entities (a manufacturer and a trader) without a statement linking them.
Where a sourcing partner earns its place
Reconciling documentation is unglamorous, technical work — and exactly where a capable sourcing partner protects the client. That means reading the CoA against the TDS before a shipment is accepted, not after; confirming that analytical methods are stated and comparable to the client's own lab; flagging name or grade divergences and obtaining a manufacturer's declaration letter to reconcile them in writing; and ensuring that when documents originate from different entities — a producer and a distributor — there is a clear, auditable link between them.
The goal is simple: when an auditor or a customs officer or a demanding customer asks a question, every document tells the same story, and the story holds.
The takeaway
Treat the document set as a system that must agree, not a formality to be filed. Before accepting any ingredient, reconcile the CoA, the TDS, and the label against each other and against your formulation — and resolve every discrepancy in writing before the batch enters production. A mismatch caught at intake is a five-minute email. The same mismatch caught in an audit is a withdrawn product.
This article is provided for general informational purposes and reflects industry practice. It is not technical, regulatory, or legal advice for any specific product or jurisdiction. Formulation and compliance decisions should be validated with qualified specialists.
