Skip to content

Wholesale guides

How to Manage Lot Codes and Recalls for Packaged Food

Set lot code rules, track shipments, and respond to a recall with records you can use quickly.

Why lot codes matter in packaged food

Lot codes let you trace a product from production through storage, shipment, and customer delivery. In a recall, you need a fast way to identify what left your facility, where it went, and which lots remain in inventory. That is the core of traceability.

For packaged food operators, the food recall process is not just a quality issue. It is a recordkeeping issue. If your inbound receipts, pick slips, and shipment logs do not carry the same lot code, you spend time reconciling paper instead of isolating the affected product.

A clean lot code process also helps with date management, customer notifications, and disposition decisions. You can separate affected inventory from safe inventory, then document what was blocked, returned, destroyed, or released after review.

Set up the process before you need it

  1. Create a lot code rule

    Decide how you will read and store each lot code before products enter inventory. Use one format for every item line, and keep it on the case label, receiving record, and outbound order record. If a supplier sends a different format, normalize it in your system so staff can search it the same way every time. Consistency matters because recalls move faster when one code means one set of records.

  2. Capture lot data at receiving

    Train receiving staff to check the lot code on every inbound case or pallet that requires traceability. Record the code with the item, quantity, and receive date. If a shipment contains multiple lots, split the receipt by lot instead of combining them into one line. That keeps inventory clean and makes later holds easier to apply without guessing which units are affected.

  3. Link lots to outbound orders

    Your shipping record should show which lot codes left the warehouse and which customer received them. If you sell by case, pallet, or mixed order, the shipment detail still needs the lot trail. This is the part many teams skip. When you only know that ten cases shipped, you still do not know which ten. Tie every shipment line to a lot before the order closes.

  4. Use a hold process for suspect inventory

    When you receive a complaint, temperature issue, label error, or supplier alert, move the lot into a visible hold status. Do not leave it mixed with saleable stock. Separate physical inventory, block it in your records, and add a clear reason for the hold. That lets warehouse staff avoid accidental picks and gives management one list to review when the food recall process begins.

  5. Build a recall contact list

    Keep current contacts for suppliers, carriers, brokers, customers, and internal staff who must act during a recall. The list should include names, roles, phone numbers, and email addresses. Store it with your traceability records, not in one employee's inbox. During an event, you need one source of truth that can support notice, confirmation, and follow-up.

  6. Document the final disposition

    After you identify affected lots, record what happened to each one. Some product is quarantined, some is returned, and some is destroyed under control. Save the reason, the date, and the person who approved the action. If you need to explain your traceability later, that final record is as important as the receiving log.

What to record for each lot

Core fields that support traceability and recall review
RecordWhat to captureWhy it matters
ReceivingItem, lot code, quantity, dateShows what entered inventory
StorageLocation, status, hold reasonSeparates saleable and blocked stock
ShippingCustomer, order, lot code, quantityShows where affected product went
Recall fileNotice date, actions, dispositionCreates the audit trail

Common questions

What is the first step when you get a recall notice?

Stop movement of the named lot immediately. Place any matching inventory on hold, then compare the notice against receiving and shipment records. The goal is to identify what you still have and what already left your facility.

Do you need lot codes on every product?

Use lot codes on any packaged food item where traceability may be needed by law, customer agreement, or internal policy. The exact rule depends on the product and market, but your process should be consistent across the items you handle.

How long should you keep recall records?

Keep them long enough to support traceability reviews, customer questions, and regulator requests. Your retention policy should be written, easy to find, and followed for receiving, shipping, hold, and disposal records.

How does BoxNCase fit into this workflow?

BoxNCase can support structured wholesale records for stores, SKUs, and order history. The Free plan costs $0 per month and includes up to 1 store and up to 200 SKUs[1][2][3].

When should you test the process?

Run a mock recall on a schedule that matches your operation. Use a real lot code, pull a sample shipment trail, and confirm that staff can identify affected inventory without delay. If the drill takes too long, fix the record gaps.

Put traceability into one workflow

Use one system for stores, SKUs, and order history so recall records are easier to find.

More wholesale guides

Sources

  1. [1]BoxNCase Free plan costs $0 per month. BoxNCase pricing (captured 2026-10-15)
  2. [2]BoxNCase Free plan includes up to 1 store. BoxNCase pricing (captured 2026-10-15)
  3. [3]BoxNCase Free plan includes up to 200 SKUs. BoxNCase pricing (captured 2026-10-15)

Last reviewed 2026-10-15.

More wholesale guides