FSMA 204 needs Key Data Elements on Critical Tracking Events—receive, transform, ship—with lot linkage. In Odoo, enforce lot tracking, capture TLCs on stock.lot, record KDEs on pickings and manufacturing orders, and export traceability within twenty-four hours. Map each CTE to stock.picking types and mrp.production with consistent location and partner identifiers.
Steps
- Define Critical Tracking Events aligned to receipts, MOs, and deliveries in your SOP.
- Require lot_id on all regulated product move lines; use GS1 barcode where applicable.
- Store Traceability Lot Code on stock.lot (custom field or lot name standard).
- Capture ship-from, ship-to, quantity, and reference document on stock.picking at validation.
- For transforms, link input lots to output lots on mrp.production with move line trace.
- Build spreadsheet or API export filtered by date and product for FDA request drills.
- Test mock recall: trace one lot upstream and downstream in under twenty-four hours.
Common mistakes
- Mixing non-tracked and tracked flows on the same SKU.
- Inconsistent TLC format between co-packers and internal lots.
- Missing partner GLN on res.partner for retail shipments.
- Relying on invoice data instead of stock.move.line lot history.
- No documented export procedure during weekends or holidays.
Odoo version notes
FSMA traceability uses core stock models in Odoo 16–18; KDE fields often need light customization or OCA traceability extensions. Enterprise barcode helps receipt accuracy. Community is viable with strict process discipline. Validate exports after each version upgrade because custom modules may alter lot naming rules.
When to bring in help
If the fix touches custom modules, regulated traceability, or production outages, a focused rescue sprint beats months of trial and error. See our Odoo service.
See our industry practice