Control inventory through 3 linked records: why stock moved, what a physical count found and why replenishment was proposed. Do not manage stock solely by typing a new balance whenever the shelf looks wrong. A useful system preserves enough evidence to explain the quantity and the decision that follows from it.
Odoo’s official inventory-adjustment and reordering documentation supplies the examples below. It does not establish that a particular installation matches your warehouse, units or accounting requirements. This guide states no universal minimum-stock figure and reports no stock count or system test performed for a client.
How should movements and physical counts remain traceable?
Start with stable item identity, location and unit of measure. A quantity has little meaning if staff cannot tell whether it describes individual units, packs or another measure. Record those distinctions before comparing systems. The same item description can conceal materially different quantities when one person counts packages and another records their contents.
Odoo’s inventory-adjustment guide distinguishes On Hand, the quantity recorded in the database, from Counted, the quantity physically observed. It also describes a Difference field and the unit of measure. Keep those meanings visible in your own process. The count is evidence to reconcile with the ledger, not permission to overwrite unexplained history.
The guide associates stock records with locations where storage-location functionality is enabled and with lots or serial numbers where relevant. Use the dimensions your business actually needs. Do not promise serial traceability from a system configuration that has never recorded serials, or compare counts taken from different locations as though they described the same stock.
Record the reason for an adjustment. A receiving error, damage, an issue posted against the wrong item and an unexplained count difference should not all disappear behind the same balance edit. The proposed system should show how the responsible person records the decision and how another colleague can reconstruct it later.
Keep counting and applying a change distinct. The inventory documentation describes the person counting and the person applying the count as potentially different roles. Decide how that fits your operation. A physical observer may establish the count while another authorised person resolves the discrepancy and applies the adjustment.
Test the relationship between a transaction and its stock effect. A sale, return or receipt should have a source reference that makes sense to the business. If the system displays only a changed balance, ask what evidence explains the change. Do not accept a demonstration that quietly edits the starting quantity whenever an exception appears.
Use this original control sheet to connect observed stock to the next decision.
| Control record | Evidence to retain | Problem it should expose |
|---|---|---|
| Movement | Item, unit, location and source reference | Quantity changed without a business event |
| Physical count | Observed quantity and count context | A balance accepted without observation |
| Difference | Recorded versus counted quantity | Unexplained variance hidden by overwrite |
| Adjustment decision | Reason, authority and related record | Correction cannot be reconstructed |
| Replenishment proposal | Forecast basis and configured rule | Order suggested from an arbitrary minimum |
| Exception | Unresolved item and responsible owner | Operational issue disappears from reports |
How do you set reorder levels and test the resulting action?
Odoo’s reordering-rules guide describes maintaining forecasted stock through minimum and maximum quantities and the replenishment route. Those are configurable rules, not ready-made business targets. Choose their values from the actual replenishment process and evidence about demand and supply, rather than copying figures from a generic tutorial.
Write the basis beside each proposed rule. Identify what the business needs to cover, which existing movements affect the forecast and who checks changes to the assumptions. If no reliable evidence exists, keep the rule provisional and review the resulting proposals before activation. Do not invent a numerical stock threshold to make the setup appear complete.
The documentation distinguishes what the route creates. A Buy route can generate a request for quotation, while a Manufacture route can create a manufacturing order. Those are different operational outputs. Ask the demonstrator to show the proposed route for your item, including who receives and acts on the generated record.
Inspect the forecast rather than relying only on shelf quantity. A replenishment decision can depend on expected incoming or outgoing stock. The proposed system should make the relevant basis understandable to the operator. A low physical count does not, by itself, explain whether another order is needed if an incoming receipt already exists.
Check unit multiples where the procurement unit differs from the stock unit. Odoo documents order multiples as part of reordering rules. Establish the actual relationship for your item and test it. An apparently correct replenishment quantity can still be unusable if it ignores how the product is purchased or produced.
Run a fictional receipt, issue, return and count difference in a controlled environment. Retain the source reference and the resulting stock state for each. The exercise should show how the system handles normal events and corrections, not only whether a dashboard total changes. No real warehouse or customer transaction is needed to make the requirements concrete.
Include a repeated event and an unresolved mismatch. If an import or connector receives the same source transaction again, specify how the implementation avoids applying the stock effect twice. If an item cannot be matched confidently, retain an exception rather than assigning it to a convenient product. Those are requirements for the actual configuration to demonstrate.
Inspect access and history with an ordinary operational user. Establish who may count, apply adjustments, change master data and alter replenishment rules. Avoid solving every permission problem by granting broad administration rights. A stock history is useful only if the business can understand how it was produced and who can change the relevant controls.
After the trial, record which functions were observed and which remain manual. A deliberate approval step can be suitable when its owner is clear. Do not label the process fully automatic while someone still reconciles quantities outside the system or manually transfers every reorder proposal.
For related application requirements, see Spout’s web development page and the POS systems guide for the wider sales context. Get started with a redacted control sheet and the stock discrepancy you need the system to explain, keeping supplier and customer records outside the initial brief.
By Spout Team. AI-assisted drafting by Codex, grounded in the linked primary documentation.