COA, MSDS, and TDS Overview
A Certificate of Analysis, an MSDS or SDS, and a Technical Data Sheet are different documents. A COA reports quality results for a defined batch or lot. An SDS focuses on hazard communication, handling, storage, and transport. A TDS explains product characteristics and technical information for procurement or formulation. A reliable B2B review matches all documents to the same product code, grade, revision, intended use, and target market.
Key Takeaways
- A COA is batch-specific; it is not a general promise for all future shipments.
- An SDS is not a purity or product-performance document.
- A TDS is not a substitute for a COA, quality audit, or project-specific review.
- Product code, grade, revision, batch, method, and date must align.
- Missing information should become a documented question, not an assumed fact.
1. The Three Documents at a Glance
| Document | Main purpose | Typical user | Main question |
| COA | Batch-quality result | Quality and procurement | Did this batch meet its specification? |
| SDS or MSDS | Hazard communication | Safety, warehouse, logistics | How should the material be handled and stored? |
| TDS | Technical product information | Formulation and procurement | What are the product characteristics and application conditions? |
The documents may be delivered together, but they are not interchangeable. A buyer should retain each document under its proper role.
2. What a COA Tells a Buyer
A COA normally records the product name or code, batch number, test date, specification limits, actual results, test methods, and a release or approval section. The exact layout depends on the product and quality system.
The first check is identity. The name and code should match the quotation, sample, packaging, purchase record, specification, and technical data. Next, check the batch number, manufacturing or release date, test method, units, limits, result, and sign-off.
A result without a method or acceptance range may require clarification. A result from one batch does not represent every future shipment. Ask how each batch is released, whether testing is routine or customer-specific, and how deviations are handled.
3. What an SDS or MSDS Tells a Buyer
An SDS focuses on hazard communication, handling, storage, transport, emergency information, exposure controls, and related safety sections. In the United States, buyers may receive an SDS under the terminology used by the supplier’s safety documentation system.
Review the material identity, hazard sections, handling, storage, exposure controls, accidental release guidance, transport information, and revision date. The SDS is not a product specification and should not be used to infer purity, marker content, nutritional value, or finished-product performance.
The document should match the supplied material format. A powder, solution, premix, or blended product may require a different document. Confirm the exact product, grade, concentration, and revision.
4. What a Technical Data Sheet Adds
A TDS usually provides practical product information for procurement, formulation, and technical discussions. It may include appearance, solubility, particle size, active or marker content, recommended storage, packaging, shelf life, application notes, and available documentation.
For a botanical extract, a buyer may look for botanical identity, plant part, extract ratio, standardization, and contaminant controls. For a liposomal material, a buyer may ask about active concentration, particle size, dispersibility, encapsulation efficiency, stability, and storage.
A TDS should be treated as a product document, not as a general corporate claim. If it uses “typical,” “target,” or “expected,” ask whether the field is a release requirement or informational value.
5. How to Match the Three Documents
Create one document-control check:
If one field does not match, ask the supplier to clarify before approval. A common issue is a COA for one grade being compared with a TDS for another grade. Another is an SDS for a concentrated material being used for a diluted or blended product.
6. Check Test Methods and Units
Two documents can show different values because they use different methods, reference standards, sample preparation, units, or reporting bases. This matters for marker compounds, purity, moisture, particle size, solubility, and encapsulation-related measurements.
Ask:
- Which laboratory performed the test?
- Is the method internal or externally referenced?
- How was the sample prepared?
- Is the result batch-specific?
- Is the result reported on an as-is or dry basis?
- Which specification limit controls release?
A number without context can be difficult to compare across suppliers.
7. Document Revision and Expiry Control
Record the issue date, revision number, review date, and expiry or retest information when available. A revised specification may change limits, methods, packaging, or product description. A current document should replace an older version in the active supplier file, while the older version remains archived for traceability.
For dynamic information, define when a new review is required. Examples include a formula change, facility change, new grade, new packaging, new test method, certificate renewal, or change in target-market requirements.
8. Build a Missing-Document Workflow
Some projects need additional records, such as allergen statements, non-GMO statements, origin information, traceability records, packaging declarations, stability data, or third-party testing. Define the required list before supplier approval.
Use a simple gap log:
| Gap | Why it matters | Owner | Due date | Status |
| Missing COA | Batch release cannot be reviewed | Supplier quality | [date] | Open |
| Missing storage data | Warehouse conditions unclear | Supplier technical team | [date] | Open |
| Method not stated | Results cannot be compared | Quality reviewer | [date] | Open |
| Intended use unclear | Product category cannot be confirmed | Buyer and regulatory team | [date] | Open |
If a document is not available, record the gap as a question rather than filling it with a general statement.
9. Keep Product Claims Separate From Document Claims
Having a COA does not establish a medical effect, market authorization, or universal compliance result. Having an SDS does not establish ingredient purity. Having a TDS does not establish that a finished consumer product will perform in a particular way.
Use each document for its intended purpose. Keep product claims tied to the relevant evidence, product version, intended use, and review status. This gives procurement, quality, formulation, and regulatory teams a clearer record.
10. US B2B Documentation Request Package
When requesting documents, include:
This prevents a supplier from sending a generic product file that does not match the project.
11. Archive and Retrieval Practices
Document control continues after supplier approval. Store the active specification, current COA, SDS, TDS, approval notes, and clarification emails in one controlled location. Use a consistent file name that includes product code, grade, document type, revision, and date. Restrict editing rights for approved records and make sure the purchasing team can identify which version was used for a purchase decision.
When a new document arrives, compare it with the previous version before replacing the active copy. Note changes to limits, test methods, packaging, storage, product name, facility, or intended use. A small wording change can create a meaningful quality question if it changes the product definition or release basis.
12. When to Escalate a Document Review
Escalate the review when product identity is unclear, a batch result falls outside the stated range, a test method changes without explanation, a certificate scope does not match the facility, an SDS describes a different material, or the product is being considered for a new category or market. The escalation record should state the question, source documents, affected batch or version, owner, and required decision.
Common Questions
Is a COA enough for supplier approval?
Usually not. A COA supports batch-quality review, while supplier approval may also require an SDS, TDS, facility information, traceability, audit records, and other documents.
Is an SDS the same as a TDS?
No. An SDS focuses on hazard communication and handling. A TDS focuses on product characteristics, technical information, and application-related details.
Can a buyer use an old COA as a current specification?
An old COA may be useful as a reference, but it is tied to its original batch and date. Confirm the current specification and request a current representative or shipment-specific record.
Why do two documents show different values?
Possible reasons include different batches, methods, units, versions, or reporting bases. Ask the supplier to explain the difference and identify which document controls the current product.
Should US buyers request an SDS for every ingredient?
The document package depends on the material, intended use, workplace, transport, customer requirements, and applicable rules. Buyers should define the required list with their quality and regulatory teams.
How should a document revision be controlled?
Record the revision, issue date, approval status, review date, and replacement relationship. Keep the active version in the working file and archive older versions for traceability.
Does a COA confirm a product’s market status?
No. A COA reports quality results for a batch. Market status, labeling, intended use, and other regulatory questions require a separate product and market review.
Can Bolin provide documentation for a product inquiry?
Availability depends on the product, grade, batch, and public-release permission. Buyers should request the current specification, COA, SDS, TDS, and other records for the exact product under discussion.
Request a Documentation Package
For a product inquiry, include the product code, grade, intended use, target market, requested volume, packaging, and required quality fields. This helps the supplier send a package that matches the project.
