For an Odoo business in Belgium or France, a putaway rule that points to an already full location does not make stock more reliable. Odoo Enterprise storage categories add capacity, weight, product or package-type constraints to locations. They give shop-floor teams a consistent framework when they represent actual physical constraints rather than a copied theoretical layout.
Start with the limits that really matter
Identify areas where exceeding a limit creates risk: pallet locations, load-limited racking, chilled areas, small-item picking or restricted reserve storage. For each, decide whether the meaningful limit is total weight, the number of units of one product, the number of packages, or a combination. A category does not replace safety procedures or human checks; it makes Odoo’s suggested choice clearer.
Avoid one category per location when the rules are identical. Name categories after their purpose — for example, “heavy pallet” or “high-turnover picking” — and assign them to the relevant sub-locations. This simplicity matters when rolling out Odoo Enterprise across Belgian and French sites.
Connect category, location and putaway rule
A category is assigned to locations; a putaway rule can then use it to route a receipt. First validate the physical hierarchy: dock, inspection, stock, reserve and picking do not have the same purpose. Then link products and package types to the most specific rules. Our guide to Odoo putaway rules explains how to document scope and priority.
Do not confuse storage capacity with a removal strategy. FIFO or FEFO decide what to pick; the category helps choose a destination location. For lot and expiry-date controls, also keep the checks in our Odoo lots, expiry dates and FEFO guide.
Plan for a receipt that exceeds capacity
An essential test: Odoo can recommend a location based on its category, but it does not automatically split an oversized receipt across several locations. If a pallet or receipt exceeds the first destination’s limit, the team needs an operational decision: receive partially, move the excess to an approved area, or review packaging. This exception should be understood before go-live, not discovered at the dock one morning.
Acceptance test units, pallets and an exception
Fictional Underside scenario: a distributor receives 36 cartons of a product, packed on pallets of 12. Each reserve location accepts two pallets and picking accepts 24 units. Acceptance testing verifies the suggested destination, validated move, stock by location and the result when three pallets arrive at once.
- Test a receipt within the limit and one that exceeds it.
- Test weight alone, product alone and package type when each is used.
- Test an unavailable destination and an internal transfer to reserve stock.
- Compare Odoo stock with the physical count after validation.
- Run the scenario with a storekeeper and manager using their actual rights.
Manage deviations, not just settings
Track manual destination changes, observed overruns, extra transfers and time from receipt to storage. A repeated exception may reveal a poorly set capacity, incomplete product weights or uncontrolled supplier packaging. Odoo cycle counts provide a useful second view to confirm that location logic matches the shop floor.
Official source and scope
Reference: Odoo 19 documentation on storage categories. Verify the settings available in your Odoo edition and installed modules. The framing, acceptance scenarios and metrics are Underside’s analysis.
Frame your Odoo storage capacities with Underside, based on your actual locations, packages and constraints.