The three documents answer three different questions, and no one of them substitutes for another. A COA answers 'what did this batch test at'. A TDS answers 'how should this ingredient be used and stored'. An MSDS answers 'how do we handle, transport and declare it safely'.
COA: batch-specific results
A certificate of analysis is tied to a batch number. Check that the number matches the drum label, that the purity line names its analytical method, that identity confirmation is present, and that water and residual solvent results are stated where relevant. A signature without method detail is not a comparable result.
TDS: grade-level guidance
A technical data sheet is not batch-specific. It usually carries solubility, appearance, recommended handling, storage conditions and compatibility notes. Formulation teams use it before a sample is ordered; QA teams use the COA after a batch ships. Ask for the current revision date so you are not formulating against an obsolete sheet.
MSDS: safety and transport
The safety data sheet is written for handlers, carriers and customs. Check that the language and format match the destination market, that it is current, and that the product name and supplier details match the commercial invoice. An outdated MSDS is a frequent, entirely avoidable customs delay.
Which set to request at each stage
Before sampling: TDS plus a redacted sample COA. At supplier qualification: the document list your market requires, with methods and validity. Before dispatch: the batch COA, MSDS, packing list and invoice with matching batch numbers. Third-party reports are usually qualification documents, not per-shipment ones.
Tell us the destination market and we will list the documents available for the grade in the quotation, so your QA team knows exactly what will arrive with the batch.