An Odoo inventory setup is ready when a warehouse employee can receive, locate, move, deliver and count stock with records that match the physical operation. Importing a product list is only one part of that job. The harder decisions concern product identity, units, storage locations, ownership and the treatment of exceptions.
This checklist helps a growing business prepare a controlled first release. Technical references use Odoo 19 documentation. Test the workflow in your installed version and configuration before applying it to live stock.
1. Agree what each product record represents
Start with a small sample that includes ordinary stock, a variant, an item bought in one unit and sold in another, and any item requiring traceability. Give each distinct item an agreed internal reference. Resolve duplicate names before import; a warehouse should not need to guess which of two almost identical records is correct.
Build a simple preparation sheet with the internal code, description, stock unit, purchase unit, supplier reference and tracking requirement. Assign an owner to confirm each field. Keep a supplier’s reference separate from your own code where the two serve different purposes.
Review physical labels alongside the sheet. If staff recognise a carton code but sell individual pieces, the test must demonstrate the intended conversion. Do not assume a clean-looking spreadsheet proves that quantities will be interpreted correctly.
2. Design a location structure people can use
In Odoo, warehouses represent physical sites and locations provide detail within them. Location types distinguish internal stock, suppliers, customers and other movements. The official inventory management guide explains this structure.
Start with the level of detail needed to find stock and control a handoff. A small storeroom may need a few clear locations; an operation with receiving, inspection and picking areas may need more. The process map should explain both where goods are and who must act next.
| Area to decide | Question for the team | Evidence from the pilot |
|---|---|---|
| Receiving | Who records a shortage or damaged delivery? | A receipt with an exception and an identified owner |
| Storage | How will someone find the item without asking a colleague? | A matching location label and stock record |
| Picking | How is a part-delivery handled? | A completed dispatch and an understandable remaining quantity |
| Returns | Who decides whether returned goods can be sold again? | A documented disposition and corresponding stock movement |
| Adjustments | Who investigates and authorises a discrepancy? | A count record with a clear explanation |
3. Establish an opening-stock cut-off
Choose when the opening count represents reality. Identify any receipts or dispatches that can occur while counting, and define how those movements will be reconciled. Otherwise, staff may compare a morning physical count with an afternoon system balance and mistake timing differences for missing stock.
Odoo distinguishes entering a counted quantity from applying the resulting adjustment. Applying an adjustment changes the stock record and leaves movement history. Its inventory adjustments guide also warns about stock moving between a count and its application.
Use a small test import first. Reconcile item, location, unit and quantity, then have the stock owner review the result. Keep the source count and a record of what was applied. Agree any financial reconciliation with the responsible finance team before releasing opening balances.
4. Test the arithmetic through real movements
Illustrative example, not a customer result: a fictional distributor starts with 48 filters, receives 12 and dispatches 9. The expected balance is 51. A later count finds 50. The exercise is to explain the one-unit difference before approving a correction.
Check the receiving record, dispatch quantity, unit conversion and any movement into another location. If the difference remains, record the count and reason through the agreed adjustment process. Simply replacing 51 with 50 would hide whether the underlying problem was a missed transaction or a physical loss.
Run another test where only part of a customer order is delivered. Then try a return, an incorrectly selected product and a transfer between locations. Each test needs an expected final balance and an employee who can explain the result.
5. Introduce replenishment and counting deliberately
For the first phase, review replenishment suggestions with a buyer who knows supplier lead times and order constraints. Odoo’s replenishment report provides a place to review manual reordering suggestions and adjust the proposed quantity. Configuration still needs to reflect your products, suppliers and demand.
Set a routine for checking items that create the greatest operational disruption. Odoo supports cycle counts by location, with a configurable interval after enabling storage locations. See the cycle-count documentation. Choose the frequency according to your process and investigate repeated discrepancies.
6. Release with an owner and a short issue log
Confirm that receiving, picking and stock-control staff can complete their tasks with their own permissions. Test any scanners and labels in the actual work area. Name the person who resolves duplicate products, missing locations and unexplained balances during the first operating days.
The release checklist should include a reconciled opening count, passed transaction tests, trained users and an agreed escalation contact. Track exceptions after launch and change the setup when the evidence points to a specific problem.
Explore the related retail and distribution workflows and Lava’s Odoo services. When you send an enquiry, include the number of stock locations, your current product records and the stock-control issue you want to resolve.
For a related planning step, use the Shopify and Odoo integration checklist.