Start with the batch or lot number printed on the vial, package, or product record and copy it exactly. Use that identifier to find the corresponding entry in the PSC COA library, then confirm that the product name and batch reference on the COA agree with the material in front of you. If the document includes an independent laboratory report, its sample reference and verification record should preserve that same connection.
The lookup is a chain rather than a single matching word. The label identifies the material, the COA describes a particular batch, and the laboratory report identifies the sample it received. A report for the right compound can still be the wrong report when its sample or batch reference points somewhere else.
Start with the identifier on the material
Photograph or transcribe the product name, stated amount, and complete batch or lot number before opening another document. Preserve prefixes, hyphens, leading zeroes, and letter case where possible. Characters such as 0 and O, or 1, I, and L, are easy to misread on a small label; comparing the printed identifier with the COA filename and the identifier inside the PDF usually resolves the ambiguity.
Several codes may appear in the same documentation package, and each one follows a different object:
| Identifier | What it follows |
|---|---|
| Batch or lot number | The material produced or packaged together. This is the primary link from the label to its COA. |
| Sample or client sample ID | The portion submitted to the laboratory. The report should show how this sample connects to the supplier's batch. |
| Report or task number | The laboratory document or work order. It identifies the report, not the physical batch by itself. |
| QR code or verification key | The route to a hosted laboratory record. It helps confirm the report in the laboratory's own system. |
Batch and lot are often used as equivalent traceability terms, although the exact naming convention belongs to the issuer. A sample ID can repeat the supplier's lot number or use a laboratory-assigned code. When the lab uses its own code, the PDF needs another field, sample description, or submission record that preserves the link back to the batch.
Follow the number through the records
Search the COA library for the exact batch or lot. Open the PDF and compare the product name, batch reference, stated presentation, issue or analysis dates, and any report number shown. Product names sometimes appear in abbreviated or expanded form, so the identity should still be clear enough to rule out a different compound, amount, salt form, or product variant.
Where a third-party report offers a QR code, task number, verification key, or official lookup page, open that record and compare it with the PDF. The hosted record should agree on the report number, sample name or description, reported methods, results, and date. This step catches a copied link, an outdated PDF, or a report that exists but belongs to another sample.
The document date should also fit the record sequence. Analysis normally follows sample submission, and a revised report should carry a revision marker or date that explains why two versions exist. A later testing date may reflect a new submission or retest rather than an error, but the batch connection should remain visible instead of being inferred from timing alone.
Resolve a mismatch without guessing
When no result appears, repeat the search with the ambiguous characters checked against the label photo. Look for a supplier prefix, omitted hyphen, leading zero, or a newer product-page record. An old bookmark or cached PDF may point to a previous batch even though the current library has already changed.
If the COA and label show different identifiers, keep both records and ask for the missing link. A useful request includes the label photo, product name, full batch number, order reference where relevant, and the URL or report number that produced the mismatch. At PSC, that gives us enough information to locate an amended file, correct a library link, or explain whether the laboratory used a separate sample ID.
A compound name, cap colour, cake appearance, or similar testing date cannot repair a broken batch link. Until the identifiers are reconciled, the document may describe another sample of the same named material. The dedicated guide on how to read a COA becomes useful after the correct record has been found; interpretation cannot substitute for traceability.
The scope of a completed match
A complete lookup lets the reader state a narrow, useful conclusion: the label and COA identify the same batch, and the linked laboratory record reports the listed analyses for the submitted sample associated with that batch. The conclusion remains tied to the tests, sample, and dates shown in those records.
The match does not turn one report into evidence about every vial, every contaminant, later storage conditions, or uses the laboratory did not evaluate. Its value is precise: it prevents a result for one batch from being silently applied to another and gives any later question a traceable starting point. Once the material, batch, COA, and laboratory record point to one another, the reader can evaluate the actual document rather than a look-alike report.
Sources and context
- The World Health Organization's model certificate of analysis includes the material, batch number, dates, specifications, methods, results, and authorization expected in a traceable analytical record.
- WHO's good practices for pharmaceutical quality control laboratories describes batch-specific certificates and controlled laboratory records.
- Health Canada's GMP guide for drug products explains the role of batch documentation, certificates of analysis, and record integrity in traceability.
Research-use notice: Precision Synthetics Canada products and documentation are provided strictly for lawful, non-clinical laboratory research purposes only. COAs and testing records are not medical documents, safety guarantees, sterility guarantees, therapeutic endorsements, dosing guidance, or approval for human or veterinary use.