A folded coffee bag can hold several small identities at once. Bars gather into a rectangle. Letters and numbers sit near the seam. Another code may be stamped later, slightly crooked, in ink that catches on the paper. They are close together. They do not necessarily answer the same question.
GS1 distinguishes three levels of identification. A Global Trade Item Number, or GTIN, identifies a kind of product. A GTIN paired with a batch or lot number can identify a production group. A GTIN paired with a serial number can identify one individual instance. Product, batch, and instance are different sizes of answer.
The syntax can make that distinction precise. In GS1 Digital Link, Application Identifier 01
means GTIN, 10 means batch or lot, and 21 means serial number. But that precision applies
only when the data carrier actually uses the GS1 system. An unexplained string printed beside a
barcode does not become a lot code because it looks like one. Its function remains Unknown
until the responsible business or a conforming record establishes it.
Even a confirmed lot code stays bounded. It can narrow the bag from “this product type” to “this production group.” It does not automatically name a coffee farm, cooperative, harvest, worker, roast date, facility, route, or chain of custody. Those fields require their own records and a connection between the records and this lot.
A link can make that connection easier to expose. GS1 Digital Link provides a way for an identifier to lead to one or more human- or machine-readable resources. The standard also warns applications not to assume that every conforming-looking URL reaches a conformant resolver. A route for disclosure is not the same thing as disclosed evidence. The actual destination still has to be opened and assessed.
Behind that destination, a business could use EPCIS to record events. Its TransformationEvent can connect identified inputs with identified outputs. That is a useful model for a process that turns one group of things into another. EPCIS is not, however, a public database, and use of the standard does not mean a consumer can see a company’s records.
If a brand explains that its code refers to a roast batch, production line, date, facility, or set of input lots, that statement belongs in this ledger as Reported, with the exact speaker, wording, package, and date attached. One brand’s code key should never be borrowed to decode another brand’s marks. If an accessible record independently supports a field, that field can be assessed separately.
Verified, Reported, Inferred and Unknown are this page’s editorial labels, not regulatory categories. The careful move is not to dismiss the code or ask it to tell a larger story than it can. It is to identify the size of the thing it names, then follow any supported link one step at a time.
Photograph one complete code panel. Keep the product identifier and the nearby characters separate. Ask one narrow question: “What does this exact lot code identify?”
Evidence in this journey
- verifiedGS1 distinguishes class-level identification (
GTIN), batch/lot-level identification (GTIN + batch/lot number), and instance-level identification (GTIN + serial number). - verifiedIn GS1 Digital Link syntax, Application Identifier
01is the GTIN,10is the batch/lot identifier, and21is the serial number. - verifiedEPCIS defines a TransformationEvent that can record relationships between identified inputs and outputs.
- inferredA confirmed lot code can narrow a package to a production group, but not automatically to a farm, route, or complete history.
- reportedThe brand’s attributed explanation of what its own lot code encodes.
- unknownThe function of an uninterpreted printed code and every upstream field for which no connected record is supplied.
Editorial labels, not regulatory classifications. How the ledger works.