odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.md

@@ -0,0 +1,219 @@
+---
+title: "Batch picking"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.html"
+---
+
+=============
+# Batch picking
+
+.. _inventory/misc/batch_picking:
+
+*Batch picking* enables a single picker to handle multiple orders at once, reducing the number of
+times needed to navigate to a warehouse location. When picking in batches, orders are grouped and
+consolidated into a picking list. After the picking, the batch is taken to an output location, where
+the products are sorted into their respective delivery packages.
+
+Since orders *must* be sorted at the output location after being picked, this picking method suits
+businesses with a few products that are ordered often. Storing high-demand items in easily
+accessible locations can increase the number of orders that are fulfilled efficiently.
+
+Batch picking is ideal for industries or warehouses that handle high order volumes with a stable
+demand. This method increases efficiency by allowing workers to pick items for multiple orders in
+one trip through the warehouse, reducing travel time and boosting productivity.
+
+# Configuration
+
+To activate the batch picking option, begin by going to :menuselection:`Inventory app -->
+Configuration --> Settings`. Under the :guilabel:`Operations` section, check the :guilabel:`Batch,
+Wave & Cluster Transfers` box.
+
+.. image:: batch/batch-transfer-checkbox.png
+   :alt: Enable the *Batch Transfers* in Inventory > Configuration > Settings.
+
+Since batch picking is a method to optimize the *pick* operation in Odoo, the :guilabel:`Storage
+Locations` and :guilabel:`Multi-Step Routes` options under the :guilabel:`Warehouse` heading must
+also be checked on this settings page. When finished, click :guilabel:`Save`.
+
+.. image:: batch/locations-routes-checkbox.png
+   :alt: Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings.
+
+.. seealso::
+   - :doc:`Delivery in two steps <../daily_operations/receipts_delivery_two_steps>`
+   - :doc:`../daily_operations/delivery_three_steps`
+
+# Create batch transfers
+
+To manually group transfers directly from the :menuselection:`Inventory app`, hover over the
+desired operation type from the :guilabel:`Inventory Overview` menu (e.g. the :guilabel:`Receipts`
+Kanban card), click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon, then select
+:guilabel:`Prepare Batch`.
+
+.. image:: batch/prepare-batch.png
+   :alt: The Inventory dashboard with the Prepare Batch option highlighted.
+
+On the batch transfer form, fill the following fields out accordingly:
+
+- :guilabel:`Responsible`: employee assigned to the picking. Leave this field blank if *any* worker
+  can fulfill this picking.
+- :guilabel:`Operation Type`: from the drop-down menu, select the operation type under which the
+  picking is categorized.
+- :guilabel:`Scheduled Date`: specifies the date by which the :guilabel:`Responsible` person should
+  complete the transfer to the output location.
+
+.. seealso::
+   To learn more about the :guilabel:`Dock Location`, :guilabel:`Vehicle`, and :guilabel:`Vehicle
+   Category` fields, see :doc:`dispatch management system
+   <../../shipping_receiving/setup_configuration/dispatch>`.
+
+Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to open the :guilabel:`Add:
+Transfers` window.
+
+If the :guilabel:`Operation Type` field was filled, the list will filter transfer records matching
+the selected :guilabel:`Operation Type`.
+
+Click the :guilabel:`New` button to create a new transfer.
+
+Once the transfer records are selected, click :guilabel:`Confirm` to confirm the batch picking.
+
+.. example::
+   A new batch transfer is assigned to the :guilabel:`Responsible`, `Joel Willis`, for the `Pick`
+   :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` is set to `August 11`.
+
+   .. image:: batch/batch-transfer-form.png
+      :alt: View of *Batch Transfers* form.
+
+   Clicking the :guilabel:`Add a line` button opens the :guilabel:`Add:Transfers` window,
+   displaying only pickings. This is because the :guilabel:`Operation Type` was set to `Pick` on the
+   batch transfer form.
+
+   Click the checkbox to the left of the transfers, `WH/PICK/00001` and `WH/PICK/00002`, to include
+   them in the new transfer. Then, click the :guilabel:`Select` button to close the
+   :guilabel:`Add:Transfers` window.
+
+   .. image:: batch/add-transfers-window.png
+      :alt: Select multiple transfers from the *Add:Transfers* window.
+
+.. _inventory/warehouses_storage/add-batch-transfers:
+
+## Add batch from transfers list
+
+Another method of creating batch transfers is available using the :guilabel:`Add to batch` option in
+a list. Navigate to the :menuselection:`Inventory app --> Operations` drop-down menu, and select any
+of the :guilabel:`Transfers` to open a filtered list of transfers.
+
+.. image:: batch/transfers-drop-down.png
+   :alt: Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,
+         Manufacturings, Batch Transfers, Dropships.
+
+On the transfers list, select the checkbox to the left of the selected transfers to add in a batch.
+Next, navigate to the :icon:`fa-cog` :guilabel:`Actions` button, and click :guilabel:`Add to batch`
+from the resulting drop-down menu.
+
+.. image:: batch/add-to-batch.png
+   :alt: Use *Add to batch* button, from the *Action* button's list.
+
+Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee
+:guilabel:`Responsible` for the picking can be assigned.
+
+Choose from the two radio options to add to :guilabel:`an existing batch transfer` or create
+:guilabel:`a new batch transfer`.
+
+Add a :guilabel:`Description` for this batch.
+
+> **tip**:
+>    The :guilabel:`Description` field can be used to add additional information to help workers
+   identify the source of the batch, where to place the batch, what shipping containers to use, etc.
+
+To create a batch to be processed at a later time, select the :guilabel:`Draft` checkbox.
+
+Conclude the process by clicking :guilabel:`Confirm`.
+
+.. image:: batch/add-to-batch-window.png
+   :alt: Show *Add to batch* window to create a batch transfer.
+
+## Automatic batches
+
+Batches can be automatically created and assigned based on several criteria. The *Automatic Batches*
+option is defined on the *operation type* level.
+
+.. example::
+   In a multi-steps delivery process, the picking operation can be grouped by customer, while the
+   shipping operation can be organized by carrier and destination country.
+
+To enable *Automatic Batches*, navigate to :menuselection:`Inventory app --> Configuration -->
+Operation Types`, and select the desired operation type (e.g. :guilabel:`Delivery`,
+:guilabel:`Pick`, etc). Then, select one or more :guilabel:`Batch Grouping` criteria by ticking the
+appropriate checkbox. Even if more than one grouping option is selected, only one batch is created.
+
+Batches can be automatically generated based on the following criteria:
+
+- :guilabel:`Contact`
+- :guilabel:`Carrier`
+- :guilabel:`Destination Country`
+- :guilabel:`Source Location`
+- :guilabel:`Destination Location`
+
+.. image:: batch/auto-batch-grouping.png
+   :alt: The Batch and Wave Transfers settings page with the Auto batch grouping criteria visible.
+
+# Process batch transfer
+
+Handle batch transfers in the :menuselection:`Inventory app --> Operations --> Batch Transfers`
+page.
+
+From here, select the intended transfer from the list. Then, on the batch transfer form, input the
+:guilabel:`Done` quantities for each product, under the :guilabel:`Detailed Operations` tab.
+Finally, select :guilabel:`Validate` to complete the picking.
+
+> **tip**:
+>    Be certain the batch transfer is complete when the :guilabel:`Validate` button is highlighted in
+   purple. If the :guilabel:`Check Availability` button is highlighted instead, that means there are
+   items in the batch that are currently *not* available in-stock.
+
+.. _inventory/management/batch-transfers-example:
+
+.. example::
+   In a batch transfer involving products from pickings, `WH/PICK/00001` and `WH/PICK/00002`, the
+   :guilabel:`Detailed Operations` tab shows that the product, `Cabinet with Doors`, has been picked
+   because the :guilabel:`Done` column matches the value in the :guilabel:`Reserved` column.
+   However, `0.00` quantities have been picked for the other product, `Cable Management Box`.
+
+   .. image:: batch/process-batch-transfer.png
+      :alt: Show batch transfer of products from two pickings in the *Detailed Operations* tab.
+
+Only in-stock products are visible in the :guilabel:`Detailed Operations` tab.
+
+To view the complete product list, switch to the :guilabel:`Operations` tab. On this list, the
+:guilabel:`Demand` column indicates the required quantity for the order. The :guilabel:`Reserved`
+column shows the available stock to fulfill the order. Lastly, the :guilabel:`Done` column specifies
+the products that have been picked, and are ready for the next step.
+
+.. example::
+   The product, `Desk Pad`, from the same batch as the :ref:`example above
+   <inventory/management/batch-transfers-example>`, is only visible in the :guilabel:`Operations`
+   tab because there are no :guilabel:`Reserved` quantities in stock to fulfill the batch transfer.
+
+   Click the :guilabel:`Check Availability` button to search the stock again for available products.
+
+   .. image:: batch/operations-tab.png
+      :alt: Show unavailable reserved quantities in the *Operations* tab.
+
+## Create backorder
+
+On the batch transfer form, if the :guilabel:`Done` quantity of the product is *less* than the
+:guilabel:`Reserved` quantity, a pop-up window appears.
+
+This pop-up window provides the option: :guilabel:`Create Backorder?`.
+
+Clicking the :guilabel:`Create Backorder` button automatically creates a new batch transfer.
+
+> **note**:
+>    When creating a new backorder, the transfers that have **not** been validated in the batch will
+   be removed from it.
+
+Click :guilabel:`No Backorder` to finish the picking *without* creating another batch picking.
+
+Click :guilabel:`Discard` to cancel the validation, and return to the batch transfer form.
+
+.. image:: batch/create-backorder.png
+   :alt: Show the *Create Backorder* pop-up.

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.md

@@ -0,0 +1,167 @@
+---
+title: "Cluster picking"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/cluster.html"
+---
+
+===============
+# Cluster picking
+
+.. _inventory/misc/cluster_picking:
+
+.. |SO| replace:: :abbr:`SO (Sales Order)`
+.. |SOS| replace:: :abbr:`SOs (Sales Orders)`
+
+Cluster picking is an advanced picking method that combines the efficiency of :ref:`batch picking
+<inventory/misc/batch_picking>` with immediate sorting during the picking process. It is best suited
+for warehouses with high order volumes where organization and speed are critical.
+
+Unlike batch picking, which requires a separate sorting step after picking, cluster picking sorts
+items directly into designated bins or containers for each *sales order* (SO). This eliminates the
+need for post-picking consolidation, making it ideal for operations prioritizing speed and accuracy.
+
+Cluster picking is particularly effective in environments where immediate organization is crucial,
+and orders contain a mix of items that need precise sorting during, rather than after, the picking
+process.
+
+However, cluster picking does have some disadvantages. For instance, urgent orders cannot be
+prioritized, and optimized batches must be manually created beforehand. As a result, the picking
+process can lead to bottlenecks.
+
+.. _inventory/misc/cluster_picking/example:
+
+.. example::
+   #. |SO| 1 calls for one apple and orange
+   #. |SO| 2 calls for one apple and banana
+   #. |SO| 3 calls for one apple, orange, and banana
+
+   Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C.
+
+   To pick products for three orders at once, the cart is loaded with three empty packages.
+
+   Starting at Shelf A, the picker places apples into each package. Next, the picker navigates to
+   Shelf B, and places oranges in the packages designated for |SO| 1 and |SO| 3. Finally, the picker
+   pushes the cart to Shelf C, and loads packages for |SO| 2 and |SO| 3 with a banana, each.
+
+   With the packages for all three |SOS| packed, the picker pushes the cart to the output location,
+   where the packages are sealed and prepared for shipment.
+
+   .. image:: cluster/cluster-example.png
+      :alt: Show example of fulfilling sales orders 2 and 3 at once.
+
+# Configuration
+
+To enable cluster picking, begin by navigating to :menuselection:`Inventory app --> Configuration
+--> Settings`. Under the :guilabel:`Operations` heading, activate the :guilabel:`Packages` and
+:guilabel:`Batch, Wave & Cluster Transfers` options.
+
+.. image:: cluster/configs.png
+   :alt: Activate *Packages* and *Batch Transfers* features in the settings.
+
+Since batch picking is used to optimize the *pick* operation in Odoo, the :guilabel:`Storage
+Locations` and :guilabel:`Multi-Step Routes` options, under the :guilabel:`Warehouse` heading, must
+also be checked on this settings page.
+
+*Storage locations* allow products to be stored in specific locations they can be picked from, while
+*multi-step routes* enable the picking operation itself.
+
+When finished, click :guilabel:`Save`.
+
+.. image:: cluster/locations-routes-checkbox.png
+   :alt: Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration > Settings.
+
+.. _inventory/misc/create-package:
+
+## Packages setup
+
+To configure the containers to be used during the picking process, navigate to
+:menuselection:`Inventory app --> Products --> Packages`. Click the :guilabel:`New` button to create
+a new package.
+
+On the new package form, the :guilabel:`Package Reference` is pre-filled with the next available
+`PACK` number in the system. :guilabel:`Pack Date` is automatically set to the creation date of the
+form.
+
+Set the :guilabel:`Package Use` field to :guilabel:`Reusable Box`.
+
+.. seealso::
+   :doc:`Packages <../../product_management/configure/package>`
+
+.. example::
+   A package intended for cluster picking is named `CLUSTER-PACK-3` for easy identification. For
+   this workflow, the products are directly packed using their intended shipping boxes, so
+   :guilabel:`Package Use` is set to :guilabel:`Reusable Box`.
+
+   .. image:: cluster/cluster-package.png
+      :alt: Create new package form.
+
+# Create cluster batch
+
+To create a cluster, navigate to :menuselection:`Inventory app` and select the operation type card,
+:guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first operation in the delivery
+flow).
+
+> **note**:
+>    Cluster pick batches can be created for outgoing shipments in one, two, or three steps.
+
+.. seealso::
+   - :doc:`Delivery in one step <../daily_operations/receipts_delivery_one_step>`
+   - :doc:`Delivery in two steps <../daily_operations/receipts_delivery_two_steps>`
+   - :doc:`Delivery in three steps <../daily_operations/delivery_three_steps>`
+
+Click the checkbox to the left of the corresponding outgoing operation to add them to the batch.
+With the desired pickings selected, click the :icon:`fa-cog` :guilabel:`Actions` button, and select
+the :guilabel:`Add to batch` option from the resulting drop-down menu.
+
+.. example::
+   To create a cluster batch, as shown in the :ref:`example above
+   <inventory/misc/cluster_picking/example>`, in a warehouse configured with two-step outgoing
+   shipments, the following pick operations are selected:
+
+   - `WH/PICK/00007`: linked to |SO| 88 for one apple and orange.
+   - `WH/PICK/00008`: linked to |SO| 89 for one apple and banana.
+   - `WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana.
+
+   .. image:: cluster/select-picks.png
+      :alt: Use *Add to batch* button, from the *Action* button's list.
+
+Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the employee
+:guilabel:`Responsible` for the picking can be assigned.
+
+Choose from the two options in the :guilabel:`Add to` field to either: add to :guilabel:`an existing
+batch transfer`, or create :guilabel:`a new batch transfer`.
+
+Then, add a :guilabel:`Description` for this batch.
+
+> **tip**:
+>    The :guilabel:`Description` field can be used to add additional information to help workers
+   identify the source of the batch, where to place the batch, what shipping containers to use, etc.
+
+To create draft batch pickings to be confirmed at a later date, select the :guilabel:`Draft`
+checkbox.
+
+Conclude the process by clicking :guilabel:`Confirm`.
+
+.. image:: cluster/add-to-batch-window.png
+   :alt: Show *Add to batch* window to create a batch transfer.
+
+# Process batches
+
+To process batches, navigate to :menuselection:`Inventory app --> Operations --> Batch Transfers`.
+Click on a batch to select it.
+
+In the :guilabel:`Detailed Operations` tab, products that are to be picked are grouped by location.
+
+Set the :guilabel:`Destination Package` to the package dedicated to that particular order.
+
+.. example::
+   Process the cluster batch for the three orders of apples, oranges, and bananas :ref:`example
+   <inventory/misc/cluster_picking/example>` by assigning each picking to a dedicated package.
+
+   At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in all three pickings
+   to one of the three reusable packages, `CLUSTER-PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`.
+
+   Record this in Odoo using the :guilabel:`Destination Package` field in the :guilabel:`Detailed
+   Operations` tab.
+
+   .. image:: cluster/cluster-batch-example.png
+      :alt: Example of processing cluster pickings in *Inventory*.

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.md

@@ -0,0 +1,135 @@
+---
+title: "Wave transfers"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/wave.html"
+---
+
+==============
+# Wave transfers
+
+.. |SO| replace:: :abbr:`SO (sales order)`
+
+While a batch transfer is a group of several pickings, a **wave transfer** contains certain parts
+of different pickings. In Odoo, wave transfers are batch transfers with an extra step: transfers are
+split before being grouped in a batch.
+
+Wave picking is ideal for warehouses that need to optimize the handling of high order volumes while
+managing complex picking criteria. With wave transfers, orders are grouped into waves based on
+factors like product location, category, or scheduled shipping times. Each wave is assigned to a
+different employee for the most efficient execution.
+
+Wave picking is particularly useful for operations where multiple sales orders (SOs), or a single
+order, must be picked across different waves. This approach enables flexible scheduling, allowing
+warehouses to align picking activities with shipping deadlines, or resource availability.
+
+.. example::
+   #. |SO| 1 calls for one apple and one orange
+   #. |SO| 2 calls for one apple and one banana
+   #. |SO| 3 calls for one apple, one orange, and two bananas
+
+   Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C. A warehouse employee is
+   assigned to the wave, and is provided with the following instructions:
+
+   - Shelf A: Pick three apples. Place them into a central cart designated for the wave.
+   - Shelf B: Pick two oranges. Add them to the same cart.
+   - Shelf C: Pick three bananas. Add them to the cart.
+
+   The employee then takes the cart to the sorting/packing station. Items are then sorted and packed
+   into individual orders.
+
+# Configuration
+
+To enable wave picking, begin by navigating to :menuselection:`Inventory --> Configuration -->
+Settings`. In the :guilabel:`Operations` section, tick the :guilabel:`Batch, Wave & Cluster
+Transfers` checkbox to enable the setting.
+
+.. image:: wave/wave-transfers-setting.png
+   :alt: View of Odoo Inventory app settings to enable the wave transfers option.
+
+Next, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, under the
+:guilabel:`Warehouse` heading, must also be checked on this settings page.
+
+*Storage locations* allow products to be stored in specific locations they can be picked from, while
+*multi-step routes* enable the picking operation itself.
+
+Then, click :guilabel:`Save` to save the changes.
+
+# Create a wave
+
+Wave transfers can only contain product lines from transfers of the same operation type. To view
+all the transfers and product lines in a specific operation, navigate to the
+:menuselection:`Inventory app`. Find the desired Kanban card, then click the :icon:`fa-ellipsis-v`
+:guilabel:`(vertical ellipsis)` icon to open the options menu. Under :guilabel:`New`, click
+:guilabel:`Prepare Wave`.
+
+.. image:: wave/list-of-operations.png
+   :alt: How to get an operation type's list of operations.
+
+## Create a new wave
+
+On the :guilabel:`Prepare Wave` pop-up, stock moves lines are grouped by source location. Select the
+checkboxes for the product lines that should be added. Then, click :guilabel:`Add to Wave`.
+
+.. image:: wave/select-lines.png
+   :alt: Select lines to add to the wave.
+
+> **tip**:
+>    Use the :guilabel:`Filters` in the search bar to group lines with the same product, location,
+   carrier, etc.
+
+## Add products to an existing wave
+
+To add products to an existing wave, navigate to :menuselection:`Inventory --> Operations --> Wave
+Transfers`. Click on the appropriate wave from the list to open it.
+
+Under the :guilabel:`Detailed Operations` tab, click :guilabel:`Add a line`. Then, in the
+:guilabel:`Product` field, search for the desired product.
+
+# Process a wave
+
+To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations -->
+Wave Transfers`. Click on the appropriate wave from the list to open it.
+
+To assign the wave to a specific employee, click the :guilabel:`Responsible` field and select the
+appropriate name from the drop-down list.
+
+To designate a :ref:`Dock location <inventory/shipping_receiving/docks>`, select an option from the
+drop-down menu in the :guilabel:`Docks Location` field.
+
+> **note**:
+>    The :doc:`dispatch management system <../../shipping_receiving/setup_configuration/dispatch>`
+   feature in Odoo is used to plan and build shipments. Assigning batches to loading docks ensures
+   the right products are pack into the appropriate trucks for delivery.
+
+Select a :guilabel:`Vehicle` from the drop-down. Making a selection in this field automatically
+updates the :guilabel:`Vehicle Category` field.
+
+Enter a :guilabel:`Description` for this wave, if desired.
+
+> **note**:
+>    The :guilabel:`Description` field is automatically generated for :ref:`automatic waves
+   <inventory/shipping_receiving/auto-waves>`.
+
+.. _inventory/shipping_receiving/auto-waves:
+
+# Automatic waves
+
+Waves can be automatically created and assigned based on different criteria. The *Automatic Batches*
+option is defined on the *operation type* level, which enables the creation of waves with distinct
+grouping criteria for each operation type.
+
+To enable *Automatic Batches*, navigate to :menuselection:`Inventory app --> Configuration -->
+Operation Types`, and select the desired operation type (e.g. :guilabel:`Delivery`,
+:guilabel:`Pick`, etc). Under the :guilabel:`Batch & Wave Transfers` heading, tick the
+:guilabel:`Automatic Batches` checkbox.
+
+Then, select one or more :guilabel:`Wave Grouping` criteria by ticking the appropriate checkbox.
+Even if more than one grouping option is selected, only one wave is created.
+
+Automatic waves can be created based on the following criteria:
+
+- :guilabel:`Product`: Split transfers by product, then group transfers that have the same product.
+- :guilabel:`Product Category`: Split transfers by product category, then group transfers that have
+  the same product category.
+
+.. image:: wave/auto-wave-grouping.png
+   :alt: The Automatic batches feature with the wave grouping option for product category selected.

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods.md

@@ -0,0 +1,15 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods.html"
+---
+
+:nosearch:
+# 
+# Picking methods
+
+.. toctree::
+   :titlesonly:
+
+   picking_methods/batch
+   picking_methods/cluster
+   picking_methods/wave

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.md

@@ -0,0 +1,100 @@
+---
+title: "Closest location removal"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/closest_location.html"
+---
+
+========================
+# Closest location removal
+
+For the *Closest Location* removal strategy, products are picked based on the alphanumeric order of
+storage location titles.
+
+The goal of this strategy is to save the warehouse worker from taking a long journey to a farther
+shelf when the product is also available at a closer location.
+
+.. seealso::
+   :doc:`About removal strategies <../removal_strategies>`
+
+.. _inventory/warehouses_storage/sequence:
+
+To understand *location sequence* in the closest removal strategy, consider the following example:
+
+.. example::
+   A product is stored in the following locations: `Shelf A/Pallet`, `Shelf A/Rack 1`, and `Shelf
+   A/Rack 2`.
+
+   .. image:: closest_location/locations.png
+      :align: center
+      :alt: Show a mockup of real storage location in a warehouse.
+
+   The sublocation, `Pallet`, is on the ground level. Products stored here are easier to retrieve,
+   compared to requiring a forklift to reach `Rack 1` and `Rack 2`. The storage locations were
+   strategically named in alphabetic order, based on ease of access.
+
+> **important**:
+>    To use this removal strategy, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`
+   settings **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings`.
+
+.. seealso::
+   :ref:`Set up removal strategy <inventory/warehouses_storage/removal-config>`
+
+.. _inventory/warehouses_storage/location-name:
+
+# Location names
+
+To configure location names, begin by navigating to :menuselection:`Inventory app --> Configuration
+--> Locations`. Then, select an existing location, or click :guilabel:`New` to create a new one, and
+then enter the desired name in the :guilabel:`Location Name` field.
+
+Once the locations are named in alphabetical order, based on their proximity to the output or
+packing location, set the removal strategy on the :ref:`parent location
+<inventory/location-hierarchy>`.
+
+To do that, in the :guilabel:`Locations` list, select the parent location of the alphabetically
+named storage locations.
+
+Doing so opens the form for the parent location. In the :guilabel:`Removal Strategy` field, select
+:guilabel:`Closest Location`.
+
+.. example::
+   In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest to the packing area,
+   where products retrieved from shelves are packed for shipment. The popular product, `iPhone
+   charger` is stored in three locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and
+   `WH/Stock/Shelf 3`.
+
+   To use closest location, set the removal strategy on the parent location, 'WH/Stock'.
+
+# Workflow
+
+To see how the closest location removal strategy works, consider the following example, featuring
+the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`,
+and `WH/Stock/Shelf 3`.
+
+Fifteen, five, and thirty units are in stock at each respective location.
+
+> **tip**:
+>    To check the on-hand stock at each storage location, navigate to the product form, and click the
+   :guilabel:`On Hand` smart button.
+
+   .. image:: closest_location/on-hand-stock.png
+      :align: center
+      :alt: Show on-hand stock at all locations.
+
+Create a :ref:`delivery order <inventory/delivery/one-step>` for eighteen units of the `iPhone
+charger` by navigating to the :menuselection:`Sales app` and creating a new quotation.
+
+After adding the products, clicking :guilabel:`Confirm` creates a delivery order that reserves items
+stored at the closest location, using the removal strategy.
+
+For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)`
+icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window that
+displays how the reserved items were picked, according to the removal strategy.
+
+In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where
+the quantities to fulfill the :guilabel:`Demand` are picked. All fifteen of the units stored at the
+closest location, `WH/Stock/Shelf 1`, are picked first. The remaining three units are then selected
+from the second closest location, `WH/Stock/Shelf 2`.
+
+.. image:: closest_location/stock-move-window.png
+   :align: center
+   :alt: Display *Pick From* quantities for the order for iPhone chargers.