A shipment arrives and its usual storage location is full. Does the receiving employee know where the remainder belongs, and can the picker find it later? In the Odoo application, putaway rules direct incoming goods to locations, while storage categories add capacity conditions by product, weight or package type 1. GS1 makes a useful identification distinction: application identifier 410 means a delivery destination, while 414 identifies a physical location when marked there 2. For a Saudi distributor, start by matching the location in the system to the space employees recognise; the homepage explains the wider implementation approach.
What should the receiver know before unloading?
The desired result is straightforward: a known destination, a quantity recorded in the right place, and a clear procedure when space is insufficient. A warehouse record alone does not tell a picker which aisle or rack holds these cartons.
Take a representative shipment and identify who inspects it, chooses its destination and validates the movement. Your process might include receipt, inspection and storage, or something simpler. We start with the actual handoff and aim for a setup the receiving employee can follow during the shift.
Location, putaway rule and capacity are different decisions
A location describes a place in the warehouse hierarchy. A putaway rule connects the arrival of a product, category or package type to a destination. A storage category adds requirements such as capacity and whether products may be mixed. Odoo 19 documents a destination below the arrival location, and enabling Multi-Step Routes activates Storage Locations 1.
If you have a general beverages rule and a more specific package-and-product rule, testing only the general case is insufficient. Rule priority affects the recommendation. We test an item matching several rules and record why a location was selected, so the warehouse owner can explain a different result after a product or package change.
Will Odoo split the receipt across available locations?
Do not assume it will. The Odoo 19 storage-category documentation explicitly says incoming quantities are not automatically split between several locations. All incoming items can remain directed to one recommended location even when that exceeds its capacity. We therefore inspect the detailed operations and agree when the user separates quantities into lines with different destinations 1.
The Closest Location option is not evidence that the software measured the physical distance from the unloading door. It uses the storage-category locations and their configuration. When those sublocations are full, the parent destination and the employee’s next action also need an acceptance test.
Worked example: a planned manual split
These are hypothetical planning figures, not customer data or rack-engineering specifications. Locations X1 and X2 each have a recorded capacity of 20 cartons and 300 kg. Each carton weighs 15 kg. Cartons are the counted unit in this example.
| Item | X1 | X2 |
|---|---|---|
| Cartons before receipt | 14 | 10 |
| Weight before receipt | 210 kg | 150 kg |
| Remaining carton capacity | 6 | 10 |
| Remaining weight capacity | 90 kg | 150 kg |
| Proposed manual receipt allocation | 6 cartons | 6 cartons |
| Cartons after validation | 20 | 16 |
| Weight after validation | 300 kg | 240 kg |
The incoming shipment is 12 × 15 = 180 kg. X1 has room for only 6 of the 12 cartons. After checking the physical space, the responsible employee manually splits the receipt into 6 and 6 in the detailed operations. The combined total in X1 and X2 is 36 cartons weighing 540 kg, with space for 4 cartons or 60 kg remaining in X2 under these assumptions. This is a human-reviewed allocation, not a promise that a putaway rule makes the split automatically.
Arithmetic space may be unusable because of an obstruction or a different physical arrangement. Rack limits need appropriate approval, and product units and weights must match the data used by the system. To scope the cost of organising and implementing the workflow, use the implementation cost and savings calculators; the quantities above do not establish a financial saving.
When is an external location identifier such as GLN useful?
An internal name such as X1 can support your team’s process when it is clear on the rack and document. Exchanging location data with a carrier or customer may require a shared identifier. GS1 distinguishes a GLN used as a delivery destination with AI 410 from a GLN marked at a physical location with AI 414 2.
An Odoo location name or a printed barcode does not become a GLN simply by being printed. We check the trading partner’s requirement, the identifier’s origin and how it will be read before defining labels or interfaces. The aim is meaningful identification, not extra codes employees cannot use.
What belongs in the implementation scope?
Together with the warehouse owner, we define the location map, label names, product units and weights, storage categories and receipt-routing rules. We also identify who resolves an exception: a full location, an unsuitable quantity, or goods requiring inspection before they can join available stock.
Decide whether a location may mix products, accept only the same product, or begin receiving a product only when empty. The choice should support picking and counting practices your team can maintain. See how the Inventory application fits a retail and wholesale workflow.
Implementation effort depends on warehouses, locations, packages, labels, interfaces and the quality of the starting data. Start with a representative sample before extending the rules. The sales and inventory demo illustrates the general interface; putaway and capacity behavior are tested in an environment for your licensed version.
Acceptance checks that make the recommendation explainable
- Receive an item with a specific rule and compare the proposed destination with the physical location and label.
- Test an item matching a general and a more specific rule, then explain the selected destination.
- Use the 12-carton example: inspect the recommendation, manually split 6 and 6, and reconcile both locations after validation.
- Fill the sublocations and check the parent-location fallback and the employee’s procedure before validation.
- Test a different product in a location that restricts mixing, then review its unit and weight data.
- Pick a customer order after putaway and confirm that the employee can find and reconcile the quantity.
FAQ
Does a storage category prevent every capacity overrun? It does not replace checking the movement. The 19 documentation describes the automatic-splitting limitation, so test the quantity and destination before validation, especially for receipts requiring multiple locations.
Must every location be renamed? No. Retain understandable names, resolve ambiguity or duplication, and match the physical label to the location used in operations.
Will this improve stock-count accuracy? Recording movements at the correct location gives counting a clearer starting point. Measure actual discrepancies after rollout rather than assuming a percentage improvement from configuration alone.
Start with a representative receipt
Prepare a small location map, a normal shipment and a full-location case, then discuss them with us. The aim is a clear decision for the receiver and a findable quantity for the picker. Review the Odoo application for your business and estimate the implementation scope and cost to choose the next step.
Source notes
[1] Odoo 19 documentation on Putaway Rules and Storage Categories: destinations, capacity, rule priority and the receipt-splitting limitation.
[2] GS1 GO guidance on identifying a physical location with a GLN, updated 28 August 2024: the distinction between application identifiers 410 and 414.
