Odoo 19 Lot & Serial Number Tracking:
Full Traceability from Receipt to Customer

Your Inventory Is Only as Good as Your Ability to Trace It

A customer calls about a defective batch of electronic components they received last Tuesday. Your warehouse manager opens the ERP, searches the delivery order, and finds… nothing. No lot number, no serial number, no link back to the supplier shipment that brought those components in. The only way to investigate is to manually cross-reference purchase orders, delivery dates, and supplier invoices—a process that takes hours instead of seconds.

This scenario plays out daily in companies that skip lot and serial number configuration during their Odoo implementation. The inventory module ships with powerful traceability features, but they require deliberate setup. Traceability doesn't happen by default—it happens by design.

This guide covers every layer of lot and serial number tracking in Odoo 19: the difference between lots and serials, how to configure products for tracking, how to assign numbers during receipt and delivery, how to run traceability reports, and how to manage expiry dates and product recalls. We include the actual Python models, XML views, and operational workflows so you can implement full traceability in your warehouse.

Lot Tracking vs Serial Number Tracking: When to Use Each

Odoo offers two distinct tracking mechanisms, and choosing the wrong one creates operational headaches that are painful to reverse once you have live inventory. Understanding the difference upfront saves hours of data cleanup later.

Assigning Lot and Serial Numbers During Receipt and Delivery

Configuration means nothing if your warehouse team doesn't assign tracking numbers during operations. Odoo enforces this at the stock move level—you cannot validate a picking for a tracked product without assigning lot or serial numbers. Here's the complete workflow.

Lot Assignment on Receipt (Incoming Shipment)

When a purchase order generates a receipt, tracked products require lot/serial assignment before validation:

1. Open the receipt (Inventory → Operations → Receipts)
2. Click Detailed Operations (or the serial number icon) on the move line
3. For lot-tracked products: enter the lot name (or scan the supplier's lot barcode) and the quantity received in that lot
4. For serial-tracked products: enter each serial number individually, or use Generate Serial Numbers to create a range automatically
5. Click Validate—Odoo creates the stock.lot records and links them to the stock moves

class StockLot(models.Model):
    _name = "stock.lot"
    _description = "Lot/Serial"

    name = fields.Char(
        string="Lot/Serial Number",
        required=True, index=True,
    )
    product_id = fields.Many2one(
        "product.product", string="Product",
        required=True, index=True,
    )
    company_id = fields.Many2one(
        "res.company", string="Company",
        required=True, index=True,
    )
    # Traceability link
    quant_ids = fields.One2many(
        "stock.quant", "lot_id",
        string="Quants",
    )

    _sql_constraints = [
        ("unique_lot",
         "unique(name, product_id, company_id)",
         "The lot/serial number must be unique "
         "per product and company!"),
    ]

Serial Number Assignment on Delivery (Outgoing Shipment)

When a sales order generates a delivery, Odoo requires the warehouse operator to specify which lot or serial number is being shipped. This is the critical link that enables end-to-end traceability—from the supplier who sent you the goods to the customer who received them:

# stock/models/stock_move.py (simplified)
class StockMove(models.Model):
    _inherit = "stock.move"

    def _action_done(self):
        for move in self:
            if move.has_tracking != "none":
                for ml in move.move_line_ids:
                    if not ml.lot_id and not ml.lot_name:
                        raise UserError(_(
                            "You need to supply a Lot/Serial "
                            "Number for product: %s",
                            move.product_id.display_name,
                        ))
                    if (move.has_tracking == "serial"
                            and ml.quantity > 1):
                        raise UserError(_(
                            "A serial number can only be "
                            "linked to a single unit of %s. "
                            "Quantity: %s",
                            move.product_id.display_name,
                            ml.quantity,
                        ))
        return super()._action_done()

Expiry Date Tracking and Product Recall Management

For industries dealing with perishable goods—food, pharmaceuticals, cosmetics, chemicals—lot tracking without expiry dates is incomplete. Odoo 19's Expiration Dates feature extends the stock.lot model with date fields that integrate into inventory valuation, FEFO picking strategies, and automated alerts.

Enabling Expiry Date Tracking

Activate Expiration Dates under Inventory → Configuration → Settings → Traceability. This adds four date fields to every lot:

class StockLot(models.Model):
    _inherit = "stock.lot"

    use_date = fields.Datetime(
        string="Best Before Date",
        help="Date after which the product may begin to "
             "deteriorate, without necessarily being dangerous.",
    )
    expiration_date = fields.Datetime(
        string="Expiration Date",
        help="Date after which the product becomes dangerous "
             "and must not be consumed or sold.",
    )
    removal_date = fields.Datetime(
        string="Removal Date",
        help="Date after which the product should be removed "
             "from stock (before expiration).",
    )
    alert_date = fields.Datetime(
        string="Alert Date",
        help="Date on which an alert should be raised about "
             "the lot approaching expiry.",
    )

FEFO Removal Strategy (First Expiry, First Out)

With expiry dates on lots, you can configure locations or product categories to use FEFO (First Expiry, First Out) as the removal strategy. This ensures the warehouse picks the lot closest to expiry first, reducing waste:

<record id="stock_location_fefo_example"
        model="stock.location">
  <field name="name">Cold Storage</field>
  <field name="usage">internal</field>
  <field name="removal_strategy_id"
         ref="product_expiry.removal_fefo"/>
</record>

<!-- Available removal strategies:
     - FIFO (First In, First Out) - default
     - LIFO (Last In, First Out)
     - FEFO (First Expiry, First Out)
     - Closest location -->

Managing Product Recalls

When a recall is necessary, the workflow combines traceability reports with expiry tracking:

1. Identify the affected lot(s) using the supplier's recall notice or your quality inspection records
2. Run a downstream traceability report to find every customer who received units from the affected lot
3. Check current stock—search stock.quant to find units from the recalled lot still in your warehouse
4. Create a scrap order or internal transfer to quarantine recalled stock
5. Notify affected customers using the partner list from step 2

# Find all quants for the recalled lot
recalled_lot = self.env["stock.lot"].search([
    ("name", "=", "FOOD-2026-00089"),
], limit=1)

quants = self.env["stock.quant"].search([
    ("lot_id", "=", recalled_lot.id),
    ("location_id.usage", "=", "internal"),
    ("quantity", ">", 0),
])

# Create scrap orders for each quant
for quant in quants:
    self.env["stock.scrap"].create({
        "product_id": quant.product_id.id,
        "lot_id": quant.lot_id.id,
        "scrap_qty": quant.quantity,
        "location_id": quant.location_id.id,
        "origin": "RECALL: FOOD-2026-00089",
    })

3 Lot & Serial Number Tracking Mistakes That Break Traceability in Production

Optimization Metadata