How to Read a Supplement Certificate of Analysis (COA)

Start with the document identity block

Start by identifying what the issuer calls the document. Under U.S. dietary-supplement CGMP rules, the cited certificate-of-analysis provision concerns a supplier-provided certificate for a component; a laboratory may separately issue a test report or certificate for a submitted finished-product sample. MIHEN must not rename one document as the other. Its transcription template records the issuer, document title, unique report identifier, issue date, page references, and any revision wording that the document actually displays.

For a report represented as operating under ISO/IEC 17025, use the standard's reporting framework and the laboratory's own form rather than inventing a universal COA layout. Headers, pagination, repeated identifiers, revision notices, and authorization fields are captured only when present. A logo, screenshot, or cropped result row does not by itself establish who performed the work or whether the full report was reviewed. Record the retrieval source and date; MIHEN's file hash and completeness fields are editorial controls, not claims that a regulation requires that exact public workflow.

Identify the product, lot, and submitted sample

Identify the item or sample exactly as the report describes it. Capture product or material name, item code, laboratory sample identifier, client-supplied lot or batch value, package description, client identity, and receipt or test dates only when those fields appear. Keep a laboratory sample identifier separate from a production lot. For U.S. finished dietary supplements, the batch production record is the primary cited rule that connects a finished batch to lots of packaged and labeled product; a laboratory report alone does not create that manufacturing link.

Transcribe identifiers exactly, including punctuation, leading zeros, suffixes, and spaces. State whether the report says the laboratory sampled the material or received a client-submitted sample, without inferring an undocumented chain of custody or representativeness. FDA's component-COA provision should not be used to imply that a retail finished package was tested. If a component certificate appears beside a finished product, label the matrix as component and leave the package connection unresolved unless the report and the manufacturer's traceability records explicitly establish it.

Read the result table as a set of linked fields

Read each result as the set of fields the document actually links. The U.S. component-COA provision expressly calls for the test or examination methods, test limits, and actual results. An ISO/IEC 17025 report may also present an item or analyte, result, unit, method, specification, qualifier, uncertainty information, or conformity statement as applicable to that report. Preserve symbols such as less than, greater than, not detected, and not tested; replacing one with zero or a blank changes the reported statement.

A reported result, a specification limit, and a conformity statement are separate fields. ILAC G8 explains that a conformity statement is tied to identified results, the specification or standard, and the decision rule applied. Therefore, do not translate pass into a free-standing product claim, and do not invent the source of a limit that the report does not name. MIHEN can transcribe what criterion the issuer used and flag an unstated decision rule without deciding that the criterion is suitable for a health purpose or another jurisdiction.

Keep methods, units, and qualifiers attached

Method identifiers may refer to an official compendium, a regulator method, a published standard, or an internal laboratory procedure. Copy the complete identifier, revision, and modifier when available. A familiar instrument name is not the same as a complete method, because preparation, extraction, calibration, calculation, and reporting rules also shape a result. When a certificate states only a short method label, report that limited description rather than expanding it from assumptions or from a different laboratory's procedure.

Units and reporting bases require equal care. A value may refer to mass per capsule, mass per serving, concentration in a prepared sample, percentage by weight, count per gram, or another basis. Do not convert between bases unless the certificate provides every required input and the conversion has been independently checked. Qualifiers, footnotes, detection limits, and uncertainty statements belong with the row they modify. Detaching a result from those notes can create false precision even when the copied number itself is accurate.

Check authorization, laboratory identity, and scope

The closing block may name an analyst, reviewer, laboratory director, or authorized signatory and may include an electronic approval record. Record the role, date, and signature status without publishing personal contact details that are not necessary for verification. An unsigned draft, preliminary result, or customer portal preview should remain labeled as such. An authorized signature shows that the issuer completed its stated approval process; it is not a universal guarantee about sampling, accreditation, market compliance, or every product claim.

If the certificate displays an accreditation symbol or certificate number, verification is a separate task. The laboratory's identity, accreditation status, issuing accreditation body, and detailed scope should be checked in the relevant official directory. Accreditation can cover particular locations, fields, matrices, or methods rather than every service offered by the organization. Record verified, not located after a documented search, expired, or scope unresolved as distinct evidence states. Do not convert the mere appearance of an accreditation mark into a broader quality conclusion.

State the certificate's evidence boundary

A careful summary identifies the document type, issuer, named sample or component, client-supplied lot when shown, tests listed, dates, and any unresolved package link. It can report a conformity statement only in the scope in which the issuer presents it and, where relevant, with the named specification and decision rule. It should not rewrite that narrow statement as proof that every package was tested, that future lots are identical, that an issuer endorses the brand, or that a product has a particular health effect.

Use an evidence table with direct transcription, source page, verification status, and limitation for each important claim. Preserve the original certificate link where publication rights allow, but avoid presenting an isolated cropped row without context. Schedule a review when a replacement certificate, revised method, corrected result, or new lot appears. If identifiers cannot be matched, the accurate conclusion is that the connection remains unresolved. A useful COA guide makes the verification trail reproducible and the uncertainty visible rather than turning a technical report into a promotional badge.

• Record the issuer, report number, issue date, revision, and page count.
• Match repeated identifiers and pagination across the complete document.
• Transcribe product, lot, sample, and material identifiers separately.
• Keep every result attached to its method, unit, specification, and qualifier.
• Record who supplied or collected the sample when the certificate states it.
• Distinguish draft, preliminary, revised, and authorized versions.
• Verify any accreditation claim in the issuer's official directory and scope.
• Publish unresolved links and evidence boundaries instead of a product verdict.