A lot number identifies a group of products; a serial number identifies one individual item. Several ice packs can share a lot code, while item-level serial tracking distinguishes one pack from another. Neither should be confused with the SKU or product identifier used to describe the type being ordered.
For a bulk buyer, the useful question is how precisely the product needs to be identified when it is received, split across warehouses or investigated after a complaint. This guide compares the identifiers and provides a record checklist to discuss with the supplier before approving labels.
On this page
Lot number vs serial number: a quick comparison
Scroll horizontally on smaller screens to see all columns.
| Question | Lot or batch number | Serial number |
|---|---|---|
| What does it distinguish? | A defined group of products | One individual item within the agreed product-identification system |
| Can several packs share it? | Yes, when they belong to the same defined lot | Each tracked item needs a distinct identifier within the system |
| What question does it help answer? | Which batch supplied these packs? | Which particular item is this? |
| Typical buyer decision | Define the lot and link it to receiving and distribution records | Determine whether individual-item history is needed and can be maintained |
The GS1 Global Traceability Standard, Release 2.0 distinguishes product-level, batch/lot-level and individual-instance identification. In the GS1 framework, a GTIN identifies the trade item, while adding a batch/lot or serial attribute provides a more specific level of identification. The framework is not proof that a particular supplier has implemented it.
How do these differ from a SKU, GTIN or barcode?
A SKU is an organization’s stock-keeping reference. A GTIN is a standardized trade-item identifier. Those references help identify what the product is; the lot or serial reference adds information about which group or item you received.
A barcode is a data carrier. Its appearance alone does not tell you whether it contains just a product identifier or additional traceability attributes. GS1’s live reference identifies AI (10) as batch or lot number and AI (21) as serial number. Follow the applicable identifier, data-format and association rules when using that system.
Keep barcode artwork and packaging-level decisions in the private-label barcode and labeling guide. Here the focus is the relationship between identifiers and records, rather than selecting a barcode or creating printable artwork.
When is lot tracking useful, and when might serial tracking be needed?
Discuss lot tracking when your main task is to connect a group of finished packs with the relevant production, inspection, receipt and shipment records. If a concern appears in part of a delivery, you need to know which products share the recorded history and where they went.
Discuss item-level tracking when a customer, service process or applicable requirement needs a history for each individual unit. Additional detail also means additional labeling, capture and reconciliation work. Do not request serial numbers merely because they sound more thorough; establish which decision requires that level of detail.
Lot and serial references can coexist. Oracle NetSuite’s explanation of lot and serial tracing describes linking finished goods backward to materials and forward to orders and customers. Its software features are examples, not a statement about Cryozin’s systems.
A simple example for a split delivery
Imagine that one approved ice-pack SKU is received from two different lots. Your warehouse sends some units from each lot to a second location. If the transfer record contains only the SKU and total quantity, the receiving team cannot tell which lot is now at each site.
A useful transfer record preserves the product reference, the separate lot quantities, the source and destination, and the date. If individual serials are required, those identities must remain linked through the transfer too. This is an illustrative record problem, not a Cryozin shipment example.
A buyer’s identification and record checklist
Use these original discussion fields to agree what the supplier and receiving team will capture. They are procurement prompts, not a claim that every field is available for every Cryozin order.
- Product identity: approved SKU or part reference, specification revision and selling-unit configuration.
- Lot definition: what starts or ends a lot, who assigns the reference, and how mixed lots are handled.
- Item identity: whether serials are needed, their uniqueness rules and the product reference they accompany.
- Marking location: pouch, sleeve, retail pack, case or another agreed location; state what remains visible after unpacking.
- Record links: which material, production, inspection and release records can be retrieved for the reference.
- Movement history: quantity by lot or item, receipt or dispatch reference, source, destination and date.
- Exceptions: how damaged labels, returns, relabeling and mixed cases are recorded without losing the original relationship.
- Retrieval: contact owner, agreed access and retention requirements, and the evidence needed for an investigation.
For shipment and receipt events, GS1’s traceability framework connects the object identifier with the parties, locations and dates. The checklist above adds buyer-side questions for the proposed ice-pack program; it is not a universal legal record list.
Check the record chain before relying on the code
Ask for an agreed demonstration using a representative sample or clearly identified test record. Start with the visible identifier and check whether the corresponding product and receipt can be found. Then check a transfer or dispatch record in the other direction. Record missing links and who must resolve them.
A readable code is one part of that check. It does not by itself establish product conformity, a valid expiration date, a complete recall system or regulatory compliance. Keep the product evidence and finished-goods inspection and release criteria tied to the approved specification.
Frequently asked questions
Is a batch number the same as a lot number?
The terms are often used together, including in GS1’s batch/lot field. Agree on the actual grouping and record definition with the supplier instead of assuming the words describe an identical production boundary.
Can I read the manufacturing or expiry date from a lot code?
Only if the documented coding scheme provides that meaning. Ask for the code interpretation and relevant records. Do not derive a storage-life claim from a string of digits.
Does a new purchase order always mean a new lot?
Do not assume that relationship. One delivery may contain several lots, and a lot may be distributed through more than one shipment. Preserve the agreed mapping in the receipt and distribution records.
Define the tracking need before approving labels
Choose the level of identification that supports the actual buying and receiving task. For a Cryozin bulk project, review the wholesale sourcing route and send your product, labeling and record requirements. The marking method, available records and any serialization arrangement need project-specific confirmation.
Images are editorial concept illustrations. Blank cards illustrate group and individual identification; they are not production codes or evidence of a Cryozin tracking system.
