An order appears available in Odoo, but the picker cannot find the parts in the specified location. Adding safety stock does not resolve the gap between warehouse reality and system records. For businesses using Odoo in Belgium or France, cycle counts can help identify discrepancies before they disrupt deliveries. This Odoo Enterprise guide combines documented Odoo 19 capabilities with a control process proposed by Underside.
Start with locations and an initial count
In Odoo 19, cycle counts are organised by location. The documentation requires enabling storage locations and setting a count interval in days for the relevant location. Applying the initial adjustment triggers calculation of the next date using that interval. The physical inventory screen supports filtering entries by location.
Choose an area where discrepancies have a real cost
We recommend starting with a picking area where errors regularly hold up orders. Bring together the warehouse manager, a picker and the person responsible for master data to identify likely causes: similar product references, misunderstood packaging, unrecorded transfers or returns put away too quickly.
Frequency should reflect risk and available time. A stable area may need less attention than shelves holding fast-moving small parts. Set a pilot schedule, measure the time actually spent and review it after several rounds. This is an operational choice to test, rather than a universal interval dictated by the software.
Control movements while counting
Before each session, agree on a reference time and how to handle receipts, transfers and picks already in progress. We recommend a short window without movements in the counting area where operations allow it. If the area must remain active, assign someone to reconcile movements between the physical count and the correction.
Underside acceptance scenario: Odoo shows 48 units, but the operator counts 45. Before concluding that three units are missing, the operator checks whether a pick for three units still awaits recording. The expected test outcome is an explained difference followed by a single justified correction. Also test a product found in the neighbouring location.
Test barcodes and easily missed exceptions
Odoo documents inventory counting through the Barcode app, including counting an entire location when storage locations are enabled. This can support the pilot, but the team still needs to define its scope.
- Test an expected product that is missing and an unexpected product that is present.
- Check the unit being counted: individual item, carton or another packaging unit.
- Include a lot-tracked product and check the lot physically present.
- Define who recounts a discrepancy and who may apply an adjustment.
Connect these tests with your Odoo barcode processes and your approach to lots and expiration dates.
Prepare for migration or deployment across both countries
For an Odoo project in Belgium or France, we recommend agreeing on shared discrepancy categories while retaining a local owner for each warehouse. Before migration, compare imported quantities, locations, units and lots against a physical sample. Keep the count timestamp and subsequent movements so the opening data does not become outdated before launch.
Ask finance to validate the consequences of adjustments. This guide addresses operational controls; it does not define national inventory obligations.
Underside’s analysis: measure causes as well as corrections
We recommend tracking counts completed on time, recurring discrepancies by location and time to resolution. Stock corrected every week for the same reason points to a process issue. Fixing a label, unit definition or transfer workflow may be more useful than increasing count frequency.
Start with standard configuration and a short procedure. If you later connect an external warehouse system, define which system owns quantities, how duplicate messages are handled and how processing resumes after an interruption. Decide on custom development only after the pilot identifies an unmet requirement.
Official sources
Functional references: Odoo 19 cycle counts and inventory adjustments with the Barcode app. Acceptance scenarios and operational recommendations are Underside’s analysis.
Select an area and a few recent discrepancies to plan your Odoo cycle-count pilot with Underside.