Buying Metals Online: COA, SDS and TDS Documents to Request
Buying metals online starts with a clear specification and the right supporting documents. For USA and international metals buyers, a clear documentation request helps connect purchasing, engineering and receiving teams. Gallium Global, LLC reviews document requirements with the material specification so the proposed supply can be evaluated against your acceptance criteria.
On this page
On this page
COA vs SDS vs TDS is a practical distinction for anyone reviewing a metals or compounds quotation. Each document answers a different question: what was analysed, what safety information applies, or what the product is generally intended to meet. Request the right document for the stage of the enquiry rather than treating the three names as interchangeable.
COA SDS TDS: compare the purpose of each document
| Document | Main purpose | Review focus |
|---|---|---|
| COA — Certificate of Analysis | Reports analytical information for the identified sample or lot. | Identity, reference, test results, units and specification limits. |
| SDS — Safety Data Sheet | Communicates product safety, handling and related information. | Correct product identity, revision and applicable supplier information. |
| TDS — Technical Data Sheet | Describes general product characteristics and technical specifications. | Grade, properties, forms, test basis and the scope of stated values. |
A document title alone is not enough. Read its scope and references, and confirm that it relates to the material, grade and supply being reviewed.
COA SDS TDS: review a COA against the acceptance specification
Start with the material name, lot or sample identifier and grade. Compare each reported result with the corresponding acceptance limit. Check units carefully; the same numerical value has a different meaning when expressed as percent, ppm or another unit.
Ask which analytical methods were used and what any detection or reporting limit means. If a critical element is absent from the report, do not assume it was tested or passed. Request clarification before treating the document as evidence for that requirement.
A representative or sample COA can help an initial technical review. That COA should not be treated as the batch evidence for a different lot. Confirm the documentation that will accompany the offered or shipped material.
COA SDS TDS: use the SDS for the correct product and grade
Check that the SDS product identity agrees with the quotation and packaging information. A metal, its oxide and a different compound are separate product identities; a document for one should not be assumed to cover another.
Confirm the revision and supplier details and have the relevant receiving, transport and site teams review the document. Packaging and transport arrangements depend on the actual product, shipment route and applicable requirements. An SDS is not a purity certificate or confirmation of every analytical acceptance limit.
COA SDS TDS: read the TDS as general technical information
A TDS helps describe the product offered, such as nominal grade, physical form, particle-size information or dimensional scope. Determine whether a value is a typical observation, a target, a limit or a guaranteed characteristic in the agreed specification.
For application-critical properties, ask for the measurement method, units and tolerance. General product literature should support the discussion, while the accepted specification and order documents define the proposed supply.
See our purity-grade guide for the difference between nominal N notation and an impurity specification.
COA SDS TDS: build a document checklist before ordering
- Identify the exact material, grade and physical form.
- Provide the receiving specification and required tests.
- Separate representative documents from lot-specific evidence.
- State any origin, traceability or independent-inspection requirements.
- Agree which documents are needed for review, shipment and receiving acceptance.
Origin documentation and inspection reports have their own purpose. Do not treat a COA or SDS as a substitute for a separately required origin or inspection document.
Discuss your quality documentation requirements with sales@galliumgloballlc.com, or include them in a materials quotation request. Availability and timing must be confirmed for the specific enquiry.
Further reading on COA and SDS terminology
The NIST reference-material definitions provide background on reference-material certificates. For the structure of safety information, see OSHA’s safety data sheet guide (PDF).
Use these resources alongside the quality documentation overview and the document requirements agreed for your own enquiry.
COA vs SDS vs TDS across the buying process
A useful document review follows the progress of the enquiry. At the initial stage, the buyer needs enough information to determine whether the proposed product belongs on a shortlist. A technical data sheet can help explain the product description, available form and specification scope. A representative certificate of analysis can show how results are presented. Keep the purpose of those early documents clear so that reference information is not confused with evidence for a shipment that has not yet been allocated.
During technical approval, compare the documents against your own requirements line by line. Record the document title, revision or issue date, product description and reference number. Where the terminology differs from the purchase specification, ask for a written explanation. For example, a table expressed in percent should be compared carefully with limits expressed in ppm, and a result without a stated basis may need clarification before acceptance.
Separate missing information from a failed result
A blank field, an omitted element and a reported value above a limit are different findings. Do not turn an omission into a pass or a failure without asking what was tested and what the document covers. Send focused questions that identify the exact row, parameter or property requiring clarification. This is more useful than requesting “better documents” without explaining what your team needs to decide.
For a COA, review whether the listed limits match the agreed acceptance specification and whether the sample or batch reference is identifiable. For a TDS, distinguish general characteristics from values explicitly included in the offer. For an SDS, check that the material identity corresponds with the proposed product. These checks support different decisions, even when the documents are reviewed by the same purchasing team.
Create a clear document handover
Before dispatch, agree who will receive the final document package and how the records will be delivered. A purchasing contact, a warehouse team and a technical reviewer may need different information. Identify the required references so the receiving team can connect the delivery with the purchase order, packing information and applicable analytical records. Resolve any request for translations, additional copies or independent reports during the quotation stage.
When a document is revised, retain the version used for the approval decision and identify what changed. Avoid circulating multiple unnamed files with no clear relationship to the offered material. A simple document register can list the product, supplier reference, document type, revision, review status and responsible reviewer. That creates a practical record without treating every piece of product literature as a batch certificate.
If an independent laboratory report or origin document is required, name it separately in the RFQ. A request for a COA does not explain the full scope of an inspection programme, and a safety data sheet does not establish origin. Use our metals RFQ checklist to combine documentation, packaging and delivery requirements in one request.
For Gallium Global, LLC enquiries, send your document checklist with the material name, grade, quantity and destination. Our quality documentation page provides the next point of contact for reviewing what is available and what must be confirmed for the proposed supply.
COA SDS TDS before order confirmation
A COA SDS TDS review should identify what each document covers and how it relates to the material offered. Keep the material reference, document date and applicable lot or product scope with the review. Do not treat a general technical sheet as a replacement for the analytical evidence required by your specification.
Before confirming an order, record which COA SDS TDS documents are available at the enquiry stage and which relate to an allocated lot. Ask the supplier to clarify any missing reference or parameter. Retain the agreed document package with the purchase specification so your receiving team can match the delivered material to the requirements reviewed before acceptance.
A practical COA SDS TDS review worksheet
Build the review around the questions your organization needs answered before acceptance. Identify the material offered, the specification you intend to purchase against and the documents the supplier has provided. Record each document reference separately so the reviewer can see which statement comes from which source. Keep a representative example distinct from evidence associated with the proposed lot.
Use one row for each mandatory requirement. The row should show the requested limit or condition, the supplier response, the supporting document and any question still open. Do not mark a requirement as resolved merely because a document contains a similar product name. Ask whether its stated scope and revision apply to the material being offered.
| Review question | Record to retain |
|---|---|
| Which material and form does the document describe? | Complete material identity and the supplier product reference. |
| Is the information representative or connected to a particular lot? | The stated document scope and any applicable batch reference. |
| Which requirements are supported by the evidence? | Parameter-by-parameter comparison against the purchase specification. |
| Are any units, reporting statements or method references unclear? | The written clarification and the source document reference. |
| Which version controls the acceptance decision? | Revision references for the specification, offer and supporting records. |
Handover between purchasing and technical review
Assign an owner to each unresolved technical question. Purchasing may coordinate the quotation while another team reviews the material requirements. Keep both teams on the same document references. If a supplier sends a replacement attachment, identify the version it supersedes and recheck the requirements affected by the change. A price confirmation alone does not close a technical question that remains unanswered.
When the technical review is complete, record the outcome in a short acceptance note. List the documents reviewed, the specification revision and any conditions attached to the decision. Retain the supplier responses used to close questions. This gives the purchasing team a clear reference when it prepares the purchase order and reduces reliance on an informal summary of earlier conversations.
Document requirements for a new lot or repeat order
A completed COA SDS TDS review can provide a useful starting point for repeat purchasing, but it should not obscure what needs to be confirmed again. Identify which requirements remain unchanged and which documents are expected for the next offered lot. If your process requires a new lot reference or another analytical record, state that requirement in the release request rather than assuming the previous file covers it.
Keep document availability and timing explicit. Ask which records are available during the enquiry and which are associated with material allocation or shipment. If a required document is pending, retain it as an open item and identify when it must be reviewed. The commercial agreement should make any document-related acceptance condition clear before an order is confirmed.
Match the document file to receiving records
At receipt, use the agreed order references and package identification to locate the relevant document file. Record any difference between the delivered identification and the records expected by your receiving team. Follow the order-specific process for raising questions, and keep the supporting evidence with the enquiry. A well-organized file should allow another colleague to trace the sequence from the original requirement through the accepted offer to the delivered material without guessing which attachment was used.
For a new materials enquiry, send the required document list with the specification, quantity and destination through the quotation request form. A clear COA SDS TDS request helps the supplier respond to the actual acceptance requirements and gives your technical team a consistent basis for review.