Odoo putaway rules: send each receipt to the right location

For an Odoo business in Belgium or France, choosing a location at random on receipt quickly turns into searching, unreliable theoretical stock and needless travel. Odoo Enterprise putaway rules route a product, category or package type to a sub-location. They work when the warehouse layout and its exceptions have first been decided on the shop floor.

Start with the physical decisions

A rule cannot fix a warehouse whose areas have no clear purpose. First distinguish receiving, inspection, reserve, picking, quarantine and dispatch. Use names that Belgian and French teams interpret in the same way, then confirm every location exists physically, is labelled and can be scanned.

Do not model every temporary variation. Create a rule when a product should normally reach a specific area to be accessible, protected or separated. A one-off instruction can remain a team instruction; a repeatable decision deserves an Odoo rule.

Choose a readable scope and anticipate priority

Odoo can apply rules by product, category and package type. A general rule is useful as a safety net, but more specific rules take precedence. Document the choices: should a pallet of a sensitive product go to a dedicated area even when its category points to a shared reserve?

Maintain a simple decision table: arrival condition, trigger location, expected destination, rule owner and business reason. It exposes duplicates before a receipt takes an unexpected route.

Connect capacity, traceability and picking

Putaway is not only about distance. An area may have a capacity, maximum weight, temperature constraint or lot requirement. Connect rules to the relevant locations and storage categories, without confusing putaway with a removal strategy: FIFO or FEFO decide what is picked, while putaway decides where a receipt is routed.

For lot-tracked items, test scanning both the lot and location. The right destination must preserve traceability and make moves understandable to teams, including a partial receipt or internal transfer.

Acceptance test the cases that divert the flow

Fictional Underside scenario: a distributor receives standard cartons and a pallet of the same product. Cartons go to the picking area; the pallet goes to reserve storage. Acceptance testing confirms the suggested destination, movement validation, stock by location and the next sales-order picking.

• Test the targeted product, an item in the same category and one outside scope.
• Test two package types when their priority differs.
• Test a full, unavailable or non-scannable destination.
• Test a partial receipt, vendor return and internal transfer.
• Repeat the scenario with a storekeeper and supervisor using their actual rights.

Measure exceptions before multiplying rules

Track manual location corrections, cancelled moves, time from receipt to storage and inventory discrepancies in affected areas. More exceptions often indicate a poorly designed destination, inadequate labelling or a rule that is too broad. Our guide to Odoo cycle counts helps control discrepancies, while the batch-picking guide connects putaway to order execution.

Official source and scope

Reference: Odoo 19 documentation on putaway rules. Verify the settings available in your Odoo edition and installed modules. The framing, tests and metrics are Underside’s analysis.