Frozen on and use by record different events
Identify the EU first-freezing-date requirement for specific frozen foods and keep that date separate from packing and use-by information.
A package can carry several dates because it records several events. A frozen-on date is not interchangeable with a packing date or a use-by date. Keep each date with its printed label before putting it into an app, spreadsheet or shopping comparison.
Check the category before expecting the date
Regulation (EU) No 1169/2011, Annex III point 6 and Annex X point 3, covers the freezing date, or first-freezing date when frozen more than once, for frozen meat, frozen meat preparations and frozen unprocessed fishery products. The words Frozen on must be accompanied by the date itself or a reference to where the date appears. The date uses an uncoded day, month and year, in that order.
This is not a universal requirement to find a frozen-on date on every item in a freezer. A prepared mixed meal and an unprocessed fish product should not automatically be assigned the same category.
Build a fictional event timeline
Imagine a hypothetical product record gives a first-freezing date of 20 September 2026, a packing date of 25 September 2026 and a separately labeled use-by date in 2027. These are invented observations solely for explaining the fields; the example does not establish an appropriate shelf life.
| Event | Record action |
|---|---|
| First freezing: 20 September 2026 | Retain the earliest freezing event identified by the source |
| Packing: 25 September 2026 | Keep it in a separate packing field |
| Use by: separately printed date | Copy the complete date and its label independently |
The packing date being later does not authorize overwriting the first-freezing field. If the product was frozen more than once, a later freezing event does not become the first merely because it is more recent.
Leave unreadable events unresolved
When a date appears elsewhere on the package, photograph both the directing phrase and the date it points to. Keep enough surrounding text to distinguish a batch code from a calendar date. If the year is cropped, do not supply it from the purchase date.
A long interval between two recorded events does not, by itself, prove unsafe handling. Nor does a clear first-freezing date establish that the cold chain remained intact. These event labels provide different evidence from storage history.
Read and follow the actual product's storage and preparation directions. To explore app-assisted label reading, visit Ingredi AI on the App Store or Google Play. Check that captured dates retain their event labels instead of becoming one ambiguous expiry field.