Odoo Inventory: Warehouses, Locations, and Stock Moves

Introduction

Picture the classic scene: sales confirms delivery Friday, the planner finds out Thursday night, and Odoo Inventory was never part of the conversation. That is the gap this guide addresses.

We ranked ten scenarios from creating a BOM for a simple table to running a deliberately exaggerated level-10 production puzzle, each with a click-by-click Odoo checklist.

Odoo Inventory is where physical reality (stock, batches, pickings, production) meets what customers and finance expect. When it works, nobody retypes quantities. When it does not, everyone blames the ERP.

Plenty of factories and warehouses run on experience, WhatsApp, and Excel tabs called FINAL_v3. It holds until you scale, add a second site, or audit traceability.

Picture the classic scene: sales confirms delivery Friday, the planner finds out Thursday night, and Odoo Inventory was never part of the conversation. That is the gap this guide addresses.

With Inventory, you model how goods actually move: receive, store, pick, manufacture, ship, scrap, replenish. Each step leaves a record your future self will thank you for.

You will read ten use cases with concrete company examples, from first BOM to barcode on the shop floor.

Operations directors, warehouse leads, and production planners are the primary audience. Developers can join later; this is business language first.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Inventory.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Inventory is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Sales promises delivery Friday. The planner learns Thursday evening because the order lived in email, not in Odoo Inventory. Expedite fees eat the margin, and finance discovers the stock gap at month-end, not on Tuesday.

Warehouses and factories run on experience, yet stock and production data often live outside Odoo. That gap creates stockouts, urgent purchases, and month-end surprises.

Sound familiar? Teams usually hit these walls:

• Stock files that do not match what sales promises
• Production or purchasing plans made without live quantities
• Traceability gaps when customers or auditors ask questions

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Inventory, and measure what changes.

Top 10 Inventory Use Cases

10 use cases for Odoo Inventory, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Receive your first vendor delivery in two clicks Level 1 — Easy

Level 1 is the simplest possible Inventory action: one user, one truck, one stock move. No routes, no barcode, no automation, just a confirmed receipt that updates the on-hand quantity.

Here's how you'd do it in Odoo:

1. Open the related Purchase Order and click the Receive Products smart button to open the linked transfer.
2. Click Check Availability, then adjust the Done quantity per line to match what the driver actually delivered.
3. Click Validate to confirm the receipt; Odoo posts the stock move from Vendors into WH/Stock.
4. Open Inventory, Reporting, Stock to confirm the new on-hand quantity matches what is on the dock.
5. Print the receipt PDF from the chatter and file it as proof of reception for the accounting team.

What you get: What is on the dock matches what is in the system in under a minute, with zero re-keying between Purchase and Inventory.

2. Pick, pack and ship a customer order with a carrier and tracking link Level 2 — Easy

Level 2 stays on a single user but covers the full outbound flow. One delivery order, one carrier, one tracking number sent automatically to the customer once stock leaves the warehouse.

Here's how you'd do it in Odoo:

1. Open a confirmed Sales Order and click the Delivery smart button to open the outgoing transfer.
2. Click Check Availability so Odoo reserves the stock from WH/Stock onto the picking lines.
3. Pick the goods, then fill the Done quantity per line and pick a Carrier and Tracking Reference for the shipment.
4. Click Validate to release the stock move and trigger the shipment confirmation email to the customer.
5. Open Inventory, Reporting, Stock Moves to confirm the move history links Sales, Inventory and the invoice draft.

What you get: On-hand quantities reflect reality the moment the truck leaves, and the customer gets a tracking link without anyone typing it twice.

3. Set reordering rules so Odoo opens the right RFQ before you stock out Level 3 — Easy

Level 3 introduces automatic replenishment. Odoo watches your fastest movers and proposes a purchase order before the bin runs empty, without anyone walking the aisles to check.

Here's how you'd do it in Odoo:

1. Open a fast-moving product and click the Reordering Rules smart button to add a new rule.
2. Set Min Quantity, Max Quantity, Preferred Vendor and Lead Time, then save the rule on the product.
3. Repeat the operation for the top twenty SKUs identified from the Sales Reporting Pareto view.
4. Go to Inventory, Operations, Run Scheduler and let Odoo create the proposed Requests for Quotation.
5. Review the proposed RFQs in Purchase, adjust quantities if needed, then confirm them as real POs.

What you get: Bestseller stockouts drop measurably without anyone watching the shelves, and slow movers stop tying up cash.

4. Track lots and serials so a recall takes minutes, not days Level 4 — Medium

Level 4 turns on full traceability. Every incoming unit gets a lot or serial number so Odoo can replay the upstream and downstream history of any item on demand.

Here's how you'd do it in Odoo:

1. Open a product and set Tracking to By Lots or By Unique Serial Number on the Inventory tab.
2. On the next reception, type the lot number from the vendor packaging into the Detailed Operations panel and validate.
3. On each customer delivery, Odoo enforces which lot is being shipped and stamps the outgoing move accordingly.
4. Open Inventory, Products, Lots and Serial Numbers, pick a lot and click Traceability to see every move it touched.
5. Test a mock recall: filter customer deliveries by lot, export the list and confirm the report is ready in minutes.

What you get: Audit-grade traceability is built in, and a recall is filtered, exported and notified in minutes instead of mobilizing a team for a full day.

5. Map the warehouse layout with Zone, Aisle, Shelf and Bin locations Level 5 — Medium

Level 5 encodes the physical floor inside Odoo. Storage Locations and Putaway rules let pickers reach the right bin directly instead of walking the whole warehouse looking for a product.

Here's how you'd do it in Odoo:

1. Go to Settings, Inventory and enable Storage Locations and Multi-Step Routes for the warehouse.
2. Open Inventory, Configuration, Locations and build the hierarchy Zone, Aisle, Shelf, Bin under WH/Stock.
3. Print the location barcode labels from each location form and stick one per bin on the shelving.
4. On each product, set a Putaway Strategy so receipts land in the right zone automatically on validation.
5. Run a quick test transfer to confirm Odoo suggests the correct destination bin on each picking line.

What you get: Pickers stop walking randomly; productivity rises measurably with the same headcount and the same warehouse footprint.

6. Block defects with a multi-step receipt: dock, quality, stock Level 6 — Medium

Level 6 splits the inbound move into stages. The truck unloads at the dock, Quality inspects at a buffer location, and only validated lots reach the salable WH/Stock zone.

Here's how you'd do it in Odoo:

1. Open Inventory, Configuration, Warehouses, edit the main warehouse and set Incoming Shipments to Receive in 3 steps.
2. Confirm Odoo creates the new buffer locations WH/Input and WH/Quality Control under the stock hierarchy.
3. Install the Quality app and create a Quality Control Point on the Quality Control location for the product family that needs checks.
4. On reception, validate the dock to quality transfer, run the inspection, then validate the quality to stock transfer for accepted lots.
5. Route failed lots to WH/Scrap with a reason code so vendor performance reports in Reporting stay data-driven.

What you get: Defective lots are caught at the buffer, never in a customer's hands, and vendor scoring becomes a real KPI.

7. Dropship long-tail SKUs directly from supplier to customer Level 7 — Hard

Level 7 introduces a route where you sell the product but never touch the box. The supplier ships directly to the customer while Odoo tracks the full chain end to end.

Here's how you'd do it in Odoo:

1. Go to Settings, Purchase and enable Dropshipping under the Logistics section.
2. On each chosen product, open the Inventory tab and set Route to Dropship with a Vendor and a realistic Lead Time.
3. Confirm a customer Sales Order on those products; Odoo auto-creates a Purchase Order pointing to the customer address.
4. Confirm the PO; the vendor ships directly to the customer and the tracking number lands on the customer record.
5. Receive the vendor bill against the PO; AP, AR and the Sales Order reconcile in Accounting automatically.

What you get: Long-tail SKUs generate revenue with zero warehouse footprint and zero double handling on the inventory team.

8. Roll out the Barcode app on the warehouse floor Level 8 — Hard

Level 8 adds a hardware layer. A handheld scanner replaces typed SKUs and bin codes, dropping picking error rates to near zero and increasing the number of lines processed per hour.

Here's how you'd do it in Odoo:

1. Install the Barcode app from Apps and assign a Barcode Nomenclature to the main warehouse.
2. Generate and print product and location barcodes from Inventory, Reporting, Print Labels.
3. Equip the floor with handheld scanners or tablets logged into the Barcode interface.
4. Run the next reception in Barcode mode: scan the supplier label, scan each product, scan the destination bin, then validate.
5. Open Inventory, Reporting, Operations to compare error rates and picking time before and after the rollout.

What you get: Wrong-SKU shipments drop to near zero and the warehouse processes more order lines per hour with the same headcount.

9. Balance stock across a hub-and-spoke multi-warehouse network Level 9 — Hard

Level 9 is the multi-site setup. One central hub feeds several regional spoke warehouses with daily inter-warehouse transfers, without anyone phoning depots to ask who has what.

Here's how you'd do it in Odoo:

1. Go to Inventory, Configuration, Warehouses and create one Hub and several Spoke warehouses with their own short codes.
2. On each Spoke, set the Resupply path to pull from the Hub through scheduled internal transfers with a defined lead time.
3. Configure Reordering Rules per spoke per SKU so the scheduler proposes inter-warehouse moves before any spoke stocks out.
4. Run Inventory, Operations, Run Scheduler daily and review the proposed transfers between the Hub and the Spokes.
5. Open Reporting, Stock by Warehouse to spot imbalances and adjust Min and Max per location every week.

What you get: Each region holds the right stock without anyone manually phoning depots, and inter-site transfers run on a published cadence.

Designing the route graph, the resupply priorities per spoke and the daily transfer cadence is the kind of multi-warehouse setup Dasolo runs as a partner-led Inventory engagement.

10. Run a fully automated WMS with IoT, AI demand forecasts, EDI and live dashboards Level 10 — Expert

Level 10 is the full operating system. IoT scans, AI forecasts, EDI feeds and carrier APIs combine into a warehouse where humans only handle exceptions and the system runs the rest.

Here's how you'd do it in Odoo:

1. Connect IoT scanners and label printers through the Odoo IoT box so every dock event posts a stock move with zero typing.
2. Enable Cycle Counts and ABC Storage so the system schedules continuous physical inventory instead of one yearly stocktake.
3. Train an Odoo AI Demand Forecast on twenty-four months of sales history and let it adjust Min and Max on Reordering Rules weekly.
4. Wire EDI flows with key vendors so RFQs, confirmations, ASNs and vendor bills travel without anyone typing a single line.
5. Map carrier APIs (DHL, UPS, GLS) so each delivery order picks the cheapest service that still meets the promised customer date.
6. Build a Spreadsheet dashboard Warehouse Live tracking dock activity, picking time, fill rate and stock turn, refreshed in real time and piped to leadership by webhook.

What you get: The warehouse runs as a system, not as a team putting out daily fires, with a consistent fill rate and a finance-grade stock value at all times.

Designing the IoT layout, the AI feedback loop, the EDI mappings and the live operations dashboard is the architecture Dasolo assembles in a partner-led Inventory program. Most teams need an outside team to wire these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Inventory, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Inventory includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo