Quick Answer
A TDS, SDS and COA answer three different purchasing questions. The technical data sheet describes the product’s intended application, performance claims and typical properties. The safety data sheet communicates hazards, handling, storage, transport and regulatory information in a structured format. A certificate of analysis records agreed test results for a particular batch. None of the three, by itself, proves every claim on a label. An importer should match all three to the quotation, formulation, pack, label, licence evidence and production batch before shipment.[1] [2]
Table of Contents
- What TDS, SDS and COA each do
- Side-by-side document comparison
- How to review a TDS
- How to review an SDS
- What a useful COA should show
- Performance claims and licence checks
- Seven-step document-matching workflow
- Common importer mistakes
- Pre-order document checklist
- Frequently Asked Questions
- Sources & References
What TDS, SDS and COA each do
Lubricant buyers often ask for “the certificate” as if one document can confirm performance, safety, origin and batch quality. That shortcut creates avoidable risk. A TDS is mainly a technical and commercial product document. An SDS is a hazard-communication document governed by the destination market’s rules. A COA is a batch record built around a defined test plan.
The documents should describe the same saleable product, but they are not interchangeable. A flash point on an SDS may be reported for hazard communication; a viscosity on a TDS is normally a typical value; a viscosity on a COA should be an actual result for the stated lot. Treating these values as if they have the same purpose can lead to rejected labels, customs questions or disputes after arrival.
TDS vs SDS vs COA: side-by-side
| Document | Decision it supports | What to expect | What it does not prove |
|---|---|---|---|
| TDS | Application and product-positioning review | Product name, viscosity grade, performance wording, applications, exclusions and typical properties | It is not normally batch-specific and does not automatically prove an approval or licence |
| SDS | Hazard, handling, storage, transport and workplace review | Product identifier, supplier details, classification, first aid, handling, physical data, transport and revision date | It is not an engine-performance report or a substitute for the TDS |
| COA | Batch release or pre-shipment conformity review | Batch number, production/sample date, test method, specification limits where agreed, actual results, units and release status | It proves only the reported batch and tests; it does not replace performance testing or licensing evidence |
| API/OEM directory evidence | Verification of a licensed or approved claim | Current marketer/product/grade/category listing or a verifiable approval reference | A logo image, supplier letter or TDS sentence alone is not equivalent to a directory listing |
How to review a lubricant TDS
Start with identity. The product name, SAE grade, product code and revision should match the quotation and label artwork. Then read the wording around API, ILSAC, ACEA or OEM requirements carefully. “Meets performance requirements,” “suitable for use” and “officially licensed/approved” describe different evidence positions. Do not shorten one into another when translating a label.
Next review the application list and exclusions. A broad passenger-car claim is less useful than a clear statement of engine type, fuel, model-year boundary or specification. Typical physical properties should include units and recognizable test methods where relevant. They help compare consistency and formulation positioning, but typical values are not guaranteed batch limits unless the commercial specification says so.
The published pages for KATMOTO K9 ECO 0W-20 and KATMOTO K9 ECO 5W-30 illustrate why the exact grade and performance wording must remain connected to the exact SKU. Importers should request the current TDS for the formulation and pack quoted rather than reusing a sheet from a similar viscosity.[7] [8]
How to review an SDS for the destination market
The UN GHS provides a global framework for hazard classification, labels and safety data sheets, while national and regional authorities implement it through their own rules. The 2025 eleventh revised edition continues to treat labels and SDSs as core hazard-communication tools.[1]
OSHA requires a 16-section SDS format for hazardous chemicals in the United States. Its standard identifies sections covering identification, hazards, composition, first aid, fire fighting, accidental release, handling and storage, exposure controls, physical properties, stability, toxicology, ecology, disposal, transport, regulations and revision information. ECHA similarly explains that SDS format and content in the EEA are specified by REACH and may require relevant exposure scenarios.[2] [3] [4]
For procurement, check that the product identifier matches the label; supplier and emergency contacts are usable in the destination market; the revision date is current; Sections 2, 3, 9 and 14 are internally consistent; and the language meets local requirements. Never infer “non-hazardous everywhere” from an SDS prepared for one jurisdiction.
What a useful COA should show
A COA becomes useful only after buyer and supplier agree what is being certified. At minimum, connect it to the product code, batch or lot number, production or sample date, test methods, units, results and release authority. If acceptance limits are important, state them in the purchase specification before production.
For engine oil, a practical COA may include agreed blending-control properties such as kinematic viscosity and other batch-release checks. It should not be presented as proof that every engine sequence or licensing test was rerun on that batch. Full performance programmes use specialized tests and licensing controls that are different from routine blending release.
Decide when the COA is issued. A pre-production sample COA cannot certify the later shipping batch. For private label orders, the most useful record is normally tied to the finished batch and retained with label version, filling record and shipment documents.
Performance claims and licence checks
API’s Engine Oil Licensing and Certification System is voluntary and authorizes marketers meeting its requirements to use API quality marks. API directs buyers to its online EOLCS directory, which lists active licensees and licensed products and is updated frequently.[5] [6]
If an engine-oil label uses an API certification mark, check the current directory for the marketer, brand, viscosity grade and service category. If a supplier instead states that a product meets a performance level, ask what technical support backs that wording and ensure the label does not imply an official licence. Apply the same discipline to OEM approvals: request a verifiable approval reference and check the OEM’s current list where one exists.
Seven-step document-matching workflow
- Freeze the quotation: product code, formulation, viscosity, performance wording, pack, label language and destination.
- Match the current TDS to the quoted SKU and record its revision.
- Review the destination-market SDS, including language, contacts, classification, transport and revision date.
- Verify licensed or approved claims in the relevant official directory; save dated evidence.
- Agree the COA test plan, methods, units, limits and batch timing before production.
- Compare final label, carton, TDS, SDS, COA, invoice and packing list for identical product identity.
- Retain the approved document set with the batch and shipment record for traceability.
Common importer mistakes
- Using an SDS as proof of engine performance.
- Treating typical TDS values as guaranteed batch specifications.
- Accepting a COA without a batch number, method, unit or agreed limit.
- Reusing one document across several viscosities or formulations.
- Translating “meets requirements” into “approved” or “licensed.”
- Checking documents after label printing instead of before artwork approval.
- Keeping files without revision dates or a clear replacement history.
B2B pre-order document checklist
| Checkpoint | Acceptable evidence | Red flag | Importer action |
|---|---|---|---|
| Product identity | Same code/name/grade across quote, label, TDS, SDS and COA | Different suffix, viscosity or old brand name | Stop artwork and reconcile every document |
| Performance claim | Exact wording plus current licence/approval evidence where claimed | Logo screenshot or unsupported “approved” wording | Verify the official directory or change the claim |
| SDS suitability | Correct jurisdiction, language, supplier contact and revision | Foreign-market SDS with unusable emergency contact | Request a destination-ready SDS review |
| COA plan | Batch-linked methods, units, limits and release result | Generic template or sample-batch results | Define acceptance before production |
| Change control | Supplier notification rule for formulation, source, document or label change | Silent replacement of documents | Add written change-notification terms |
| Shipment file | Final label, COA, invoice, packing list and batch codes match | Shipping batch cannot be traced to records | Hold release until traceability is complete |
Frequently Asked Questions
Is a TDS legally required for lubricant imports?
A TDS is commonly requested for technical and commercial review, but its legal status and required content differ from an SDS. Check destination rules and the contract.
Can an SDS replace a TDS?
No. The SDS communicates hazards and safe handling; it does not provide a complete application or performance recommendation.
Does a COA prove API licensing?
No. API licensing should be checked in API’s current EOLCS directory. A COA reports selected tests for a batch.
Should every shipment have a COA?
That depends on the purchase agreement and risk level. If required, define the test plan and whether the COA must be approved before shipment.
What is the difference between a typical value and a specification limit?
A typical value describes expected product data and can vary. A specification limit is an agreed acceptance boundary used for release or rejection.
Which document should be translated?
Labels and SDSs often have destination-language requirements. TDS and COA translations should preserve identifiers, units, methods and claim wording exactly.
How often should document revisions be checked?
Check before each new order, label reprint, specification change and regulated-market launch, and require the supplier to notify you of changes.
Sources & References
- UNECE — Globally Harmonized System of Classification and Labelling of Chemicals, Rev. 11 (2025).
- U.S. OSHA — 29 CFR 1910.1200 Hazard Communication.
- U.S. OSHA — Hazard Communication Standard: Safety Data Sheets.
- European Chemicals Agency — Safety Data Sheets.
- American Petroleum Institute — Engine Oil Licensing & Certification System.
- American Petroleum Institute — EOLCS Licensee Directory.
- KATMOTO — K9 ECO 0W-20 product information.
- KATMOTO — K9 ECO 5W-30 product information.
Build a traceable lubricant import file before production
Send KATMOTO the target market, engine-oil grades, performance wording, pack sizes and private-label plan. We can align product selection and the document list needed for a controlled quotation review.
