Lot Numbers and Traceability From Container to Record

Keep different identifiers in different fields

ICH Q7 defines a batch number as an identifying combination of characters through which production and distribution history can be determined. [A6] That pharmaceutical definition explains the purpose of the identifier; it does not establish the numbering system or record completeness of a research-material supplier.

For your own records, distinguish the following references. Their actual names and formats depend on the issuer.

These are functional distinctions, not a description of the Knockout Labs label design. Do not decode a date, production site or sequence from a lot string unless the issuer has explained its convention. A matching-looking number from another supplier is not enough to establish the same lot.

Make one record for each container

Record the product name, labelled amount or presentation, lot text, order reference and receipt date together. If you assign an internal container ID, keep it in a separate field and retain the supplier's identifier unchanged. Capture a readable image of the original label before wear makes it harder to interpret.

Preserve capitalisation, punctuation and leading zeroes. If a character could be “0” or “O”, record the uncertainty and ask the issuer. Avoid renaming the original photograph or downloaded report in a way that removes its existing reference; a descriptive copy or accompanying log can add your local context.

The ordering and documentation FAQ provides general support routes. For the actual documents associated with an order, use retrieving order and batch documents.

One order can require more than one lot record

This fictional ledger contains two containers of the same catalogue item in one order. Every identifier is invented; none demonstrates the supplier's format or fulfilment practice.

The report for DEMO-LOT-A does not become evidence for DEMO-LOT-B because the containers share an order number. Keep the second connection unresolved until an appropriate record is supplied. Likewise, two containers sharing a lot number are still two physical containers; an internal identifier can help distinguish them without changing their lot identity.

If a report uses a different batch code, ask for the documented relationship. Repackaging, supplier and laboratory references may differ, but their relationship should not be guessed. Matching a certificate to a batch and a container explains how to assess the evidence behind that connection.

Handle an unreadable label without guessing

Start with what is available: the full product label, packaging, order confirmation and any dispatch paperwork. If the order documents name a lot, record that as a document entry; do not silently treat it as a verified reading of an unreadable container label.

A useful support request is: “Please confirm the lot associated with this container. The product is [name], the order reference is [reference], and the attached label image has an unreadable character at [position]. Please also identify the applicable batch report, if available.” Fill in only details you can verify.

For a mismatch, preserve both strings exactly. For example, “container shows DEMO-LOT-B; report shows DEMO-LOT-A” is more useful than “wrong certificate”. It allows the issuer to address the specific discrepancy without assuming its cause. Use contact and technical support for clarification or a quality concern; this guide does not promise a particular investigation or response time.

Keep the identifier with the evidence it retrieves

Use the batch report library to seek the relevant documents. Retain the report reference, version or issue date as supplied, the date you obtained it and any explanation connecting different identifiers. If a corrected document is issued, keep the relationship to the earlier version clear.

A traceable record answers “which material does this document concern?” The document's methods, results and limitations answer different questions. The quality and batch-documentation hub provides those onward routes. Until a missing connection is resolved, describe it as unverified rather than extending another lot's result to the container in front of you.