Food safety/Allergen management

Ingredient label checks at receiving: preserve the actual product evidence

A receiving label check should identify the actual delivered product and retain relevant label or specification information. The record should make a mismatch visible rather than automatically inheriting details from the product originally ordered.

At goods receiving, a gloved receiver turns a sealed ingredient sack to photograph its actual original supplier label before moving it into stock. The sack, receipt pallet and original label dominate the photograph; all label text naturally out of focus.
AI-generated editorial illustration

At a glance

A receiving label check should identify the actual delivered product and retain relevant label or specification information. The record should make a mismatch visible rather than automatically inheriting details from the product originally ordered.

Define the decision behind the record

Make the order reference available without treating it as proof of what arrived. Labels can change, and deliveries can include substitutes. Ask for readable evidence with the product identity and date, while avoiding unnecessary personal information in photographs.

Compare the delivered product with its expected evidence

Prepare the receipt reference and approved ingredient information before reviewing the delivery. The task concerns the product actually received, not only the item ordered. Define which label evidence and discrepancies should be captured and who reviews an unexpected change.

Connect the physical label to the correct receipt and supplier lot. Keep the actual received identity, quantity and relevant specification reference together. If the label differs, preserve that evidence and the authorised receiving decision; do not overwrite it with an image from a previous delivery or a generic supplier brochure.

Test the record using two lots on one delivery and one changed product label. A reviewer should associate each image with the right physical lot and understand which comparison was made. Keep the supplier question and its resolution linked to the receipt so later recipe or batch investigations can retrieve the evidence without reconstructing an email trail.

Worked example

An operator notices packaging information that differs from the stored reference. They attach a readable image and record the discrepancy. The relevant reviewer assesses the information and any effect on recipes or handling before the record is treated as resolved.

Build a usable record

Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.

  • Order and actual product identities
  • Supplier lot and receipt date
  • Label or specification evidence
  • Observed discrepancy
  • Assessment and affected records

Example record and review decision

Fictional record example: REC-03 / LOT-B: actual received label and delivery evidence; SPEC-B-v2: approved ingredient reference; REVIEW-03: discrepancies.

Compare the physical product received with the expected specification, rather than confirming only the purchase order.

An updated label photographed against the wrong receipt can leave the real delivered ingredient without usable evidence.

Test the review, not just the form

Find the evidence from a selected receiving record and check that it is readable. Then follow a discrepancy to its review decision. Retain the original image separately from annotations or extracted text so transcription errors can be investigated.

A few useful answers

Can extracted label text replace the original image?

Keep the source evidence available. Any extracted text should be checked before being used as approved product information.

Is a supplier’s latest brochure enough evidence for the received label?

It can be supporting information, but it does not replace identification of the actual delivered product. Retain the receipt-specific evidence and any documented comparison or clarification.

Sources and further reading

Markdown