{"id":657,"date":"2026-08-25T13:47:02","date_gmt":"2026-08-25T05:47:02","guid":{"rendered":"https:\/\/www.katmoto.com\/2026\/08\/25\/lubricant-tds-vs-sds-vs-coa-importer-checklist\/"},"modified":"2026-08-25T13:47:02","modified_gmt":"2026-08-25T05:47:02","slug":"lubricant-tds-vs-sds-vs-coa-importer-checklist","status":"publish","type":"post","link":"https:\/\/www.katmoto.com\/zh\/2026\/08\/25\/lubricant-tds-vs-sds-vs-coa-importer-checklist\/","title":{"rendered":"Lubricant TDS vs SDS vs COA: An Importer\u2019s Document Checklist"},"content":{"rendered":"
\n

Written and technically reviewed by:<\/strong> Leo Zhuang \u2014 Automotive Lubricants Product Lead
Published:

\n

Quick Answer<\/h2>\n

A TDS, SDS and COA answer three different purchasing questions. The technical data sheet describes the product\u2019s 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]<\/a> [2]<\/a><\/sup><\/p>\n<\/section>\n

\nTable of Contents<\/strong><\/summary>\n
    \n
  1. What TDS, SDS and COA each do<\/a><\/li>\n
  2. Side-by-side document comparison<\/a><\/li>\n
  3. How to review a TDS<\/a><\/li>\n
  4. How to review an SDS<\/a><\/li>\n
  5. What a useful COA should show<\/a><\/li>\n
  6. Performance claims and licence checks<\/a><\/li>\n
  7. Seven-step document-matching workflow<\/a><\/li>\n
  8. Common importer mistakes<\/a><\/li>\n
  9. Pre-order document checklist<\/a><\/li>\n
  10. Frequently Asked Questions<\/a><\/li>\n
  11. Sources & References<\/a><\/li>\n<\/ol>\n<\/details>\n

    What TDS, SDS and COA each do<\/h2>\n

    Lubricant buyers often ask for \u201cthe certificate\u201d 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\u2019s rules. A COA is a batch record built around a defined test plan.<\/p>\n

    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.<\/p>\n

    TDS vs SDS vs COA: side-by-side<\/h2>\n
    \n\n\n\n\n\n\n\n\n
    Document<\/th>\nDecision it supports<\/th>\nWhat to expect<\/th>\nWhat it does not prove<\/th>\n<\/tr>\n<\/thead>\n
    TDS<\/td>\nApplication and product-positioning review<\/td>\nProduct name, viscosity grade, performance wording, applications, exclusions and typical properties<\/td>\nIt is not normally batch-specific and does not automatically prove an approval or licence<\/td>\n<\/tr>\n
    SDS<\/td>\nHazard, handling, storage, transport and workplace review<\/td>\nProduct identifier, supplier details, classification, first aid, handling, physical data, transport and revision date<\/td>\nIt is not an engine-performance report or a substitute for the TDS<\/td>\n<\/tr>\n
    COA<\/td>\nBatch release or pre-shipment conformity review<\/td>\nBatch number, production\/sample date, test method, specification limits where agreed, actual results, units and release status<\/td>\nIt proves only the reported batch and tests; it does not replace performance testing or licensing evidence<\/td>\n<\/tr>\n
    API\/OEM directory evidence<\/td>\nVerification of a licensed or approved claim<\/td>\nCurrent marketer\/product\/grade\/category listing or a verifiable approval reference<\/td>\nA logo image, supplier letter or TDS sentence alone is not equivalent to a directory listing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    How to review a lubricant TDS<\/h2>\n

    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. \u201cMeets performance requirements,\u201d \u201csuitable for use\u201d and \u201cofficially licensed\/approved\u201d describe different evidence positions. Do not shorten one into another when translating a label.<\/p>\n

    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.<\/p>\n

    The published pages for KATMOTO K9 ECO 0W-20<\/strong><\/a> and KATMOTO K9 ECO 5W-30<\/strong><\/a> 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]<\/a> [8]<\/a><\/sup><\/p>\n

    \"KATMOTO
    Use the exact product code, viscosity and pack shown on the quotation when matching the TDS and label artwork.<\/figcaption><\/figure>\n

    How to review an SDS for the destination market<\/h2>\n

    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]<\/a><\/sup><\/p>\n

    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]<\/a> [3]<\/a> [4]<\/a><\/sup><\/p>\n

    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 \u201cnon-hazardous everywhere\u201d from an SDS prepared for one jurisdiction.<\/p>\n

    What a useful COA should show<\/h2>\n

    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.<\/p>\n

    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.<\/p>\n

    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.<\/p>\n

    \"KATMOTO
    A batch COA should identify the exact finished product and lot shipped, not merely a similar 5W-30 formulation.<\/figcaption><\/figure>\n

    Performance claims and licence checks<\/h2>\n

    API\u2019s 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]<\/a> [6]<\/a><\/sup><\/p>\n

    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\u2019s current list where one exists.<\/p>\n

    Seven-step document-matching workflow<\/h2>\n
      \n
    1. Freeze the quotation: product code, formulation, viscosity, performance wording, pack, label language and destination.<\/li>\n
    2. Match the current TDS to the quoted SKU and record its revision.<\/li>\n
    3. Review the destination-market SDS, including language, contacts, classification, transport and revision date.<\/li>\n
    4. Verify licensed or approved claims in the relevant official directory; save dated evidence.<\/li>\n
    5. Agree the COA test plan, methods, units, limits and batch timing before production.<\/li>\n
    6. Compare final label, carton, TDS, SDS, COA, invoice and packing list for identical product identity.<\/li>\n
    7. Retain the approved document set with the batch and shipment record for traceability.<\/li>\n<\/ol>\n

      Common importer mistakes<\/h2>\n