-
Notifications
You must be signed in to change notification settings - Fork 10.7k
[ADD] Inventory: Use locations to manage inventory #3843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
59 changes: 59 additions & 0 deletions
59
...pplications/inventory_and_mrp/inventory/management/warehouses/use_locations.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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 added
BIN
+9.04 KB
...ory_and_mrp/inventory/management/warehouses/use_locations/new-location-form.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.