Three facts in a few characters
On this page13
The establishment where the product was packed
Which identifies a place rather than a company. For a processor with two sites the code distinguishes them.
The product contained therein
So one code does not cover a line. Each product gets its own identifier inside the code.
And the year, day, and period during which it was packed
Three time units, not one. A year and a day and a period within the day.
Which is finer than a date
A period within a day means a shift or a run, so a code identifies a production window rather than a calendar day.
And the packing period code has to change
Often enough to enable ready identification of lots during their sale and distribution. The frequency follows from how the product moves.
So the code is sized by the recall problem
A finer code identifies a smaller lot, which means a smaller recall. That is the trade the frequency requirement is about.
All of it in code rather than in words
Which keeps the mark short enough to put on a jar and keeps the key with the processor.
The product element is the one people forget
A date code alone satisfies the when and none of the what. Three facts are required and a date is one of them.
And our data supports none of it
We publish no lot number, no coding service and no markability attribute. The compounding property names the same lot gap under cGMP.
Which is consistent across the catalog
We identify a product by a dc sku and a case pack. Identifying a production run is the packer's job and we supply nothing for it.
The honest division is clear
We sell the jar and the code goes on it by some process we do not supply.
Ask about coding when you buy the closure
Because the 11 metal lug caps here take a mark far better than the glass does, and that is a purchase decision.