← Back to Blog Odoo Implementation

Lot Traceability in Odoo: What Food and Pharma Companies Actually Need

One FDA Audit Away from a Very Bad Quarter

If you manufacture food, dietary supplements, or pharmaceutical products and your ERP cannot produce full lot traceability on demand, you have a compliance problem wearing a software mask. The audit doesn't warn you when it's coming. The recall doesn't wait for you to pull records from three spreadsheets and a shared drive.

The regulations are specific. The Food Safety Modernization Act (FSMA) requires manufacturers to maintain records enabling the identification of every immediate previous source and every immediate subsequent recipient of a food article — one step back, one step forward, on demand. The Drug Supply Chain Security Act (DSCSA) goes further for pharma: full transaction history from manufacturer to dispenser. 21 CFR Part 11 adds electronic records and audit trail requirements for any computer system used in a regulated context.

Most companies subject to these regulations are doing it with spreadsheets, paper batch records, and a lot of hoping. That works fine — until a supplier lot is contaminated, an ingredient fails QA after it's already in finished goods, or a regulator asks for a forward trace of every unit containing lot number 2024-0847 within 48 hours.

What Your ERP Actually Needs to Do

Traceability isn't a checkbox feature. It's a system architecture requirement. Here's what a real implementation needs to deliver:

Lot Numbers Auto-Assigned at Receiving

Every incoming ingredient or raw material gets a lot number at the point of receipt — tied to the supplier lot, purchase order, and receiving date. This can't be a manual step that someone might skip. It has to be enforced by the receiving workflow itself. If the system lets you receive inventory without capturing a lot number on a lot-tracked item, you don't have lot traceability — you have lot suggestions.

Full Upstream and Downstream Traceability

The critical query every food and pharma company needs to be able to run in under five minutes: given a finished product lot, show me every raw material lot that went into it. And the inverse: given a raw material lot, show me every finished product lot that contains it, and every customer order those lots shipped on.

Odoo's double-entry inventory system makes this tractable. Every stock move — receipt, transfer, manufacturing consumption, shipment — creates a traceable record linking source to destination. That's not a special traceability feature; it's how the inventory engine works. The lot tracking rides on top of that foundation, which means the data is accurate at the transaction level, not reconstructed after the fact.

Expiration Date Management and FEFO Picking

First Expired, First Out (FEFO) picking is non-negotiable for food and supplement manufacturers. If your warehouse picks FIFO by default and someone has to manually verify expiration dates, you will eventually ship expired product. Odoo supports FEFO as a removal strategy configured per product or product category. The picking workflow surfaces expiration dates automatically and sorts lot selection accordingly.

This also applies to work-in-process. If you're using an ingredient with an expiration date in a manufacturing order, the system should be warning you when the lot you've reserved will expire before the planned production date.

Quality Hold States That Block Shipment

When a lot is flagged for quality review — whether because a supplier sent a COA that doesn't match spec, an in-process check failed, or QA is waiting on microbial results — that lot needs to be unreachable by the picking system until QA releases it. Not "someone will remember to check the QA spreadsheet before shipping." Actually blocked.

In Odoo, this is handled through quality control points and lot-level availability states. A lot under hold can exist in a dedicated quarantine location that the fulfillment routes never touch, or it can be placed in a "blocked" state that prevents it from appearing in available inventory. Either approach works — the implementation choice depends on your warehouse layout and workflow.

Recall Simulation in Minutes

Before you have a real recall, you should be able to run a mock recall. Feed the system a supplier lot number. It should return every finished product lot containing that ingredient, every sales order those lots appear on, and the current location of any units not yet shipped. The answer should come back in minutes, not days.

Odoo's lot traceability report does exactly this. It's not a custom report — it's a built-in feature in the inventory module. The accuracy of the output is only as good as the receiving and manufacturing data, which is why the workflow enforcement at receiving and production is so important.

Where Odoo Delivers Without Custom Development

The five requirements above — lot assignment at receiving, bidirectional traceability, FEFO picking, quality hold states, and recall simulation — are all covered by Odoo's standard inventory and manufacturing modules without custom code. This is worth emphasizing because the common assumption is that regulated-industry traceability requires expensive vertical solutions or heavy customization.

For a food manufacturer with 50-200 employees, Odoo's standard modules handle the core traceability requirements. The implementation work is in mapping your actual batch record and receiving workflow to Odoo's configuration options correctly from day one, not in building custom functionality.

How Odoo's Double-Entry Inventory Enables Traceability

Most inventory systems record a transaction as a single event: "20 units of item X moved from warehouse to customer." Odoo records it as two linked stock moves: a consumption from the source location and a creation at the destination location. Every move has a source, a destination, and a reference to the lot or serial number involved.

This matters for traceability because it means the data structure is inherently traceable — it's not reconstructed from receipts and shipments that happened to mention the same item. When you ask Odoo for the traceability of lot 2024-0847, it traverses a chain of linked stock moves from receipt to current location or final shipment. The chain is complete because every link was created at the time of the physical transaction.

The practical implication: if your receiving team scans the supplier lot barcode at receipt, and your production team scans the lot being consumed when starting a manufacturing order, the traceability data is captured as a side effect of the normal workflow. Nobody is doing separate traceability data entry. The audit trail is the operations record.

Configuring FEFO: What It Actually Looks Like

In Odoo, FEFO is a removal strategy — meaning it's the rule the system uses to select which lot to pick when a picking order is generated. You enable it on the product or product category, and you must also enable expiration date tracking on the product.

When a picking order is created, Odoo's removal strategy logic queries available lots for the product, filters by the requested quantity, and sorts by expiration date ascending. The lot with the earliest expiration date that has sufficient quantity is reserved first. The warehouse worker sees the lot pre-selected — they're confirming the pick, not making a judgment call.

One configuration detail that trips up implementations: FEFO only works correctly if expiration dates are consistently captured at receiving. If even 20% of receipts are missing expiration dates, the removal strategy will deprioritize those lots (null expiration sorts inconsistently) and your FEFO compliance breaks down. Enforce expiration date capture as a required field on the receipt workflow for every lot-tracked product.

What Implementation Actually Looks Like for a Food Company

A typical food manufacturer implementation for traceability follows this sequence:

Week 1-2: Product and lot configuration. Enable lot tracking on all raw materials, packaging, and finished goods that require traceability. Configure expiration date fields and FEFO removal strategies. Set up your warehouse location hierarchy — raw material, quarantine, WIP, finished goods, shipping dock.

Week 3-4: Receiving workflow. Configure the receipt operation type to require lot numbers and expiration dates for tracked items. Set up supplier lot capture from the vendor's COA. Run receiving team through the workflow with actual products.

Week 5-6: Manufacturing workflow. Configure Bills of Materials with lot-tracked components. Set up manufacturing orders to consume from specific lots. Train production team on lot selection during manufacturing consumption.

Week 7-8: Quality integration. Configure quality control points at receiving and finished goods inspection. Set up quarantine location and quality hold workflow. Run mock recall using historical data loaded during setup.

This isn't a six-month project. A focused implementation with a clear scope and a team that does the configuration work correctly up front runs 6-10 weeks for a 50-150 person food manufacturer.

Is Your Current System Giving You Recall-Ready Traceability?

Run this test. Pick any supplier lot number from a receipt in the last 90 days. Ask your system: which finished product lots contain this ingredient, and which customers received those lots? How long does it take to get a complete, accurate answer?

If the answer is longer than 15 minutes, or if the answer requires pulling records from more than one system, or if you're not confident the answer is complete — you have a traceability gap. The question is whether you find out about it in a mock drill or during an FDA inspection.