Guide · · 12 min read
Lot and Batch Traceability in Canadian Fulfillment: Receiving, Holds and Recalls
Lot traceability connects each inbound unit to its storage status and outbound order. Done well, it supports precise holds, sensible expiry rotation and faster, evidence-based recall lookup.
A lot number is useful only if it stays attached to inventory as the product moves. The identifier received on a case must remain connected to quantity, status, location, picks, shipments, returns and adjustments. Break that chain and a brand facing a quality concern may have to hold far more stock—or contact far more customers—than necessary. Lot tracking fulfillment Canada programmes therefore combine reliable product data, barcode capture, physical segregation, allocation logic and an audit trail that can answer two directions of inquiry: where did this lot come from, and where did it go? The appropriate controls depend on product, channel, contractual obligations and applicable requirements. This article describes sound operational patterns rather than prescribing legal or regulatory compliance. Brands should identify their own obligations and obtain advice from qualified product, quality and legal specialists; a 3PL should implement the documented handling rules it has agreed to support.
Design traceability around identities, events and statuses
Begin by defining the traceable unit. A lot may be assigned by a manufacturer, co-packer or brand, while a batch may be represented differently in each system. Preserve the original identifier and avoid free-form aliases unless a governed translation table links them. Decide whether expiry, best-before, manufacture date or serial number must accompany the lot and at which packaging level. Then map the events that change custody or availability: receipt, inspection, putaway, replenishment, pick, pack, ship, return, hold, release, adjustment and disposal. Each event should capture item, quantity, lot, location, timestamp, user or device, source document and resulting status. This event model is more durable than a spreadsheet snapshot because it explains both the current balance and how it arose.
Traceability is a chain of recorded events, not a lot-number field. If adjustments, returns or repacking break the chain, the final inventory report cannot repair it.
Capture lots and dates at receiving before stock becomes available
The inbound notice should state expected SKU, quantity, lot and relevant dates where the supplier can provide them. At the dock, scan standardized barcodes when available and validate human-readable values against labels and documents. Configure format, date-order and shelf-life checks to prevent plausible but incorrect entries. Mixed-lot pallets or cases need explicit breakdown rather than one convenient lot applied to every unit. If identity, condition or date is uncertain, route goods to a pending or quarantine status; do not make them allocatable while someone investigates. Record overages, shortages and substitutions against the receipt. Sampling intensity can vary by supplier history and product risk, but the rule for accepting a lot should be written, trained and auditable.
- Pre-advise expected SKU, lot, quantity and relevant date fields.
- Scan source barcodes and verify readable labels where practical.
- Separate mixed lots at the appropriate handling level.
- Block incomplete, damaged or mismatched stock from allocation.
- Retain receipt, supplier and source-document relationships.
Make quarantine a system status backed by physical control
A hold should prevent allocation in the WMS and prevent accidental access on the floor. Use distinct statuses for pending inspection, quality hold, recall hold, damaged stock and disposition, rather than a generic unavailable bucket that obscures purpose. Restrict release authority to named roles and require a reason and supporting reference. Physical segregation may use designated locations, licence-plate controls, signage or secured areas according to risk. Transfers into and out of hold must preserve lot and quantity. Also define what happens to open orders allocated before a hold was applied: they may need deallocation, pack-station interception or carrier escalation. A regular report comparing held system balances with held physical locations helps reveal control gaps.
Use FEFO allocation without confusing it with FIFO
First-expired, first-out selects eligible inventory with the earliest applicable date, while first-in, first-out selects the oldest receipt. They can produce different picks when production and transport timing vary. FEFO is valuable for dated products, but it needs a minimum remaining shelf-life rule for each channel or customer. A unit may be sellable for one channel yet unsuitable for a retailer requiring more life at delivery. Configure allocation by expiry and lot status, then control exceptions such as customer-designated lots, quality releases and short-dated promotions. Monitor inventory approaching thresholds and act before it becomes stranded. The brand should approve rotation and shelf-life policy; the warehouse should execute it consistently and report exceptions.
| Workflow | Control point | Required record | Failure prevented |
|---|
| Receiving | Validate lot and date before availability | Receipt, source lot, quantity, status | Unknown or misdated stock |
| Storage | Separate status and preserve lot by location | Movement event and licence plate | Lot commingling |
| Allocation | Apply FEFO and channel shelf-life | Rule and selected lot | Short-dated shipment |
| Hold | Block system allocation and floor access | Scope, reason, authority, time | Accidental release |
| Recall lookup | Trace backward and forward | Supplier receipt and outbound orders | Over-broad or incomplete search |
Preserve lot identity through picking, packing and returns
Scanning at pick or pack confirms that the allocated lot became the shipped lot. If operators can override allocation, the system should validate eligibility and record who changed it and why. Repacking, kitting and decanting require consumption and production transactions that link component lots to the resulting kit or container. Returns are a common break point: customer-reported lot information may be unreliable, labels may be missing and product condition may be uncertain. Returned lot-controlled goods should enter a non-sellable status until identity and disposition are established under the brand's policy. If restocking is permitted, preserve the original shipment link and record the inspection. Never assign a convenient replacement lot merely to balance the system.
Build a recall lookup that works in both directions
A backward trace starts with affected finished goods and identifies supplier, receipt, purchase order and source lot. A forward trace starts with a lot and identifies on-hand quantity and status, internal movements, kits that consumed it, outbound orders, destinations and returns. Define the fields and report format before an incident. Search logic must account for partial picks, split shipments, substitutions, kits and inventory moved between facilities. The 3PL can provide warehouse records and execute holds, but the brand or designated responsible party should define scope, communications and disposition with appropriate professional guidance. Contact and escalation lists must remain current. Periodic exercises reveal missing data and access issues while there is time to correct them.
A recall report should reconcile the lot's received quantity to on-hand, shipped, returned, adjusted, transformed and disposed quantities—with explained differences.
Protect audit trails, permissions and record quality
Audit records should be append-oriented: corrections create attributable events instead of overwriting history. Use role-based access for holds, releases, adjustments and master-data changes, with stronger approval for high-impact actions. Synchronize timestamps and retain stable transaction identifiers across integrations. Establish retention and export expectations based on the brand's assessed needs and applicable obligations rather than an arbitrary default. Monitor null lot values, impossible date sequences, negative balances, manual overrides and unexplained adjustments as data-quality exceptions. Barcode standards can improve interoperability, but only when suppliers, systems and warehouse processes use them consistently. Access to an exportable history also reduces dependency on a single dashboard during investigation.
- Record who, what, when, where, quantity, lot, status and reason.
- Restrict and review hold releases and inventory adjustments.
- Link corrections to original transactions instead of replacing them.
- Reconcile lot balances after repacking, kitting and transfers.
- Test report access and data exports before an incident occurs.
Run traceability exercises and close the gaps they expose
Select a real lot and conduct a time-boxed desk exercise using current systems and contacts. Verify backward source records, forward orders, on-hand locations, hold execution, kit genealogy and quantity reconciliation. Include customer care, quality, technology and leadership—not only warehouse staff—because communications and decisions often create the delay. Record unavailable fields, manual joins, permissions, response times and unexplained balances. Then assign corrective actions and repeat the exercise after material system, supplier or product changes. An exercise is not proof of compliance and should not be presented as such; it is an operational control that helps a brand evaluate whether its traceability design performs as intended.
Frequently Asked Questions
What is lot tracking in fulfilment?
It is the capture and preservation of a manufacturer or brand lot identifier through receipt, storage, allocation, shipment, returns, holds and adjustments, so inventory can be traced backward to source and forward to destinations.
What is the difference between FIFO and FEFO?
FIFO selects the inventory received first. FEFO selects eligible inventory with the earliest expiry or relevant date. Dated products often benefit from FEFO combined with channel-specific remaining shelf-life rules.
Can quarantined inventory remain in the same warehouse?
Operational design depends on risk and product needs, but a hold should combine a non-allocatable WMS status with effective physical controls. Release authority, reason and evidence should be recorded.
What should a recall lookup return?
It should identify source receipts, on-hand and held quantity, internal movements, transformed kits, shipments and destinations, returns, adjustments and disposition, with a reconciliation of the affected lot.
How should returned lot-controlled products be handled?
They should normally enter a non-sellable status until identity, condition and disposition are assessed under the brand's documented policy. Any approved restock should preserve the original shipment and inspection trail.
Does a traceability exercise prove regulatory compliance?
No. It tests whether operational records and people can perform an intended lookup and hold. Brands should assess applicable obligations with qualified specialists and should not treat an exercise alone as legal or regulatory assurance.
Related ByExpress resources