A shipment can arrive on time, match the purchase order, and still be unusable for one simple reason: nobody can establish which supplier lot is inside the container.
Maybe the label is torn. The ink has rubbed away. One case carries a code that conflicts with the packing slip. Or twelve bags arrived, but only eleven have readable identities. The quantity may be physically present, yet releasing it immediately can create a traceability gap that follows the material into every later batch.
The safest operational response is not to guess. It is to pause availability, preserve the evidence, and route the exception to a clear decision.
Protect identity before you count the material as usable
Receiving answers two different questions:
- What physically arrived?
- What is approved and identifiable enough to use?
Those answers are not always the same. A business can record 50 kilograms received while keeping all 50 on hold, separating quantity from production availability.
Good raw material lot tracking begins before the material reaches a production shelf. If the source identity is unclear, assign a temporary internal receipt ID to the receiving event, mark the stock as held, and keep it physically separated or visibly controlled according to your process.
An internal ID does not repair the supplier’s missing information. It gives your team a stable reference while the question is open.
Name the exception accurately
“Bad label” is too vague. Separate the problem into one of four paths:
| Receiving exception | What it means | First action |
|---|---|---|
| Missing | No supplier lot code is present | Hold and document that no code was found |
| Unreadable | A code exists but cannot be interpreted confidently | Photograph it, hold it, and request confirmation |
| Conflicting | The container, case, and paperwork show different codes | Preserve every code and ask the supplier to resolve the conflict |
| Mixed | Containers in one delivery carry different lots or some have no code | Separate by visible identity and hold the uncertain portion |
This distinction prevents one person from “cleaning up” the record by choosing the most convenient value. A missing supplier lot number is not the same problem as an unreadable lot code, and neither should be silently converted into the code from another container.
Create a temporary hold card
The hold record should take minutes. Capture:
- material name and internal item code;
- supplier and purchase-order reference;
- received date, quantity, unit, and container count;
- temporary internal receipt ID;
- the exact exception type;
- every visible code exactly as shown;
- photographs of labels, seals, cases, and paperwork;
- current location and held quantity; and
- receiver, next-action owner, and due date.
Record literal identifiers. Preserve zeros, letters, spaces, and dashes rather than correcting what looks like a typo. If a character could be `0` or `O`, write that uncertainty in the exception note instead of deciding by instinct.
The broader guide to raw material lot tracking from receipt into production explains the full incoming-lot record. This hold card is the exception layer that keeps uncertain material out of ordinary approved stock.
Preserve evidence before opening or moving containers
Photograph the shipment as received: the overall delivery, outer case, container, visible code, seal condition, and paperwork reference. Keep each label connected to its container.
A photo supports the material receiving record, but it should not replace searchable text. Enter readable identifiers directly and note what cannot be read. Files named `IMG_4832` in a phone gallery are not a dependable supplier record.
Do not open sealed material to hunt for a code unless your procedure allows it and the action will not compromise the material.
Ask the supplier a complete question
A message that says “What lot is this?” invites another email. Send:
- purchase-order and supplier item numbers;
- delivery date and packing-slip reference;
- quantity and number of containers affected;
- photographs of the outer case and container labels;
- every visible code or partial code;
- description of the conflict or missing field; and
- the confirmation needed in writing.
Ask whether all affected containers belong to one supplier lot and how that was determined. Preserve the response with the receiving record.
If this repeats, treat it as a supplier-performance issue. Consider clearer purchase requirements, better labels, a receiving agreement, or a sourcing change—not creative internal guesses.
Decide usability with the right authority
A missing code does not prove the material is defective. It means expected identity evidence is absent.
The authorized decision owner should determine whether to:
- accept the supplier’s documented clarification;
- keep the material on hold pending more evidence;
- accept only the clearly identified containers;
- return or reject the uncertain portion; or
- escalate for product-specific technical or regulatory review.
Requirements differ by product and market. FDA’s Food Traceability Rule applies additional records to certain foods; current dietary-supplement component rules differ. Use qualified guidance instead of treating this checklist as compliance advice.
Record the decision, date, evidence reviewed, affected quantity, and decision owner. “Looks fine” is not a closure note.
Release the material without erasing the exception
If the identity is resolved and the lot becomes available, preserve the original hold and the resolution. Do not rewrite history so the delivery appears to have arrived perfectly labeled.
Update the record with the confirmed supplier lot, source of confirmation, status change, approver, and release date. Label each container or secondary container so it reconnects to the same source record.
When production uses the material, record the actual lot and quantity on the run. The small-batch production record checklist shows how material identity belongs beside formula version, process facts, checks, exceptions, yield, and disposition.
For a new but clearly identified supplier lot, the next concern is different: compare its first use against the approved process. See the supplier-lot change batch review for that later step.
Run a two-direction trace test
After resolution, test batch traceability both ways:
- Start with the received lot. Can another person find every production batch that used it?
- Start with one finished batch. Can that person identify the incoming lot, receiving exception, supporting supplier records, and final release decision?
If either path depends on memory, the exception is not fully closed. Use the production-record exception stress test to challenge the rest of the record before a live problem does it for you.
Frequently asked questions
Can we assign our own lot number when the supplier code is missing?
You may assign an internal receipt ID, but label it as internal. Do not present it as the supplier’s lot or use it to hide missing source identity.
What if only one container in a shipment has a readable code?
Do not assume the code covers every container. Separate the clearly identified unit from the uncertain units and ask the supplier to confirm the relationship.
Can a photo replace entering the lot code as text?
No. A photo preserves context, but readable identifiers should also be entered as searchable text. Keep both when the image supports the record.
Does a missing supplier lot automatically mean the material must be rejected?
Not universally. Hold it while the authorized person evaluates the evidence, product requirements, supplier response, and applicable obligations. Document the final disposition.
Practical takeaway
The moment a lot code is missing or questionable, stop treating the shipment as ordinary stock. Classify the exception, create the hold card, preserve exact evidence, ask the supplier a complete question, and record an authorized decision.
Then trace the resolved lot into one finished batch and back again. The goal is not a perfect receiving story. It is an honest record that keeps uncertain identity from becoming invisible production risk.
