Odoo Inventory is the module that governs every physical movement of product. Upstream it receives needs from Purchase (receipts) and Sales (deliveries). Downstream it feeds Manufacturing (component consumption and finished goods) and Accounting (stock valuation). This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise; where Odoo 19 differs, it says so.
When an implementation is healthy
An inventory implementation works when five conditions hold:
- every product movement goes through Odoo, with no parallel records on paper or in spreadsheets;
- the receipt, delivery and internal-movement flows follow the physical reality of the warehouse, without needless customisation;
- replenishment comes from reordering rules and not from purchase requests made by hand;
- the quantities in Odoo match physical stock within an acceptable tolerance;
- where process or regulation requires it, lot or serial traceability is complete from one end of the chain to the other.
The module has five areas: products (catalogue, tracking, valuation), warehouses and locations (structure, routes, operation types), transfers (receipts, deliveries, internal moves), replenishment (reordering rules, make to order) and reporting (forecast stock, stock valuation, moves history).
Module basics for daily users
Before going into the settings it is worth checking that operators know the platform's tools, because many adoption "anomalies" start there.
| View | Typical use in the warehouse |
|---|---|
| Kanban | Inventory Overview: one card per operation type, with the transfers to work |
| List | All transfers of an operation type, bulk validation, filters by state |
| Form | A single transfer (receipt, delivery, internal), with lines and entry of lots or serials |
| Pivot | Stock value by product category, volumes moved by period |
| Graph | Forecast stock over time, trend of replenishment demand |
The Inventory Overview is the screen the operator opens every morning. Each card (Receipts, Deliveries, Internal Transfers and so on) shows how many transfers are to be processed. In a healthy implementation the "late" counts are low and there is no backlog older than forty-eight hours.
A few filters are used every day. On transfers: state (ready, waiting, done), scheduled date, partner, grouped by operation type or by responsible. On products: type (good or service) and route (buy, manufacture, make to order), grouped by category. On reordering rules: location and product, sorted by quantity on hand so that imminent stock-outs show up. On lots and serial numbers: grouped by product and filtered by expiry date, useful for FEFO. Recurring views are saved as favourites, for example "Receipts to validate today", "Late deliveries", "Components below minimum".
Every transfer and every product has a chatter with three tools: the internal note for exceptions (damaged goods, count difference, carrier problem), the message to notify a partner directly from the document and the activity to assign a follow-up (chase a supplier for confirmation, order a recount). An example from practice: a receipt is blocked because the supplier delivered 48 units out of 50. The manager notes "Supplier sent 48 units, the order was 50. Awaiting the credit note", schedules an "Upload Document" activity for when the credit note arrives and mentions the purchasing manager so they contact the supplier.
Product form and tracking
Every inventory operation depends on how the product is configured. Three settings decide what Odoo can do with it: the product type, the tracking and, if there is tracking, its level.
A service never generates stock movements. A good does, but only if it has a tracking value: a good with the field empty is untracked and has no quantity on hand, no forecast, no reordering rules and does not appear in inventory adjustments. A physical item loaded as a service and a good without tracking are the two most frequent configuration errors, and in both cases the symptom is the same: "Odoo does not show me the stock".
In Odoo 20 tracking is chosen in a single field, Tracking, with three values: by quantity (generic stock, no identification of the single unit), by lots (traceability by production batch) and by unique serial number (one number per unit). Clearing the field makes the product untracked. In Odoo 19 there was a Track Inventory checkbox instead, so anyone coming from an older project looks for a box that no longer exists.
Choosing the type of tracking follows two questions:
| Question | If the answer is yes |
|---|---|
| Do you need traceability of the single unit (warranty, recall, device ID)? | Serial number |
| Does the product come in production batches (food, pharma, chemicals)? | Lot |
| Neither | By quantity (default) |
Lots and serials require three things: the number is entered at receipt (or generated from the vendor's lot), you state at delivery which lot the goods were taken from, and the traceability report must be able to rebuild the complete chain upstream and downstream. Switching tracking on for a product that already has stock without lots raises a warning: the existing stock has to be assigned to a lot with an inventory adjustment before tracking is really operational. This is why it is decided before opening balances are loaded.
Receipt and delivery flows
Odoo offers three inbound and three outbound flows. You choose the one that matches how the warehouse works, not the most sophisticated.
| Flow | Path | When to use it |
|---|---|---|
| One-step receipt | Vendor, then straight to Stock | small warehouse, low-risk products, no inspection |
| Two-step receipt | Vendor, Input, Stock | most SMEs with a receiving area: check or unboxing before the shelf |
| Three-step receipt | Vendor, Input, Quality Control, Stock | regulated sectors (food, pharma), with a formal quality sign-off |
| One-step delivery | Stock, then Customer | small warehouse, direct pick and ship |
| Two-step delivery | Stock, Output, Customer | separate picking and shipping teams, an output area |
| Three-step delivery | Stock, Pick, Pack, Customer | high volumes: orders consolidated, packed and then shipped |
Steps beyond reality produce phantom transfers: operators skip them, validate them without checking or forget them. The opposite case is just as common. If the warehouse has a separate receiving area but the flow is one-step, the receipt is recorded only when the goods are on the shelf, sometimes two days later, and meanwhile purchasing sees as "not arrived" goods that are already in the building. The fix is to move to the two-step flow.
The path of a two-step receipt: the confirmed purchase order creates the receipt in the Ready state. The operator physically receives the goods, opens the receipt, enters the actual quantities (and the lot or serial if the product has one) and validates. The move goes from Vendors to Input. Odoo itself creates the internal transfer from Input to Stock, which the operator validates when the goods are on the shelf; only then does the quantity in Stock update. Outbound, two-step, the confirmed sales order creates the pick (waiting or ready depending on availability). The operator picks, confirms quantities and validates: the move goes from Stock to Output. Odoo creates the delivery order, which shipping validates by taking the goods from Output to Customers. The sales order status becomes "delivered" and the invoice can go out.
Operation types define what kind of transfer is created and between which locations. Receipts go from Vendors to Input (two-step) or to Stock (one-step). Deliveries leave from Stock or Output and arrive at Customers. Internal transfers go from any internal location to any other. Pick goes from Stock to Output (two-step) or to Pack (three-step), pack from Output to the Packing Zone (three-step only), and manufacturing takes components from Stock to the virtual production location. With the right number of steps, sources and destinations are born correct. When they turn out wrong, someone has usually changed the steps and then patched the symptoms by hand.
Locations, putaway and removal strategies
The standard location tree of a warehouse has the warehouse short code as its root. Below it sit Stock (where goods go after receipt), Input (transit area in two and three-step inbound, before the check), Quality Control (three-step receipt only), Output (outbound transit in two and three-step) and Packing Zone (three-step delivery only). Under Stock you add the physical locations of the warehouse: shelves, cells, the cold room. Outside the warehouse there are virtual locations: Vendors (where goods "come from"), Customers (where they "go"), Inventory Loss (gains and losses from counts) and the designated scrap location for damaged or obsolete goods.
Internal locations have to be enabled in the settings (the Storage Locations feature). Without it, Odoo sees the warehouse as one undifferentiated space: putaway rules and counts by zone do not exist. Enabling them at go-live costs nothing. Adding them later, with goods already inside, takes an inventory.
Putaway rules send incoming goods to specific locations: a fragile product to shelf B, the "cold chain" category to the cold room, a raw material to shelf A. They are defined by product or by category. Without rules, in a warehouse with several locations everything lands in Stock and the operator decides by hand where to put it; rules remove that decision at receiving time.
The removal strategy sets which lot or location goes out first and is configured by product category:
- FIFO: what came in first goes out first (receipt date). It is the default for most products;
- FEFO: what expires first goes out first. Required for food and pharma, it works only if expiry dates are entered on lots at receipt. If dates are not entered, the strategy stays configured but cannot work;
- LIFO: the last arrival goes out first. Rarely used;
- Closest location: shortens travel, suited to large warehouses;
- Least packages: always available in the Odoo 20 location form.
It must not be confused with valuation: the removal strategy decides which lot goes out, valuation at what cost it reaches the accounts.
Routes are not customisation
Routes are the standard tool by which Odoo knows how a product moves between locations. They are not a workaround: they are the intended configuration.
- Buy: the need generates a request for quotation to the supplier, then the receipt, then stock.
- Manufacture: the need generates a manufacturing order, then finished goods go to stock.
- Make to order (MTO): confirming the sales order triggers replenishment at once, with no safety stock.
- Dropshipping: the sales order generates an order to the supplier, who ships directly to the customer.
A product can have several routes, even combined, and the right combination starts procurement without manual intervention. If replenishment has to be triggered by hand every time, the routes are not configured. The Odoo 20 documentation distinguishes automatic warehouse routes (generated by the receipt and delivery steps) from optional routes, which can be assigned to products, categories, package types, shipping methods and sales order lines; with several sources available, Odoo picks the route able to handle the product. With several warehouses, the resupply routes between them also have to be configured.
Using make to order for everything, so as not to hold stock, looks prudent but has a precise cost: every customer order sits waiting for a supplier order, and the date promised to the customer is the supplier's lead time. Products that turn over need a buffer, governed by reordering rules.
Reordering rules
For each product held in stock, the reordering rule defines four values: the minimum quantity, below which (as forecast quantity) replenishment is triggered; the maximum quantity, up to which stock is replenished; the order multiple, that is the supplier's minimum lot; and the lead time, made up of the supplier's time plus the security time, which says how many days before a stock-out to order.
The scheduler runs daily. For every rule it compares the forecast quantity with the minimum and, if lower, creates a request for quotation (buy route) or a draft manufacturing order (manufacture route). Purchasing confirms the request, which becomes an order, and the receipt is born from it. When the receipt is validated, stock realigns and the forecast quantity goes back above the minimum.
The indicator to watch is habit: if purchases start because "we order every Monday" looking at the shelves, and not from the scheduler's output, the rules are not in use. The predictable result is overstock on what is bought by reflex and stock-outs on what has irregular consumption.
Stock valuation
The valuation method is set by product category and determines how the value of stock is calculated and carried to the accounts. It cannot be changed after go-live without a delicate intervention with finance, so it must be decided before any movement. There are three methods:
- Standard cost: the product has a fixed cost and the variance is recorded when the actual cost differs. Simple and suited to manufactured products with stable costs.
- Weighted average cost (AVCO): the cost is recalculated as a weighted average at every receipt. The typical choice for goods bought at variable prices.
- FIFO: the oldest stock is valued at its original purchase cost and goes out first. Used for perishables and lot-tracked products.
The second choice is between automated and manual valuation. With automated, every stock movement generates its accounting entry in real time, with no manual posting. With manual, the accountant posts at intervals. Automated is strongly preferable: manual produces an accounting lag and one more reconciliation. A note for those coming from Odoo 19: in Odoo 20 the stock input and output accounts are no longer used, and balances other than zero have to be cleared on upgrade (from 18 this is handled automatically). The detail sits in the Accounting area.
Adjustments, scrap and returns
Physical inventory starts from the Operations menu, choosing the products or locations to count. Operators enter the counted quantities, also by scanning barcodes, and Odoo highlights the differences between system and counted quantity. "Apply All" posts the adjustment to Inventory Loss, and with automated valuation an accounting entry follows between Inventory Loss and the stock account.
Every difference has to be investigated to understand its cause: an adjustment made without understanding why the stock did not match hides a problem that will come back. A one-off count at month end lets variances accumulate for thirty days; the alternative is cycle counting, that is continuous partial counts by zone.
Scrap is recorded from stock, from a transfer (cog, then Scrap) or from the form of a lot or serial number: you give product, quantity, lot or serial and reason, then confirm. The goods go to the designated scrap location, with the option of triggering replenishment. If the scrap was a mistake it is reverted from the Moves History report: "Scrapped" filter, select the move, then Actions and Revert (administrator access is needed).
Customer returns and scrap are different flows. Using the scrap location for returns mixes resaleable goods with goods to destroy and distorts the value of stock.
What changes with Odoo 20
Odoo 20 Enterprise is the baseline, unless the project states Odoo 19. Before classifying a request as development (Studio or custom), it is worth comparing it with the features of the version, because many needs that used to require bespoke work are now standard. The novelties are grouped by theme.
Transfers and picking. Batch, wave and cluster transfers have been reworked: they can be added to a batch from the batch form, from the transfers list (Actions, Add to batch, optionally as draft) or move line by move line. Automatic batches are configured per operation type (automatic creation, with maximums for transfers, lines or weight, auto-confirm and grouping by product, category, source location, carrier or date). Batches appear in a timeline or Gantt view with employee assignment, and when transport management is enabled the dispatch details (location or vehicle) show up. Still in place from Odoo 19: merged batch pickings, packages inside packages, customer and vendor names and warehouse short codes in traceability reports, and improved pick and delivery reports.
Routes and reordering. Route configuration per product is more automatic, with settings to activate make to order, default routes when a vendor lacks the product and several routes on sales order lines. Reordering rules have time horizons, last reorder date, previews, suggestions from the vendor catalogue and multiples taken from pricelists and bills of materials. The replenishment report has a horizon in days and a Suggest button that recalculates minimum and maximum from order history over a chosen period, with a growth percentage. Resupply between warehouses and between companies runs through make to order or reordering rules, and the report indicates the sourcing warehouse and the available quantity. Just-in-time logic shows only the demand that falls within the supplier's lead time plus the horizon.
Locations, scrap and allocation. The location form carries the location type, storage category, replenishments (destination for buy and manufacture routes), inventory frequency (last and next expected), removal strategy (FIFO, LIFO, closest location, least packages, FEFO) and buttons for putaway rules and products. For scrap there is no dedicated checkbox: scrapped goods go to the designated scrap location (Inventory adjustment); you can revert from Moves History and scrap directly from the form of a lot or serial. The Allocation report (Inventory, Reporting) assigns incoming units from purchase or manufacturing to specific sales or manufacturing orders, also from the forecast report. With the Location for allocation the assigned units stay apart from stock until delivery or consumption: nothing moves until the incoming operation is validated and already reserved quantities cannot be allocated.
Reports and analysis. The Locations report is now called Detailed Stock (dead stock, stranded inventory, discrepancy reports). Moves analysis has an Aging Report favourite that follows remaining quantity and value month over month.
Documents, labels and devices. The CMR consignment note for road transport is printed from the delivery order or, one per delivery, from a batch transfer; Odoo fills in what it knows and the rest is completed by hand. In Inventory, Configuration, Manage Printers you configure ePOS printers, ZPL printers over the network without an IoT box and IoT printers for automatic printing on validation. Barcodes are defined per package and per product variant. With barcode, scanning a package processes its whole content, lines show source, destination and destination packages, the Quality Checks button appears when checks are required, and scanning a product that belongs to another open receipt of the same vendor offers batch receipts. Supported RFID readers are CipherLab RS36 and RS38 (also with the barcode PWA or a browser), Zebra TC53e-RFID and Zebra RFD90XX and RFD40XX.
Shipping and small renamings. There is a ShipStation integration; the Sendcloud connector has been reworked (pickup points, return labels, customs documents) and so has the FedEx connector (for v18 onwards, with a testing environment). On the product, Customer Lead Time is now called Delivery Time and the Check Availability button is now called Reserve.
For development requests the guidance is this: manual stock monitoring, replenishment and stock aging analysis on spreadsheets, bespoke traceability exports, hand-filled consignment notes, custom label-printing bridges and custom route logic are first tested against the routes, reordering, packages, barcode, printers and reports of Odoo 20.
The rationalisations you hear
Some phrases are almost always the symptom of a configuration or process problem.
| In the company they say | What it really is |
|---|---|
| "We have three-step quality control, but we validate it together with the receipt" | It is a one-step receipt with more clicks. Either use the step or remove it. |
| "The storekeeper checks the shelves and tells purchasing what to order" | Reordering rules exist to automate this. Manual checks are a daily tax on operators' time. |
| "We do not use lots because they slow the warehouse" | Without lots there is no traceability: a product recall or a customer dispute becomes unsolvable. |
| "Stock in Odoo does not match, we only use it for orders" | Then Odoo Inventory is an order register: valuation, forecasting and replenishment are all wrong. |
| "We adjust stock at month end to match the physical count" | Daily differences pile up silently for thirty days. The alternative is cycle counting. |
| "We have a single Stock location for everything" | Locations cost nothing at go-live. Without them putaway rules, reports by location and counts by zone are impossible. |
| "Valuation is manual, finance posts at month end" | Automated valuation posts an entry per move in real time. Manual creates a thirty-day lag and a reconciliation. |
| "We use make to order for everything so we hold no stock" | Make to order blocks every sales order waiting for a purchase order: lead times and promise dates become unmanageable. |
Warning signs
- Goods with an empty Tracking field, or services in place of goods.
- System stock differing from the physical count by more than two per cent with no adjustment in progress.
- Transfers validated without entering the real quantities: "done" equals "demanded" and nobody checked.
- Lot or serial traceability configured but lots not entered at receipt: the chain is broken from day one.
- Every product on the make to order route: no buffer, every sales order generates a purchase order and the lead time becomes the supplier's.
- No reordering rules: replenishment driven only by manual purchase requests.
- A one-step flow with a real, distinct receiving area.
- Adjustments performed without investigating the cause of the variance.
- FEFO active but expiry dates not entered at receipt.
- Storage locations not enabled: putaway rules unavailable and counts by location impossible.
- Automated valuation not configured: accounting receives no real-time stock entries.
- Several warehouses in Odoo but no resupply route between them.
- Scrap location used for customer returns.
How to verify a configuration
After configuring or assessing inventory, verification goes through these checks:
- all stocked products are of type good and have a Tracking value;
- the receipt and delivery steps match the physical operation (one, two or three);
- storage locations are enabled and the tree reflects real zones and shelves;
- operation types have correct sources and destinations for each flow;
- products that require traceability have lot or serial tracking before opening stock is loaded;
- putaway rules are configured for the products or categories directed to specific sub-locations;
- the removal strategy (FIFO, FEFO, LIFO) is set by category, and for FEFO expiry dates are entered at receipt;
- reordering rules exist for all stocked products, with minimum, maximum, multiple and lead times;
- at least one inventory count has been done and the results reconciled before go-live;
- the valuation method (standard, average, FIFO) is set by category before any movement;
- automated valuation is configured and entries post without manual intervention;
- the scheduler has been tested: below the minimum, requests for quotation or manufacturing orders really appear;
- the thirty-day stock forecast has been read for stock-outs.
Standard, configuration, integration or custom development
To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: multi-warehouse and multi-location stock management with location-level tracking, automatic replenishment with minimum and maximum rules or the make-to-order route, lots and serials with complete upstream and downstream traceability, barcode scanning for receipts, picks and internal transfers, three-step routing, allocation of landed costs to stock value, inventory adjustments and cycle counting, scrap with reversal, stock aging, CMR consignment notes, network label printing without IoT and the three valuation methods.
Six questions help classify each gap before asking for development:
- How is stock kept today? In an ERP, a spreadsheet, a warehouse management system or from memory? How often is it reconciled with physical reality? A spreadsheet is replaced by the standard. An external warehouse management system to keep leads to an integration.
- What triggers a replenishment order? A person watching stock, an automatism, a periodic review? A manual trigger is solved with reordering rules. Demand planning with complex forecasts beyond the native planner may need an external tool.
- Are lots or serials tracked? For which products and for what purpose (traceability, warranty, recall)? If a regulation requires it, it is configuration. If expiry is needed, it is configuration with lots and expiry dates. A complex production genealogy is configured in the manufacturing context.
- How is picking done? Paper lists, mobile scanner, verbal instructions? How are errors caught? Paper picking is standard plus a process change. A warehouse management system with very deep scanning logic leads to an integration.
- Is there negative stock? How often, in which areas, from what cause? It is always a configuration gap (routes or confirmation flow) or a process gap (receipts not confirmed before consumption).
- How are differences handled after a count? Who adjusts, who approves, how is the accounting entry made? If the entry is manual, it is solved with Odoo's adjustment and the automatic entry.
The typical classification of the commonest cases is this:
| Common gap | Typical path | Signals that push towards custom |
|---|---|---|
| Stock kept on a spreadsheet | Standard | Extremely complex location logic (automated storage and retrieval) |
| Manual replenishment | Configuration (reordering rules) | Demand-driven MRP with forecasts beyond the native planner |
| No lot or serial tracking | Configuration | An external regulatory system must remain the official traceability record |
| Paper picking | Standard plus process change | Customer-branded pick labels with non-standard fields |
| Stock aging analysis in Excel | Standard (Aging report) | Aging rules that depend on data Odoo does not hold |
| CMR consignment notes filled by hand | Standard (print the consignment note) | Carrier-specific transport documents beyond the CMR |
| Frequent negative stock | Configuration and process change | None |
| External warehouse management system in use | Integration | The system's contract has exit penalties: replace it only if total cost justifies it |
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-inventoryGuide to designing and assessing the Odoo 20 Enterprise Inventory module: product form and tracking, one, two or three-step receipt and delivery flows, locations, routes, reordering rules, valuation, adjustments and scrap. It includes warning signs, the rationalisations heard in companies and the questions that decide between standard, configuration, integration and custom development. Use it when setting up or checking Inventory in Odoo, with or without user interviews.