Wholesale guides
How to manage lot codes and recalls for packaged food
Build a simple traceability routine so you can find affected lots fast, contact buyers, and keep records that support a recall.
Why lot codes matter
A lot code links a finished case or unit to one production run. In a recall, that link lets you narrow the scope instead of pulling every pallet in the warehouse. That matters when you ship to many stores, regions, or distributors and need to act with discipline.
Your food recall process should start before an issue appears. If you build records around supplier lots, production lots, ship dates, and buyer accounts, you can trace product in both directions. You can see where ingredients came from and where finished goods went. That is the core of traceability.
For packaged food, the work is usually simple, but it must be consistent. Use one naming rule, one place to store lot data, and one person to verify it. If people enter codes differently, the record loses value. A clear routine makes the next call, email, or withdrawal easier to manage.
Set up a traceability routine
Define the lot code format
Choose a format that your team can read without guessing. Include the fields you need for traceability, such as production date, line, site, or run. Keep the format stable across products when you can. If you change the pattern, write the new rule down and train the people who print, pack, and receive the goods.
Capture lot data at receiving
Record the supplier lot as soon as product arrives. Match the code on the pallet, case, or unit to the purchase record and the item master. If the lot is missing or unclear, quarantine the shipment until someone resolves it. A clean receiving step prevents confusion later when you need to identify what is safe to ship.
Carry the lot through production and picking
When you transform or repack a product, assign a new lot if your process requires it. Then carry both the input lot and the finished lot in your records. At pick and pack, scan or write the shipped lot onto the order record so you know which buyer got which run. That link is what makes a targeted recall possible.
Keep a shipment trace log
Store the ship-to name, order number, lot code, quantity, and ship date in one log that you can search quickly. If a regulator, supplier, or buyer calls, you should be able to pull the history without rebuilding it by hand. The log should show who handled the case from receipt to dispatch and where it moved next.
Test the food recall process
Run a mock recall on a regular schedule. Pick one lot and trace it backward to the supplier and forward to the buyers. Time the exercise and note where the process slows down. If staff cannot find the record in a few minutes, improve the file structure, the scan step, or the person responsible for the search.
Prepare your contact list and script
Keep current contacts for suppliers, carriers, buyers, and internal staff. Use a short recall script that says what product is affected, which lot codes are involved, and what the buyer should do next. Clear language matters. You want one version of the facts going out, not multiple messages with different details.
Use this reference for your review
| Record | What to capture | Why it matters |
|---|---|---|
| Receiving | Supplier lot, item, quantity, date received | Shows what entered your system |
| Production | Input lot, finished lot, line, date | Connects raw material to finished goods |
| Shipping | Buyer, order number, lot, quantity, ship date | Shows where product went |
| Recall log | Issue date, affected lots, actions taken | Documents the response |
| Verification | Mock recall results, gaps found, follow-up | Shows that the process works |
FAQ
What is the main goal of lot code traceability?
The goal is to identify affected product quickly and accurately. Good traceability lets you isolate the lot, notify the right buyers, and avoid pulling unrelated inventory. It also gives you a record of what you received, what you made, and what you shipped.
How often should you test a recall process?
Test it on a regular schedule that fits your operation and risk profile. The point is not the calendar alone. The point is to confirm that staff can find records, contact the right parties, and document each action without delay.
Should every packaged food item have a unique lot code?
Yes, each production run should be distinguishable in your records. You may use one format across many items, but the code must identify the run clearly enough to trace forward and backward. If a code repeats without control, the record becomes less useful.
What if a supplier lot is missing or unreadable?
Hold the product until you resolve it. Do not mix uncertain inventory with clean inventory. A missing lot creates risk in a recall, because you cannot prove what the product is or where it belongs. Quarantine first, then investigate and document the result.
How does BoxNCase fit into this workflow?
You can use BoxNCase to organize product, buyers, and shipment records in one place, which supports traceability when you need to review a lot history. The key is discipline in your own data entry and review process, because the software only helps when the records are complete.
Put your traceability process in one place
Use a simple system for products, buyers, and shipment records so recall work stays orderly.
Related wholesale guides
- What is a GTIN / UPC and why wholesale buyers require one
- What is FEFO inventory rotation
- How to Handle a Wholesale Order From Quote to Delivery
- How to List Products on a Wholesale Marketplace
- What is wholesale pricing and how it differs from retail
- Wholesale Central alternatives
- BoxNCase vs Faire
- BoxNCase vs Amazon Business
- BoxNCase vs Sysco
- /wholesale
Last reviewed 2026-09-02.