COA vs. Third-Party Test Report: A Procurement Guide

01

Define the two evidence types

A certificate of analysis is normally issued within the manufacturer, quality unit, partner or authorized supply workflow and reports information for an identified material and batch. A third-party report is issued by a separate laboratory for the sample submitted to that laboratory.

Either document can be useful, but they answer different chain-of-custody questions. The buyer must know who selected the sample, who submitted it and which batch or container it represents.

02

Check the batch and sample link first

A report with the correct product name can still be irrelevant if the batch number does not match. A third-party report can be independent yet unrepresentative if the sample origin is unclear.

Before reading the headline result, match the product, batch or accession number, sample condition, dates, issuer and order.

• Product or sample name
• Batch, lot or accession number
• Sample source and submission date
• Test date and report date
• Issuing organization
• Link to the offered material

03

Read criteria and results separately

A specification or acceptance limit states the requirement. A result states what the method reported for the sample. The two should be visually and logically distinguishable.

For APIs within its scope, FDA ICH Q7 describes COA content including tests performed, acceptance limits and numerical results where tests are numerical. Outside that scope, the same separation remains a useful procurement discipline.

04

Review the method context

A purity percentage without a named method and sample reference has limited value. Ask what test was performed, which method or method reference was used, and whether the report provides enough context to interpret the result.

HPLC and mass-spectrometry data do not automatically prove the same attribute. The report should state what was measured rather than leave the buyer to infer it.

05

Distinguish internal, partner and independent issuers

An internal laboratory and a long-term manufacturing partner may be part of the supply workflow. Their records should be identified accurately rather than presented as third-party evidence.

A separate laboratory may provide greater independence, but independence alone does not establish sample representativeness or method suitability. ISO/IEC 17025 addresses competence, impartiality and consistent laboratory operation; accreditation relevance should be checked against the activity required.

06

Protect customer-owned reports

A customer may purchase material and commission testing in its own name. That report belongs to the customer’s transaction and may contain confidential information.

Redacting the customer’s identity does not make the report suitable as catalog-wide evidence. It remains linked only to the submitted sample and cannot be reused to prove another batch.

07

Apply data-integrity questions

FDA’s data-integrity guidance describes complete, consistent and accurate records that are attributable, legible, contemporaneous, original or a true copy, and accurate. The exact regulatory framework depends on the material and use, but these questions are valuable for document review.

Look for unexplained edits, missing identifiers, inconsistent dates, cropped pages or results separated from their method and sample context.

08

Specify the required evidence in the RFQ

Do not ask for a generic document package. State whether a product specification, batch COA, HPLC, MS or independent report is required for each item and when it must be available.

Stablize Peptides confirms document availability by eligible product and order. Internal and third-party records are identified separately, and customer-owned reports are not published.

RELATED GUIDANCE

Continue the procurement review