odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/product_management/configure/type.md

@@ -0,0 +1,339 @@
+---
+title: "Product type"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/product_management/configure/type.html"
+---
+
+============
+# Product type
+
+.. |BOM| replace:: :abbr:`BoM (Bill of Materials)`
+
+In Odoo, goods and services are both set up as *products*. When setting up a new product, there are
+several fields that should be carefully chosen, as they determine how to invoice and track a
+business' goods or services.
+
+To configure an existing product, go to :menuselection:`Inventory app --> Products --> Products`,
+and select the desired product from the list. Alternatively, from the :guilabel:`Products` menu,
+click :guilabel:`New` to create a new product.
+
+.. seealso::
+   [Odoo Tutorials: Product Type ](https://www.youtube.com/watch?v=l6j0ZkP5mLM)
+
+.. _inventory/product_management/for-sale-or-purchase:
+
+# For sale vs. purchase
+
+Goods and services can be designated as those that can be bought, sold, or both. On the product
+form, tick the :guilabel:`Sales` checkbox if a product can be *sold* to a customer (e.g. finished
+goods). Tick :guilabel:`Purchase` if the product can be *purchased* (e.g. raw materials).
+
+.. example::
+   If a resale clothing shop buys discounted denim jackets and sells them at a higher cost to the
+   end consumer, the `Jacket` product form might have *both* the :guilabel:`Sales` and
+   :guilabel:`Purchase` checkbox ticked.
+
+   On the other hand, say the store occasionally sews new jackets using denim and thread as
+   raw materials. In the `Denim` and `Thread` product forms, only :guilabel:`Purchase` should be
+   ticked, whereas the `Handmade Jacket` product form would only tick :guilabel:`Sales`.
+
+# Goods vs. services
+
+When configuring a product, a :guilabel:`Product Type` needs to be selected on the
+:guilabel:`General Information` tab of a product form. Each product type impacts different
+operations in other Odoo applications, such as **Sales** and **Purchase**, and should be chosen
+carefully.
+
+- :guilabel:`Goods`: a tangible, material object (e.g. anything from a hamburger to a house)
+- :guilabel:`Service`: an intangible, immaterial offering (e.g., a repair, a haircut, call center
+  assistance)
+- :guilabel:`Combo`: any mix of goods and services (e.g. a new car (*good*) with an oil change
+  included (*service*))
+
+> **note**:
+>   Due to their immaterial nature, services are not trackable in Odoo's **Inventory** application.
+
+.. _inventory/product_management/manufacture:
+
+# Configure goods
+
+Selecting :guilabel:`Goods` as the :guilabel:`Product Type` automatically triggers the appearance of
+a few fields and tabs in the product form:
+
+- :guilabel:`Inventory` tab: From here,
+  :doc:`purchasing and manufacturing routes <../../shipping_receiving/daily_operations/use_routes>`
+  and product logistics, such as product weight and customer lead time, can be specified.
+- :ref:`Invoicing Policy <inventory/product_management/invoicing-policy>` field: This field
+  determines at what point in the sales process a customer is invoiced.
+
+  > **important**:
+>      The :guilabel:`Invoicing Policy` field **only** appears if the **Sales** app is installed.
+
+- :ref:`Track Inventory <inventory/product_management/tracking-inventory>` field: This checkbox
+  determines whether Odoo tracks inventory for this product.
+- Smart buttons: Some smart buttons appear above the form when :guilabel:`Goods` is selected;
+  others show upon selecting a :guilabel:`Track Inventory` method. For example,
+  :guilabel:`On Hand` and :guilabel:`Forecasted` display when :guilabel:`Track Inventory` is
+  ticked. In general, most smart buttons on a product form link to :ref:`inventory operations
+  <inventory/product_management/inventory-ops-by-product-type>`.
+
+.. image:: type/product-form.png
+   :alt: Designate a product as a good or service.
+
+.. _inventory/product_management/invoicing-policy:
+
+## Invoicing policy
+
+The :guilabel:`Invoicing policy` field only shows on the product form if a product is for sale (in
+other words, if :guilabel:`Sales` is ticked, and the **Sales** app is installed).
+
+When configuring a product for sale, it is necessary to choose an
+:doc:`invoicing policy <../../../../sales/sales/invoicing/invoicing_policy>`. When an invoicing
+policy of :guilabel:`Ordered quantities` is selected, customers are invoiced once the sales order
+is confirmed. When :guilabel:`Delivered quantities` is selected, customers are invoiced once the
+delivery is completed.
+
+.. _inventory/product_management/tracking-inventory:
+
+## Tracked vs. untracked goods
+
+The :guilabel:`Track Inventory` field on the product form determines a lot of Odoo's **Inventory**
+operations.
+
+*Tracked* products are those for which stock and inventory are maintained. Examples include finished
+goods and, often, the raw materials or components needed to make them.
+
+When :guilabel:`Track Inventory` is ticked, a drop-down menu appears, offering for inventory to be
+tracked one of three ways: :guilabel:`By Unique Serial Number`, :guilabel:`By Lots`, or
+:guilabel:`By Quantity`.
+
+.. image:: type/tracked.png
+   :alt: Configure a tracked good.
+
+*Untracked* products (sometimes referred to as *non-inventory* products) are typically consumed in a
+short period of time, meaning that stock/inventory does *not* need to be maintained. Non-inventory
+products are often essential, but exact counts are unnecessary. Examples include: office supplies,
+packaging materials, or items used in production that do not need to be individually tracked.
+
+> **tip**:
+>    Tick the :guilabel:`Track Inventory` checkbox if it is necessary to track a product's stock at
+   various locations, for inventory valuation, with lots and/or serial numbers, or when using
+   reordering rules.
+
+.. seealso::
+   :doc:`Tracking storable products using lot and serial numbers <../product_tracking>`
+
+.. _inventory/product_management/inventory-ops-by-product-type:
+
+## Inventory operations by product type
+
+:ref:`Whether a good is tracked or untracked <inventory/product_management/tracking-inventory>`
+affects common **Inventory** operations, like transfers and reordering rules.
+
+The table below summarizes which operations (and smart buttons) are enabled for tracked vs.
+untracked goods. Click highlighted chart items to navigate to detailed sections and related
+documents.
+
+.. list-table::
+   :header-rows: 1
+   :stub-columns: 1
+
+   * - Inventory operation
+     - Tracked
+     - Untracked
+   * - :ref:`Show on-hand quantity <inventory/product_management/on-hand>`
+     - Yes
+     - No
+   * - :ref:`Show forecasted quantity <inventory/product_management/on-hand>`
+     - Yes
+     - No
+   * - :ref:`Use reordering rules <inventory/product_management/replenishment>`
+     - Yes
+     - No
+   * - :ref:`Can be included in a purchase order <inventory/product_management/po>`
+     - Yes
+     - Yes
+   * - :ref:`Use putaway rules <inventory/product_management/putaway>`
+     - Yes
+     - No
+   * - :ref:`Can be manufactured, subcontracted, or used in another good's BoM
+       <inventory/product_management/manufacturing>`
+     - Yes
+     - Yes
+   * - :doc:`Use inventory adjustments <../../warehouses_storage/inventory_management/count_products>`
+     - Yes
+     - No
+   * - :doc:`Use inventory valuation <../inventory_valuation/using_inventory_valuation>`
+     - Yes
+     - No
+   * - :ref:`Create transfer <inventory/product_management/transfer-store>`
+     - Yes
+     - Yes
+   * - :doc:`Use lot/serial number tracking <../product_tracking>`
+     - Yes
+     - No
+   * - :doc:`Can be placed in a kit <../../../manufacturing/advanced_configuration/kit_shipping>`
+     - Yes
+     - Yes
+   * - :ref:`Can be placed in a package <inventory/product_management/package>`
+     - Yes
+     - Yes
+   * - :ref:`Appears on inventory reports <inventory/product_management/report>`
+     - Yes
+     - No
+
+### Inventory
+
+.. _inventory/product_management/on-hand:
+
+On-hand and forecasted quantities
+*********************************
+
+A tracked product's on-hand and forecasted quantities, based on incoming and outgoing orders, are
+reflected on the product form with two smart buttons:
+
+- :icon:`fa-cubes` :guilabel:`On-Hand Quantity`: This represents the number of units currently
+  available in inventory. Click the button to view or add stock levels for a tracked product.
+- :icon:`fa-area-chart` :guilabel:`Forecasted`: This represents the number of units *expected* to be
+  available in inventory after all orders are taken into account. In other words,
+  :math:`\text{forecasted} = \text{on hand quantity} + \text{incoming shipments} - \text{outgoing shipments}`.
+  Click the button to view the :guilabel:`Forecasted Report`.
+
+On the other hand, untracked products are regarded as *always* available. Consequently,
+:guilabel:`On-Hand Quantity` is not tracked, and there is no :guilabel:`Forecasted` quantity
+available.
+
+.. _inventory/product_management/putaway:
+
+Putaway rules and storage
+*************************
+
+Both tracked and untracked goods can optimize storage using:
+
+- :icon:`fa-random` :doc:`Putaway Rules <../../shipping_receiving/daily_operations/putaway>`:
+  This represents putaway rules that apply to a good, such as where to store it when a new shipment
+  arrives.
+- :icon:`fa-cubes`
+  :doc:`Storage Capacities <../../shipping_receiving/daily_operations/storage_category>`:
+  This represents any storage capacity limitations specified for this good. For example, a warehouse
+  may require that only ten (or less) sofas be stored there at any given time, due to their large
+  size.
+
+.. _inventory/product_management/replenishment:
+
+Replenishment
+*************
+
+#### Reordering rules
+
+Only tracked products can trigger
+:doc:`reordering rules <../../warehouses_storage/replenishment/reordering_rules>` to generate
+purchase orders. Untracked goods *cannot* be managed using reordering rules.
+
+Reordering rules can be configured directly on the product form via the
+:icon:`fa-refresh` :guilabel:`(refresh)` icon.
+
+> **note**:
+>    If reordering rules already exist on a product, Odoo re-labels this button to
+   :guilabel:`Min / Max`, to show the minimum and maximum number of units that must be in stock.
+
+.. _inventory/product_management/po:
+
+#### Create purchase orders
+
+Both tracked and untracked products can be included in a request for quotation in the **Purchase**
+app. However, when receiving untracked products, their on-hand quantity does not change upon
+validating the receipt (`WH/IN`).
+
+#### Replenish smart button
+
+The :guilabel:`Replenish` smart button allows all goods to be restocked directly from the product
+form, according to the *Preferred Route*.
+
+.. seealso::
+   :doc:`Replenishment <../../warehouses_storage/replenishment>`
+   [Odoo Tutorials: Replenishment Methods for Manufacturing
+   ](https://www.youtube.com/watch?v=vtjeMGcG8aM)
+
+.. _inventory/product_management/manufacturing:
+
+### Manufacturing
+
+Both tracked and untracked products can be manufactured,
+:doc:`subcontracted <../../../manufacturing/subcontracting>`, or included in another product's
+:doc:`bill of materials (BoM) <../../../manufacturing/basic_setup/bill_configuration>`.
+
+.. _inventory/product_management/BoM:
+
+On the product form for a tracked or untracked good, there are several smart buttons that may
+appear for manufacturing operations:
+
+- :icon:`fa-flask` :guilabel:`Bill of Materials`: This shows the BoMs used to make this product.
+- :icon:`fa-level-up` :guilabel:`Used In`: This shows other goods that include this product in their
+  BoM.
+
+.. _inventory/product_management/transfer-store:
+
+### Transfer goods
+
+*Transfers* are warehouse operations that involve the movement of goods. Examples of transfers
+include :doc:`deliveries and receipts
+<../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, as well as
+:doc:`internal transfers <../../warehouses_storage/replenishment/resupply_warehouses>` between
+warehouses.
+
+When creating a transfer for tracked products in the **Inventory** app, transfers modify the on-hand
+quantity at each location. For example, transferring five units from the internal location
+`WH/Stock` to `WH/Packing Zone` decreases the recorded quantity at `WH/Stock` and increases it at
+`WH/Packing Zone`.
+
+For untracked products, transfers can be created, but exact quantities at each storage location are
+not tracked.
+
+.. _inventory/product_management/package:
+
+### Packages
+
+Both tracked and untracked (non-inventory), products can be placed in :doc:`packages <package>`.
+
+However, for non-inventory products, the quantity is not tracked, and the product is not listed in
+the package's :guilabel:`Contents` (which can be accessed by going to :menuselection:`Inventory app
+--> Products --> Packages`, and selecting the desired package).
+
+.. figure:: type/package-content.png
+   :alt: Show Packages page, containing the package contents list.
+
+   An untracked product was placed in the package, but the **Content** section does not list it.
+
+Additionally, if the *Move Entire Packages* feature is enabled, moving a package updates the
+location of the contained tracked products but not the contained untracked products. To enable this
+feature, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`, select
+any operation, and tick the :guilabel:`Move Entire Packages` checkbox.
+
+.. _inventory/product_management/report:
+
+### Inventory reports
+
+**Only** tracked products appear on the following reports.
+
+> **important**:
+>    These reports are only available to users with
+   :doc:`administrator access <../../../../general/users/access_rights>`.
+
+- :doc:`Stock report <../../warehouses_storage/reporting/stock>`: This report provides a
+  comprehensive list of all on-hand, unreserved, incoming, and outgoing tracked inventory. To access
+  the report, go to :menuselection:`Inventory app --> Reporting --> Stock`.
+- :doc:`Location report  <../../warehouses_storage/reporting/locations>`: This report shows a
+  breakdown of which tracked products are held at each location (internal, external, or virtual).
+  The report is only available with the *Storage Location* feature activated
+  (:menuselection:`Inventory app --> Configuration --> Settings`). To access it, go to
+  :menuselection:`Inventory app --> Reporting --> Locations`.
+- :doc:`Moves History report <../../warehouses_storage/reporting/moves_history>`: This report
+  summarizes where and when this good has moved in/out of stock. To access the report, go to
+  :menuselection:`Inventory app --> Reporting --> Moves History`. Alternatively, click the
+  :icon:`fa-exchange` :guilabel:`In / Out` smart button on a product form to filter the report
+  on that product's specific moves history.
+- :guilabel:`Moves Analysis`: This report provides a pivot table view of inventory transfers by
+  operation type.
+- :ref:`Stock Valuation report <inventory/management/reporting/valuation-report>`: A detailed record
+  of the monetary value of all tracked inventory.
+

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/product_management/configure/uom.md

@@ -0,0 +1,167 @@
+---
+title: "Units of measure"
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/product_management/configure/uom.html"
+---
+
+================
+# Units of measure
+
+.. |UOM| replace:: :abbr:`UoM (Unit of Measure)`
+.. |PO| replace:: :abbr:`PO (Purchase Order)`
+.. |POs| replace:: :abbr:`POs (Purchase Orders)`
+.. |RFQ| replace:: :abbr:`RFQ (Request for Quotation)`
+.. |SO| replace:: :abbr:`SO (Sales Order)`
+
+In some cases, handling products in different units of measure is necessary. For example, a business
+can buy products from a country that uses the metric system, and then sell those products in a
+country that uses the imperial system. In that case, the business needs to convert the units.
+
+Another case for unit conversion is when a business buys products in a big pack from a supplier, and
+then sells those products in individual units.
+
+Odoo can be set up to use different *units of measure (UoM)* for one product.
+
+# Configuration
+
+To use different units of measure in Odoo, first go to :menuselection:`Inventory app -->
+Configuration --> Settings`, and under the :guilabel:`Products` section, activate the
+:guilabel:`Units of Measure` setting. Then, click :guilabel:`Save`.
+
+.. image:: uom/uom-enable-setting.png
+   :align: center
+   :alt: Enable Units of Measure in the Inventory settings.
+
+# Units of measure categories
+
+After enabling the *Units of Measure* setting, view the default units of measure categories in
+:menuselection:`Inventory app --> Configuration --> UoM Categories`. The category is important for
+unit conversion; Odoo can convert a product's units from one unit to another **only** if both units
+belong to the same category.
+
+.. image:: uom/category.png
+   :align: center
+   :alt: Set units of measure categories.
+
+Each units of measure category has a reference unit. The reference unit is highlighted in blue in
+the :guilabel:`Uom` column of the :guilabel:`Units of Measure Categories` page. Odoo uses the
+reference unit as a base for any new units.
+
+To create a new unit, first select the correct category from the :guilabel:`Units of Measure
+Categories` page. For example, to sell a product in a box of six units, click the :guilabel:`Unit`
+category line. Then, on the category page that appears, click :guilabel:`Add a line` in the
+:guilabel:`Units of Measure` tab. Then, in the :guilabel:`Unit of Measure` field, title the new
+unit, such as `Box of 6`, then in the :guilabel:`Type` field, select the appropriate size reference,
+such as :guilabel:`Bigger than the reference Unit of Measure`.
+
+If applicable, enter a :guilabel:`UNSPSC Category`, which is a globally recognized [code managed by
+GS1 ](https://www.unspsc.org/), that **must** be purchased in order to use.
+
+In the :guilabel:`Ratio` field, enter how many individual units are in the new |UOM|, such as
+`6.00000` when using the example of the `6-Pack` (since a box of six is six times *bigger* than the
+reference unit, `1.00000`).
+
+.. image:: uom/convert-products-by-unit.png
+   :align: center
+   :alt: Convert products from one unit to another as long as they belong to the same category.
+
+# Specify a product's units of measure
+
+To set units of measure on a product, first go to :menuselection:`Inventory app --> Products -->
+Products` and select a product to open its product form page.
+
+In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of Measure` field to specify
+the unit of measure that the product is sold in. The specified unit is also the unit used to keep
+track of the product's inventory and internal transfers.
+
+Edit the :guilabel:`Purchase UoM` field to specify the unit of measure that the product is purchased
+in.
+
+.. _inventory/product_replenishment/unit-conversion:
+
+# Unit conversion
+
+Odoo automatically converts unit measurements when products have different :abbr:`UoMs (Units of
+Measure)` and purchase :abbr:`UoMs (Units of Measure)`.
+
+This occurs in various scenarios, including:
+
+#. :ref:`Vendor orders <inventory/product_replenishment/buy-in-uom>`: purchase |UOM| on purchase
+   orders (POs) converts to |UOM| on internal warehouse documents
+#. :ref:`Automatic replenishment <inventory/product_replenishment/replenish>`: generates |POs| when
+   the stock levels of a product (tracked in |UOM|) dips below a certain level. But, the |POs| are
+   created using the purchase |UOM|
+#. :ref:`Sell products <inventory/product_replenishment/sell-in-uom>`: if a different |UOM| is used
+   on the sales order (SO), the quantity is converted to the warehouse's preferred |UOM| on the
+   delivery order
+
+.. _inventory/product_replenishment/buy-in-uom:
+
+## Buy products in the purchase UoM
+
+When creating a new request for quotation (RFQ) in the *Purchase* app, Odoo automatically uses the
+product's specified purchase unit of measure. If needed, manually edit the :guilabel:`UoM` value on
+the |RFQ|.
+
+After the |RFQ| is confirmed into a |PO|, click the :guilabel:`Receipt` smart button at the top of
+the |PO|.
+
+Odoo automatically converts the purchase unit of measure into the product's sales/inventory unit of
+measure, so the :guilabel:`Demand` column of the delivery receipt shows the converted quantity.
+
+.. example::
+   When the product's purchase :guilabel:`UoM` is `Box of 6`, and its sales/inventory unit of
+   measure is `Units`, the |PO| shows the quantity in boxes of six, and the receipt (and other
+   internal warehouse documents) shows the quantity in units.
+
+   .. figure:: uom/on-po.png
+      :align: center
+      :alt: Image of a purchase order that is using the purchase unit of measure.
+
+      An order of three quantities is placed using the purchase "UoM": `Box of 6`.
+
+   .. figure:: uom/on-receipt.png
+      :align: center
+      :alt: Image of receipt displaying the unit of measure.
+
+      Upon warehouse receipt, the recorded quantities are in the internal "Unit of Measure":
+      `Units`.
+
+.. _inventory/product_replenishment/replenish:
+
+## Replenishment
+
+A request for quotation for a product can also be generated directly from the product form using
+the :guilabel:`Replenish` button.
+
+After clicking :guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit of
+measure can be manually edited in the :guilabel:`Quantity` field, if needed. Then, click
+:guilabel:`Confirm` to create the |RFQ|.
+
+> **important**:
+>    A |PO| can **only** be automatically generated if at least **one** vendor is listed in the
+   product form's :guilabel:`Purchase` tab.
+
+.. image:: uom/replenish.png
+   :align: center
+   :alt: Click Replenish button to manually replenish.
+
+Navigate to the created |PO| by clicking the :guilabel:`Forecasted` smart button on the product
+form. Scroll down to the :guilabel:`Forecasted Inventory` section, and in the :guilabel:`Requests
+for quotation` line, click the |RFQ| reference number to open the draft |RFQ|. If necessary, the
+purchase |UOM| can be edited directly on the |PO|.
+
+.. _inventory/product_replenishment/sell-in-uom:
+
+## Sell in a different UoM
+
+When creating a new quotation in the *Sales* app, Odoo automatically uses the product's specified
+unit of measure. If needed, the :guilabel:`UoM` can be manually edited on the quotation.
+
+After the quotation is sent to the customer, and confirmed into a sales order (SO), click the
+:guilabel:`Delivery` smart button at the top of the |SO|. Odoo automatically converts the unit of
+measure into the product's inventory unit of measure, so the :guilabel:`Demand` column of the
+delivery shows the converted quantity.
+
+For example, if the product's |UOM| on the |SO| was changed to `Box of 6`, but its inventory unit of
+measure is `Units`, the |SO| shows the quantity in boxes of six, and the delivery shows the quantity
+in units.

package/payload/skills/odoo18-docs/references/docs/applications/inventory_and_mrp/inventory/product_management/configure.md

@@ -0,0 +1,169 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/inventory_and_mrp/inventory/product_management/configure.html"
+---
+
+:show-content:
+
+.. |UoM| replace:: :abbr:`UoM (Unit of Measure)`
+.. |UoMs| replace:: :abbr:`UoMs (Units of Measure)`
+
+# 
+# Configure product
+
+A group of products in Odoo can be further defined using:
+
+- :doc:`Units of measure (UoM) <configure/uom>`: a standard quantity for specifying product amounts
+  (e.g., meters, yards, kilograms). Enables automatic conversion between measurement systems in
+  Odoo, such as centimeters to feet.
+
+  - *Ex: Purchasing fabric measured in meters but receiving it in yards from a vendor.*
+
+- :doc:`configure/package`: A physical container used to group products together, regardless of
+  whether they are the same or different.
+
+  - *Ex: A box containing assorted items for delivery, or a storage box of two hundred buttons on a
+    shelf.*
+
+- :doc:`configure/packaging`: groups the *same* products together to receive or sell them in
+  specified quantities.
+
+  - *Ex: Cans of soda sold in packs of six, twelve, or twenty-four.*
+
+# Comparison
+
+This table provides a detailed comparison of units of measure, packages, and packaging to help
+businesses evaluate which best suits their requirements.
+
+.. list-table::
+   :header-rows: 1
+   :stub-columns: 1
+
+   * - Feature
+     - Unit of measure
+     - Packages
+     - Packaging
+   * - Purpose
+     - Standardized measurement for product units (e.g., cm, lb, L)
+     - Tracks the specific physical container and its contents
+     - Groups a fixed number of items together for easier management (e.g., packs of 6, 12 or 24)
+   * - Product uniformity
+     - Defined per product; saved as one |UoM| in the database
+     - Allows mixed products
+     - Same products only
+   * - Flexible
+     - Converts between vendor/customer |UoMs| and database |UoM|
+     - Items can be added or removed from the container
+     - Quantities are fixed (e.g., always packs of 6, 12 or 24)
+   * - Complexity
+     - Simplest for unit conversions
+     - More complex due to container-level inventory tracking
+     - Simpler; suitable for uniform product groupings
+   * - Inventory tracking
+     - Tracks product quantities within the warehouse in the specific |UoM| defined in the product
+       form
+     - Tracks package location and contents within the warehouse
+     - Tracks grouped quantities but not individual items' locations
+   * - Smooth barcode operations
+     - Not available
+     - Requires scanning both the package and individual items for reception. (even if there are 30
+       items in a package). Can enable the :ref:`Move Entire Packages
+       <inventory/product_management/move-entire-pack>` feature to update the package's contained
+       items' locations, when moving the package
+     - Scanning a packaging barcode automatically records all included units. (e.g. 1 pack = 12
+       units)
+   * - Product lookup
+     - Not available
+     - Scanning a product's barcode identifies its typical storage location in the Odoo database
+     - Barcode identifies grouped quantity, not storage location
+   * - Unique barcodes
+     - Not available
+     - Unique barcodes for individual packages (e.g. Pallet #12)
+     - Barcodes set at the packaging type level (e.g. for a pack of 6)
+   * - Reusability
+     - Not applicable
+     - Can be disposable or reusable, configured via the :ref:`Package Use
+       <inventory/warehouses_storage/cluster-pack>` field
+     - Disposable only
+   * - Container weight
+     - Not applicable
+     - Weight of the container itself is included in the *Shipping Weight* field of a package
+       (:menuselection:`Inventory app --> Products --> Packages`)
+     - Weight of the container is defined in the *Package Type* settings
+   * - Lot/serial number tracking
+     - Requires manual adjustments to track |UoMs| via lots (See :ref:`use case
+       <inventory/product_management/lots-uom>` for details)
+     - Applies only to contained products
+     - Applies to both contained products and the container
+   * - Custom routes
+     - Cannot be set
+     - Cannot be set
+     - Routes can define specific warehouse paths for a particular packaging type
+
+# Use cases
+
+After comparing the various features, consider how these businesses, with various inventory
+management and logistics workflows, came to their decision.
+
+## Pallets of items using packaging
+
+A warehouse receives shipments of soap organized on physical pallets, each containing 96 bars. These
+pallets are used for internal transfers and are also sold as standalone units. For logistical
+purposes, the pallet's weight must be included in the total shipping weight for certain deliveries.
+Additionally, the pallet requires a barcode to facilitate tracking, and the number of individual
+bars of soap must be included in the stock count when the pallet is received.
+
+After evaluating various options, *product packaging* was the most suitable solution. Packaging
+enables assigning a barcode to a pallet, identifying it as a "pallet type" containing 96 soap bars.
+This barcode streamlines operations by automatically registering the grouped quantity. Key
+distinctions include:
+
+- **Warehouse tracking limitations**: Odoo tracks only the total quantity, not the number of
+  packagings. For instance, if a pallet with 12 and 24 quantities is received, Odoo records 36
+  quantities, not the pallet details.
+- **Packaging barcodes are type-specific, not unique**: Barcodes represent packaging types (e.g.,
+  "pallet of 96 soap bars") but do not uniquely identify individual pallets, such as Pallet #1 or
+  Pallet #2.
+
+## Capture product information using barcode
+
+An Odoo user expects the **Barcode** app to display the typical storage location of a product by
+scanning a barcode for a container.
+
+*Packages* was the most suitable. When the :ref:`appropriate setting is enabled
+<inventory/warehouses_storage/enable-package>`, scanning a package barcode displays its contents in
+the **Barcode** app.
+
+Packages represent physical containers, enabling detailed tracking of the items they hold.
+Scanning a package provides visibility into its contents and facilitates operations, like inventory
+moves.
+
+.. _inventory/product_management/lots-uom:
+
+## Track different units of measure in storage
+
+A fruit juice distributor tracks multiple |UoMs| for their operations:
+
+- Fruits are purchased in tons.
+- Juice is produced and stored in kilograms.
+- Small samples are stored in grams for recipe testing.
+
+*Unit of Measure* was most suitable. Odoo automatically converts tons to kilograms during
+receipts. However, since Odoo tracks only one |UoM| per product in the database, the company uses
+lot numbers to differentiate |UoMs|:
+
+- LOT1: Grams (g)
+- LOT2: Kilograms (kg)
+
+Manual inventory adjustments are required to convert between lots, such as subtracting 1 kg from
+LOT2 to add 1,000 g to LOT1. While functional, this workaround can be time-consuming and prone to
+errors.
+
+.. toctree::
+   :titlesonly:
+
+   configure/type
+   configure/uom
+   configure/package
+   configure/packaging
+