odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.md

@@ -0,0 +1,140 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.html"
+---
+
+:show-content:
+:hide-page-toc:
+# 
+# Inventory management
+
+In the Odoo *Inventory* app, :doc:`warehouses <inventory_management/warehouses>` handle the broader
+organization and distribution of stock across different physical sites, while :doc:`locations
+<inventory_management/use_locations>` provide a more detailed breakdown within each warehouse for
+efficient item management.
+
+This document serves as an introduction to the terminology and concepts necessary to master
+*Inventory*. For specific instructions and examples of how things work, refer to individual
+documentation pages.
+
+.. seealso::
+   [Odoo Tutorials: Warehouses & Locations ](https://www.youtube.com/watch?v=zMvudZVLuUo)
+
+# Warehouses
+
+:doc:`Warehouses <inventory_management/warehouses>` represent a physical place, with a physical
+address, where a company's items are stored.
+
+Configure :doc:`routes <../shipping_receiving/daily_operations/use_routes>` in a warehouse to
+control how products move to customers, from vendors, within the warehouse, or :doc:`between
+warehouses <replenishment/resupply_warehouses>`.
+
+# Locations
+
+:doc:`Locations <inventory_management/use_locations>` refer to specific areas within a warehouse,
+such as shelves, floors, or aisles. These are sub-divisions within a warehouse, and are unique to
+that warehouse. Users can create and manage numerous locations within a single warehouse to organize
+inventory more precisely.
+
+.. seealso::
+   - :doc:`inventory_management/use_locations`
+   - :doc:`inventory_management/count_products`
+   - :doc:`inventory_management/cycle_counts`
+   - :doc:`inventory_management/scrap_inventory`
+
+.. _inventory/warehouses_storage/location-type:
+
+## Location types
+
+*Location types* in Odoo help categorize and manage where products are, and what actions need to be
+taken with them. By default, on the :menuselection:`Inventory app --> Configuration --> Locations`
+page, only internal locations are displayed.
+
+To view the seven location types in Odoo, select any location, and in the :guilabel:`Location Type`
+field, there are:
+
+- :guilabel:`Vendor Location`: defines an area where products purchased from vendors originate.
+  Items here are **not** in stock.
+
+- :guilabel:`View`: used to organize and structure the warehouse hierarchy. For example, the view
+  location `WH` (short for warehouse) groups all internal locations, such as `Stock`, receiving
+  docks, quality checkpoints, and packing areas to show they all belong to the same warehouse.
+
+  > **important**:
+>      View locations should **not** contain products, but it is possible to move them there.
+
+- :guilabel:`Internal Location`: storage locations within the warehouse. Items stored in these
+  locations are accounted for in :doc:`inventory valuation
+  <../product_management/inventory_valuation/using_inventory_valuation>`.
+
+- :guilabel:`Customer Location`: where sold products are tracked; items here are no longer in stock.
+
+- :guilabel:`Inventory Loss`: counterpart location to consume missing items or create stock,
+  accounting for discrepancies.
+
+  In Odoo, examples of inventory loss locations are *Inventory Adjustment*, used to account for
+  discrepancies during an inventory count, and *Scrap*, which is where damaged goods are sent to
+  account for inventory losses.
+
+   .. example::
+      `Virtual Locations/Inventory Adjustment` is a location with the :guilabel:`Inventory Loss`
+      type. The database shows `65` units in `WH/Stock`, but an inventory check reveals `60`. To
+      correct the quantity, five units are moved from `WH/Stock` to `Virtual Locations/Inventory
+      Adjustment`.
+
+      .. image:: inventory_management/inventory-loss.png
+         :align: center
+         :alt: Product ends up in Virtual Locations/Inventory Adjustment.
+
+- :guilabel:`Production`: where raw materials are consumed, and :doc:`manufactured products
+  <../../manufacturing>` are created.
+
+- :guilabel:`Transit Location`: used for inter-company or inter-warehouse operations to track
+  products shipped between different addresses, such as :ref:`Physical Locations/Inter-warehouse
+  transit <inventory/warehouses_storage/interwarehouse-transit>`.
+
+.. image:: inventory_management/locations.png
+   :align: center
+   :alt: List of locations in Odoo.
+
+> **note**:
+>    In Odoo, location types are color-coded:
+     - **Red**: internal locations
+     - **Blue**: view locations
+     - **Black**: external locations (including inventory loss, vendor, and customer locations).
+
+## View locations in Odoo
+
+Odoo databases include pre-configured view locations to organize the hierarchy of locations. These
+provide helpful context, and distinguish between internal and external locations.
+
+- *Physical locations* serve as an umbrella for external locations, without changing a product's
+  inventory value. (Inventory valuation changes occur when products move from internal to external
+  locations).
+
+.. _inventory/warehouses_storage/interwarehouse-transit:
+
+  .. example::
+     When moving products in warehouses `WH` and `WH2`, the items are not in either warehouse, but
+     still belong to the company. While in transit, they are placed in the `Inter-warehouse transit`
+     location, a :guilabel:`Transit Location` type.
+
+     This location is under the view location, `Physical Locations`, indicating that
+     `Inter-warehouse transit` is outside of a warehouse, but still part of the company. Doing so
+     does not affect the inventory valuation of the products.
+
+- *Partner locations* group customer and vendor locations (external locations) together. Transfers
+  to these locations affect inventory valuation.
+- *Virtual locations* are locations that do **not** exist physically, but it is where items that are
+  not in inventory can be placed. These can be items that are no longer in inventory due to loss, or
+  other factors.
+
+.. toctree::
+   :titlesonly:
+
+   inventory_management/warehouses
+   inventory_management/use_locations
+   inventory_management/count_products
+   inventory_management/cycle_counts
+   inventory_management/scrap_inventory
+   inventory_management/product_catalog

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.md

@@ -0,0 +1,376 @@
+---
+title: "Lead times"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/lead_times.html"
+---
+
+==========
+# Lead times
+
+.. |MO| replace:: :abbr:`MO (Manufacturing Order)`
+.. |MOs| replace:: :abbr:`MOs (Manufacturing Orders)`
+.. |BoM| replace:: :abbr:`BoM (Bill of Materials)`
+.. |BoMs| replace:: :abbr:`BoMs (Bills of Materials)`
+.. |RFQ| replace:: :abbr:`RFQ (Request for Quotation)`
+
+Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the
+**Inventory** app allows for comprehensive lead time configuration, allowing coordination and planning
+of manufacturing orders, deliveries, and receipts.
+
+# Lead time types
+
+Different lead times for different operations can impact various stages of the order fulfillment
+process. Here's a summary of the types of lead times in Odoo:
+
+.. image:: lead_times/all-lead-times.png
+   :alt: Show graphic of all lead times working together.
+
+- :ref:`Customer lead time <inventory/warehouses_storage/customer-lt>`: default time frame for
+  fulfilling customer orders. The customer lead time is the number of days from the date the sales
+  order (SO) is confirmed to the date the products are shipped from the warehouse. This is also
+  known as *delivery lead time*.
+
+- :ref:`Sales security lead time <inventory/warehouses_storage/sales-security-lt>`: moves the
+  *scheduled delivery date* forward by a specified number of days. This serves as a buffer to allow
+  ample time to prepare the outgoing shipment earlier, considering the possibility of delays in the
+  fulfillment process.
+
+- :ref:`Purchase lead time <inventory/warehouses_storage/purchase-lt>`: number of days from the
+  confirmation of a purchase order (PO) to the receipt of products. It provides insight on the time
+  it takes for products to arrive at the warehouse, facilitating effective scheduling and planning
+  of supplier deliveries.
+
+- :ref:`Purchase security lead time <inventory/warehouses_storage/purchase-security-lt>`: advances
+  the order deadline on a :abbr:`PO (Purchase Order)` by a specified number of days. This proactive
+  approach of placing orders earlier mitigates the risk of vendor or shipping delays. Thus, for
+  products that are set to replenish to order, the need appears on the *Replenishment report*
+  earlier, according to the specified number of days.
+
+- :ref:`Days to Purchase <inventory/warehouses_storage/days-to-purchase>`: days needed for the
+  vendor to receive a request for quotation (RFQ) and confirm it. It advances the deadline to
+  schedule a |RFQ| by a specified number of days.
+
+- :ref:`Manufacturing lead time <inventory/warehouses_storage/manuf-lt>`: number of days needed to
+  complete a manufacturing order (MO) from the date of confirmation. This lead time includes
+  weekends (non-working hours in Odoo), and is used to forecast an approximate production date for a
+  finished good.
+
+- :ref:`Days to prepare manufacturing order
+  <inventory/warehouses_storage/prepare-manufacturing-order>`: number of days needed to replenish
+  components, or manufacture sub-assemblies of the product. Either set one directly on the bill of
+  materials (BoM), or click *Compute* to sum up purchase and manufacturing lead times of components
+  in the |BoM|.
+
+- :ref:`Manufacturing security lead time <inventory/warehouses_storage/manuf-security-lt>`: moves
+  the scheduled date of the |MO| forward by a specified number of days. When used in conjunction
+  with :ref:`replenish to order <inventory/management/products/strategies>`, the security lead time
+  makes the need appear earlier on the replenishment report.
+
+.. _inventory/warehouses_storage/customer-lt:
+
+# Sales lead times
+
+Customer lead times and sales security lead times can be configured to automatically compute an
+*expected delivery date* on a :abbr:`SO (Sales Order)`. The expected delivery date ensures a
+realistic *delivery dates* setting for shipments from the warehouse.
+
+Odoo issues a warning message if the set delivery date is earlier than the expected date, as it may
+not be feasible to fulfill the order by that time, which would impact other warehouse operations.
+
+.. example::
+   A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is confirmed on July 11th. The
+   product has a customer lead time of 14 days, and the business uses a sales security lead time of
+   1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th.
+
+   .. image:: lead_times/scheduled-date.png
+      :alt: Set *Delivery Date* in a sales order. Enables delivery lead times feature.
+
+The following sections demonstrate how to automatically compute expected delivery dates.
+
+## Customer lead time
+
+Set the customer lead time on each product form, by navigating to the products page. To do so, go to
+:menuselection:`Sales app --> Products --> Products`. From there, select the desired product, and
+switch to the :guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` field, fill
+in the number of calendar days required to fulfill the delivery order from start to finish.
+
+.. example::
+   Set a 14-day customer lead time for the `Coconut-scented candle` by navigating to its product
+   form. Then, in the :guilabel:`Inventory` tab, type `14.00` days into the :guilabel:`Customer Lead
+   Time` field.
+
+   .. image:: lead_times/customer.png
+      :alt: Set *Customer Lead Time* on the product form.
+
+.. _inventory/warehouses_storage/sales-security-lt:
+
+## Sales security lead time
+
+*Sales security lead time* is set globally for the business in :menuselection:`Inventory app -->
+Configuration --> Settings`.
+
+On the configuration page, under the :guilabel:`Advanced Scheduling` heading, locate the box for
+:guilabel:`Security Lead Time for Sales`, and click the checkbox to enable the feature.
+
+Next, enter the desired number of calendar days. This security lead time is a buffer notifying the
+team to prepare for outgoing shipments earlier than the scheduled date.
+
+.. example::
+   Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes the
+   :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. In that case, if a
+   product is initially scheduled for delivery on April 6th, but with a one-day security lead time,
+   the new scheduled date for the delivery order would be April 5th.
+
+   .. image:: lead_times/sales-security.png
+      :alt: View of the security lead time for sales configuration from the sales settings.
+
+## Deliver several products
+
+For orders that include multiple products with different lead times, the lead times can be
+configured directly from the quotation itself. On a quotation, click the :guilabel:`Other Info` tab,
+and set the :guilabel:`Shipping Policy` to:
+
+#. :guilabel:`As soon as possible` to deliver products as soon as they are ready. The
+   :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's
+   date to the shortest lead time among the products in the order.
+
+#. :guilabel:`When all products are ready` to wait to fulfill the entire order at once. The
+   :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is determined by adding today's
+   date to the longest lead time among the products in the order.
+
+.. image:: lead_times/shipping-policy.png
+   :alt: Show *Shipping Policy* field in the *Other Info* tab of a quotation.
+
+.. example::
+   In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the products have a lead
+   time of 8 days and 5 days, respectively. Today's date is April 2nd.
+
+   When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as possible`, the scheduled
+   delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel:`When all
+   products are ready` configures the scheduled date to be 8 days from today: April 10th.
+
+.. _inventory/warehouses_storage/purchase-lt:
+
+# Purchase lead times
+
+Automatically determining the dates on which to place orders from suppliers can help simplify the
+procurement process.
+
+Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO (Purchase Order)` deadline,
+based on the required date the product is needed in the warehouse. By working backwards from the
+receipt date, vendor lead times and purchase security lead times are taken into account, in order to
+determine the :abbr:`PO (Purchase Order)` deadline.
+
+This deadline is the date by which the order should be confirmed, in order to ensure timely arrival
+by the expected receipt date.
+
+.. image:: lead_times/vendor-lead-times.png
+   :alt: Visualization of PO deadline and receipt date used with vendor lead times.
+
+.. seealso::
+   :doc:`PO scheduling with reordering rules <reordering_rules>`
+
+## Vendor lead time
+
+To set a vendor lead time for orders arriving in the warehouse from a vendor location, begin by
+navigating to a product form through :menuselection:`Purchase app --> Products --> Products`.
+
+Next, select the desired product, and switch to the :guilabel:`Purchase` tab. In the editable vendor
+pricelist, click the :guilabel:`Add a line` button to add vendor details, such as the
+:guilabel:`Vendor` name, :guilabel:`Price` offered for the product, and lastly, the
+:guilabel:`Delivery Lead Time`.
+
+> **note**:
+>    Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead
+   time selected will be the entry at the top of the list.
+
+.. example::
+   On the vendor pricelist of the product form, the :guilabel:`Delivery Lead Time` for the selected
+   vendor is set to `10 days.`
+
+   .. image:: lead_times/set-vendor.png
+      :alt: Add delivery lead times to vendor pricelist on a product.
+
+By setting the vendor lead time, the expected arrival date of the item is automatically determined
+as the date of the :abbr:`PO (Purchase Order)` confirmation, plus the vendor lead time. This ensures
+that warehouse employees are notified, if the products do **not** arrive within the expected
+timeframe.
+
+.. example::
+   On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product configured with a 10-day
+   vendor lead time, Odoo automatically sets the :guilabel:`Receipt Date` to July 21st. The receipt
+   date also appears as the :guilabel:`Scheduled Date` on the warehouse receipt form, accessible
+   from the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase Order)`.
+
+   .. image:: lead_times/receipt-date.png
+      :alt: Show expected *Receipt Date* of the product from the vendor.
+
+   .. image:: lead_times/scheduled-date-receipt.png
+      :alt: Show expected *Scheduled Date* of arrival of the product from the vendor.
+
+.. _inventory/warehouses_storage/purchase-security-lt:
+
+## Purchase security lead time
+
+*Purchase security lead time* is set globally for the business in :menuselection:`Inventory app -->
+Configuration --> Settings`.
+
+On the :guilabel:`Settings` page, under the :guilabel:`Advanced Scheduling` heading, tick the
+checkbox for :guilabel:`Security Lead Time for Purchase`.
+
+Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is
+set to account for potential delays in supplier deliveries. Then, click :guilabel:`Save`.
+
+.. example::
+   Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, pushes the
+   :guilabel:`Scheduled Date` of receipt back by two days. In that case, if a product is initially
+   scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for
+   the receipt would be April 8th.
+
+   .. image:: lead_times/vendor-security.png
+      :alt: Set security lead time for purchase from the Inventory > Configuration > Settings.
+
+.. _inventory/warehouses_storage/days-to-purchase:
+
+## Days to purchase lead time
+
+To set it up, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the
+:guilabel:`Advanced Scheduling` section, in the :guilabel:`Days to Purchase` field, specify the
+number of days required for the vendor to confirm a |RFQ| after receiving it from the company.
+
+.. _inventory/warehouses_storage/manuf-lt:
+
+# Manufacturing lead times
+
+Lead times can help simplify the procurement process for consumable materials and components used in
+manufactured products with bills of materials (BoMs).
+
+The |MO| deadline, which is the deadline to begin the manufacturing process to complete the product
+by the scheduled delivery date, can be determined by configuring the manufacturing lead times and
+manufacturing security lead times.
+
+.. image:: lead_times/manuf-lead-times.png
+   :alt: Visualization of the determination of planned MO date manufacturing lead times.
+
+## Manufacturing lead time
+
+Manufacturing lead times for products are configured from a product's bill of materials (BoM) form.
+
+To add a lead time to a |BoM|, navigate to :menuselection:`Manufacturing app --> Products --> Bills
+of Materials`, and select the desired |BoM| to edit.
+
+On the |BoM| form, click the :guilabel:`Miscellaneous` tab. Change the value (in days) in the
+:guilabel:`Manuf. Lead Time` field to specify the calendar days needed to manufacture the product.
+
+.. image:: lead_times/set-manufacturing.png
+   :alt: Manuf. Lead Time value specified on a product's Bill of Material form.
+
+> **note**:
+>    If the selected |BoM| is a multi-level |BoM|, the manufacturing lead times of the components are
+   added.
+
+   If the |BoM| product is subcontracted, the :guilabel:`Manuf. Lead Time` can be used to determine
+   the date at which components should be sent to the subcontractor.
+
+Establish a |MO| deadline, based on the *expected delivery date*, indicated in the
+:guilabel:`Scheduled Date` field of the :abbr:`DO (Delivery Order)`.
+
+The |MO| deadline, which is the :guilabel:`Scheduled Date` field on the |MO|, is calculated as the
+*expected delivery date* subtracted by the manufacturing lead time.
+
+This ensures the manufacturing process begins on time, in order to meet the delivery date.
+
+However, it is important to note that lead times are based on calendar days. Lead times do **not**
+consider weekends, holidays, or *work center capacity* (:dfn:`the number of operations that can be
+performed at the work center simultaneously`).
+
+.. seealso::
+   - :doc:`Manufacturing planning <../../../manufacturing/workflows/use_mps>`
+   - :doc:`Schedule MOs with reordering rules <reordering_rules>`
+
+.. example::
+   A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is August 15th. The
+   product requires 14 days to manufacture. So, the latest date to start the :abbr:`MO
+   (Manufacturing Order)` to meet the commitment date is August 1st.
+
+.. _inventory/warehouses_storage/prepare-manufacturing-order:
+
+## Days to prepare manufacturing order
+
+Configure the days required to gather components to manufacture a product by going to its |BoM|. To
+do that, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select
+the desired |BoM|.
+
+In the :guilabel:`Miscellaneous` tab of the |BoM|, specify the calendar days needed to obtain
+components of the product in the :guilabel:`Days to prepare Manufacturing Order` field. Doing so
+creates |MOs| in advance, and ensures there is enough time to either replenish components, or
+manufacture semi-finished products.
+
+> **tip**:
+>    Clicking :guilabel:`Compute`, located next to the :guilabel:`Days to prepare Manufacturing Order`
+   field, calculates the longest lead time among all the components listed on the |BoM|.
+
+   *Purchase security lead times* that impact this specific |BoM| are also added to this value.
+
+.. example::
+
+   A |BoM| has two components, one has a manufacturing lead time of two days, and the other has a
+   purchase lead time of four days. The :guilabel:`Days to prepare Manufacturing Order` is four
+   days.
+
+.. _inventory/warehouses_storage/manuf-security-lt:
+
+## Manufacturing security lead time
+
+*Manufacturing security lead time* is set globally for the business in :menuselection:`Manufacturing
+app --> Configuration --> Settings`. Under the :guilabel:`Planning` heading, tick the checkbox for
+:guilabel:`Security Lead Time`.
+
+Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is
+set to account for potential delays in the manufacturing process. Then, click :guilabel:`Save`.
+
+.. image:: lead_times/manuf-security.png
+   :alt: View of the security lead time for manufacturing from the manufacturing app settings.
+
+.. example::
+   A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` set for August 15th.
+   The manufacturing lead time is 7 days, and manufacturing security lead time is 3 days. So, the
+   :guilabel:`Scheduled Date` on the |MO| reflects the latest date to begin the manufacturing order.
+   In this example, the planned date on the |MO| is August 5th.
+
+# Global example
+
+See the following example to understand how all the lead times work together to ensure timely order
+fulfillment:
+
+- **Sales security lead time**: 1 day
+- **Manufacturing security lead time**: 2 days
+- **Manufacturing lead time**: 3 days
+- **Purchase security lead time**: 1 day
+- **Vendor lead time**: 4 days
+
+The customer places an order for a manufactured product on September 1st, and the scheduled delivery
+date from the warehouse is on September 20th. Odoo uses lead times and automated reordering rules to
+schedule the necessary operations, based on the outgoing shipment delivery date, September 20th:
+
+.. image:: lead_times/global-example.png
+   :alt: Show timeline of how lead times work together to schedule warehouse operations.
+
+- **September 1st**: Sales order created, confirmed by salesperson.
+
+- **September 9th**: Deadline to order components to ensure they arrive in time when manufacturing
+  begins (4-day supplier lead time).
+
+- **September 13th**: Scheduled date of receipt for components. Initially, it was set to 9/14, but
+  the 1-day purchase security lead time pushed the date earlier by 1 day.
+
+- **September 14th**: Deadline to begin manufacturing. Calculated by subtracting the manufacturing
+  lead time of 3 days, and the manufacturing security lead time of 2 days, from the expected
+  delivery date of September 19th.
+
+- **September 19th**: :guilabel:`Scheduled Date` on the delivery order form indicates the updated
+  expected delivery date, which was originally set as September 20th. But the sales security lead
+  time pushed the date forward by a day.
+
+Odoo's replenishment planning maps a business' order fulfillment process, setting pre-determined
+deadlines and raw material order dates, including buffer days for potential delays. This ensures
+products are delivered on time.

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.md

@@ -0,0 +1,142 @@
+---
+title: "Replenish on order (MTO)"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/mto.html"
+---
+
+========================
+# Replenish on order (MTO)
+
+.. |SO| replace:: :abbr:`SO (sales order)`
+.. |SOs| replace:: :abbr:`SOs (sales orders)`
+.. |MO| replace:: :abbr:`MO (manufacturing order)`
+.. |PO| replace:: :abbr:`PO (purchase order)`
+.. |MTO| replace:: :abbr:`MTO (make to order)`
+.. |RFQ| replace:: :abbr:`RFQ (request for quotation)`
+.. |BOM| replace:: :abbr:`BOM (bill of materials)`
+
+*Replenish on order*, also known as *MTO* (make to order), is a replenishment strategy that creates
+a draft order for a product every time it is required to fulfill a sales order (SO), or when it is
+needed as a component in a manufacturing order (MO).
+
+For products that are purchased from a vendor, a request for quotation (RFQ) is created to replenish
+the product, while an |MO| is created for products that are manufactured. The creation of an |RFQ|
+or |MO| occurs every time an |SO| or |MO| that requires the product is confirmed, regardless of the
+current stock level of the product being ordered.
+
+> **important**:
+>    In order to use the |MTO| route, the :guilabel:`Multi-Step Routes` feature must be enabled. To do
+   so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and tick the
+   checkbox next to :guilabel:`Multi-Step Routes`, under the :guilabel:`Warehouse` heading.
+
+   Finally, click :guilabel:`Save` to save the change.
+
+.. _inventory/warehouses_storage/unarchive-mto:
+
+# Unarchive MTO route
+
+By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| is a somewhat niche
+workflow that is only used by certain companies. However, it is easy to unarchive the route in just
+a few simple steps.
+
+To do so, begin by navigating to :menuselection:`Inventory app --> Configuration --> Routes`. On the
+:guilabel:`Routes` page, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon on the right
+side of the search bar, and click the :guilabel:`Archived` filter to enable it.
+
+.. image:: mto/archived-filter.png
+   :align: center
+   :alt: The archived filter on the Routes page.
+
+After enabling the :guilabel:`Archived` filter, the :guilabel:`Routes` page shows all routes which
+are currently archived. Tick the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click
+the :icon:`fa-cog` :guilabel:`Actions` button to reveal a drop-down menu. From the drop-down menu,
+select :guilabel:`Unarchive`.
+
+.. image:: mto/unarchive-button.png
+   :align: center
+   :alt: The unarchive action on the Routes page.
+
+Finally, remove the :guilabel:`Archived` filter from the search bar. The :guilabel:`Routes` page now
+shows all unarchived routes, including :guilabel:`Replenish on Order (MTO)`, which is selectable on
+the *Inventory* tab of each product page.
+
+# Configure product for MTO
+
+With the |MTO| route unarchived, products can now be properly configured to use replenish on order.
+To do so, begin by going to :menuselection:`Inventory app --> Products --> Products`, then select an
+existing product, or click :guilabel:`New` to configure a new one.
+
+On the product page, select the :guilabel:`Inventory` tab and enable the :guilabel:`Replenish on
+Order (MTO)` route in the :guilabel:`Routes` section, along with the :guilabel:`Buy` or
+:guilabel:`Manufacture` route.
+
+> **important**:
+>    The :guilabel:`Replenish on Order (MTO)` route **does not** work unless another route is selected
+   as well. This is because Odoo needs to know how to replenish the product when an order is placed
+   for it (buy or manufacture it).
+
+.. image:: mto/select-routes.png
+   :align: center
+   :alt: Select the MTO route and a second route on the Inventory tab.
+
+If the product is purchased from a vendor to fulfill |SOs|, enable the :guilabel:`Can be Purchased`
+checkbox under the product name. Doing so makes the :guilabel:`Purchase` tab appear alongside the
+other tabs below.
+
+Click the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the :guilabel:`Price` they
+sell the product for.
+
+> **important**:
+>    Specifying a vendor is essential for this workflow, because Odoo cannot generate an |RFQ| without
+   knowing who the product is purchased from.
+
+If the product is manufactured, make sure it has a bill of materials (BOM) configured for it. To do
+so, click the :guilabel:`Bill of Materials` smart button at the top of the screen, then click
+:guilabel:`New` on the :guilabel:`Bill of Materials` page to configure a new |BOM| for the product.
+
+.. seealso::
+   For a full overview of |BOM| creation, see the documentation on :doc:`bills of materials
+   <../../../manufacturing/basic_setup/bill_configuration>`.
+
+# Replenish using MTO
+
+After configuring a product to use the |MTO| route, a replenishment order is created for it every
+time an |SO| or |MO| including the product is confirmed. The type of order created depends on the
+second route selected in addition to |MTO|.
+
+For example, if *Buy* was the second route selected, then a |PO| is created upon confirmation of an
+|SO|.
+
+> **important**:
+>    When the |MTO| route is enabled for a product, a replenishment order is always created upon
+   confirmation of an |SO| or |MO|. This is the case, even if there is enough stock of the product
+   on-hand to fulfill the |SO|, without buying or manufacturing additional units of it.
+
+While the |MTO| route can be used in unison with the *Buy* or *Manufacture* routes, the *Buy* route
+is used as the example for this workflow. Begin by navigating to the :menuselection:`Sales` app,
+then click :guilabel:`New`, which opens a blank quotation form.
+
+On the blank quotation form, add a :guilabel:`Customer`. Then, click :guilabel:`Add a product` under
+the :guilabel:`Order Lines` tab, and enter a product configured to use the *MTO* and *Buy* routes.
+Click :guilabel:`Confirm`, and the quotation is turned into an |SO|.
+
+A :guilabel:`Purchase` smart button now appears at the top of the page. Clicking it opens the |RFQ|
+associated with the |SO|.
+
+Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a |PO|. A purple
+:guilabel:`Receive Products` button now appears above the |PO|. Once the products are received,
+click :guilabel:`Receive Products` to open the receipt order, and click :guilabel:`Validate` to
+enter the products into inventory.
+
+Return to the |SO| by clicking the :guilabel:`SO` breadcrumb, or by navigating to
+:menuselection:`Sales app --> Orders --> Orders`, and selecting the|SO|.
+
+Finally, click the :guilabel:`Delivery` smart button at the top of the order to open the delivery
+order. Once the products have been shipped to the customer, click :guilabel:`Validate` to confirm
+the delivery.
+
+.. seealso::
+   For information on workflows that include the |MTO| route, see the following documentation:
+
+   - :doc:`resupply_warehouses`
+   - :doc:`../../../manufacturing/subcontracting/subcontracting_basic`
+   - :doc:`../../../manufacturing/advanced_configuration/sub_assemblies`