A code fails as a lot record when the pack is marked and nobody can open the file that explains the mark. Write the two jobs on separate lines.
Confirm the code format in the traceability rule that applies to the product. The 9 August 2004 study is not today’s rule. Section 4 of that study lists “incorrect labeling or packaging” as a problem the panel rated highly for baked goods. Match the coder, ribbon, and scan rate to the equipment sheet for that line, and verify physical ink retention, contrast, and heat-seal clearance using our date code contrast, condensation rub test, and seam avoidance guide.
Incorrect labeling, in the words of that 9 August 2004 panel note, sat next to sanitation for baked goods. A code can be present and still be the wrong code for the lot file. The check is whether a person can open both and see one batch.
Roles
| Role | The question | A blank label is not enough |
|---|---|---|
| Mark | Who applies the code, and to which pack? | A blank label is the space for a code, not the lot record |
| Meaning | Which file says what that code refers to? | The code alone does not name the batch |
| Match | Who checks that the mark and the file are the same batch? | Two systems can drift |
| Break | What is written when the coder stops mid-lot? | Silence is not a record |
When the coder stops mid-lot, write the last good unit and the first unit after the restart as two rows. A single code that covers both runs hides the break and wastes the later search. Once the pack mark and batch record are aligned, follow our lot number tracking and 4-hour mock recall guide to link multi-roll packaging splices, modified atmosphere packaging gas lots, and outbound pallet manifests in a complete mass-balance ledger.
Start from the evidence checklist if the missing piece is a supplier file. Use the seal page if the missing piece is the closure check rather than the code. Confirm any legal duty in the regulation that applies to the product and the jurisdiction.
