[Blog]()Inventory # Lot traceability: how to rehearse a product withdrawal A lot report should reconstruct what was consumed, what was dispatched and what remains unrecovered. **[Jonathan Perez]()**Co-founder · Design, product and sales October 8, 2026 · 8 min read **Short answer** Test traceability in both directions: from finished goods back to their inputs, and from an input to every linked lot and destination. Reconcile quantities by unit, location and status, retaining what cannot yet be located. A notice or customer response does not prove physical recovery; this exercise does not replace a regulated recall procedure. ## Lot genealogy and recovery drill Ten checks link inputs, finished goods, destinations and outstanding quantities. [Download CSV worksheet]() In this guide - [What actually identifies a lot?]() - [Why trace backward and forward?]() - [Worked example: one input feeds two finished lots]() - [What counts as recovery and what remains outstanding?]() - [What must the drill demonstrate?]() - [How do you test your own business records?]() ## What actually identifies a lot? An isolated number can repeat across products or suppliers. Define the combination identifying a lot and retain the supplier’s external reference alongside the internal one. Include receipts, production consumption, repacking, returns and shipments. If a required lot field accepts “various,” it will not produce useful traceability. Check that product and unit accompany the identifier in every exported report, including records shared between departments. Odoo distinguishes a lot grouping multiple units from a serial identifying one unit, and documents origin, storage and recipient reports. It is a product reference rather than evidence that your catalog is complete. [Read the tracking documentation](). A report can reconstruct only the links actually recorded. ## Why trace backward and forward? Backward tracing answers which inputs formed a finished lot. Forward tracing answers where an input was consumed, which products resulted and who received them. GestionAPPCC describes links between supplier, material, lot, production and finished product. [Published traceability features](). Turn that chain into a demonstration question: request concrete documents and identify missing links rather than assuming one screen proves the entire journey. ## Worked example: one input feeds two finished lots **Internal drill with synthetic data** M01 contains 100 kg of input. F01 consumes 60 kg and produces 120 packs of 0.5 kg; F02 consumes 30 kg and produces 60 identical packs. This simplified case has no loss. Ten kg of input remain. These are not a customer’s quantities or yields. | Finished lot |Customer A |Customer B |Customer C |At site | | --- | --- | --- | --- | --- | | F01: 120 packs |70 |30 |0 |20 | | F02: 60 packs |0 |0 |40 |20 | | Total |70 |30 |40 |40 | Flagging M01 as suspect in this exercise identifies F01 and F02: 90 kg consumed equals 180 packs of 0.5 kg. Forty packs remain at site and 140 were delivered. Retain the remaining 10 kg of M01 as well. An M02 lot with no documented link should not automatically be included, even if it is the same product. If F02’s consumption link is missing, show uncertainty instead of claiming a complete list. ## What counts as recovery and what remains outstanding? Simulate A returning 15 F01 packs through R15. There are now 55 packs at site, held for review, and 125 outside: A has 55, B has 30 and C has 40. Repeating R15 must not change these quantities. Separately record an identified destination, prepared notice, received response and confirmed physical return. No notices are sent here; the drill uses fictional records. A verbal promise to “check” is not proof of locating or recovering goods. ## What must the drill demonstrate? - Normal: starting from M01 finds F01/F02, three shipments and the original 40 packs at site, with documents and reconciled units. - Exception: removing a consumption link creates an identified warning or review; the report must not claim unsupported complete coverage. - Retry: R15 retains lot, original shipment and quantity; the same return produces one receipt of 15. - Separation: a similar lot code from a different origin remains excluded until evidence establishes a relationship. - Closure: each outstanding quantity retains a responsible person and next action; release or disposal requires a recorded decision rather than a dashboard color change. ## How do you test your own business records? Download the [traceability drill worksheet]() and replace the example with a receipt, two production orders and their shipments, hiding personal details. First verify that purchasing, production and distribution share matching identifiers. Also review [barcode receiving]() and [expiry and FEFO](). For agricultural or food operations, the scope of [agribusiness software]() should specify these links and exceptions; this guide proves neither regulatory compliance nor actual recovery. ## Bring one complete lot chain In a free consultation we can review where receipt, production and delivery links are lost. - A receipt with supplier lot and internal reference. - Two orders consuming that lot and their quantities. - Customer shipments and a return or missing link. [Book a free consultation]()[Ask on WhatsApp]() Related - [Agribusiness software]() - [Inventory management system]() ## Frequently asked questions ### Is recording a lot at receipt enough? No. Preserve it through consumption, transformation, storage and dispatch where applicable. A missing link leaves destinations the report cannot connect. ### Are lots with the same number always related? Not necessarily. Check product, supplier and internal reference; numbers may repeat in different contexts. ### Does replying to a notice count as recovery? No. Distinguish response, location and physical receipt. Recovered quantity needs a lot, quantity and movement evidence. ### Does this drill prove legal recall compliance? No. It checks an operational chain using test data. The applicable procedure, safety decisions and external obligations require specific assessment. ## Sources 1. [Lot traceability in Odoo 19]()Odoo 2. [GestionAPPCC traceability features]()GestionAPPCC Last updated: October 8, 2026 ## Keep reading [InventoryOct 7, 2026 ### Inventory expiry: how to test lots and FEFO before accepting the system]()[InventoryOct 8, 2026 ### Supplier returns: goods, documents and stock without duplicates]()[InventoryOct 8, 2026 ### Barcode receiving: test labels, lots and duplicate events]() --- Canonical: https://nightlysoftware.com/en/blog/lot-traceability-recall-test Updated: 2026-10-08 Description: Trace materials through production to customers, reconcile quantities and separate notification from recovery with an example and test worksheet.