[ADD] Inventory: Use locations to manage inventory
closes odoo/documentation#6423
X-original-commit: 889e95037d
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
This commit is contained in:
parent
068020901c
commit
36b20ff16c
@ -12,3 +12,4 @@ Warehouses
|
|||||||
warehouses/warehouse_replenishment_transfer
|
warehouses/warehouse_replenishment_transfer
|
||||||
warehouses/warehouses_locations
|
warehouses/warehouses_locations
|
||||||
warehouses/create_a_second_warehouse
|
warehouses/create_a_second_warehouse
|
||||||
|
warehouses/use_locations
|
||||||
|
@ -0,0 +1,59 @@
|
|||||||
|
=========
|
||||||
|
Locations
|
||||||
|
=========
|
||||||
|
|
||||||
|
A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There
|
||||||
|
are three types of locations in Odoo:
|
||||||
|
|
||||||
|
- *Physical locations* are spaces within a warehouse owned by the user's company. These can be a an
|
||||||
|
area where items are stored like an aisle or shelf, or an area where operations take place, like
|
||||||
|
loading and unloading bays.
|
||||||
|
- *Partner locations* are the same as physical locations except that they exist within the warehouse
|
||||||
|
of a customer or vendor.
|
||||||
|
- *Virtual locations* are locations that do not exist physically, but where items that are not in
|
||||||
|
inventory can be placed. These can be items that have not yet entered inventory, like products
|
||||||
|
that are on the way to a warehouse, or items that are no longer in inventory due to loss or other
|
||||||
|
factors.
|
||||||
|
|
||||||
|
.. important::
|
||||||
|
In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so,
|
||||||
|
navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the
|
||||||
|
:guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox.
|
||||||
|
|
||||||
|
Create a new location inside a warehouse
|
||||||
|
========================================
|
||||||
|
|
||||||
|
Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations
|
||||||
|
--> Create`. The new location form can then be configured as follows:
|
||||||
|
|
||||||
|
- :guilabel:`Location Name`: the name that will be used to reference the location
|
||||||
|
- :guilabel:`Parent Location`: the location or warehouse that the new location exists within
|
||||||
|
- :guilabel:`Location Type`: choose the category that the location belongs to
|
||||||
|
- :guilabel:`Company`: the company that owns the warehouse that the location is inside of
|
||||||
|
- :guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored
|
||||||
|
in this location
|
||||||
|
- :guilabel:`Is a Return Location?`: check this box to allow products to be returned to this
|
||||||
|
location
|
||||||
|
- :guilabel:`Barcode`: the barcode number assigned to the location
|
||||||
|
- :guilabel:`Removal Strategy`: the :ref:`strategy <inventory/routes/strategies/removal>` for how
|
||||||
|
items should be taken from inventory
|
||||||
|
|
||||||
|
.. image:: use_locations/new-location-form.png
|
||||||
|
:align: center
|
||||||
|
:alt: The form for creating a new location.
|
||||||
|
|
||||||
|
Create location hierarchies
|
||||||
|
===========================
|
||||||
|
|
||||||
|
The *Parent Location* setting on the new location form allows for a location to exist within a
|
||||||
|
warehouse or another location. Every location can serve as a parent location, and every parent
|
||||||
|
location can have multiple locations within it, allowing for the creation of a virtually infinite
|
||||||
|
hierarchical structure.
|
||||||
|
|
||||||
|
.. example::
|
||||||
|
Location hierarchy could be organized so that a shelf is located within an aisle, which is
|
||||||
|
located within a room, which is located within the overall warehouse.
|
||||||
|
|
||||||
|
To create the location hierarchy in the example above, set the warehouse as the parent of the room,
|
||||||
|
the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted
|
||||||
|
to a hierarchy of any magnitude.
|
Binary file not shown.
After Width: | Height: | Size: 9.0 KiB |
@ -2,8 +2,10 @@
|
|||||||
What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?
|
What is a Removal Strategy (FIFO, LIFO, FEFO, Closest location)?
|
||||||
================================================================
|
================================================================
|
||||||
|
|
||||||
Usually, *Removal Strategies* are defined in picking operations to select the best products,
|
.. _inventory/routes/strategies/removal:
|
||||||
optimize the distance for the worker, for quality control purposes, or to first move products
|
|
||||||
|
Usually, *Removal Strategies* are defined in picking operations to select the best products to
|
||||||
|
optimize the distance for the worker, for quality control purposes, or to first move the products
|
||||||
with the closest expiration date.
|
with the closest expiration date.
|
||||||
|
|
||||||
When a product movement needs to be done, Odoo finds available products that can be assigned to
|
When a product movement needs to be done, Odoo finds available products that can be assigned to
|
||||||
|
Loading…
Reference in New Issue
Block a user