Product code and lot code answer different questions
Keep trade-item identity, batch text and printed date wording in separate fields so one cannot silently replace another.
Two jars can carry the same product identifier and different lot markings. That is not automatically a conflict. A trade-item code, a batch or lot reference and a printed date have different jobs, so your food notebook needs separate places for them.
Identify the field before interpreting its value
The GS1 Digital Link URI Syntax standard distinguishes a GTIN from batch or lot information and date attributes. Its worked examples use application identifier 01 for a GTIN and 10 for a batch or lot. Those numbered field labels define meaning in GS1 syntax; they are not instructions to treat every loose number on a jar as a GS1 field.
For example, the standard pairs the GTIN representation 09520123456788 with lot ABC123. This is a documentation example, not evidence about a grocery product. The lot remains a separate value associated with the trade item rather than becoming part of the copied GTIN.
Make a three-field package record
Now consider fictional package text: a clearly printed product barcode, a separate marking LOT B2609, and the words Best before 30 November 2026. A useful transcription is:
| Field | What to keep | What not to infer |
|---|---|---|
| Product identifier | Complete readable barcode digits and format, if established | A batch date from the digits alone |
| Lot marking | LOT B2609, including the original label wording | That 26 means a year or 09 means a month |
| Printed date | Best before 30 November 2026 | A different date type such as packed on |
Copying B2609 into the product-code column would prevent a later reader from knowing which type of evidence was saved. Reformatting it as September 2026 would also invent a decoding rule that the package did not provide.
Use the combination when investigating a question
Suppose a second jar has the same product identifier but lot B2610. Keep both package observations if the lot matters to your question. The changed lot alone does not establish a new recipe, and matching product identifiers do not prove that two jars belong to the same batch.
If a manufacturer asks for identifying details, provide the product name, complete code, lot text and exact date wording from your jar. If a form has only one field called code, ask whether it means the product identifier or the batch reference. Combining both into one unlabelled string makes the answer harder to interpret. An unreadable field stays unreadable until better evidence resolves it.
Use Ingredi AI for the separate task of everyday food-label reading through the official Apple download or official Google Play download. Keep these identification notes alongside the original package. This guide does not verify that the app decodes lot numbers, checks recalls or determines whether a food remains suitable to eat.