Odoo Logistics & Warehouse · intermediate · 10 min read
Lot & Serial Number Tracking in Odoo
Implement lot and serial traceability in Odoo: product tracking modes, receipt capture, FEFO picking, recall readiness, manufacturing alignment, and scan enforcement on the floor.
Last reviewed 2026-07-30 · Estimated effort: 2–6 weeks typical implementation slice
Table of contents
Lot tracking groups quantities sharing batch attributes such as expiry or vendor lot. Serial tracking identifies individual units end-to-end. Odoo enforces these at product level with tracking mode by lot, serial, or none.
Traceability fails when only some steps require scans — a serial captured at receipt but not at delivery breaks chain-of-custody for recalls and warranty claims.
Manufacturing may produce lots and consume serialized components. Cross-link Manufacturing for shop floor capture; this article focuses on warehouse enforcement.
Teams enable lot tracking on every product then wonder why pickers still ship the wrong batch. Tracking mode is only the start — operation types and barcode rules must require lot or serial at each move.
This article covers warehouse-side lot and serial discipline. Receiving capture and outbound picking policies connect in companion articles.
Use lot tracking for batches with expiry, regulatory lot codes, or vendor traceability. Use serial tracking when each unit is unique for warranty or regulated assets.
Do not enable tracking on high-velocity commodity SKUs unless compliance demands it — scan overhead is real.
- ▸No tracking: standard bulk SKU
- ▸By lot: batch quantity with shared attributes
- ▸By serial: one identifier per unit
- ▸Removal strategy: FEFO, LIFO, or closest location
Lots and serials should be assigned or scanned at first ownership — vendor receipt or manufacturing output — not invented at pick time.
Pre-printed vendor lot labels may need mapping to internal lot records.
Configure removal strategy so pick operations propose oldest expiry or designated lot order. Pickers still confirm by scan — strategy is not a substitute for validation.
Commingle rules: whether multiple lots may share a bin depends on product and compliance.
Delivery validation should record which lots or serials shipped to which customer for recall scope. Packing lists and carrier docs should align with system records.
Returns must re-link serials to stock or quarantine — not receive as anonymous quantity.
Run mock recall drills: given a lot, list quants, customers, and open moves within minutes. Gaps indicate missing capture points.
Keep lot master data clean — duplicate lot names across products cause false trace paths.
- ✓Enable tracking only where compliance or warranty requires it.
- ✓Require lot scan at receipt and pick for tracked SKUs.
- ✓Set FEFO removal on expiry-driven categories.
- ✓Train pickers on commingle rules per product family.
- ✓Include lot fields in cycle count procedures.
- ✓Align manufacturing lot production with warehouse naming standards.
- !Enabling serial tracking without scanning at delivery.
- !Creating lots at pick to bypass receipt discipline.
- !Mixing lots in one bin when regulations forbid it.
- !Ignoring expiry on removal strategy configuration.
- !Duplicate lot numbers across different products.
- !Treating lot as optional text on high-speed pick lines.
Lot and serial tracking in Odoo is operational discipline — capture early, enforce at every move, and prove outbound linkage when recalls or warranty calls arrive.
Pilot tracked categories with full scan paths before enabling tracking catalog-wide.
Source location
Pick from stock.
Transit / ops
Internal moves.
Destination
Customer, FG, or scrap.
Quant update
Availability refreshed.
Scan
Capture barcode.
Match
Resolve product / lot.
Confirm qty
Validate UoM.
Exception
Unknown or mismatch path.
Frequently asked questions
Can one lot span multiple locations?
Yes. Lot quants split across bins. Recall and reporting aggregate by lot across locations.
How are serial numbers generated?
Manual entry, sequential sequences, or import at receipt. Define format and uniqueness rules before go-live.
Does lot tracking slow picking?
Extra scans add time but prevent recall cost. Optimize pick path and barcode UX; see Performance for scan latency.
What about kit products?
Kits inherit component tracking rules. Manufacturing and kit assembly articles define BoM-level behavior.
Related articles
Receiving & Putaway Processes in Odoo
Run disciplined inbound warehouse operations in Odoo: dock receipt against PO, quantity validation, quarantine, putaway rules, cross-dock, and barcode-driven dock-to-stock workflows.
View →Barcode Operations Best Practices in Odoo
Run reliable barcode workflows in Odoo: label standards, scanner hardware, operation types, exception handling, UAT on the floor, and governance that prevents scan-skipping.
View →Picking, Packing & Shipping Workflow in Odoo
Design outbound warehouse execution in Odoo: delivery orders, pick policies, pack stations, batch and wave picking, carrier handoff, backorders, and SLA-driven outbound operations.
View →Inventory Accuracy & Cycle Counting in Odoo
Build inventory accuracy programs in Odoo: cycle count schedules, ABC stratification, variance investigation, adjustment governance, KPI tracking, and habits that beat annual wall-to-wall counts.
View →Related services
Implementing traceability in Odoo?
Share your compliance drivers, product mix, and current recall process — we will outline lot and serial enforcement.
