Odoo Putaway Rules: The Shelf That Organizes Itself

Take the “ask Maria” step out of receiving

A familiar scene: a truck arrives, the paperwork is checked, and someone asks, “Where do we put these?”

One person knows the answer immediately. They remember that this product is heavy, that its case packs fit a particular bay, and that another aisle needs to stay clear. The new hire does not know. The person covering the shift may not know either. So someone makes a best guess, or stops work to find the expert.

That is not a people problem. It is a sign that a useful warehouse decision lives in someone’s memory instead of in the process.

In Odoo, a putaway rule tells Inventory how to route products arriving at a specified location. A rule can apply to an individual product or a product category. If you use package types, rules can also account for packaging. Odoo then generates the operation to move the product toward its designated storage location.

That gives your team a consistent starting point. It also makes it easier to train new staff, cover busy shifts, and adjust the process as your warehouse changes.

Make locations clear before writing rules

A putaway rule is only as useful as the warehouse locations behind it. If “the back corner” means one thing to a veteran and another to everyone else, the software cannot fix the naming problem.

Start with a location structure people can understand. For example:

• WH/Stock as the parent stock location
• WH/Stock/Pallets for pallet storage
• WH/Stock/Small Parts for smaller products
• WH/Stock/Fragile for goods that need careful handling

The names should reflect how your team actually works. Keep them clear and consistent, and avoid creating more locations than you can maintain.

To set up putaway rules, Odoo’s documentation describes enabling Multi-Step Routes in Inventory settings; this also activates Storage Locations. Then create your parent and child locations and define rules from Inventory → Configuration → Putaway Rules. The Odoo putaway rules guide walks through the configuration.

A typical rule identifies the product or category, the location where the rule is triggered, and the destination. The destination needs to make sense within the location structure: when routing into a sublocation, it should sit under the relevant parent location.

Give products a predictable home

Say your distribution team receives cartons of a particular product every week. Without a rule, the right shelf might depend on who is working. With a product-level rule, Odoo can direct that product to its designated sublocation when it arrives at the specified receiving or stock location.

For a broader assortment, a category-level rule can handle similar products together. That is useful when products share a storage pattern, for example, when several items belong in the same general zone.

The Sublocation choice affects what happens next:

• No directs the product to the location specified in the rule.
• Last Used reuses the last location associated with the product or category, when one is available.
• Closest Location uses eligible locations associated with a storage category. The rule must specify that category.

This gives you a simple way to decide how much structure your warehouse needs. A fixed destination may be right for a product that always belongs in one place. A last-used location can help keep repeat products together. A storage category can help select among multiple eligible locations.

Use storage categories when capacity matters

Sometimes the right location depends on more than a product name. A bin may have a weight limit. A pallet bay may have room for only a certain number of packages. A location may be intended for one product at a time, or it may allow a mix.

That is where storage categories can help. You assign a category to eligible child locations, define relevant capacity limits, and connect it to a putaway rule. Odoo can then recommend an eligible location based on the rule and category.

For example, imagine a warehouse with two pallet locations for a family of products. Each location can hold a limited number of pallets. A putaway rule that uses the relevant storage category helps the team direct incoming pallets to an eligible location instead of relying on someone to remember which bay has space.

Be clear about one important limit: capacity rules do not automatically split an incoming quantity across multiple locations. If a receipt exceeds a location’s capacity, the system does not necessarily divide that receipt into smaller parts and distribute them for you. Review the detailed operations and split quantities when your process requires it. The Odoo storage categories guide explains capacity settings and this behavior.

Capacity logic is only as good as the information behind it. If product weights, package types, location limits, or on-hand stock are inaccurate, the recommendation can be misleading. Treat the setup like a warehouse procedure: define the rules, keep the underlying data current, and check the result.

Test the rule on the warehouse floor

Do not build a complicated rulebook and hope it works. Start with one product family and one receiving flow.

A practical test looks like this:

1. Choose a product or category with a clear storage pattern.
2. Confirm the receiving location and the destination locations exist in Odoo.
3. Create the putaway rule and, if needed, configure storage categories and capacity.
4. Process a test receipt with the people who will use the workflow.
5. Confirm that the suggested move makes sense on the floor.
6. Adjust confusing location names, product data, or rule details before expanding.

Also check how overlapping rules behave. Odoo applies a priority order to matches, with more specific combinations taking precedence over broader ones. For example, a rule tied to a package type and product can take precedence over a general product-category rule. Keep that in mind as you add exceptions; a broad rule can be perfectly reasonable until a more specific rule changes the result.

Most importantly, involve the people who receive and store the goods. They know where the awkward cartons go, which aisles get congested, and which “obvious” location is a pain to reach with a pallet jack. The system should support the operation your team actually runs.

Put good warehouse judgment into the process

The experienced person on your team is not the problem. Their knowledge is one of your best operating assets. Putaway rules help make that knowledge repeatable, so the work does not stop when they are busy, on break, or showing someone else how the warehouse runs.

Begin with one useful rule. Test it with real inventory. Make the next decision easier for the whole team.

A well-organized warehouse is not built on memory alone.