Industry · Distribution

Multi-warehouse inventory in Odoo for distributors

A second warehouse is where spreadsheets stop working. How Odoo models warehouses, routes, transfers and replenishment so sales, the warehouse floor and the books read the same stock number.

By Octagotech Team8 min read

Key takeaways

  • A warehouse is a site with its own routes; a location is a place inside it. Many design mistakes start by mixing the two.
  • Each warehouse receives and ships in one, two or three steps, set independently.
  • Resupply routes and reorder rules move stock between sites and draft purchase orders from real demand.
  • Landed costs, lots and drop-ship are standard; the Barcode app is Enterprise.
  • EDI and 3PL links run through a connector or an integration, not out of the box.
  • With automated valuation, the stock report and the general ledger agree by design.

A distributor with one warehouse can get by on a good spreadsheet. Add a second site, a 3PL or a drop-ship vendor, and the questions change. Which warehouse should ship this order? How much is really available to promise? What is on the truck between sites? And why does the stock value in accounting never match the count?

Odoo answers these with a small set of concepts. Set them up deliberately and you get one stock number that sales, the warehouse and finance all believe. Leave them at the defaults and you can still end up with three. This guide covers the concepts we configure on Odoo projects for distributors, in the order we decide them in scoping. It assumes you know Odoo basics.

Warehouses and locations are different things

In Odoo, a warehouse is an operating site. It has an address, a short code that prefixes its transfers (WH2/OUT/00412, for example), its own receipt and delivery operations, and its own routes. A location is a place where stock sits: a zone, aisle, rack or bin inside a warehouse, or a virtual place such as a vendor, a customer, scrap or transit.

The rule we use: make it a warehouse if it receives or ships on its own, needs its own replenishment, or appears separately on a report someone reads. Make it a location if it is space inside a site that shares one receiving dock and one shipping dock. A distributor with a main distribution center (DC) and two branches has three warehouses; the aisles and bins are locations. A 3PL is set up as its own warehouse, with stock and shipments synced through the 3PL's API or file exchange.

If warehouses belong to separate legal entities, that is multi-company, a different design with inter-company rules and separate books. Decide that first; it is expensive to change later.

Receiving and shipping steps

Each warehouse chooses how many steps stock takes on the way in and out, and Odoo creates the operations and routes for whichever you pick.

StepsIncomingOutgoingUsually fits
OneReceive straight into stockDeliver from stockA small branch with one dock
TwoReceive to input, then put awayPick, then shipA mid-size site that batches picks
ThreeReceive, quality check, put awayPick, pack, then shipA busy DC that checks at packing

More steps buy control at the cost of clicks. A branch with two people is usually best on one step. A DC shipping hundreds of lines a day usually wants pick, pack and ship, so picks can be batched and errors caught at the pack bench. Choose per site, from how the floor works today; every extra step is a transfer someone has to confirm.

Behind the steps sit routes: rules for where stock comes from and where it goes. Turn on multi-step routes and storage locations in Inventory settings to see and edit them. Most distributors never write a custom route, because the ones Odoo generates from warehouse settings cover receiving, shipping, resupply and drop-ship.

Moving stock between warehouses

There are two ways to move stock between sites. An internal transfer is a one-off move someone creates by hand: product, source, destination. Resupply is the standing version: on the branch warehouse, set "Resupply From" to the main DC, and Odoo creates a route that ships from the DC and receives at the branch.

Moves between warehouses pass through a transit location. Stock on the truck is off the DC's shelf but not yet on the branch's, so it cannot be promised twice. It shows as in transit until someone at the branch receives it. That one detail ends most "we sent it, they never got it" calls, because the receipt is either done or it isn't.

Reorder rules that know which warehouse is short

A reorder rule, also called a replenishment rule, is set per product and per warehouse: a minimum, a maximum and a route. When forecasted stock at that warehouse drops below the minimum, Odoo proposes an order that brings it back up to the maximum. The route decides the kind of order: Buy drafts a purchase order to the vendor, and a resupply route creates a transfer from the DC.

This is how a distributor centralizes buying. Put Buy rules on the DC and resupply rules on the branches. Branches pull from the DC, and only the DC buys from vendors, in consolidated quantities. Vendor lead times feed the forecast, and rules can round orders to case or pallet quantities.

The replenishment report lists every product forecast to go short, per warehouse, with a suggested quantity. Buyers can order from it in bulk, or let rules trigger automatically. A sensible start is automatic triggers for steady fast movers and manual review for the rest, widening once buyers trust the numbers.

Putaway: where received stock goes

Putaway rules send received products to the right place without anyone deciding at the dock. A rule says that products in a category, arriving at a warehouse, go to a given zone, or it names one product and one bin. With storage categories, Odoo can also respect capacity and send the next pallet to a location that still has room.

Keep putaway rules at category level where you can. A rule per SKU is precise, but thousands of them become a maintenance job nobody owns. Zone-level rules plus a scan to confirm the final bin are usually enough.

Lots, serials and expiry

Tracking is set per product: none, by lot, or by unique serial number. Distributors of food, chemicals, medical supplies and anything recall-sensitive track by lot; equipment distributors usually track serials. Once a product is tracked, every receipt, transfer and delivery records the lot, and the traceability report shows where a lot came from and which customers received it.

With expiration dates turned on, lots carry an expiry date and the first-expiry-first-out (FEFO) removal strategy picks the lot that expires first. FIFO and other removal strategies can be set per product category or location. Track only what you must: every tracked product adds a scan or a typed lot number at receiving and picking.

Barcode and the warehouse floor

Batch and wave picking are part of Inventory: group many orders into one pick run, or split order lines so each picker works one zone. The Barcode app, which is Enterprise, is what makes them fast. Pickers scan the location, product and lot, and Odoo checks each scan against the transfer, stopping a wrong item before it reaches the pack bench. The same app handles receiving, putaway, internal transfers and counts. Locations can be given a count frequency, so cycle counts run a zone at a time instead of shutting the warehouse for a full count.

On Community, without the Barcode app, teams work from printed pick lists and confirm in the browser, or we build a lighter scanning screen. For high-volume picking, dedicated scanners work better than phone cameras, and the scan check is often the main reason distributors choose Enterprise.

Landed costs on imported goods

For distributors that import, the purchase price is not the cost. Freight, duty, brokerage and insurance belong in unit cost, or margins look better than they are. Odoo's landed costs feature adds those charges to the stock they relate to: enter the freight or customs bill, mark the charge as a landed cost, choose the receipts it applies to and a split method (by quantity, value, weight, volume or equally), and Odoo revalues the received stock.

Landed costs need FIFO or average cost on the product category; they do not apply to products at standard cost. With automated valuation the revaluation also posts to the general ledger. Post them before the goods sell, or the margin on early sales will look better than it was.

Drop-ship

Drop-ship is standard in Odoo. Turn it on, put the Dropship route on the product or the sales order line, and confirming the order drafts a purchase order to the vendor with the customer's delivery address. The goods never enter a warehouse, so they never distort on-hand stock, but the sale, the purchase, the delivery and the cost still sit on linked records.

Many distributors run a mixed model: stock the fast movers and drop-ship the long tail. Choosing the route per order line handles both on the same product; which products default to which is a buying decision to settle in scoping.

Reporting one stock number

Everything above exists to produce one number per product that everyone trusts. Most arguments come from mixing up three quantities. On hand is what sits in the warehouse's internal locations. Reserved is on-hand stock already allocated to confirmed orders. Forecasted adds expected receipts and subtracts planned deliveries. Sales should promise from what is free and forecasted, not from on hand.

The stock report groups by warehouse and location, the product form shows totals across all warehouses with a drill-down per site, and the sales order line shows availability for the order's warehouse before you confirm. With automated valuation, every receipt, delivery and adjustment posts to the general ledger at FIFO or average cost, so the valuation report and the balance sheet agree without a month-end reconciliation.

What breaks the single number. Stock that moves without a transaction, such as a return put back on the shelf without a receipt, and systems outside Odoo that keep their own counts. A 3PL portal, a marketplace or an EDI provider needs an integration that writes back to Odoo. X12 EDI is not built into Odoo; it runs through an EDI provider connected to Odoo, and the documents you exchange are agreed in scoping.

We have not published a distribution case study yet. The closest is our retail case: a five-store retailer whose nightly close fell from 2 hours to 11 minutes once every location's stock sat in one Odoo inventory layer. The retail case study shows how that rollout ran.

Common questions

Should each branch be a warehouse or a location in Odoo?

Make a site a warehouse if it receives or ships on its own or needs its own replenishment. Aisles, racks and bins inside a site are locations. A 3PL is usually set up as its own warehouse.

Can Odoo reorder stock for one warehouse from another?

Yes. Set the branch to be resupplied from the main warehouse and give its reorder rules the resupply route. When the branch drops below its minimum, Odoo creates a transfer from the main warehouse instead of a purchase order.

Is the Barcode app included in Odoo Community?

No. The Barcode app is Enterprise only. Batch and wave picking, lots and cycle counts are part of Inventory in both editions, but scanning them through the Barcode app needs Enterprise.


If you are scoping a multi-warehouse build, bring your warehouse count, your SKU count and your last stock-count variance to the first call, and we will sketch the warehouse and route design with you. Book a discovery call.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

We write from live Odoo engagements: 20+ implementations over 5+ years. About Octagotech.

One stock number, every warehouse.

Bring your warehouse count, your SKU count and your last stock-count variance. The first call takes 30 minutes.

Or email sales@octagotech.com