How to Read a Certificate of Analysis

A Certificate of Analysis, often called a COA, records laboratory test results for an identified sample. A page of numbers can look complicated at first. Reading it in a set order makes it easier to understand what was measured and what the report actually says.

Begin with the details that connect the document to the sample. Then move to the test tables, their units and the laboratory’s notes.

Start with the sample details

Look for the sample name, sample type, batch or lot identifier, and laboratory name. A sample ID may be the laboratory’s own reference number. Do not assume that it is the same as the batch number printed elsewhere.

Compare the available identifiers before reading the results. If the names or numbers differ, ask the issuer to explain the connection. A similar name alone does not establish that two records refer to the same material.

Give each date its own meaning

A report may show several dates. The collection date records when the sample was taken. The received date records when the laboratory received it. The reported date identifies when the report was issued. Check the report status as well: a document marked as preliminary should not be read as a final report.

Keep these dates separate in your notes. A report date is not automatically a manufacture date or an expiration date.

Read the column headings before the numbers

A test table lists the substances or properties examined, often called analytes, alongside results and other details. Read the full row, including the unit and any footnote marker.

Milligrams per gram, milligrams per milliliter and percentages express quantities in different ways. A number without its unit is incomplete. Before comparing two results, confirm that they describe the same substance, use compatible units and refer to the same reporting basis.

Understand the small abbreviations

LOD: the limit of detection, which concerns the smallest amount a method can distinguish from background.
LOQ: the limit of quantification, which concerns the smallest amount the method can measure reliably.
ND: commonly used for “not detected.” Read the report’s legend to confirm how that laboratory uses it.

“Not detected” is not the same as a proven quantity of zero. A result below a stated limit also should not be treated as an exact measurement. The method and reporting limits give those entries their meaning.

Keep the conclusions within the report

Check which tests appear and whether the document includes additional pages. A pass or fail entry relates to the test and criteria identified in that report. Do not extend it to properties that were not examined.

Save the complete document when you need a record. A cropped screenshot can remove the sample details, units or notes needed to interpret a result. If a field remains unclear, ask the issuing laboratory about that specific field and include the report number.

Sources: The New York Office of Cannabis Management explains common COA fields; Health Canada explains detection limits, units and reporting; and California’s Department of Cannabis Control describes test categories and COA results. These references explain document terminology; requirements vary by context.

What a Batch Number Can Tell You

A batch number can be easy to overlook. It may sit near a barcode, appear on a small sticker or share space with other package details. Yet that short code can be one of the most useful references when you are trying to connect an item with its records.

The key is to treat a batch number as an identifier. Its value comes from the information linked to it, not from how much you can guess from the characters.

A batch identifies a group

In a recordkeeping system, a batch or lot number helps distinguish one group of a product from another. Several items can share that identifier. It does not usually identify one individual item on its own.

GS1’s traceability standard separates three levels of identification: the product type, a particular batch of that product, and a single item. Each level answers a different question. Knowing the product type does not tell you which batch it belongs to, and knowing the batch does not necessarily distinguish two items within it.

Keep the different codes separate

Packages and records can carry several references. Read the description next to each one before assuming they serve the same purpose.

Product identifier: identifies a product type or version in a particular system.
Batch or lot number: identifies a group within the relevant records.
Serial number: identifies an individual item when used with its product identifier.
Date field: records the event described by its label, such as production or packing.

A barcode is a way to encode information. It is not itself a guarantee that the encoded information includes a batch number. Different barcode formats and applications carry different data.

A code needs its surrounding records

Traceability works by connecting identifiers with recorded events and details. As one example, the FDA’s food traceability guidance describes a lot code as a link to other information held in the relevant records. That example illustrates the recordkeeping concept; it does not establish which rules apply to any other product category.

This is why an unexplained code cannot provide a complete history by itself. A business may use a date-based format, another internal system or a combination of fields. Avoid decoding a string as a date unless its issuer explains that format.

Make the reference easy to check

If you need to ask about a record, copy the full code exactly as printed. Include the product name and the label used for that field. Keep leading zeros, letters and separators. A clear photograph can help resolve characters that look alike, such as the letter O and the number 0.

When comparing a package with a document, check both the product identity and the batch reference. If a laboratory sample ID appears instead, ask how it connects to the batch. Record the explanation rather than filling the gap with an assumption.

A useful question is specific: which record corresponds to this exact identifier? That keeps the discussion focused on information that can be checked and avoids treating a batch code as proof of details it does not state.

Sources: GS1 explains the levels of product identification in its Global Traceability Standard and the information encoded in GS1 barcodes. The FDA’s traceability lot code guide provides a food-sector example of linking codes to records.

Why Clear Label Information Matters

A label does several jobs in a small space. It identifies an item, gives quantities and provides references that can connect the package with more information. When those details are clear, the reader spends less time guessing what a number or code means.

Clear information is more than large text. It also depends on useful headings, complete units and a clear connection between each statement and the thing it describes.

Start with identity, quantity and responsibility

NIST’s guidance on packaged goods highlights three basic kinds of label information: the identity of the product, the quantity in the package, and the responsible business. These are useful starting points when reading a label, even though the details and requirements differ across product categories.

Find the descriptive name as well as the brand name. Then locate the quantity statement and business information. Each answers a different question: what the item is, how much is included, and which business is identified on the package.

Read the words around a quantity

A large number can attract attention while leaving its meaning unclear. Read the full statement, including the unit and what the number refers to. An amount for the whole package differs from an amount stated for an individual item.

Net quantity refers to the contents rather than the packaging material. NIST’s labeling guide discusses declarations by weight, volume, count and other measures. These describe different properties, so a count should not be treated as a weight or a volume.

When two quantities appear together, check whether they are equivalent units for the same amount or separate statements. Keep the nearby wording when taking notes. Copying only the largest number can remove the context needed to understand it.

Separate names, codes and dates

A label may include a descriptive name, an internal reference, a batch number and a date. Their appearance does not tell you their purpose. Look for a heading or short explanation beside each field.

If a date has no description, do not assume that it marks manufacture, testing or expiration. Likewise, an unfamiliar code is not a self-explanatory date. Ask the issuer to identify the field if the printed information does not make its meaning clear.

Follow digital information carefully

A barcode or QR code can carry identifiers or provide access to online information. GS1 describes how two-dimensional barcodes can include details such as a product identifier and batch or serial number. The information available depends on what the code contains and how the destination is set up.

After opening a linked page, compare its product details with the label in front of you. If you expected a document for a particular batch, check that the batch reference appears. Reaching a general information page does not by itself establish that connection.

Keep a complete reference

When requesting clarification, include the full field you are asking about, its unit or heading, and enough of the label to identify the item. A photograph of the relevant panel can be more useful than a cropped number.

The goal is a clear connection between the package, its statements and any supporting records. Good questions focus on the missing link: what does this field describe, and where is the explanation that goes with it?

Sources: NIST explains core label information in its packaging and labeling FAQs and quantity statements in its consumer package labeling guide. GS1 describes digital product information in its two-dimensional barcode guideline.