COA, TDS, SDS and Test Reports: A Pet Supplement Documentation Guide

The short answer is: a TDS defines the product or material version, an SDS communicates applicable handling hazards, a COA reports selected results for the item it identifies, and a test report records the testing event in more detail. The question is not merely whether each file exists, but whether that file fits the decision you need to make.

Suppose you are reviewing a pet supplement ingredient supplier. The supplier sends you a folder containing TDS.pdf, SDS.pdf, COA.pdf and Test-Report.pdf. At a glance, the file set looks complete.

Now answer three questions: Which document controls the specification? Does the COA cover the batch that will actually ship? Who produced the result marked “Pass,” and by which method?

If you cannot answer those questions, the “complete” document package has not yet started doing its job.

Here is a real example from an Anivor inquiry. Last year, a European client asked us about a batch of pet fish-oil ingredient. The supplier’s quality-document package looked complete: a Technical Data Sheet, a Safety Data Sheet and a Certificate of Analysis. The review stopped at the first step, however. The production batch shown on the COA predated the quotation by eight months. A further check found that the TDS was two years old and its EPA/DHA specifications had since been updated.

The mismatch was between the current quotation, document revision and batch reference; it did not establish that the files were fabricated.

The practical starting point is to identify the decision you need to make, then find the document that can support it. Different decisions require different documents:

• What is this material or product supposed to be? Start with the technical data sheet or specification information.
• Does it require particular workplace handling or hazard communication? Check whether an applicable safety data sheet is available or required.
• What results are reported for the referenced material, sample or batch? Review the certificate of analysis.
• Who tested what, by which method, and what did they find? Review the underlying or related test report where it is available and relevant.

None of these documents, by itself, establishes complete regulatory compliance, market approval, clinical efficacy or that every possible risk has been tested. Their value depends on what they cover and whether they match your project.

On this page

The four documents at a glance

Document	Main question it helps answer	Common scope	What to check first
Technical Data Sheet (TDS)	What technical information describes this material or product?	A product, ingredient, grade or version	Exact name, version/date, units, stated properties and intended scope
Safety Data Sheet (SDS)	What hazard and safe-handling information applies?	A substance or mixture under the applicable hazard-communication framework	Product identifier, supplier, revision date, hazard classification and handling/storage sections
Certificate of Analysis (COA)	What specifications or results are reported for the referenced item?	A raw material, sample, lot or finished-product batch	Item identity, lot/sample reference, tests, specifications, results, units, dates and issuer
Test report	What testing was performed and what were the reported results?	The specific sample submitted to a named laboratory or testing function	Sample identity, laboratory, method, dates, results, units, limits and report status

Templates and names vary. Treat this table as a routing tool, then read the actual document and confirm its scope. The sections below explain what each document can support and what it cannot establish for you.

In the fish-oil example, the TDS should have identified the current EPA/DHA specification and its revision; the COA should have identified the material or batch represented by its results; an SDS would have answered applicable handling questions rather than batch quality; and a related test report, where available, could have shown the sample, method and underlying results. The review failed before those files could support a decision because the TDS version and the COA batch reference did not align with the current quotation.

What a TDS can—and cannot—tell you

A Technical Data Sheet usually summarizes technical information for an ingredient, material or finished product. Depending on the supplier and product, it may include identity, composition or grade information, physical properties, recommended storage, shelf-life information, use guidance or typical values.

TDS content and structure vary between suppliers. A document called a TDS may contain firm specifications, typical values, general product information or a mixture of these. Organize your review around the following questions rather than assuming that every supplier uses the same fields:

1. What exact product, grade and format does this sheet cover?
2. Is each value a specification, a typical value or a descriptive statement?
3. What units and test conditions apply?
4. What is the revision date, and is this the version used for the current project?
5. Does a separate approved specification control purchasing or release decisions?

A TDS can help define the product you are discussing. It does not show that the particular batch you will receive was tested and met the listed values.

What an SDS is for

A Safety Data Sheet communicates hazard, protection, storage, handling, exposure-response and related workplace safety information where the relevant hazard-communication rules apply. Under the US Occupational Safety and Health Administration Hazard Communication Standard, covered hazardous chemicals use a specified 16-section SDS format. In the European Union, the format, content and supply conditions are addressed under a different framework described by the European Chemicals Agency. Confirm the rules for the destination and use rather than treating either framework as a universal requirement for every pet supplement or finished product.

The first question is therefore not “Where is the SDS?” It is “Does an SDS apply to this substance, mixture, use and destination, and which jurisdiction’s requirements are being used?”

If an SDS is supplied, match the product identifier and supplier, check its revision date, and review the sections relevant to hazards, first aid, handling, storage, exposure controls and transport. If the document says a product is not classified as hazardous, that statement still does not make the SDS a nutritional specification, COA or batch-release record.

What a COA can—and cannot—support

A Certificate of Analysis connects reported checks or results to the item identified on the certificate. That item might be an ingredient, a development sample, an in-process material or a finished-product lot. Do not assume which one: read the document.

At minimum, ask whether the COA shows:

• the exact material or product name and format;
• a lot, batch or sample identifier that can be reconciled with your records;
• the tests or attributes reviewed;
• the applicable specifications or acceptance criteria, where relevant;
• actual results and units rather than an unexplained “pass”;
• manufacturing, sampling, testing or issue dates, as applicable;
• the organization issuing or approving the certificate; and
• whether testing was performed in-house, by an external laboratory, or through a combination of sources.

A COA only supports the tests, specifications and item it identifies. It does not prove that unlisted contaminants were tested, that a different batch is equivalent, or that the product is approved for sale in your target market.

These checks make the COA section usable on its own.

What to look for in a test report

A laboratory test report normally gives more detail about the testing event: the sample received, the laboratory or testing function, dates, methods, results, units and any stated limits or interpretations. It may support a COA, be attached to it, or exist as a separate record. When a shelf-life decision needs evidence collected over time, use the guide to planning stability tests and documenting shelf-life decisions.

The title is not enough. A useful review asks:

• Does the report’s sample description match the ingredient, sample or batch under review?
• Who selected and submitted the sample?
• Which laboratory performed the work, and is the relevant test within its demonstrated scope where accreditation is being relied on?
• Which method was used, and is the result reported with the necessary units and detection or reporting limits?
• Is the report final, amended or preliminary?
• Who compares the result with the applicable product, market or customer requirement?

ISO/IEC 17025 addresses the competence, impartiality and consistent operation of testing and calibration laboratories. The linked ISO page is the official standard overview; access to the complete standard may require purchase. Accreditation can add useful confidence when its scope covers the relevant work, but it is not a product approval and should not be treated as one.

Anivor’s Testing & QC page explains how testing questions, available reports and review responsibilities can be coordinated within a project.

Why the documents cannot be used interchangeably

Consider an ingredient proposed for a calming soft chew:

• The TDS may describe the ingredient grade, technical properties and storage conditions.
• The SDS, if applicable, may explain workplace hazards and safe handling.
• The COA may show selected results for the supplied lot against listed specifications.
• A test report may provide the laboratory’s methods and numerical findings for the submitted sample.

Sending an SDS in response to a request for batch test results leaves the batch question unanswered. Sending a COA without the applicable specification may make “pass” difficult to interpret. Sending a TDS for one grade when the quotation covers another creates an identity and version problem.

The US Food and Drug Administration’s animal-food cGMP guidance illustrates the broader distinction: reviewing specifications or guarantees and performing relevant sampling or testing are different ways a facility may examine incoming materials. The appropriate combination depends on the material and the facility’s controls; the guidance does not create a universal document bundle for every project.

A five-step documentation check

1. 01Match the object
2. 02Match the version
3. 03Match the sample or batch
4. 04Match the scope
5. 05Assign review responsibility

Apply the following five checks to the files you receive. This is a buyer-side document review checklist, distinct from Anivor’s broader project coordination process.

1. Match the object

Is the document about a raw ingredient, packaging material, development sample, in-process material or finished product? Confirm the exact name, grade, dosage form and supplier or manufacturer named in the file.

2. Match the version

Record the issue or revision date. Confirm that the TDS, SDS or specification belongs to the version currently quoted or sampled. Keep superseded files for traceability rather than silently replacing them.

3. Match the sample or batch

For a COA or test report, reconcile the lot, batch or sample identifier with the physical sample, production record, invoice or other project record. A sample COA can show the expected format before an order; it is not the production-batch COA.

4. Match the scope

List what the document actually covers. Which attributes or analytes were tested? Which specifications, limits, methods and units apply? What is missing from the decision you need to make?

If the remaining gap concerns the manufacturing site or the connection between records and production, use the same-batch traceability check during a factory visit to plan the next verification step.

5. Assign the review responsibility

Record who supplied the document, who checks technical consistency, who reviews target-market requirements, who approves exceptions and who keeps the final version. Document collection and document approval are different responsibilities.

For an Anivor-coordinated project, Anivor coordinates the agreed document request and version handoff. The manufacturer or laboratory remains responsible for the record it issues. The buyer and its appointed advisers remain responsible for final market, compliance and approval decisions. See Quality & Documentation for the service scope and responsibility boundaries.

Turn a document mismatch into a focused follow-up

Record the mismatch, the decision it affects and the record needed to resolve it. Send one consolidated request naming the document and version or batch reference, then agree who will review the response and by when.

What you find	What to request next	Who to ask and what to record
TDS revision or grade does not match the quotation	The technical sheet or approved specification for the quoted version, with the changes identified	Ask the supplier’s technical contact; record the version your reviewer will use.
COA identifies a different sample or batch	An explanation of the item the results represent and the relevant batch-specific documents available for your order	Ask the supplier’s quality contact; keep the affected batch decision open until the references reconcile.
A result says “Pass” without enough context	The applicable specification or acceptance criterion, result and unit, method or reference, and issuer	Ask the issuer through the agreed supplier contact; assign the technical review owner.
A laboratory report cannot be linked to your sample	The sample description and submission or receipt references linking the report to the item reviewed	Ask the submitting supplier and, through the agreed channel, the laboratory; record the missing connection.
An SDS was sent in place of batch-quality evidence	The relevant COA or testing information, while retaining any applicable SDS for handling questions	Ask the document supplier to separate the requests; record which question each file answers.

Close the item when the responsible reviewer has checked the returned evidence against the question. If the response is only a partial example, keep its limits visible in the review record.

Five common myths in document review

In practice, the problem is often not that a file is missing. It is that a file is being used to answer the wrong question. These are five common mistakes we have observed in project discussions.

#	Common myth	Why it is wrong	Better approach
1	“The supplier provided an SDS, so the product meets safety standards.”	An SDS addresses workplace hazard communication. A statement that a product is not classified as hazardous does not show whether contaminants were tested or whether the product meets a market specification.	Use the SDS for hazard classification, handling and storage. Use the COA and relevant test reports to review the specified quality and safety tests.
2	“The COA says ‘Pass,’ so the batch is acceptable.”	An unexplained “Pass” cannot be assessed. Pass against which specification? What was the reporting limit? Which batch was tested?	Ask for the identified item and batch, test, specification or acceptance criterion, actual result and unit, method or method reference, and issuer. If essential context is missing, treat the conclusion as unverified until it is clarified.
3	“The TDS lists the specification, so we can receive the batch against it.”	A TDS describes the relevant product or ingredient version; it does not report what was found in the particular batch received. Version mismatch creates another risk: the quotation may cover one grade while the TDS covers another grade or an older revision.	Use the TDS or approved specification to define what the product should be, and the applicable batch evidence to review what was reported for the batch. Do not base a receiving decision on the TDS alone.
4	“The result came from an ISO/IEC 17025-accredited laboratory, so it can be accepted without further review.”	Accreditation concerns a laboratory’s competence for activities within its scope. It is not product approval, does not show that the relevant test is within scope, and does not establish that the sample matches your batch.	Ask whether the test is within the accredited scope, whether the report is final and whether the sample identifier matches your batch. Accreditation can add confidence; it is not a waiver of document review.
5	“The document package is complete, so the project is in order.”	A file set can contain all four document types and still fail to match the current version, actual batch, relevant attributes or appropriate testing scope. The unit of review is the decision, not the folder.	Return to the five checks: object, version, sample or batch, scope and responsibility. The folder contains evidence to review; it is not the conclusion.

What to request at each project stage

If the product direction and project requirements are still being defined, start with the eight-part pet supplement manufacturing brief before requesting detailed documentation.

If the development route is still open, compare private label and custom formulation before requesting route-specific records. If the dosage format is still being shortlisted, use the soft-chew, powder and liquid guide to connect serving, packaging and sample findings with the documents you request.

Project stage	A focused request might include
Ingredient or supplier screening	Current technical/specification information; applicable SDS; representative COA or testing information; supplier and manufacturing-site records relevant to the review
Sample review	Exact sample/version identification; relevant technical information; agreed sample checks; test reports where testing was commissioned
First production order	Approved product and packaging specifications; production-lot references; agreed COA and testing scope; responsibilities for release and document approval
Ongoing orders	Batch-specific documents agreed for each order; controlled versions of TDS/SDS/specifications; change notifications and retained approval records
Target-market review	Documents requested by the responsible importer, brand, marketplace, retailer, regulator or professional adviser for the specific product and destination

This is a planning list, not a universal mandatory package. The required evidence changes with the ingredient, format, claims, market, sales channel and responsibilities agreed among the parties.

Turn a generic request into a usable one

A planning checklist still needs to be translated into a request a supplier can act on. Instead of writing “Please send all certificates,” use a request such as:

Adjust the request to your project and avoid asking for confidential documents without first defining why they are needed and who may receive them.

Drafting the request is only the first step. Someone still needs to collect the files, check each one and identify the gaps. That is the role Anivor takes when coordinating project documentation.

Sources

• OSHA Hazard Communication and Safety Data Sheets, Appendix D
• European Chemicals Agency: Safety Data Sheets
• FDA Guidance for Industry #235: Current Good Manufacturing Practice Requirements for Food for Animals
• ISO/IEC 17025:2017