RFQ

TECHNICAL DOCUMENTS

Titanium Dioxide TDS, SDS & COA: What to Request

Choose the document types and product context your team needs for technical, safety or batch-quality review, then submit them in one request.

What is the difference between a TDS, SDS and COA?

A TDS supports Grade-level technical evaluation, an SDS provides safety and handling information for the relevant product, jurisdiction and language context, and a COA reports results for a specific lot or batch. Select one or more document types and add the product, Grade, revision, language, lot, batch or order details relevant to your review.

CHOOSE BY REVIEW NEED

Choose the Documents That Match Your Review

Start with the decision your team needs to make. You can choose one document type or combine several in the same request.

Multiple document needs

Select one or more document types and include the relevant product or transaction context in one request.

Select more than one

ADD PRODUCT CONTEXT

Add Product Grade Details to Your Request

Select the primary Grade for this request. Selecting a Grade adds product context to your request; it does not indicate document availability.

Additional Grades can be included as supporting context for review.

DOCUMENT COMPARISON

Compare TDS, SDS and COA

Each document supports a different review. Use the comparison below to choose the relevant type and prepare useful context.

DimensionTDSSDSCOA
Primary buyer useTechnical evaluationSafety and handling reviewLot- or batch-specific quality review
When to requestWhen reviewing Grade-level technical informationWhen reviewing safety and handling information for the relevant product and market contextWhen reviewing results tied to a specific lot, batch or order context
Typical scopeGrade + revisionProduct + jurisdiction/language + revisionLot/batch/order
Useful request contextProduct Grade; revision if relevantProduct; market or jurisdiction; language; revision if relevantProduct or Grade plus an available lot, batch or order reference

TDS

Primary buyer useTechnical evaluation
When to requestWhen reviewing Grade-level technical information
Typical scopeGrade + revision
Useful request contextProduct Grade; revision if relevant

SDS

Primary buyer useSafety and handling review
When to requestWhen reviewing safety and handling information for the relevant product and market context
Typical scopeProduct + jurisdiction/language + revision
Useful request contextProduct; market or jurisdiction; language; revision if relevant

COA

Primary buyer useLot- or batch-specific quality review
When to requestWhen reviewing results tied to a specific lot, batch or order context
Typical scopeLot/batch/order
Useful request contextProduct or Grade plus an available lot, batch or order reference

The details in the final row are useful context, not a requirement to know every item before starting a request.

PREPARE USEFUL CONTEXT

What to Include in Your Request

Share the details you already know. You do not need every item before starting a request.

  • Product Grade

    Select the primary Grade for the request.

  • Document type(s)

    Choose TDS, SDS, COA or more than one type.

  • Market or jurisdiction

    Add it when relevant to the review.

  • Language

    Include the required language when relevant.

  • Revision

    Identify it if a specific version is required.

  • Lot, batch or order reference

    Add an available reference when the request concerns transaction-specific results.

  • Additional requirements or questions

    Share other useful, non-confidential context, including other relevant Grade names.

Required fields are shown on the Request Documents form.

FOUR REVIEW STEPS

How Document Requests Work

Use one request to identify the documents and product context your team needs.

  1. 01

    Choose document types

    Select TDS, SDS, COA or more than one document type.

  2. 02

    Add product context

    Choose the primary Grade and include any useful revision, language, lot, batch or order details you know. Add other relevant Grade names as supplementary context when needed.

  3. 03

    Review your request

    Check the information carried into the request form. You can change or remove prefilled buyer context before submitting.

  4. 04

    Submit for review

    Send the request with your contact and business details. We may contact you if clarification is needed.

Document requests are reviewed after submission; submission does not confirm availability or delivery.

PRACTICAL ANSWERS

Questions Buyers Ask

CONTINUE YOUR DOCUMENT REVIEW

Related Document Paths

Continue to another document topic or return to the complete Documents overview.

DOCUMENT REQUEST

Request the Documents Needed for Your Review

Choose one or more document types, add the relevant product or transaction context, and review the details before submitting.