Odoo Inventory & Warehouse
Inventory in Odoo is one of the modules that consistently surprises people in a good way. Behind a deceptively simple UI lives a serious warehouse engine — multi-step routes, advanced putaway and removal strategies, multi-warehouse management, replenishment by rules or by MPS — that scales from a one-room storage to a real distribution centre with barcode scanners and a shift team.
After more than a hundred Odoo projects we can say: most companies use about 30% of what Odoo Inventory can do. That's not a problem — if you don't need cross-docking, advanced putaway or multi-step routes, don't configure them. But knowing what's there means you can grow into the system without changing tools every two years.
The catch is that Inventory is the module where data hygiene matters most. Wrong stock counts, badly named locations, untracked moves and the system loses credibility with the team within weeks. We've rescued more inventory implementations than any other module, and the fix is almost always the same: clean data and operational discipline, not new features.
Routes, locations and what 'multi-step' actually means
Odoo's Inventory model is built on locations and moves. Every warehouse has internal locations (stock, packing, dispatch, returns, etc.). Routes string locations together: receive in dock, putaway to stock, pick from stock, pack, ship. You can run one-step (receive directly to stock) or multi-step (receive, quality, putaway), and switch per warehouse.
Most SMEs start one-step and grow into multi-step as volume demands. Don't start with three-step receipts because the consultant loves complexity — start with what your team can do well today, and add steps when the pain point appears. We've simplified more warehouses than we've made complex.
- Locations are the atom — every move is between two locations
- Routes string locations: receive → quality → stock → pick → pack → ship
- One-step, two-step, three-step receipts and deliveries — switchable per warehouse
- Multi-warehouse with inter-warehouse transfers native
- Drop-shipping, cross-docking and make-to-order routes supported
Replenishment — rules, MPS and what to actually use
Odoo offers several replenishment mechanisms: reordering rules (min/max per product per location), MPS (master production schedule for forecast-driven replenishment), make-to-order on sale, and manual replenishment. The right mix depends on your demand patterns.
Most SMEs need a clean reordering-rule strategy on fast movers and manual review for slow movers. The mistake we see is over-engineering rules for products that move twice a year — those are better managed by a planner with a quarterly review than by an automated rule that misfires.
- Reordering rules per product per location — fast-mover staple
- MPS for forecast-driven, mid-term planning
- Make-to-order on sale — for configured or made-to-order goods
- Manual replenishment dashboard for slow movers
- Vendor lead times respected by the procurement engine
Barcode scanning and the warehouse mobile app
Odoo's Barcode app is genuinely good. Operators with handheld scanners or rugged tablets can do receipts, transfers, deliveries, inventory adjustments and putaway entirely from the app. No transcription, no paper, no waiting at a desktop. For warehouses moving more than 50 lines a day, this is a productivity step change.
What you'll need: a bar-coding strategy on products and locations, decent WiFi coverage in the warehouse, scanners that work well with the chosen device. We've seen more Barcode-app failures from bad WiFi than from bad software. Plan the WiFi survey before the go-live.
- Barcode app for receipts, transfers, deliveries, adjustments, putaway
- Works on Android, iOS and Zebra-grade rugged scanners
- Real-time stock updates as operators scan
- Bar-coding strategy on products and locations is a prerequisite
- Plan WiFi coverage early — bad WiFi kills barcode workflows
Putaway, removal strategies and slotting
Putaway strategies decide where received goods go in the warehouse. Removal strategies (FIFO, FEFO, LIFO, closest) decide which units are picked first. Both are configurable per location and per product category. For warehouses with shelf-life products (food, cosmetics) FEFO is the lifesaver.
Slotting — the design of which product goes where — is not automated by Odoo, but the location structure makes it easy to execute. We typically run a slotting workshop with the warehouse manager before go-live to optimise the layout for actual pick patterns. Five hours of design = months of saved walking time.
- Putaway strategies: fixed, dynamic, by category
- Removal strategies: FIFO, LIFO, FEFO, closest location
- Per-product or per-category strategy configurable
- FEFO essential for any product with shelf life
- Slotting design done with warehouse manager before go-live
Inventory accuracy, cycle counts and the integrity loop
Stock accuracy is the metric that proves Inventory is healthy. Odoo supports cycle counts (rotating subset counts), full physical inventories and inventory adjustments with full audit trail. The discipline that matters: count regularly, adjust transparently, and investigate large discrepancies — don't normalise them.
We recommend monthly cycle counts on A-class items, quarterly on B-class, annually on C-class. Full physical inventory becomes unnecessary in well-run warehouses — the cycle counts already cover everything. The team's relationship with stock data shifts from 'we trust nothing, count everything' to 'we trust the system, we count to confirm.'
- Cycle counts (rotating partial counts) preferred over full annual physical
- Inventory adjustments tracked with reason codes and audit trail
- Stock accuracy KPI per location and per product class
- Discrepancies investigated, not normalised
- Counted-by-rotation: A monthly, B quarterly, C annually
Inventory mistakes we keep cleaning up
These are the patterns that destroy stock data integrity within months.
- Starting multi-step receipts before the team can do one-step well — adds confusion not control.
- Bar-coding only products, not locations — half the value of the Barcode app gone.
- Reordering rules on every SKU — rules misfire on slow movers and the noise drowns the signal.
- Skipping the WiFi survey — we've seen Barcode go-lives fail purely because of dead zones.
- Normalising stock discrepancies — every untraced 'plus one' is corruption building.
Metrics that prove Odoo Inventory is healthy
These are the markers we look at quarterly to confirm the warehouse is running clean.
- Stock accuracy on A-class above 98% — measured by cycle count.
- On-time delivery rate above 95% — picking and shipping are reliable.
- Inventory turn aligned with category target — no dead stock building up.
- Average pick-line time within target — slotting and barcode are working.
- Adjustment volume trending down month-over-month — discipline is improving.
How we run inventory implementations at Flydoo
We always do a warehouse walk-through with the warehouse manager before designing anything. Locations on paper and locations on concrete are different things, and the design needs to reflect the second. We sketch locations, label products, walk pick paths — before configuration.
Bar-coding is non-negotiable for warehouses doing more than 50 lines a day. The ROI on a Barcode-app rollout is measured in weeks. We plan the bar-coding rollout, the WiFi survey and the first scanners as a single workstream alongside the configuration.
- Warehouse walk-through with the manager before designing locations
- Start one-step, evolve to multi-step only when volume demands
- Bar-coding strategy designed early — products and locations
- WiFi survey and scanner selection planned alongside configuration
- Cycle count discipline trained from go-live, not bolted on later
Practical checklist before going live with Odoo Inventory
Run this list with your warehouse manager. Most ticked = healthy go-live.
- All locations defined, labelled and bar-coded
- Products have correct dimensions, weights and bar codes
- Reordering rules set on fast movers, manual review for slow movers
- Routes (one-step / multi-step) chosen and tested per warehouse
- Barcode app tested on real devices in the actual warehouse environment
- Cycle count plan agreed (frequency by product class)
- Stock-take at go-live planned and documented
- Initial removal strategies (FIFO/FEFO/LIFO) configured per category
Key takeaways
- Odoo Inventory scales from one-room storage to real distribution centre
- Most SMEs use 30% of features — that's fine, grow into the rest
- Data hygiene matters more than features — bad data kills credibility fast
- Bar-coding products AND locations doubles the value of the Barcode app
- Cycle counts beat annual physical inventory for accuracy and team morale
- Start one-step routes, evolve to multi-step when volume demands
Frequently asked questions
Can Odoo handle a real distribution centre?
Yes — we have clients running 5,000+ SKU distribution centres with shifts, scanners, multi-step routes and barcode-driven workflows entirely in Odoo. The features are there: putaway/removal strategies, slotting, multi-warehouse, replenishment, barcode app, cycle counts. The success factor is operational discipline more than software features.
Do we need Odoo's Barcode app or can we manage without?
Below ~50 lines a day, manual works. Above that, the Barcode app pays back in weeks — fewer errors, less transcription, real-time stock. For any growing warehouse the question is when to roll it out, not if. We recommend doing it before go-live so the team learns the modern workflow from day one rather than retraining six months later.
How accurate can stock data be in Odoo?
With clean processes, 98%+ accuracy on A-class items is achievable and sustainable. We have clients above 99%. The key is cycle count discipline (rotating partial counts), enforced bar-coding on receipts and shipments, and zero tolerance for unexplained adjustments. Without that discipline, accuracy degrades regardless of software.
Can Odoo handle multi-warehouse with inter-warehouse transfers?
Yes — multi-warehouse is native, with inter-warehouse routes, transfer orders, and consolidated stock visibility. For a Belgian SME with 2-5 warehouses including drop-ship locations, this works smoothly. For very large multi-country networks (20+ warehouses, complex consolidation), the model still works but needs careful design and testing.
What about WMS-grade features — wave picking, voice picking, conveyors?
Odoo has wave-picking and batch-picking native. Voice picking and conveyor integration aren't native — for those you'd integrate a third-party WMS or use OCA modules. For the typical Belgian SME warehouse, native Odoo + Barcode app is enough. For high-throughput logistics, a dedicated WMS layered on Odoo is the right pattern.
Need help applying any of this to your own context? We're happy to talk.