msgid "**Odoo Inventory** is both an inventory application and a warehouse management system, with an advanced barcode scanner app. Learn how to manage lead times, automate replenishments, and configure advanced routes like drop-shipping, cross-docks, etc."
msgid "To process an inventory adjustment by using barcodes, you first need to open the *Barcode* app. Then, from the application, click on *Inventory Adjustments*."
msgid "Once you have clicked on *Inventory Adjustments*, Odoo will automatically create one. Note that, if you work with multi-location, you first need to specify in which location the inventory adjustment takes place."
msgid "Besides using the barcode scanner, you can also manually add a product if necessary. To do so, click on *Add Product* and fill the information in manually."
msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sale which sells products in bulk, in which the customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly."
msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in :ref:`developer mode <developer-mode>`. To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`."
msgid "The first step is to specify the **rule name**, for example Weight Barcode with 3 Decimals. You then have to specify the type for barcode nomenclature, in our case it will be Weighted Product."
msgid "The Barcode Pattern is a regular expression that defines the structure of the barcode. In this example 21 defines the products on which the rule will be applied, those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there simply to identify the product in question. The “N” define a number and the “D” define the decimals."
msgid "You can define different rules and order their priority thanks to the sequence. The first rule which matches the scanned barcode will be applied."
msgid "In case you weight 1,5 Kg of pasta, the balance will print you the following barcode 2112345015002. If you scan this barcode in your POS or when receiving products in your barcode application, Odoo will automatically create a new line for the Pasta product for a quantity of 1.5 Kg. For the point of sale, a price depending on the quantity will also be computed."
msgid "**Discounted Product**: allows you to create one barcode per applied discount. You can then scan your product in the POS and then scan the discount barcode, discount will be applied on the normal price of the product."
msgid "**Weighted Product**: allows you to identify the product and specify its weight, used in both POS (in which the price is computed based on the weight) and in inventory."
msgid "Then, you have the choice to either enter an existing transfer, by going to the corresponding operation type and manually selecting the one you want to enter, or by scanning the barcode of the transfer."
msgid "From there, you will be able to scan the products that are part of the existing transfer and/or add new products to this transfer. Once all the products have been scanned, you can validate the transfer to proceed with the stock moves."
msgid "When receiving a product in stock, you need to scan its barcode in order to identify it in the system. Once done, you can either make it enter the main location of the transfer, for example WH/Stock, or scan a location barcode to make it enter a sub-location of the main location."
msgid "When delivering a product, you have to scan the source location if it is different than the one initially set on the transfer. Then, you can start scanning the products that are delivered from this specific location."
msgid "Once the different products have been scanned, you have the possibility to scan another location, such as WH/Stock, and another page will be added to your delivery order. You can move from one to the other thanks to the *Previous* and *Next* buttons."
msgid "Now, you can validate your transfer. To do so, click on *Next* until you reach the last page of the transfer. There, you will be able to validate it."
msgid "When realizing an internal transfer with multi-location, you first have to scan the source location of the product. Then, you can scan the product in itself, before having to scan the barcode of the destination location."
msgid "If you work with serial/lot numbers taking all products into consideration, you can scan the barcode of the lot/serial number and Odoo will increase the quantity of the product, setting its lot/serial number."
msgid "If you have the same lot/serial number for different products, you can work by scanning the product barcode first, and then the barcode of the lot/serial number."
msgid "To create a transfer from the *Barcode* application, you first need to print the operation type barcodes. To do so, you can download the *Stock barcode sheet* from the home page of the app."
msgid "Once done, you can scan the one for which you want to create a new document. Then, an empty document will be created and you will be able to scan your products to populate it."
msgid "Getting started with barcode scanning in Odoo is fairly easy. Yet, a good user experience relies on an appropriate hardware setup. This guide will help you through the task of choosing and configuring the barcode scanner."
msgid "The 3 recommended type of barcode scanners to work with the Odoo **Inventory** and **Barcode Scanning** apps are the **USB scanner**, **the bluetooth scanner** and the **mobile computer scanner**."
msgid "If you scan products at a computer location, the **USB scanner** is the way to go. Simply plug it in the computer to start scanning. Just make sure when you buy it that the scanner is compatible with your keyboard layout or can be configured to be so."
msgid "The **bluetooth scanner** can be paired with a smartphone or a tablet and is a good choice if you want to be mobile but don't need a big investment. An approach is to log in Odoo on you smartphone, pair the bluetooth scanner with the smartphone and work in the warehouse with the possibility to check your smartphone from time to time and use the software 'manually'."
msgid "For heavy use, the **mobile computer scanner** is the handiest solution. It consists of a small computer with a built-in barcode scanner. This one can turn out to be a very productive solution, however you need to make sure that is is capable of running Odoo smoothly. The most recent models using Android + Google Chrome or Windows + Internet Explorer Mobile should do the job. However, due to the variety of models and configurations on the market, it is essential to test it first."
msgid "An USB barcode scanner needs to be configured to use the same keyboard layout as your operating system. Otherwise, your scanner won't translate characters correctly (replacing a 'A' with a 'Q' for example). Most scanners are configured by scanning the appropriate barcode in the user manual."
msgid "By default, Odoo has a 50 milliseconds delay between each successive scan (it helps avoid accidental double scanning). If you want to suppress this delay, you can configure your scanner to insert a carriage return at the end of each barcode. This is usually the default configuration and can be explicitly configured by scanning a specific barcode in the user manual ('CR suffix ON', 'Apply Enter for suffix', etc.)."
msgid "The barcode scanning features can save you a lot of time usually lost switching between the keyboard, the mouse and the scanner. Properly attributing barcodes to products, pickings locations, etc. allows you to work more efficiently by controlling the software almost exclusively with the barcode scanner."
msgid "To use this feature, you first need to activate the *Barcode* functionality via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you have ticked the feature, you can hit save."
msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to :menuselection:`Settings --> Configure Products Barcodes`."
msgid "Be careful to add barcodes directly on the product variants and not on the template product. Otherwise, you won’t be able to differentiate them."
msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Locations`."
msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization. You must pay the International Article Numbering Association a fee in exchange for an EAN code sequence."
msgid "In any warehouse management system, the recorded inventory counts in the database might not always match the actual inventory counts in the warehouse. The discrepancy between the two counts can be due to theft, damages, human errors, or other factors. As such, inventory adjustments must be made to reconcile the differences, and ensure that the recorded counts in the database match the actual counts in the warehouse."
msgid "To add an inventory adjustment line, click :guilabel:`Create` and fill in the :guilabel:`Product` and :guilabel:`Counted Quantity` fields. Then click :guilabel:`Save`."
msgid "At this stage, the count is recorded but not yet *applied*. Meaning the quantity on hand is not yet updated to match the new :guilabel:`Counted Quantity`."
msgid "To apply the new :guilabel:`Counted Quantity`, click :guilabel:`Apply` on the line or the :guilabel:`Apply All` button on the top of the page. If :guilabel:`Apply All` is clicked, a reference or reason can be entered before clicking :guilabel:`Apply`."
msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory --> Operations --> Inventory Adjustments` to update the :guilabel:`Counted Quantity` column for each product line."
msgid "If a count matches the :guilabel:`On Hand Quantity` recorded in the database, click on :guilabel:`Set`, which will copy the value in the :guilabel:`On Hand Quantity` field and paste it in the :guilabel:`Counted Quantity` field. A move with `0.00` :guilabel:`Quantity Done` will be recorded in the product's inventory adjustment history."
msgid "If a count does *not* match the :guilabel:`On Hand Quantity` recorded in the database, record the count in the :guilabel:`Counted Quantity` field. When :guilabel:`Apply` is clicked, a move with the difference between the :guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity` will be recorded in the product's inventory adjustment history."
msgid "Sometimes a count occurs, but can not be applied in the database right away. In the time between the actual count and applying the inventory adjustment, product moves can occur. In that case, the :guilabel:`On Hand Quantity` in the database can change and will not be consistent with the counted quantity. As an extra caution measure, Odoo will ask for confirmation before applying the inventory adjustment."
msgid ":guilabel:`Accounting Date`: the date at which the adjustments will be accounted. The column is hidden by default, but can be made visible by opening the column options icon."
msgid "To plan big counts, select the desired product lines on the :guilabel:`Inventory Adjustments` page. Then, click :guilabel:`Request a Count` and fill in the following information:"
msgid ":guilabel:`Count`: to leave the :guilabel:`On Hand Quantity` of each product line blank, select :guilabel:`Leave Empty`. To prefill the :guilabel:`On Hand Quantity` of each product line with the current value recorded in the database, select :guilabel:`Set Current Value`."
msgid "By default, after an inventory adjustment is applied, the scheduled date for the next count is the 31st of December of the current year. To modify the default scheduled date, go to :menuselection:`Inventory --> Configuration --> Settings --> Operations` and change the date in the :guilabel:`Annual Inventory Day and Month` setting."
msgid "In most companies, the stock is only counted once a year. That's why by default, after making an inventory adjustment in Odoo, the scheduled date for the next count is set on the 31st of December. However, for some businesses it's crucial to have an accurate inventory count at all times."
msgid "In Odoo, cycle counts are location-based. The frequency of the counts is defined by the storage location. To activate storage locations, go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate the :guilabel:`Storage Locations` setting. Next, click :guilabel:`Save` to apply the setting."
msgid "Then, click on a location to open the location settings. Next, click on :guilabel:`Edit`. In the :guilabel:`Inventory Frequency (Days)` field, set the number of days. For example, a location that needs an inventory count every 30 days would set the :guilabel:`Inventory Frequency (Days)` value to `30`. Once the value is entered, click :guilabel:`Save` to apply the setting to the location. Now, once an inventory adjustment is applied to this location, the next scheduled count date will be automatically set based on the number of days in the :guilabel:`Inventory Frequency (Days)` setting."
msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app."
msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales."
msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food."
msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products"
msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault."
msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all."
msgid "In many companies, products have expiration dates and they should be managed based on those dates. In the food industry, for example, tracking and managing product stock based on expiration dates is mandatory to avoid selling expired products to customers."
msgid "To use expiration date tracking, open the *Inventory* application and go to :menuselection:`Configuration --> Settings` and activate the *Lots & Serial Numbers* and *Expiration Dates* features."
msgid "Product Use Time: the number of days before the goods start deteriorating, without being dangerous. This is used to calculate the Best before date on each lot/serial number received."
msgid "Product Life Time: the number of days before the goods may become dangerous and must not be consumed. This is used to calculate the Expiration date on each lot/serial number received."
msgid "Product Removal Time: shows the number of days before the goods should be removed from the stock. This is used to calculate the Removal date on each lot/serial number received."
msgid "Product Alert Time: refers to the number of days before an alert should be raised on the lot/serial number. This is used to calculate the Alert date on each lot/serial number received. Once the Alert date is reached, an Activity is assigned on the relevant lot/serial number to the Responsible user defined on the Product."
msgid "When receiving a product into inventory, the dates will automatically be updated on the corresponding lot/serial number. These updates will be based on the receipt date of the product and the days set on the product form."
msgid "You can access expiration alerts from the *inventory* app. To do so, go to :menuselection:`Master Data --> Lots/Serial Numbers`. There, you can use the pre-existing filter to show all the lots/serial numbers that have exceeded their respective alert dates."
msgid "*Lots* are one of the two ways to identify and track products in Odoo. A lot usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse, but can also pertain to a batch of products manufactured in-house, as well."
msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps to identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their lifecycles."
msgid "Lots are useful for products that are manufactured or received in large quantities (such as clothes or food), and can be used to trace a product back to a group. This is especially useful when managing product recalls or expiration dates."
msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes."
msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be configured to be tracked using lots. To do this, go to the :menuselection:`Inventory app --> Products --> Products`, and choose a product."
msgid "Once on the product form, click :guilabel:`Edit` to make changes to the form. Then, click the :guilabel:`Inventory` tab. In the :guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click :guilabel:`Save` to save changes. Existing or new lot numbers can now be assigned to newly-received or manufactured batches of this product."
msgid "If a product has stock on-hand prior to activating tracking by lots or serial numbers, an inventory adjustment might need to be performed to assign lot numbers to the existing stock."
msgid "New lots can be created for products already in stock with no assigned lot number. To do this, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a separate page where a new :guilabel:`Lot/Serial Number` is generated automatically."
msgid "While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number."
msgid "Once the new :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned."
msgid "This form also provides the option to adjust the :guilabel:`Quantity`, assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and assign this specific lot or serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)."
msgid "After a new lot number has been created, saved, and assigned to the desired product, navigate back to the product form in the :menuselection:`Inventory` app, by going to :menuselection:`Products --> Products`, and selecting the product to which this newly-created lot number was just assigned."
msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new lot number. When additional quantity of this product is received or manufactured, this new lot number can be selected and assigned to it."
msgid "Lot numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form."
msgid "To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form."
msgid "On this :abbr:`RFQ (request for quotation)`, fill out the necessary information by adding a :guilabel:`Vendor`, and adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` (under the :guilabel:`Products` tab)."
msgid "Once the :abbr:`RFQ (request for quotation)` has been filled out, click :guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is confirmed, it becomes a :guilabel:`Purchase Order`, and a :guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form."
msgid "Clicking :guilabel:`Validate` before assigning a lot number to the ordered product quantities will result in a :guilabel:`User Error` pop-up. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a lot number being assigned."
msgid "From here, click the :guilabel:`Additional Options` menu, represented by a :guilabel:`hamburger (four horizontal lines)` icon, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up."
msgid "In this pop-up, configure a number of different fields, including the assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up."
msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity."
msgid "If quantities should be processed in multiple locations and lots, click :guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for additional quantities. Repeat until the :guilabel:`Quantity Done` matches the :guilabel:`Demand`."
msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines."
msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #` assigned, and more."
msgid "On this blank quotation form, fill out the necessary information by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`."
msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, it becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears."
msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up."
msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with the full :guilabel:`Reserved` quantity taken from that specific lot (if there is enough stock in that particular lot)."
msgid "If there is insufficient stock in that lot, or if partial quantities of the :guilabel:`Demand` should be taken from multiple lots, change the quantity in the :guilabel:`Done` column to only include that specific part of the total quantity."
msgid "The lot automatically chosen for delivery orders varies, depending on the selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will also depend on the quantity ordered, and if there is enough quantity in one lot to fulfill the order."
msgid "Then, click :guilabel:`Add a line`, select an additional (different) :guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click the :guilabel:`Validate` button to deliver the products."
msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned."
msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order, if the product quantities shared the same lot number."
msgid "In Odoo, the creation of new lots is only allowed upon **receiving** products from a purchase order, by default. **Existing** lot numbers cannot be used."
msgid "To change the ability to use new (or existing) lot numbers on any operation type, go to the :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`."
msgid "For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes."
msgid "For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. Be sure to click the :guilabel:`Save` button to save all changes."
msgid "For inter-warehouse transfers involving products tracked by lots, it can be useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for warehouse receipts."
msgid "Manufacturers and companies can refer to traceability reports to see the entire lifecycle of a product: where (and when) it came from, where it was stored, and who (and when) it went to."
msgid "To see the full traceability of a product, or group by lots, go to the :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :menuselection:`Lots/Serial Numbers` dashboard."
msgid "From here, products with lot numbers assigned to them will be listed by default, and can be expanded to show the lot numbers those products have assigned to them."
msgid "To group by lots (or serial numbers), begin by removing any filters in the search bar. Then, click the :guilabel:`Group By` drop-down, select :guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from the drop-down menu. Then, click :guilabel:`Apply`."
msgid "*Serial numbers* are one of the two ways to identify and track products in Odoo. A serial number is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items and products."
msgid "Serial numbers can consist of many different types of characters: they can be strictly numerical, they can contain letters and other typographical symbols, or they can be a mix of all of the above."
msgid "The goal of assigning serial numbers to individual products is to make sure that every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services to products that they sell and deliver."
msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes."
msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a desired product to track."
msgid "Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number` option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be selected and assigned to newly-received or manufactured batches of this product."
msgid "If a product doesn't have a serial number assigned to it, a user error pop-up window will appear. The error message states that the product(s) in stock have no lot/serial number. However, a lot/serial number can be assigned to the product by making an inventory adjustment."
msgid "New serial numbers can be created for products already in stock with no assigned serial number. To do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new :guilabel:`Lot/Serial Number` is generated automatically."
msgid "While Odoo automatically generates a new lot/serial number to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number."
msgid "Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned."
msgid "This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)."
msgid "After a new serial number has been created, assigned to the desired product, and saved, navigate back to the product form, by going to :menuselection:`Products --> Products`, and selecting the product that this newly-created serial number was just assigned to."
msgid "Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, lot numbers are assigned directly on the purchase order form. For outgoing goods, lot numbers are assigned directly on the sales order form."
msgid "To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form."
msgid "On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a :guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product`, under the :guilabel:`Products` tab."
msgid "When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert the :abbr:`RFQ (request for quotation)` to a purchase order."
msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned."
msgid "In this pop-up, configure a number of different fields, including the assignation of a serial number (or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up."
msgid "There are three ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet."
msgid "To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed Operations` pop-up, and first choose the location where the product will be stored under the :guilabel:`To` column."
msgid "Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed."
msgid "If a large quantity of products need individual serial numbers assigned to them, Odoo can automatically generate and assign serial numbers to each of the individual products."
msgid "To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations` pop-up window, and type the first serial number in the desired order to be assigned."
msgid "To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all of the serial numbers received from the supplier (or manually chosen upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column."
msgid "For purchase orders that include large quantities of products to receive, the best method of serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial numbers from being reused or duplicated, and improves traceability reporting."
msgid "Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button to close the pop-up. Then, click :guilabel:`Validate`."
msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more."
msgid "Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more."
msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`."
msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears."
msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)."
msgid "To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up."
msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned."
msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order (PO), if any of the product quantities shared a serial number assigned during receipt of that specific :abbr:`PO (purchase order)`."
msgid "By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is true: new serial numbers cannot be created on the delivery order, only existing serial numbers can be used."
msgid "To change the ability to use new (or existing) serial numbers on any operation type, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`."
msgid "For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes."
msgid "For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes."
msgid "Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a product: where it came from (and when), where it was stored, and who it went to."
msgid "To see the full traceability of a product, or group by serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard."
msgid "From here, products with serial numbers assigned to them will be listed by default, and can be expanded to show what serial numbers have been specifically assigned to them."
msgid "To group by serial numbers (or lots), first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`."
msgid "Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of products with that assigned number. For unique serial numbers that are not reused, there should be just one product per serial number."
msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number."
msgid "Batch picking allows a single picker to handle a batch of orders, reducing the number of times he must visit the same location. In Odoo, it means you can regroup several transfers into the same batch transfer, then process it, either via the barcode application or in the form view."
msgid "Now, determine the batch transfer responsible and the type of transfers you want to include in the batch. To add the types of transfers, click on *Add a line*."
msgid "In the example below, a filter was applied to only see the transfers that are in the *Pick* step. After that, the different transfers that needed to be included in the batch transfer were selected."
msgid "To see the products to pick for the different transfers, click on *Select*. If *Multi-locations* has been activated, the document also shows the locations they have been reserved from."
msgid "While gathering the products, you can edit the batch transfer and update the *Quantity done* for each product. Once everything has been picked, select *Validate* so the different transfers contained in the batch are validated too."
msgid "In the batch transfer, products are classified per location. The source document is visible on each line and a color-code helps differentiate them."
msgid "Most of the time, products stored in a company's warehouse are either purchased from suppliers, or are manufactured in-house. However, suppliers will sometimes let companies store and sell products in the company's warehouse, without having to buy those items up-front. This is called *consignment*."
msgid "Consignment is a useful method for suppliers to launch new products, and easily deliver to their customers. It's also a great way for the company storing the products (the consignee) to earn something back for their efforts. Consignees can even charge a fee for the convenience of storing products they don't actually own."
msgid "To receive, store, and sell consignment stock, the feature needs to be enabled in the settings. To do this, go to :menuselection:`Inventory --> Configuration --> Settings`, and under the :guilabel:`Traceability` section, check the box next to :guilabel:`Consignment`, and then click :guilabel:`Save` to finish."
msgid "With the feature enabled in Odoo, consignment stock can now be received into a warehouse. From the main :menuselection:`Inventory` dashboard, click into the :guilabel:`Receipts` section. Then, click :guilabel:`Create`."
msgid "Consignment stock is not actually purchased from the vendor; it is simply received and stored. Because of this, there are no quotations or purchase orders involved in receiving consignment stock. So, *every* receipt of consignment stock will start by creating manual receipts."
msgid "Choose a vendor to enter in the :guilabel:`Receive From` field, and then choose the same vendor to enter in the :guilabel:`Assign Owner` field."
msgid "Since the products received from the vendor will be owned by the same vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields must match."
msgid "Once the vendor-related fields are set, enter products into the :guilabel:`Product` lines, and set the quantities to be received into the warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be changed, as well. Once all the consignment stock has been received, :guilabel:`Validate` the receipt."
msgid "Once consignment stock has been received into the warehouse, it can be sold the same as any other in-stock product that has the :guilabel:`Can Be Sold` option enabled on the product form."
msgid "To create a sales order, navigate to the :menuselection:`Sales` app, and from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, choose a customer to enter into the :guilabel:`Customer` field."
msgid "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` that supplied the consignment stock received (and stored) in the warehouse."
msgid "Add the consignment product under the :guilabel:`Product` column in the order lines, set the :guilabel:`Quantity`, and fill out any other pertinent product details on the form. Once the quotation is complete, click :guilabel:`Confirm`."
msgid "Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will become a sales order. From here, the products can be delivered by clicking on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate` to validate the delivery."
msgid "Although consignment stock is owned by the vendor who supplied it, and not by the company storing it in their warehouse, consignment products will *still* appear in certain inventory reports."
msgid "Since the consignee does not actually own consigment stock, these products are *not* reflected in the :guilabel:`Stock Valuation` report, and have no impact on the consignee's inventory valuation."
msgid "To view all information about on-hand stock moves, navigate to the the :guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory --> Reporting --> Product Moves`. For consignment products, the information in this report is the same as any other product: the history of its product moves can be reviewed; the :guilabel:`Quantity Done` and :guilabel:`Reference` document are available; and its :guilabel:`Locations` are available, as well. The consignment stock will originate from :guilabel:`Partner Location/Vendors`."
msgid "To view a consignment product's moves by ownership, select the :guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to finish."
msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consigment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place."
msgid "While a batch transfer is a group of several pickings, a **wave transfer** only contains some parts of different pickings. Both methods are used to pick orders in a warehouse, and depending on the situation, one method may be a better fit than the other."
msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings`. In the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and :guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the settings."
msgid "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, first go to the :guilabel:`Inventory` dashboard and locate the desired operation type's card. Then, open the options menu (the three dots icon in the corner of the operation type's card) and click :guilabel:`Operations`."
msgid "To add the selected lines to an existing wave transfer, select the :guilabel:`an existing wave transfer` option and select the existing wave transfer from the drop-down menu."
msgid "To create a new wave transfer, select the :guilabel:`a new wave transfer` option. If creating a new wave transfer, an employee can also be set in the optional :guilabel:`Responsible` field. Once the desired options are selected, click :guilabel:`Confirm` to add the product lines to a wave."
msgid "To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers can also be viewed in the :guilabel:`Barcode` app by going to :menuselection:`Barcode --> Batch Transfers`."
msgid "Providing the best possible service to customers is vital for business. It implies planning every move: manufacturing orders, deliveries, receptions, and so on. To do so, you need to configure lead time properly and coordinate scheduled dates."
msgid "By using lead times, Odoo provides end dates, the **Commitment Date**, for each process. On a sales order, for example, this is the date your customer will get the products he ordered."
msgid "From the customers’ side, the commitment date is important because it gives them an estimation of when they will receive their products. The dates take all other lead times, such as manufacturing, delivery, or suppliers, into account."
msgid "As said above, there are several types of lead times. Each is calculated based on various indicators. Before going through the configuration, here is a brief summary of how lead times are calculated and what they are:"
msgid "**Customer Lead Time**: the customer lead time is the default duration you set. Therefore, the expected date on the sales orders is today + customer lead time."
msgid "**Sales Security Lead Time**: the purpose is to be ready shipping that many days before the actual commitment taken with the customer. Then, the default scheduled date on the delivery order is **SO delivery date - Security Lead Time**."
msgid "**Purchase Security Lead Time**: margin of error for vendor lead times. When the system generates Purchase Orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays."
msgid "**Purchase Delivery Lead Time**: this is the expected time between a PO being confirmed and the receipt of the ordered products. The **Receipt scheduled date - Vendor delivery date** is the default *PO Order By* date."
msgid "**Days to Purchase**: number of days the purchasing department takes to validate a PO. If another RFQ to the same vendor is already opened, Odoo adds the line to the RFQ instead of creating a new one. Then, the specific date is set on the line."
msgid "**Manufacturing Lead Time**: this is the expected time it takes to manufacture a product. This lead time is independent of the quantity to produce and does not take the routing time into account."
msgid "**Manufacturing Security Lead Time**: additional time to mitigate the risk of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead Time** is the default *Manufacturing Order* planned date."
msgid "In the *Sales* app, there is an option called *Delivery Date*. It allows seeing an additional field on the sales orders, *Expected Date*. This one is automatically computed based on the different lead times previously configured."
msgid "The *Customer Lead Time* is the time needed for your product to go from your warehouse to the customer place. It can be configured on any product by going to :menuselection:`Sales --> Products --> Products`. There, open your product form, go in the inventory tab, and add your *Customer Lead Time*."
msgid "For example, product B is ordered on the 2nd of April but the *Customer Lead Time* is two days. In that case, the expected delivery date is the 4th of April."
msgid "In sales, *Security Lead Time* corresponds to backup days to ensure you are able to deliver the products in time. The purpose is to be ready shipping earlier in order to arrive on time."
msgid "For example, product B is scheduled to be delivered on the 6th of April but the *Security Lead Time* is one day. In that case, the scheduled date for the delivery order is the 5th of April."
msgid "In many cases, customers order several products at the same time. Those can have different lead times but still need to be delivered, at once or separately. Fortunately, Odoo can help you handle these cases easily."
msgid "From the *Other Info* tab of your *Sale Order*, you can choose between *When all products are ready* and *As soon as possible*. The first one is to deliver products at once, while the second is to deliver them separately."
msgid "For example, products A and B are ordered at the same time. A has 8 lead days and B has 5. With the first option, the *Expected Date* is calculated based on the product with the most lead days, here A. If the order is confirmed on the 2nd of April, then the *Expected Date* is on the 10th of April."
msgid "With the second option, the *Expected Date* is calculated based on the product with the least customer lead days. In this example, B is the product with the least lead days. So, the *Expected Date* is on the 7th of April."
msgid "The *Supplier Lead Time* is the time needed for a product you purchased to be delivered. To configure it, open a product from :menuselection:`Purchase --> Products --> Products` and add a vendor under the *Purchase* tab."
msgid "By clicking on *Add a line*, a new window is displayed. You can specify the *Delivery Lead Time* there. If done so, the delivery day for every purchase of that product is now equal to *Date of the Purchase Order + Delivery Lead Time*."
msgid "The *Security Lead Time* for purchase follows the same logic as the one for *Sales*, except that you are the customer. Then, it is the margin of error for your supplier to deliver your order."
msgid "The *Manufacturing Lead Time* is the time needed to manufacture the product. To specify it, open the *Inventory* tab of your product form and add the number of days the manufacturing takes."
msgid "When working with *Manufacturing Lead Times*, the *Deadline Start* of the *MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s deadline start date for an order having a commitment date on the 10th of July is June 27th."
msgid "For example, a customer orders B with a delivery date scheduled on the 20th of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead Time* is 3 days, so the manufacturing of B needs to start at the latest on the 3rd of June, which is the MO’s planned date."
msgid "Let’s say that a customer orders B on the 1st of September and the delivery date is planned to be within 20 days (September 20th). In such a scenario, here is when all the various steps are triggered."
msgid "**September 14th**: the deadline start date for the manufacturing (19th - 3 days of manufacturing lead time - 2 days of security lead time for Manufacturing)"
msgid "In Odoo, there are two strategies for replenishing inventory: **Reordering Rules** and the **Make to Order (MTO)** route. Although these strategies differ slightly, they both have similar consequences: triggering the automatic creation of a purchase or manufacturing order. The choice of which strategy to use depends on the business's manufacturing and delivery processes."
msgid "Reordering rules are used to ensure that there's always a minimum amount of a product in stock in order to manufacture products and/or fulfill sales orders. When the stock level of a product reaches its minimum, Odoo automatically generates a purchase order with the quantity needed to reach the maximum stock level."
msgid "Make to Order (MTO) is a procurement route that creates a draft purchase order or manufacturing order each time a sales order is confirmed, *regardless of the current stock level*."
msgid "Unlike products replenished using reordering rules, Odoo automatically links the sales order to the purchase order (PO) or manufacturing order (MO) generated by the MTO route. Another difference between reordering rules and MTO is with MTO, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` immediately after the sales order is confirmed. With reordering rules, Odoo generates a draft :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` when the product's forecasted stock falls below the set minimum quantity. In addition, Odoo will automatically add quantities to the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` as the forecast changes, as long as the :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` is not confirmed."
msgid "To access the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`. By default, the replenishment report shows every product that needs to be manually reordered. If there is no specific rule for a product, Odoo assumes that the :guilabel:`Minimum Quantity` and :guilabel:`Maximum Quantity` stock are both `0.00`."
msgid "For products that don't have a set reordering rule, Odoo calculates the forecast as sales orders, deliveries, and receipts are confirmed. For products that have a set reordering rule, Odoo calculates the forecast normally, but also takes into account the purchase/manufacturing lead time and security lead time."
msgid "Before creating a new reordering rule, make sure the product has a vendor or a bill of materials configured on the product form. Also, make sure the :guilabel:`Product Type` is set to `Storable Product` on the product form. By definition, a consumable product does not have its inventory levels tracked, so Odoo can not account for a consumable product in the stock valuation."
msgid "To create a new reordering rule from the replenishment report, go to :menuselection:`Inventory --> Operations --> Replenishment`, click :guilabel:`Create`, and set the :guilabel:`Product`. If desired, set a :guilabel:`Min Quantity` and a :guilabel:`Max Quantity`. Finally, click :guilabel:`Save`."
msgid "To create a new reordering rule from the product form, go to :menuselection:`Inventory --> Products --> Products`, select a product to open its product form, click the :guilabel:`Reordering Rules` smart button, and click :guilabel:`Create`. Then, fill out the fields and save the new reordering rule."
msgid "By default, the quantity in the :guilabel:`To Order` field is the quantity required to reach the set :guilabel:`Max Quantity`. However, the :guilabel:`To Order` quantity can be adjusted by clicking on the field, changing the value, and clicking :guilabel:`Save`. To replenish a product manually, click :guilabel:`Order Once`."
msgid "To automate replenishment, click :guilabel:`Automate Orders`. When this button is clicked, Odoo will automatically generate a draft :abbr:`PO (Purchase Order)`/:abbr:`MO (Manufacturing Order)` every time the forecasted stock level falls below the set :guilabel:`Min Quantity` of the reordering rule."
msgid "A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by a manual replenishment will have `Replenishment Report` as the source document. A :abbr:`PO (Purchase Order)` or :abbr:`MO (Manufacturing Order)` created by an automated reordering rule will have the sales order(s) reference number(s) that triggered the rule as the source document."
msgid "Activating the :guilabel:`Multi-Step Routes` setting also activates :guilabel:`Storage Locations` setting. If these features aren't applicable to the warehouse, disable these settings after unarchiving the MTO route."
msgid "To set a product's procurement route to MTO, go to :menuselection:`Inventory --> Products --> Products`, click on a product to open the product form, and click :guilabel:`Edit`. Then, click on the :guilabel:`Inventory` tab and in the :guilabel:`Routes` options, select :guilabel:`Replenish on Order (MTO)`. For products purchased directly from a vendor, make sure the :guilabel:`Buy` route is selected in addition to the MTO route and a vendor is configured in the :guilabel:`Purchase` tab. For products manufactured in-house, make sure the :guilabel:`Manufacture` route is selected in addition to the MTO route and a bill of materials is configured for the product. Finally, click :guilabel:`Save`."
msgid "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, so 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."
msgid "To use different units of measure in Odoo, first go to :menuselection:`Inventory --> Configuration --> Settings --> Products` and activate the :guilabel:`Units of Measure` setting. Then, click :guilabel:`Save`."
msgid "After enabling the units of measure setting, view the default units of measure categories in :menuselection:`Inventory --> Configuration --> Units of Measures --> UoM Categories`. The category is important for unit conversion, Odoo can only convert a product's units from one unit to another only if both units belong to the same category."
msgid "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."
msgid "To create a new unit, first select the correct category. For example, to sell a product in a box of six units, click on the :guilabel:`Unit` category line. Next, click :guilabel:`Edit`. After that, click :guilabel:`Add a line`. Then, in the :guilabel:`Unit of Measure` field, title the new unit `Box of 6`. In the :guilabel:`Type` field, select :guilabel:`Bigger than the reference Unit of Measure`. In the :guilabel:`Ratio` field, enter `6.00000` since a box of six is six times bigger than the reference unit (`1.00000`). Finally, click :guilabel:`Save`."
msgid "Click :guilabel:`Add a line`. As an example, we will create a Box of 6 units that we will use for the Egg product. The box of 6 is 6 times bigger than the reference unit of measure for the category which is “Units” here."
msgid "To set units of measure on a product, first go to :menuselection:`Inventory --> Products --> Products` and click on a product to open its settings. Then, click on :guilabel:`Edit`."
msgid "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 will also be 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."
msgid "When creating a new request for quotation (RFQ) in the Purchase app, Odoo automatically uses the product's specified purchase unit of measure. However, if needed, the :guilabel:`UoM` can be manually edited on the RFQ."
msgid "After the RFQ is confirmed into a purchase order (PO), click on the :guilabel:`Receipt` smart button at the top right corner 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."
msgid "For example, if the product's purchase 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 delivery receipt shows the quantity in units."
msgid "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 here if needed. Then, click :guilabel:`Confirm` to create the RFQ."
msgid "Next, click the :guilabel:`Units Forecasted` smart button on the product form and scroll down to :menuselection:`Forecasted Inventory --> Requests for quotation`. Click on the RFQ reference number to open the draft RFQ. The purchase UoM can also be edited here if needed."
msgid "When creating a new quotation in the Sales app, Odoo automatically uses the product's specified unit of measure. However, if needed, the :guilabel:`UoM` can be manually edited on the quotation."
msgid "After the quotation is sent to the customer and confirmed into a sales order (SO), click on the :guilabel:`Delivery` smart button at the top right corner 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."
msgid "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."
msgid "Units of measure specify the unit used to handle a product. In Odoo, you have the possibility to specify the unit of measure in which you manage your stock and the one which is used when purchasing the product to your supplier."
msgid "Once a product has a :guilabel:`Unit of Measure` and a :guilabel:`Purchase UoM` set on the product form, Odoo can automatically convert the different units in the product's purchase/sales orders and the orders' respective delivery orders/receipts. The only condition is that all the units have to be in the *same category* (Unit, Weight, Volume, Length, etc.)."
msgid "For example, a product can have its :guilabel:`Unit of Measure` set to `feet (ft)` and its :guilabel:`Purchase UoM` set to `centimeters (cm)`. When a purchase order (PO) is created for that product, it will list the quantity in centimeters. Then, when the PO is confirmed, Odoo automatically generates a receipt and converts the centimeters to feet. The receipt will list the quantity in feet."
msgid "A package refers to the physical container that holds one or several products from a picking. For example, when a product is ready for delivery, its quantities can be separated into two different packages. In Odoo, the quantity of products in each package can be recorded in the database. Make sure the :guilabel:`Packages` option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Operations`."
msgid "On a delivery order, separate the products into different packages by setting the :guilabel:`Done` quantity to the desired quantity in the first package. Then, click :guilabel:`Put in Pack` to record the first package. Repeat for each package."
msgid "Packaging refers to a standard container that holds several unit of a product. For example, cans of soda can be in a 6-pack, 15-pack, or even a pallet for the packaging."
msgid "In Odoo, packagings are used for indicative purposes on sales/purchase orders and inventory transfers. The main difference between packagings and units of measure is that packagings are defined at the product level while UoMs are generic."
msgid "Packaging is also useful during product reception. When scanning the barcode of the packaging, Odoo automatically adds the number of units contained in the packing on the picking."
msgid "The landed cost feature in Odoo allows the user to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product."
msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also gives the option to set a :guilabel:`Default Journal` in which the landed costs accounting entries will be recorded."
msgid "After a vendor fulfills a purchase order and sends a bill, click :guilabel:`Create Bill` on the purchase order to create a vendor bill in Odoo. If the vendor bill includes landed costs, such as custom duties, tick the box in the :guilabel:`Landed Costs` column on the vendor bill invoice line."
msgid "For charges that are always landed costs, create a landed cost product in Odoo. That way, the landed cost product can be quickly added to the vendor bill as an invoice line instead of manually entering the landed cost information every time a vendor bill comes in."
msgid "First, create a new product in :menuselection:`Inventory --> Products --> Products --> Create`. Next, name the landed cost product. Then, set the :guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must always be a service product type. After that, go to the :guilabel:`Purchase` tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click :guilabel:`Save` to finish creating the landed cost product."
msgid "Once the landed cost is added to the vendor bill (either by checking the :guilabel:`Landed Cost` option on the invoice line or adding a landed cost product to the bill), click the :guilabel:`Create Landed Costs` button at the top of the bill. Odoo automatically creates a landed cost record with the set landed cost pre-filled in the :guilabel:`Additional Costs` product lines. From here, decide which picking the additional costs apply to by clicking :guilabel:`Edit` and selecting the picking reference number from the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`."
msgid "After setting the picking, click :guilabel:`Compute` on the landed cost record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. Finally, click :guilabel:`Validate` to post the landed cost entry to the accounting journal."
msgid "The product that the landed cost is applied to must have a product category set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average Costing)` method."
msgid "Landed cost records can also be directly created in :menuselection:`Inventory --> Operations --> Landed Costs`, it is not necessary to create a landed cost record from the vendor bill."
msgid "All of a company's stock on-hand contributes to the valuation of its inventory. That value should be reflected in the company's accounting records to accurately show the value of the company and all of its assets."
msgid "By default, Odoo uses a periodic inventory valuation (also known as manual inventory valuation). This method implies that the accounting team posts journal entries based on the physical inventory of the company, and that warehouse employees take the time to count the stock. In Odoo, this method is reflected inside each product category, where the :guilabel:`Costing Method` field will be set to `Standard Price` by default, and the :guilabel:`Inventory Valuation` field will be set to `Manual`."
msgid "Alternatively, automated inventory valuation is an integrated valuation method that updates the inventory value in real-time by creating journal entries whenever there are stock moves initiated between locations in a company's inventory."
msgid "Automated inventory valuation is a method recommended for expert accountants, given the extra steps involved in journal entry configuration. Even after the initial setup, the method will need to be periodically checked to ensure accuracy, and adjustments may be needed on an ongoing basis depending on the needs and priorities of the business."
msgid "Verify the accounting mode by activating the :ref:`developer-mode` and navigating to :menuselection:`Accounting --> Configuration --> Settings`."
msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means that the cost of a good is only recorded as an expense when a customer is invoiced for a product. *Interim Stock Accounts* are used for the input and output accounts, and are both *Asset Accounts* in the balance sheet."
msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Additionally, a single *Expense* account is used for both input and output accounts in the balance sheet."
msgid "**Standard Price**: is the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form."
msgid "**Average Cost (AVCO)**: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products."
msgid "**First In First Out (FIFO)**: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it's highly sensitive to input data and human error."
msgid "Changing the costing method greatly impacts inventory valuation. It's highly recommended to consult an accountant first before making any adjustments here."
msgid "Make changes to inventory valuation options by navigating to :menuselection:`Inventory --> Configuration --> Product Categories`, and choose the category/categories where the automated valuation method should apply."
msgid "Under the :guilabel:`Inventory Valuation` heading are two labels: :guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the desired :guilabel:`Costing Method` using the drop-down menu (e.g. :guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to :guilabel:`Automated`."
msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, the numerical value in the :guilabel:`Cost` field for products in the respective product category will no longer be editable, and will appear grayed out. The :guilabel:`Cost` amount will instead automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders."
msgid "On the same screen, the :guilabel:`Account Stock Properties` fields will appear, as they are now required fields given the change to automated inventory valuation. These accounts are defined as follows:"
msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products."
msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product."
msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product."
msgid "To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`. At the top of the dashboard, change the :guilabel:`As of` field value to :guilabel:`Today`, and adjust the filtering :guilabel:`Options` to :guilabel:`Unfold All` in order to see all of the latest data displayed, all at once."
msgid "Under the parent :guilabel:`Current Assets` line item, look for the nested :guilabel:`Stock Valuation Account` line item, where the total valuation of all of the inventory on hand is displayed."
msgid "Access more specific information with the :guilabel:`Stock Valuation Account` drop-down menu, by selecting either the :guilabel:`General Ledger` to see an itemized view of all of the journal entries, or by selecting :guilabel:`Journal Items` to review all of the individualized journal entries that were submitted to the account. As well, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`."
msgid "*Inventory valuation* is a quintessential accounting procedure that calculates the value of on-hand stock. Once determined, the inventory valuation amount is then incorporated into a company's overall value."
msgid "In Odoo, this process can be conducted manually— by warehouse employees physically counting the products— or automatically through the database."
msgid "In order to understand how moving products in and out of stock affects the company's overall value, consider the following product and stock moves scenario below."
msgid "For example, consider an physical product, a simple *table*, which is categorized as `Office Furniture` in the product form's :guilabel:`Product Category` field."
msgid "Navigate to the the product category itself by going to :menuselection:`Inventory app --> Configuration --> Product Categories`, and on the form, set the :guilabel:`Costing Method` as `First In First Out (FIFO)` and the :guilabel:`Inventory Valuation` field as `Automated`."
msgid "Alternatively access the :guilabel:`Product Categories` dashboard by clicking on the :guilabel:`internal link` arrow on the individual product's form, by hovering over the :guilabel:`Product Category` field."
msgid "Next, assume 10 tables are purchased at a price of $10.00, each. The :abbr:`PO (Purchase Order)` for those tables will show the subtotal of the purchase as $100, plus any additional costs or taxes."
msgid "After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, use the :guilabel:`Valuation` smart button to view how the value of inventory was impacted."
msgid "The :doc:`consignment </applications/inventory_and_mrp/inventory/management/misc/owned_stock>` feature allows ownership to items in stock. Thus, products owned by other companies are not accounted for in the host company's inventory valuation."
msgid "The :guilabel:`Stock Valuation` dashboard then displays valuation of all products in the shipment, along with their quantities and valuation. In the example of 10 tables being purchased, the :guilabel:`Total Value` column of the dashboard would display a calculated valuation of $100."
msgid "In Odoo, automatic inventory valuation records are also recorded in the *Accounting* app. To access these accounting entries, navigate to :menuselection:`Accounting --> Journal Entries`, and look for inventory valuation entries with the `STJ` prefix in the :guilabel:`Journal` and :guilabel:`Number` columns, respectively."
msgid "In the same logic, when a table is shipped to a customer and leaves the warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock valuation record as it does on a :abbr:`PO (Purchase Order)`"
msgid "To view the current value of all products in the warehouse, go to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`. The records in the table are organized by product, and selecting a product's drop-down menu displays detailed records with the :guilabel:`Date`, :guilabel:`Quantity`, and :guilabel:`Total Value` of the inventory."
msgid "The :guilabel:`Inventory At Date` button, located in the top-left corner of the :guilabel:`Stock Valuation` dashboard, shows the inventory valuation of products available during a prior specified date."
msgid "For any company: lead times, supply chain failures, and other risk factors can contribute to invisible costs. Although Odoo attempts to accurately represent the stock value, *manual valuation* serves as an additional tool to update the unit price of products."
msgid "Manual valuation is intended for products that can be purchased and received for a cost greater than 0, or have product categories set with :guilabel:`Costing Method` set as either `Average Cost (AVCO)` or `First In First Out (FIFO)`."
msgid "Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard by first navigating to :menuselection:`Inventory app --> Reporting --> Inventory Valuation`, and then click the little gray drop-down icon to the left of a product's name, to then reveal stock valuation line items below as well as a teal :guilabel:`+ (plus)` button on the right."
msgid "Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product Revaluation` form, where updates to the calculation of inventory valuation can be made, by increasing or decreasing the unit price of each product."
msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps."
msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products."
msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location."
msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location."
msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies."
msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse."
msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped."
msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy."
msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)."
msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock."
msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping."
msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy."
msgid "Some companies process large amounts of deliveries every day, many of which include multiple products or require special packaging. To make this efficient, a packing step is needed before shipping out products. For this, Odoo has a three step process for delivering goods."
msgid "In the default three-step delivery process, products that are part of a delivery order are picked in the warehouse according to their removal strategy, and brought to a packing zone. After the items have been packed into the different shipments in the packing zone, they are brought to an output location before being shipped. These steps can be modified if they do not fit the needs of the business."
msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step <inventory/receipts_delivery_one_step>`, so the settings need to be changed in order to utilize three step deliveries. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*."
msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes."
msgid "Activating three-step receipts and deliveries will create two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`."
msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`."
msgid "A :guilabel:`Delivery` smart button will appear in the top right. Clicking on it will show the picking order, packing order, and the delivery order, which are all associated with the sales order."
msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`."
msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be packed. The status of the packing order and delivery order will both be :guilabel:`Waiting Another Operation`, since the packing and delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` when the packing has been marked :guilabel:`Done`."
msgid "The receipt can also be found in the *Inventory* application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Pick` kanban card."
msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`. Then the packing order will be ready. Since the documents are linked, the products which have been previously picked are automatically reserved on the packing order."
msgid "The packing order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Pack` kanban card."
msgid "Once the packing order is validated, the product leaves the :guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` location. Then, the status of the document will change to :guilabel:`Done`."
msgid "The delivery order will be ready to be processed once the packing is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Delivery Orders` kanban card."
msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`."
msgid "By default, incoming shipments are configured to be received directly into stock, and outgoing shipments are configured to be delivered directly from stock to the customer; the default setting for warehouses in Odoo is one step receipts and deliveries."
msgid "Incoming and outgoing shipments do not need to be configured with the same steps. For example, products can be received in one step, but shipped in three steps."
msgid "Begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, click on the desired warehouse, and click :guilabel:`Edit`. Next, on the :guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` section, select :guilabel:`Receive goods directly (1 step)` for :guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 step)` for :guilabel:`Outgoing Shipments`, and :guilabel:`Save` the changes to finish."
msgid "On the main :menuselection:`Purchase` application dashboard, start by making a new quote by clicking :guilabel:`Create`. Then, select (or create) a :guilabel:`Vendor` from the drop-down field, add a storable :guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` to finalize the quote as a new purchase order."
msgid "A :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (purchase order)` form — click it to reveal the associated receipt for the purchase order."
msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card."
msgid "If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ (bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon enables the :guilabel:`Detailed Operations` screen to pop-up. This allows the location(s) to be specified for the received product(s)."
msgid "Once the receipt is validated, the product leaves the :guilabel:`Supplier Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives here, it will be available for manufacturing, sales, etc. Then, the status of the document will change to :guilabel:`Done`, thus completing the reception process in one step."
msgid "Start my navigating to the main :menuselection:`Sales` app dashboard, and make a new quote by clicking :guilabel:`Create`. Then select (or create) a :guilabel:`Customer` from the drop-down field, add a storable :guilabel:`Product` that is in stock to the order lines, and click :guilabel:`Confirm` to finalize the quotation as a sales order."
msgid "A :guilabel:`Delivery` smart button will appear in the top-right corner of the :abbr:`SO (Sales Order)` form — click it to reveal the associated delivery order for the sales order."
msgid "Delivery orders can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Delivery Orders` kanban card."
msgid "Once the picking order is validated, the product leaves the :guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers location`. Then, the status of the document will change to :guilabel:`Done`, thus completing delivery in one step."
msgid "Depending on a company's business processes, multiple steps may be needed before receiving or shipping products. In the two-step receipt process, products are received in an input area, then transferred to stock. Two-step receipts work best when various storage locations are being used, such as locked or secured areas, freezers and refrigerators, or various shelves."
msgid "Products can be sorted according to where they are going to be stored, and employees can stock all the products going to a specific location. The products are not available for further processing until they are transferred into stock."
msgid "In the two-step delivery process, products that are part of a delivery order are picked from the warehouse according to their removal strategy, and brought to an output location before being shipped."
msgid "One situation where this would be useful is when using either a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy, where the products that are being picked need to be selected based on their receipt date or expiration date."
msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step <inventory/receipts_delivery_one_step>`, so the settings need to be changed in order to utilize two-step receipts and deliveries. Incoming and outgoing shipments do not need to be set to have the same steps. For example, products can be received in two steps, but shipped in one step. In the following example, two steps will be used for both receipts and deliveries."
msgid "First, make sure the :guilabel:`Multi-Step Routes` option is enabled in :menuselection:`Inventory --> Configuration --> Settings`, under the ::guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` the changes."
msgid "Next, the warehouse needs to be configured for two-step receipts and deliveries. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to change the warehouse settings."
msgid "Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and then deliver (2 steps)` for :guilabel:`Outgoing Shipments`. :guilabel:`Save` the changes to finish."
msgid "Activating two-step receipts and deliveries will create new *input* and *output* locations, which by default, are labeled :guilabel:`WH/Input` and :guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard. To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, and then click :guilabel:`Edit`. On the location form, update the ::guilabel:`Location Name`, make any other changes (if necessary) and :guilabel:`Save` the changes."
msgid "For businesses with multiple warehouses that have different step configurations, the :guilabel:`Deliver To` field on the ::abbr:`PO (Purchase Order)` form may need to be specifed as the correct *input location* connected to the two-step warehouse, which can be done by selecting the warehouse from the drop-down selection that includes the `Receipts` label at the end of the name."
msgid "After confirming the ::abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (Purchase Order)` form — click it to reveal the associated receipt."
msgid "The receipt and internal transfer will be created once the purchase order is confirmed. The status of the receipt will be :guilabel:`Ready`, since the receipt must be processed first. The status of the internal transfer will be :guilabel:`Waiting Another Operation`, since the transfer cannot happen until the receipt is completed. The status of the internal transfer will only change to :guilabel:`Ready` once the receipt has been marked as :guilabel:`Done`."
msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`."
msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product into stock. Navigate to the :menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Internal Transfers` kanban card."
msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders."
msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select (or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`."
msgid "After confirming the ::abbr:`SO (Sales Order)`, a :guilabel:`Receipt` smart button will appear in the top-right corner of the :abbr:`PO (Sales Order)` form — click it to reveal the associated receipt."
msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` kanban card."
msgid "The picking and delivery order will be created once the sales order is confirmed. When the :guilabel:`Delivery` smart button appears, click it to arrive to the :guilabel:`Transfers` dashboard, which lists both the picking and the delivery orders."
msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another Operation`, since the delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` once the picking has been marked as :guilabel:`Done`."
msgid "Click on the picking delivery order to begin processing it. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the delivery order will be ready for processing. Since the documents are linked, the products which have been previously picked are automatically reserved on the delivery order."
msgid "The delivery order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application, on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kanban card to begin."
msgid "The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by clicking on the ::guilabel:`Delivery` smart button again, and choosing the delivery order on the ::guilabel:`Transfers` page (which should now be marked as ::guilabel:`Ready`)."
msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`."
msgid "Some companies require a quality control process before receiving goods from suppliers. To accomplish this, Odoo has a three-step process for receiving goods."
msgid "In the three-step receipt process, products are received in an input area, then transferred to a quality area for inspection. Products that pass the quality inspection are then transferred into stock. The products are not available for further processing until they are transferred out of the quality area and into stock."
msgid "Odoo is configured by default to :ref:`receive and deliver goods in one step <inventory/receipts_delivery_one_step>`, so the settings need to be changed in order to utilize three-step receipts. First, make sure the *Multi-Step Routes* option is enabled in :menuselection:`Inventory --> Configuration --> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes` will also activate *Storage Locations*."
msgid "Next, the warehouse needs to be configured for three-step receipts. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes."
msgid "Activating three-step receipts and deliveries will create two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`."
msgid "In the :menuselection:`Purchase` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`."
msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order."
msgid "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`."
msgid "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed."
msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`."
msgid "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card."
msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`."
msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card."
msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders."
msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card."
msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders."
msgid "A *warehouse* is a physical building or space where items are stored. In Odoo, it is possible to set up multiple warehouses and transfer stored items between them."
msgid "By default, the Odoo platform has one warehouse that is already configured, with the address set as the company's address. To create a second warehouse, select :menuselection:`Configuration --> Warehouses`, then click :guilabel:`Create` and configure the form as follows:"
msgid ":guilabel:`Company`: the company that owns the warehouse; this can be set as the company that owns the Odoo database or the company of a customer or vendor"
msgid "The options below will only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Configuration --> Settings` under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules <use-routes>`."
msgid "Creating a second warehouse will automatically enable the *Storage Locations* setting, which allows location tracking of products within a warehouse. To toggle this setting, navigate to :menuselection:`Configuration --> Settings` and click the checkbox under the :guilabel:`Warehouse` heading."
msgid "If a new warehouse is created that has existing inventory in it, the inventory counts should be added to Odoo so that the stock listed in the Odoo database reflects what is in the physical warehouse. To add inventory to a new warehouse, navigate to :menuselection:`Inventory --> Operations --> Inventory Adjustments`, and then click :guilabel:`Create`. The inventory adjustment form can then be filled out as follows:"
msgid ":guilabel:`Locations`: the location(s) where the inventory is stored; include the new warehouse and any locations within it that inventory will be added to"
msgid ":guilabel:`Include Exhausted Products`: include products with a quantity of zero; does not affect inventory adjustments for new warehouses since they have no existing inventory"
msgid ":guilabel:`Counted Quantities`: choose whether the counted quantities for products being added should default to stock on hand or zero; does not affect inventory adjustments for new warehouses since they have no existing inventory"
msgid "Once the form is properly configured, click on :guilabel:`Start Inventory` to be taken to the next page where products can be added to the inventory adjustment. Add a new product by clicking on :guilabel:`Create` and then fill out the product line as follows:"
msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse; this can be set as the overall warehouse or a location within the warehouse"
msgid ":guilabel:`On Hand`: the total quantity of the product stored in the location for which inventory is being adjusted; this should be zero for a new location or warehouse"
msgid ":guilabel:`Difference`: the difference between the *On Hand* and *Counted* values; this will automatically update to reflect the value entered in the :guilabel:`Counted` column"
msgid "After adding all the products already stored in the new warehouse, click :guilabel:`Validate Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will update to reflect those in the :guilabel:`Counted` column and the products added will appear in the inventory of the new warehouse."
msgid "A common use case for multiple warehouses is to have one central warehouse that resupplies multiple shops, and in this case, each shop is considered a local warehouse. When a shop wants to replenish a product, the product is ordered to the central warehouse. Odoo allows the user to easily set which warehouse(s) can resupply another warehouse."
msgid "To resupply from another warehouse, first go to :menuselection:`Inventory --> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-Step Routes`. Then, click :guilabel:`Save` to apply the setting."
msgid "Create a new warehouse by clicking :guilabel:`Create`. Then, give the warehouse a name and a :guilabel:`Short Name`. Finally, click :guilabel:`Save` to finish creating the warehouse."
msgid "After that, go back to the :guilabel:`Warehouses` page and open the warehouse that will be resupplied by the second warehouse. Then, click :guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the :guilabel:`Resupply From` field, and check the box next to the second warehouse's name. If the warehouse can be resupplied by more than one warehouse, make sure to check those warehouses' boxes too. Finally, click :guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can resupply this warehouse."
msgid "After configuring which warehouse(s) to resupply from, a new route is now available on all product forms. The new route appears as :guilabel:`Supply Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route with a reordering rule or the make to order (MTO) route to replenish stock by moving the product from one warehouse to another."
msgid "When a product's reordering rule is triggered and the product has the :guilabel:`Supply Product from [Warehouse Name]` route set, Odoo automatically creates two pickings. One picking is a *delivery order* from the second warehouse, which contains all the necessary products, and the second picking is a *receipt* with the same products for the main warehouse. The product move from the second warehouse to the main warehouse is fully tracked in Odoo."
msgid "On the picking/transfer records created by Odoo, the :guilabel:`Source Document` is the product's reordering rule. The location between the delivery order and the receipt is a transit location."
msgid "For companies that use multiple warehouses, it is often necessary to transfer items between them. This is referred to as an *inter-warehouse transfer*. Odoo *Inventory* handles the administrative process of inter-warehouse transfers to ensure that inventory counts remain accurate during and after the transfer. This document will detail the method for conducting an inter-warehouse transfer using replenishment."
msgid "First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by navigating to :menuselection:`Inventory --> Configuration --> Settings`, and then check the box under the :guilabel:`Warehouse` tab. This will provide additional configuration options when creating a second warehouse that are needed for inter-warehouse replenishment."
msgid "By default, Odoo comes with a main warehouse already configured. If an additional warehouse has not already been created, do so now from the :guilabel:`Inventory` module by selecting :menuselection:`Configuration --> Warehouses --> Create`. Otherwise, select the warehouse that products will be transferred to from the :guilabel:`Warehouses` page and then click :guilabel:`Edit` to change its settings. Configure the warehouse as follows:"
msgid "Click :guilabel:`Save` and the new warehouse will be created. In addition, a new :guilabel:`Resupply From` field will appear on the warehouse's form. Click :guilabel:`Edit` and then check the box next to the warehouse that will be used to resupply the warehouse that is currently being configured."
msgid "For the purposes of this demonstration, the warehouse that products are transferred from (outgoing) will be titled \"San Francisco\", and the warehouse that products are transferred to (incoming) will be titled \"San Francisco 2\"."
msgid "Products must also be configured properly in order for them to be transferred between warehouses. Navigate to :menuselection:`Inventory --> Products --> Products` and select an existing product or :guilabel:`Create` a new one, if necessary."
msgid "Then, on the product form, go to the :guilabel:`Inventory` tab and enable the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the warehouse receiving the transferred products and *Y* being the warehouse that products are transferred from."
msgid "Starting in the :menuselection:`Inventory` module, select :menuselection:`Products --> Products` and then choose the product that will be replenished. Click the :guilabel:`Replenish` button on the top left of the product page and fill out the pop-up form as follows:"
msgid ":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* being the warehouse to be replenished and *Y* being the warehouse that the product will be transferred from"
msgid "Click :guilabel:`Confirm` and a delivery order will be created for the outgoing warehouse along with a receipt for the warehouse that will receive the product. Depending on the configuration settings for the outgoing and incoming warehouses, processing delivery orders and receipts will require between one and three steps. This document will detail how to process one-step deliveries and receipts."
msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped."
msgid "Once the goods arrive at the incoming warehouse, the receipt created for that warehouse must be processed as well. Return to the :menuselection:`Inventory` dashboard and select the :guilabel:`X to Process` button on the :guilabel:`Receipts` card for the incoming warehouse, then the receipt created for the replenishment. On the receipt page, click the :guilabel:`Validate` button in the top left of the page to register the quantities received."
msgid "After processing the receipt, the products transferred will now appear in the inventory of the incoming warehouse. The stock numbers for both warehouses can be viewed by returning to the product page and selecting the :guilabel:`X Units On Hand` button at the top of the screen."
msgid "To get started, navigate to :menuselection:`Inventory --> Products --> Products`, and then choose the product that will be replenished. From the product page, select the :guilabel:`Reordering Rules` smart button at the top of the form, and then on the next page, click :guilabel:`Create` to configure the form as follows:"
msgid ":guilabel:`Multiple Quantity`: specify if the product should be replenished in batches of a certain quantity; for example, a product could be replenished in batches of 20"
msgid ":guilabel:`UoM`: the unit of measure used for reordering the product; this value can simply be `Units`, or a specific unit of measurement for weight, length, etc."
msgid "Finish by clicking :guilabel:`Save` and the reordering rule will be created. Now, when the scheduler runs automatically each day, a transfer will be created for each reordering rule that has been triggered."
msgid "To manually trigger reordering rules, start from the :menuselection:`Inventory` module and select :menuselection:`Operation --> Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the pop-up that appears."
msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above."
msgid "In Odoo, a **Warehouse** is the actual building/place in which a company's items are stocked. Multiple warehouses can be set up in Odoo and the user can create moves between warehouses."
msgid "A **Location** is a specific space within the warehouse. It can be a sublocation of the warehouse (a shelf, a floor, an aisle, and so on). Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. In Odoo, as many locations can be configured as needed under one warehouse."
msgid "The **Physical Locations** are internal locations that are part of the warehouses that the company owns. They can be the loading and unloading areas of the warehouse, a shelf, a department, etc."
msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as physical locations, with the only difference being that they are not owned by the user's company."
msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when recording lost products (**Inventory Loss**), or accounting for products that are on their way to the warehouse (**Procurements**)."
msgid "In Odoo, locations are structured hierarchically. Locations can be structured as a tree, dependent on a parent-child relationship. This gives more detailed levels of analysis of the stock operations and the organization of the warehouses."
msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like \"WH/[first letters of location]\"."
msgid "Now, go back to the :guilabel:`Inventory` dashboard. There, new operations related to the newly created warehouse have been automatically generated."
msgid "Cross-docking is the process of sending products that are received directly to the customers, without making them enter the stock. The trucks are simply unloaded in a *Cross-Dock* area in order to reorganize products and load another truck."
msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? <https://www.odoo.com/blog/business-hacks-1/post/what-is-cross-docking-and-is-it-for-me-270>`_"
msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse."
msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`."
msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it."
msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier."
msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*."
msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*."
msgid "While keeping stock and selling inventory from one warehouse might work for smaller companies, bigger companies might need to keep stock in, or sell from, multiple warehouses in multiple locations."
msgid "In Odoo, sometimes products included in a single sales order might take stock from two (or more) warehouses. In Odoo, pulling products from multiple warehouses to satisfy sales demands can be done by using *virtual locations*."
msgid "In order to create virtual locations in warehouses and proceed to the following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features will need to be enabled in the :menuselection:`Settings` app."
msgid "To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. Then, :guilabel:`Save` the changes to finish."
msgid "Before creating any virtual stock locations, a new warehouse will need to be created. This new warehouse will act as a *virtual* warehouse, and will be the *parent* location of other physical warehouses."
msgid "Virtual warehouses are great for companies with multiple physical warehouses. This is because a situation might arise when one warehouse runs out of stock of a particular product, but another warehouse still has stock on-hand. In this case, stock from these two (or more) warehouses could be used to fulfill a single sales order."
msgid "The \"virtual\" warehouse acts as a single aggregator of all the inventory stored in a company's physical warehouses, and is used (for traceability purposes) to create a hierarchy of locations in Odoo."
msgid "To create a new warehouse, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse :guilabel:`Name` and :guilabel:`Short Name` can be changed, and other warehouse details can be changed under the :guilabel:`Warehouse Configuration` tab."
msgid "Under the :guilabel:`Shipments` heading, set the number of steps used to process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and :guilabel:`3 steps` radio buttons. The desired option for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will depend on the warehouse's procurement process, and might differ for individual products or product categories."
msgid ":doc:`How to choose the right flow to handle receipts and deliveries? </applications/inventory_and_mrp/inventory/management/shipments_deliveries>`"
msgid ":guilabel:`Manufacture`: to produce right away, move the components to the production location directly and start the manufacturing process; to pick first and then produce, unload the components from the stock to input location first, and then transfer it to the production location."
msgid "*Routes* can be set and configured directly from the :guilabel:`Warehouse` form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse is configured, virtual *Locations* can be created."
msgid "In order to apply this virtual warehouse as the *parent* location of two *child* location warehouses, there need to be two warehouses configured with physical stock locations."
msgid "In order to take stock from multiple warehouses to fulfill a sales order, there need to be at least **two** warehouses acting as *child locations* of the *virtual parent location* warehouse."
msgid "To create and edit *Locations*, go to :menuselection:`Inventory --> Configuration --> Locations`. All :guilabel:`Locations` are listed here, including the *Stock* :guilabel:`Location` of the virtual warehouse that was created. Click into the *Stock* :guilabel:`Location` for the virtual warehouse that was previously created (:dfn:`Warehouse Name/Stock`)."
msgid "Then, under the :guilabel:`Additional Information` section, change the :guilabel:`Location Type` from :guilabel:`Internal Location` to :guilabel:`View`. :guilabel:`Save` the changes."
msgid "This identifies this :guilabel:`Location` as a *virtual location*, which is used to create a hierarchical structure for a warehouse and aggregate its *child locations*."
msgid "Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), and remove any filters in the :guilabel:`Search Bar`. Then, click into the first physical warehouse :guilabel:`Location` that was previously created to be a *child location*, and click :guilabel:`Edit`."
msgid "Under :guilabel:`Parent Location`, select the virtual warehouse from the drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the :guilabel:`Locations` overview, and repeat this step for the second physical warehouse stock location. Be sure to :guilabel:`Save` changes again."
msgid "Both locations are now *child locations* of the virtual warehouse *parent location*. This allows stock to be taken from multiple locations to fulfill a single sales order, if there is not enough stock in any one location (provided they are both tied to the same virtual warehouse *parent location*)."
msgid "To sell products from multiple warehouses using a virtual *parent* location in this flow, there must be at least **two** products and at least **two** warehouses configured - with at least **one** product with quantity on-hand in each warehouse, respectively."
msgid "To create a new request for quotation, or RFQ, navigate to the :menuselection:`Sales` app, and click :guilabel:`Create` from the :guilabel:`Quotations` overview. Fill out the information on the new quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a product` to add the two products stored in the two warehouses."
msgid "Then, click the :guilabel:`Other Info` tab on the sales order form. Under the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field value listed to the virtual warehouse that was previously created. Once the warehouse has been changed, click :guilabel:`Confirm` to convert the quotation into a sales order."
msgid "Now that the quotation has been confirmed as a sales order, click the :guilabel:`Delivery` smart button. From the warehouse delivery form, confirm that the :guilabel:`Source Location` value matches the :guilabel:`Warehouse` field value from the sales order. Both should list the virtual warehouse location."
msgid "The :guilabel:`Source Location` on the warehouse delivery form and the :guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales order form *must* match in order for the products included in the sales order to be pulled from different warehouses."
msgid "If the virtual warehouse is not the value in the :guilabel:`Source Location` field on the warehouse delivery form, then click :guilabel:`Edit`, make the change, and click :guilabel:`Save`."
msgid "If the virtual warehouse is not the value in the :guilabel:`Warehouse` field on the sales order, then a new quotation may need to be generated."
msgid "If whe :guilabel:`Warehouse` field is missing on the sales order form, then the virtual warehouse (and its children warehouses) may not have been set up correctly, in which case, review the documentation above again to make sure all settings/configuration were done properly."
msgid "Finally, on the warehouse delivery form, under the :guilabel:`Detailed Operations` tab, confirm that the *Locations* values under the :guilabel:`From` column for each product matches to the *child locations* that are tied to the virtual *parent location*."
msgid "To view which *Locations* the products are coming from on the drop-down menus, click the :guilabel:`internal link (arrow)` icon to expand the *Location* information. If needed, it can be changed from here (granted there is quantity on hand for the product in that location)."
msgid "Once everything has been properly set, click :guilabel:`Validate` and then :guilabel:`Apply` to validate the delivery. Then, navigate back to the sales order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to invoice for the sales order."
msgid "To use a virtual *parent* location as the default warehouse for sales orders, each salesperson can have the virtual warehouse assigned to them from the drop-down menu next to :guilabel:`Default Warehouse` on their employee form."
msgid "In inventory management, the supply chain strategy determines when products should be purchased/manufactured, delivered to distribution centers, and made available to the retail channel."
msgid "In Odoo, a product's supply chain strategy can be configured using *Routes*, which feature *Pull and Push Rules*. Once everything is properly configured, the Inventory app can automatically generate transfers following the configured push/pull rules."
msgid "In a generic warehouse, there are receiving docks, a quality control area, storage locations, picking and packing areas, and shipping docks. All products go through all these locations. As the products move through the locations, each location triggers the products' specified route and rules."
msgid "In this example, vendor trucks unload pallets of ordered products at the receiving docks. Operators then scan the products in the receiving area. Depending on the product's route and rules, some of these products are sent to a quality control area (for example, products that are components used in the manufacturing process), while others are directly stored in their respective locations."
msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes and conveyors bring them close to the shipping docks, ready to be delivered to customers."
msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location."
msgid "Pull Rules are used to fulfill a sales order. Odoo generates a need at the *Customer Location* for each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull rule defined on the *Customer Location*."
msgid "In this case, a \"delivery order\" pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created."
msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the \"packing\" rule that transfers products from the *Packing Area* to the *Shipping Area*. Finally, other pull rules are triggered until a transfer between the *Stock* and the *Picking Area* is created."
msgid "All these product transfers are automatically generated by Odoo based on the pull rules, starting from the end (the customer location) and going backward (the stock warehouse). While working, the operator processes these transfers in the opposite order: first the picking, then the packing, and finally the delivery order."
msgid "On the other hand, *Push Rules* are much easier to understand. Instead of generating documents based on needs, they are triggered in real time when products arrive in a specific location. Push rules basically say: \"when a product arrives at a specific location, move it to another location.\""
msgid "An example of a push rule would be: when a product arrives in the *Receipt Area*, move it to the *Storage Location*. As different push rules can be applied to different products, the user can assign different storage locations for different products."
msgid "Another push rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*."
msgid "Sets of push/pull rules like those are called *Routes*. The grouping on the rule decides if products are grouped in the same transfer or not. For example, during the picking operation, all orders and their products are grouped in one transfer, whereas the packing operation respects the grouping per customer order."
msgid "To configure a route for a product, first, open the :guilabel:`Inventory` application and go to :menuselection:`Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` feature and click :guilabel:`Save`."
msgid "To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> Configuration --> Warehouses`. Then, open a warehouse form. In the :guilabel:`Warehouse Configuration` tab, the user can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments`."
msgid "Some more advanced routes, such as pick-pack-ship, are also available. The user can select the route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are set, head to :menuselection:`Inventory --> Configuration --> Routes` to see the specific routes that Odoo generated."
msgid "On the :guilabel:`Routes` page, click on a route to open the route form. In the route form, the user can view which places the route is :guilabel:`Applicable On`. The user can also set the route to only apply on a specific :guilabel:`Company`. This is useful for multi-company environments; for example, a user can have a company and warehouse in Country A and a second company and warehouse in Country B."
msgid "At the bottom of the route form, the user can view the specific :guilabel:`Rules` for the route. Each :guilabel:`Rule` has an :guilabel:`Action`, a :guilabel:`Source Location`, and a :guilabel:`Destination Location`."
msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, and click on :guilabel:`Create`. Next, choose the places where this route can be selected. A route can be applicable on a combination of places."
msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly. Then, configure the :guilabel:`Rules` of the route."
msgid "If the route is applicable on a product category, the route still needs to be manually set on the product category form by going to :menuselection:`Inventory --> Configuration --> Product Categories`. Then, select the product category and open the form. Next, click :guilabel:`Edit` and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`."
msgid "When applying the route on a product category, all the rules configured in the route are applied to **every** product in the category. This can be helpful if the business uses the dropshipping process for all the products from the same category."
msgid "The same behavior applies to the warehouses. If the route can apply to :guilabel:`Warehouses`, all the transfers occurring inside the chosen warehouse that meet the conditions of the route's rules will then follow that route."
msgid "If the route is applicable on :guilabel:`Sales Order Lines`, it is more or less the opposite. The route must be manually chosen when creating a quotation. This is useful if some products go through different routes."
msgid "Remember to toggle the visibility of the :guilabel:`Route` column on the quotation/sales order. Then, the route can be chosen on each line of the quotation/sales order."
msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, the route must be manually set on the product form."
msgid "To set a route on a product, go to :menuselection:`Inventory --> Products --> Products` and select the desired product. Then, go to the :guilabel:`Inventory` tab and under the :guilabel:`Operations` section, select the :guilabel:`Routes`."
msgid "The rules are defined on the route form. First, go to :menuselection:`Inventory --> Configuration --> Routes` and open the desired route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` section, click on :guilabel:`Add a line`."
msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Each rule has an :guilabel:`Action`:"
msgid ":guilabel:`Pull From`: this rule is triggered by a need for the product in a specific location. The need can come from a sales order being validated or from a manufacturing order requiring a specific component. When the need appears in the destination location, Odoo generates a picking to fulfill this need."
msgid ":guilabel:`Push To`: this rule is triggered by the arrival of some products in the defined source location. In the case of the user moving products to the source location, Odoo generates a picking to move those products to the destination location."
msgid ":guilabel:`Pull & Push`: this rule allows the generation of pickings in the two situations explained above. This means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. This creates a need in the previous location and a rule is triggered to fulfill it. Once the second need is fulfilled, the products are pushed to the destination location and all the needs are fulfilled."
msgid "If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or :guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The :guilabel:`Supply Method` defines what happens at the source location:"
msgid ":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored."
msgid ":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location."
msgid "In the *Scheduling* section, you can determine how Odoo behaves when one of the chain's pickings is rescheduled. In case you decide to **Propagate Rescheduling**, the next move is also to be rescheduled."
msgid "First, a quick look at the route's rules and their supply methods. There are three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply Methods` for each rule are the following:"
msgid ":guilabel:`Take From Stock`: When products are needed in the :guilabel:`WH/Packing Zone`, *picks* (internal transfers from :guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from :guilabel:`WH/Stock` to fulfill the need."
msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`WH/Output`, *packs* (internal transfers from :guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from :guilabel:`WH/Packing Zone` to fulfill the need."
msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`Partner Locations/Customers`, *delivery orders* are created from :guilabel:`WH/Output` to fulfill the need."
msgid "This means that, when a customer orders products that have a *pick - pack - ship* route set on it, a delivery order is created to fulfill the order."
msgid "If the source document for multiple tranfers is the same sales order, the status is not the same. The status will be :guilabel:`Waiting Another Operation` if the previous transfer in the list is not done yet."
msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse."
msgid "As explained in the introduction of the documentation, the last step in the process (for this route, the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from the stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items."
msgid "A good warehouse implementation makes sure that products automatically move to their appropriate destination location. To make that process easier, Odoo uses *Putaway Rules*. Putaway is the process of taking products from the received shipments and putting them into the appropriate location."
msgid "If, for example, a warehouse contains volatile substances, it is important to make sure that certain products are not stored close to each other because of a potential chemical reaction. That's where putaway rules intervene, to avoid storing products wrongly."
msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated."
msgid "In some cases, like for a retail shop storing fruits and vegetables, products should be stored in different locations depending on several factors like frequency, size, product category, specific environment needs, and so on."
msgid "Manage those locations with putaway rules. To create a putaway rule, open the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway rule that indicated the main location the product will enter before being redirected to the right storage location."
msgid "The putaway rules can be defined either per product/product category and/or package type (the :guilabel:`Packages` setting must be enabled for that). Putaway rules are read sequentially until a match is found."
msgid "A *Storage Category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location and how the location will be selected with putaway rules."
msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Storage Categories` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated."
msgid "To create a storage category, go to :menuselection:`Inventory --> Configuration --> Storage Categories` and click :guilabel:`Create`. Then, click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to :menuselection:`Configuration --> Storage Categories` to create a new storage category."
msgid "Then, there are options to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:"
msgid "To continue the example from above, apply the \"High Frequency Pallets\" on the PAL1 and PAL2 locations and rework the putaway rules as follows:"
msgid "Usually, *Removal Strategies* are defined in picking operations to select the best products, optimize the distance for the worker, for quality control purposes, or to first move products with the closest expiration date."
msgid "When a product movement needs to be done, Odoo finds available products that can be assigned to the transfer. The way Odoo assigns these products depends on the *Removal Strategy* defined in the *Product Category* or on the *Location*."
msgid "Imagine a generic warehouse plan, with receiving docks and areas, storage locations, picking and packing areas, and shipping docks. All products go through all these locations, but some rules, such as removal strategies, can have an effect on which products are taken for the pickings."
msgid "Here, vendor trucks unload pallets of goods at the docks. Then, operators scan the products in the receiving area with the reception date and, if the product has an expiration date, the expiration date. After that, products are stored in their respective locations."
msgid "Next, several orders for the same product are made, but in this example, the goods weren't received on the same day and they don't have the same expiration date. In that situation, logically, sending those with the closest date first is preferred. Depending on the chosen removal strategy, Odoo generates a transfer with the products that fit the settings the best."
msgid "When using a *First In, First Out* (FIFO) strategy, a demand for some products triggers a removal rule, which requests a transfer for the lot/serial number that has entered the stock first."
msgid "For example, imagine there are three lots of nails in the warehouse. Those three have the following lot numbers: :guilabel:`00001`, :guilabel:`00002`, :guilabel:`00003`, each with five boxes of nails in it."
msgid ":guilabel:`00001` entered the stock on the 23rd of May, :guilabel:`00002` on the 25th of May, and :guilabel:`00003` on the 1st of June. A customer orders six boxes on the 11th of June. With the :abbr:`FIFO (First In, First Out)` removal strategy selected, a transfer is requested for the five boxes of :guilabel:`00001` and one of the boxes in :guilabel:`00002`, because :guilabel:`00001` entered the stock before the others. The box from :guilabel:`00002` is taken next because it has the oldest reception date after :guilabel:`00001`."
msgid "So, for every order of a product with the :abbr:`FIFO (First In, First Out)` strategy selected, Odoo requests a transfer for the products that have been in the stock for the longest period."
msgid "Similar to :abbr:`FIFO (First In, First Out)`, the *Last In, First Out* (LIFO) strategy moves products based on the date they entered the stock. Here, a demand for some products triggers a removal rule that requests a transfer for the lot/serial number that has entered the stock most recently."
msgid "For example, imagine there are three lots of screws in the warehouse. Those three have the following numbers: :guilabel:`10001`, :guilabel:`10002`, and :guilabel:`10003`, each with 10 boxes of screws in it."
msgid ":guilabel:`10001` entered the stock on the 1st of June, :guilabel:`10002` on the 3rd of June, and :guilabel:`10003` on the 6th of June. A customer orders seven boxes on the 8th of June. With the :abbr:`LIFO (Last In, First Out)` removal strategy selected, a transfer is requested for seven boxes of :guilabel:`10003` because that lot is the last one to have entered the stock."
msgid "Basically, for every order of a product with the :abbr:`LIFO (Last In, First Out)` strategy used, a transfer for the last lot to have entered the stock is requested."
msgid "The *First Expired, First Out* (FEFO) strategy is a bit different from the other two removal strategies. For :abbr:`FEFO (First Expired, First Out)`, the expiration date is important, not the date the product entered the stock."
msgid "For example, imagine there are three lots of six-egg boxes (in this specific case, don't forget to use :doc:`units of measure <../../management/products/uom>`). Those three lots have the following numbers: :guilabel:`20001`, :guilabel:`20002`, and :guilabel:`20003`, each with five boxes in it."
msgid ":guilabel:`20001` entered the stock on the 1st of July and expires on the 15th of July, :guilabel:`20002` entered on the 2nd and expires on the 14th of July, and :guilabel:`20003` entered on the 4th and expires on the 21st of July. A customer orders six boxes on the 5th of July. With the :abbr:`FEFO (First Expired, First Out)` strategy selected, a transfer is requested for the five boxes of :guilabel:`20002` and one from :guilabel:`20001`. The transfer for all the boxes in lot :guilabel:`20002` is because they have the closest expiration date. The transfer also requests one box from :guilabel:`20001` because has the next closest expiration date after lot :guilabel:`20002`."
msgid "Basically, for every sales order of a product with the :abbr:`FEFO (First Expired, First Out)` strategy, a transfer is requested for the product that has the nearest expiration date from the order date."
msgid "The *Closest Location* strategy is completely different from the other removal strategies. It is not related to the date of entry in the warehouse, but rather the location of the product. It is commonly used for products that do not deteriorate with time."
msgid "The aim is to avoid making the warehouse worker take a long journey to the bottom of the stock when the product is also located at a near location. This method is only available if the :guilabel:`Storage Locations` setting is on. The closest location is actually the one that comes first in the alphabetic order."
msgid "To differentiate some units from others, the units need to be tracked, either by *lot* or by *serial number*. To do so, go to :menuselection:`Inventory --> Configuration --> Settings`. Then, activate the :guilabel:`Storage Location`, :guilabel:`Multi-Step Routes`, and :guilabel:`Lots & Serial Numbers` settings."
msgid "As explained, a :abbr:`FIFO (First In, First Out)` removal strategy implies that products stocked first move out first. Companies should use this method if they are selling products with short demand cycles, such as clothes, and to ensure they are not stuck with outdated styles in stock."
msgid "In this example, there are three lots of white shirts. The shirts are from the :guilabel:`All/Clothes` category, where *FIFO* is set as the removal strategy. In the stock location (:guilabel:`WH/Stock`), the user can find the three lots available."
msgid "As seen above, :guilabel:`000001` entered the stock first. Now, create a sales order of six white shirts to check that those products from lot :guilabel:`000001` are the first ones to move out."
msgid "On the delivery order linked to the picking, the oldest lot numbers should have been reserved thanks to the :abbr:`FIFO (First In, First Out)` strategy."
msgid "With a *LIFO* strategy, that's quite the opposite. In fact, the products that are received last move out first. :abbr:`LIFO (Last In, First Out)` is mostly used for products without a shelf life."
msgid "In this example, let's use the white shirts again to test the :abbr:`LIFO (Last In, First Out)` strategy. First, open the product category via :menuselection:`Inventory --> Configuration --> Product Categories` and change the removal strategy to :abbr:`LIFO (Last In, First Out)`."
msgid "With the :abbr:`FEFO (First Expired, First Out)` removal strategy, the way products are picked is not based on the reception date. In this particular case, they are dispatched according to their expiration date."
msgid "For have more information about expiration dates, please have a look at :doc:`the related doc <../../management/lots_serial_numbers/expiration_dates>`."
msgid "By activating the :guilabel:`Expiration Dates` feature, it becomes possible to define different expiration dates on the serial/lot numbers that will be used in :abbr:`FEFO (First Expired, First Out)`. These expiration dates can be set by going to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`."
msgid "Lots are picked based on their removal date, from earliest to latest. Lots without a removal date defined are picked after lots with removal dates."
msgid "Other dates are for informational and reporting purposes only. If not removed from the stock, lots that are past the expiration dates may still be picked for delivery orders!"
msgid "To use the :abbr:`FEFO (First Expired, First Out)` strategy, go to :menuselection:`Inventory --> Configuration --> Product Categories` and set :abbr:`FEFO (First Expired, First Out)` in the :guilabel:`Force Removal Strategy` field."
msgid "When a sales order for 25 units of Hand Cream is created, Odoo automatically reserves the lots with the closest expiration date, :guilabel:`0000001` and :guilabel:`0000003`."
msgid "If you have clicked on **Validate**, the request has been made and you should have received the tracking number and the label. You can still cancel the request. Simply click on the **Cancel** button next to the **Carrier Tracking Ref**:"
msgid "After cancelling the shipping request, you can change the carrier you want to use. Confirm it by clicking on the **Send to shipper** button. You will get a new tracking number and a new label."
msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses."
msgid "To use dropshipping as a fulfillment strategy, navigate to the :menuselection:`Purchase` app and select :menuselection:`Configuration --> Settings`. Under the :guilabel:`Logistics` heading, click the :guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish."
msgid "Next, go to the :menuselection:`Sales` app, click :menuselection:`Products --> Products` and choose an existing product or select :guilabel:`Create` to configure a new one. On the :guilabel:`Product` page, make sure that the :guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are enabled."
msgid "Click on the :guilabel:`Purchase` tab and specify a vendor and the price that they sell the product for. Multiple vendors can be added, but the vendor at the top of the list will be the one automatically selected for purchase orders."
msgid "When a customer completes an online purchase for a dropshipped product, a sales order will be automatically created with an associated request for quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales orders can be viewed in the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart button at the top right of a sales order to view the associated :abbr:`RFQ (Request for Quotation)`."
msgid "Dropship sales orders can also be created manually through the :menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders --> Create` and adding a product configured for dropshipping."
msgid "Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a purchase order and a dropship receipt is created and linked to it. The receipt can be viewed by clicking the :guilabel:`Receipt` smart button in the top right corner of the purchase order form."
msgid "The dropship receipt will list the supplier in the :guilabel:`Receive From` section and the customer in the :guilabel:`Destination Location` section. Upon delivery of the product to the customer, click on the :guilabel:`Validate` button at the top left of the dropship receipt to confirm the delivered quantity."
msgid "To view all dropship orders, simply navigate to the :menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card."
msgid "To configure the price of your delivery methods, go to the **Inventory** app, click on :menuselection:`Configuration --> Delivery --> Delivery Methods`."
msgid "To invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price."
msgid "In Odoo, there are a variety of different types of shipping labels that can be selected for delivery orders. Depending on the types of shipping packages used, different label sizes may be more appropriate, and can be configured to fit the package."
msgid "In the :menuselection:`Inventory` module, go to :menuselection:`Configuration --> Delivery --> Shipping Methods.` Choose a delivery method and click :guilabel:`Edit`. For the following example, *FedEx International* will be used."
msgid "In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose one of the label types available. The availability will vary depending on the carrier. :guilabel:`Save` the changes."
msgid "When a sales order with the corresponding shipping company is confirmed and a delivery order is validated, the shipping label will be automatically created as a PDF and appear in the :guilabel:`Chatter`."
msgid "In the :menuselection:`Sales` application, click :guilabel:`Create` and select an international customer. Click :guilabel:`Add A Product` and select an item. Click :guilabel:`Add Shipping`, select a shipping method, then click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`."
msgid "Once the delivery order is validated by clicking :guilabel:`Validate` in the delivery order, the shipping documents appear in the :guilabel:`Chatter`."
msgid "Odoo can handle various delivery methods, including third party shippers linked with the transportation company tracking system. It allows you to manage the transport company, the real prices and the destination. And finally, you will be able to print the shipping labels directly from Odoo."
msgid "In the **Inventory** module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :"
msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**."
msgid "The weight on the product form is expressed in kilograms. Don't forget to do the conversion if you are used to the imperial measurement system."
msgid "If you are doing multi-packages shippings, most of the time, there will be one label per package. Each label will appear in the delivery history."
msgid "By default, Odoo considers that your delivery is composed of one package. But you can easily ship your deliveries with more than one package. It is fully integrated with the third-party shippers."
msgid "To configure the use of packages, go to the menu :menuselection:`Inventory --> Configuration --> Settings`. Locate the **Packages** section and tick **Record packages used on packing: pallets, boxes,...**"
msgid "Once the delivery order is validated, you will receive the tracking number. The **carrier Tracking ref** field will automatically be filled. Click on the **Tracking** button to check your delivery on the provider website."
msgid "Odoo can handle various delivery methods, but it is not activated by default. Delivery methods can be used for your sale orders, your deliveries but also on your e-commerce."
msgid "Delivery methods allow you to manage the transport company, the price and the destination. You can even integrate Odoo with external shippers to compute the real price and the packagings."
msgid "Delivery methods are handled by the **Delivery costs** module. Go to **Apps** and search for the module. You should remove the **Apps** filter in order to see it :"
msgid "If the price is fixed, tick **Fixed price**. You'll just have to define the price. If you want the delivery to be free above a certain amount, tick the option **Free if Order total is more than** and set a price."
msgid "If the price varies according to rules, tick **Based on Rules**. Click on **add an item to a pricing rule**. Choose a condition based on either the weight, the volume, the price or the quantity."
msgid "Finally you can limit the delivery method to a few destinations. The limit can be applied to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce."
msgid "You can integrate Odoo with external shippers in order to compute the real price and packagings, and handle the printing the shipping labels. See :doc:`third_party_shipper`"
msgid "You can now choose the **Delivery Method** on your sale order. If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product."
msgid "Sendcloud is a shipping service aggregator that facilitates the integration of European shipping carriers with Odoo. Once integrated, users can select shipping carriers on inventory operations in their Odoo database."
msgid "To get started, go to `Sendcloud's platform <https://www.sendcloud.com>`_ to configure the account and generate the connector credentials. Log in with the Sendcloud account, or create a new one if needed."
msgid "For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Added Tax Identification)` number or :abbr:`EORI (Economic Operators' Registration and Identification)` number. After completing the account setup, activate (or deactivate) the shipping carriers that will be used in the Odoo database."
msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank account is linked, since Sendcloud won't ship for free. To use shipping rules or individual custom carrier contacts, a paid plan of Sendcloud is required."
msgid "Once logged into the Sendcloud account, navigate to :menuselection:`Settings --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse address`."
msgid "To allow Sendcloud to process returns as well, a :guilabel:`Return Address` is required. Under the :guilabel:`Miscellaneous section`, there is a field called :guilabel:`Address Name (optional)`. The Odoo warehouse name should be entered here, and the characters should be exactly the same."
msgid "Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo configuration and the Sendcloud configuration, are the exact same."
msgid "In the Sendcloud account, navigate to :menuselection:`Settings --> Integrations` in the menu on the right. Next, search for :guilabel:`Odoo Native`. Then, click on :guilabel:`Connect`."
msgid "After clicking on :guilabel:`Connect`, the page redirects to the :guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and Secret Keys` are produced. The next step is to name the :guilabel:`Integration`. The naming convention is as follows: `Odoo CompanyName`, with the user's company name replacing `CompanyName` (e.g. `Odoo StealthyWood`)."
msgid "Then, check the box next to :guilabel:`Service Points` and select the shipping services for this integration. After saving, the :guilabel:`Public and Secret Keys` are generated."
msgid "After the Sendcloud account is set up and configured, it's time to configure the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, search for the :guilabel:`Sendcloud Shipping` integration, and install it."
msgid "Once installed, activate the :guilabel:`Sendcloud Shipping` module in :menuselection:`Inventory --> Configuration --> Settings`. The :guilabel:`Sendcloud Connector` setting is found under the :guilabel:`Shipping Connectors` section."
msgid "After activating the :guilabel:`Sendcloud Connector`, click on the :guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`."
msgid "In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping products` link."
msgid "Sendcloud does not provide test keys when a company tests the sending of a package in Odoo. This means if a package is created, the configured Sendcloud account will be charged, unless the associated package is canceled within 24 hours of creation."
msgid "Odoo has a built-in layer of protection against unwanted charges when using test environments. Within a test environment, if a shipping method is used to create labels, then those labels are immediately canceled after the creation — this occurs automatically. The test and production environment settings can be toggled back and forth from the :guilabel:`Smart Buttons`."
msgid "When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label documents are automatically generated in the chatter, which include the following:"
msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels."
msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order."
msgid "When using a personal carrier contract in Sendcloud, if the the price is not accurately reflected when creating a quotation in Odoo, then the pricing information needs to be updated in Sendcloud."
msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)."
msgid "First, verify that product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier."
msgid "Odoo can handle various delivery methods, including third party shippers. Odoo can be linked with the transportation company tracking system. It will allow you to manage the transport company, the real prices and the destination."
msgid "In the inventory module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :"
msgid "The delivery methods for the chosen shippers have been automatically created. Most of the time, there will be **2** delivery methods for the same provider: one for **international** shipping and the other for **domestic** shipping."
msgid "In the pricing tab, the name of the provider chosen under the **Price computation** means that the pricing will be computed by the shipper system."
msgid "Finally you can limit the delivery method to a few destinations. You can limit it to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce. It is useful for the domestic providers. For example, USPS US only delivers from the United States to the United States."
msgid "The weight on the product form is expressed in kilograms. Don't forget to make the conversion if you are used to the imperial measurement system."
msgid "If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price."
msgid "Otherwise, the real price (computed when the delivery is validated) will automatically be added to the invoice. For more information, please read the document :doc:`../operation/invoicing`"
msgid "Click on **Validate** to receive the tracking number. The **Carrier Tracking ref** field will automatically be filled. Click on the **Tracking** button to check your delivery on the provider website."
msgid "Note that only customers located in the US can open a UPS account online. If you are located outside the US, you will need to contact UPS Customer Service in order to to open an account."
msgid "You can read additional information about opening a UPS account on the their website, on the page, `How to Open a UPS Account Online <https://www.ups.com/content/us/en/resources/sri/openaccountonline.html?srch_pos=2&srch_phr=open+ups+account>`_"
msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q"
msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact."
msgid "**Odoo Manufacturing** helps manufacturers schedule, plan and process manufacturing orders. With the work center control panel, put tablets on the shop floor to control work orders in real-time and allow workers to trigger maintenance operations, feedback loops, quality issues, etc."
msgid "In Odoo, **equipment** refers to any item that is used in everyday operations, including the manufacturing of products. This can mean a piece of machinery on a production line, a tool that is used in different locations, or a computer in an office space. Equipment registered in Odoo can be owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case of equipment rentals."
msgid "Using Odoo **Maintenance**, it is possible to track individual pieces of equipment, along with information about their maintenance requirements. To add a new piece of equipment, navigate to the :guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`, and configure the equipment as follows:"
msgid ":guilabel:`Equipment Category`: the category that the equipment belongs to; for example, computers, machinery, tools, etc.; new categories can be created by navigating to :menuselection:`Configuration --> Equipment Categories` and clicking :guilabel:`Create`"
msgid ":guilabel:`Used By`: specify if the equipment is used by a specific employee, department, or both; select :guilabel:`Other` to specify both an employee and a department"
msgid ":guilabel:`Maintenance Team`: the team responsible for servicing the equipment; new teams can be created by navigating to :menuselection:`Configuration --> Maintenance Teams` and selecting :guilabel:`Create`; the members of each team can also be assigned from this page"
msgid ":guilabel:`Technician`: the person responsible for servicing the equipment; this can be used to assign a specific individual in the event that no maintenance team is assigned or when a specific member of the assigned team should always be responsible for the equipment; any person added to Odoo as a user can be assigned as a technician"
msgid ":guilabel:`Used in location`: the location where the equipment is used; this is a simple text field that can be used to specify locations that are not work centers, like an office, for example"
msgid ":guilabel:`Work Center`: if the equipment is used at a work center, specify it here; equipment can also be assigned to a work center by navigating to :menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a work center or creating a new one using the :guilabel:`Create` button, and clicking the :guilabel:`Equipment` tab on the work center form"
msgid ":guilabel:`Effective Date`: the date that the equipment became available for use; this is used to calculate the :abbr:`MTBF (Mean Time Between Failures)`"
msgid "The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on maintenance requests if any exist."
msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form."
msgid "Manufacturing several different products simultaneously at the same work center is a common issue for manufacturing companies. Although in practice, employees can manufacture the goods at another work center instead of waiting for one to be available, it's not always simple to have visibility on which work center is busy and plan resources accordingly in real-time."
msgid "With Odoo, you can configure alternative work centers to solve this issue. This automatically checks which work center is busy and which equivalent ones are free, and schedules orders and maintenance accordingly."
msgid "First, go to the :menuselection:`Manufacturing app --> Configuration --> Settings`. Then, enable the :guilabel:`Work Orders` feature and hit :guilabel:`Save`."
msgid "Now, go to :menuselection:`Configuration --> Work Centers` and create two new work centers. Add the second work center as an alternative to the first one and vice versa."
msgid "Next, go to :menuselection:`Products --> Bills of Materials`, choose your product, and add these work centers to the operations of your :abbr:`BoM (Bill of Materials)`."
msgid "Go to :menuselection:`Operations --> Manufacturing Orders`, and hit :guilabel:`Create`. There, add your product to your manufacturing order and plan it. You can then retrieve them from the :guilabel:`Work Orders` list view, under :menuselection:`Operations > Work Orders`."
msgid "Each new *Work Order*, which will be created before the end of the first one, will be scheduled at the alternative work center you configured, as shown below."
msgid "Keep in mind that, if you add time after production to your work center, you may have work orders scheduled for your alternative work center even if the usual one is free."
msgid "A *Bill of Materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process."
msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so that even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`."
msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*."
msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`."
msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled."
msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`."
msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form."
msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column."
msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`."
msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`."
msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature."
msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`."
msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`."
msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`."
msgid "A *kit* is a set of unassembled components. Kits may be sold as products, but are also useful tools for managing more complex bills of materials (BoMs). To use kits, the :guilabel:`Manufacturing` and :guilabel:`Inventory` applications need to be installed."
msgid "To use a kit as a sellable product or simply as a component organization tool, the kit should first be created as a product. To create a kit product, go to :menuselection:`Manufacturing or Inventory --> Products --> Products`, and then click :guilabel:`Create`."
msgid "Next, set the :guilabel:`Product Type` to :guilabel:`Storable Product`: this allows for management of kit inventory. The :guilabel:`Route` designation under the :guilabel:`Inventory` tab does not matter, since Odoo uses the routes of the kit's components for replenishment purposes. All other parameters for the kit product may be modified according to preference. Finally, click :guilabel:`Save`."
msgid "The kit's components must also be configured as products via :menuselection:`Manufacturing or Inventory --> Products --> Products`. These components require no specific configuration."
msgid "After fully configuring the kit product and its components, create a :abbr:`BoM (Bill of Materials)` for the kit product. Go to :menuselection:`Manufacturing --> Products --> Bills of Materials`, and then click :guilabel:`Create`. Next, set the :guilabel:`Product` field to the previously configured kit product. Then, set the :guilabel:`BoM Type` to :guilabel:`Kit`. Finally, add each component and specify its quantity. Make sure to :guilabel:`Save` the changes."
msgid "If the kit is solely being used as a sellable product, then only components need to be added under the :guilabel:`Components` tab, and configuring manufacturing operations is not necessary."
msgid "When a kit is sold as a product, it appears as a single line item on the quotation and sales order. However, on delivery orders, each component of the kit is listed."
msgid "Kits are also used to manage *multilevel* :abbr:`BoMs (Bills of Materials)`. These are products that contain other products as components and therefore require nested :abbr:`BoMs (Bills of Materials)`. Incorporating pre-configured kits into multilevel :abbr:`BoMs (Bills of Materials)` allows for cleaner organization of bundled products. Under :guilabel:`Components`, list a kit as a component in a higher-level product's :abbr:`BoM (Bills of Material)` to eliminate the need to add the kit's parts individually. Any :guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM (Bill of Materials)`."
msgid "To access a comprehensive overview of the multilevel :abbr:`BoM's (Bill of Material's)` components, click on the :guilabel:`Structure & Cost` smart button. Sublevel :abbr:`BoMs (Bills of Materials)` can be expanded and viewed from this report."
msgid "When creating a manufacturing order for a product with a multilevel :abbr:`BoM (Bill of Materials)`, the kit product automatically expands to show all components. Any operations in the kit's :abbr:`BoM (Bill of Materials)` are also added to the list of work orders on the manufacturing order."
msgid "Kits are primarily used to bundle components together for organization or sale. To manage multilevel products that require manufactured subcomponents, refer to :doc:`this documentation <sub_assemblies>` on sub-assemblies."
msgid "Odoo allows one bill of materials (BoM) to be used for multiple variants of the same product. Having a consolidated BoM for a product with variants saves time by preventing the need to manage multiple BoMs."
msgid "To activate variants, simply navigate to :menuselection:`Inventory --> Configuration --> Settings --> Products`, and then enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting. For more information on configuring product variants, refer to :doc:`this page <../../../sales/sales/products_prices/products/variants>`."
msgid "Next, create a new BoM or edit an existing one by going to :menuselection:`Manufacturing --> Products --> Bills of Materials`. Then, click :guilabel:`Edit`. The :guilabel:`Apply on Variants` option to assign components to specific product variants on the BoM is available once the :guilabel:`Variants` setting is activated from the :guilabel:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu."
msgid "Each component can be assigned to multiple variants. Components with no variants specified are used in every variant of the product. The same principle applies when configuring operations and by-products."
msgid "When defining variant BoMs by component assignment, the :guilabel:`Product Variant` field in the main section of the BoM should be left blank, as shown below. This field is used only when creating a BoM specifically for one product variant."
msgid "Whether you want to control the quality of your production, or the production of your subcontractor, before registering the products into your stock, you can rely on Odoo's Quality module."
msgid "To control the quality of your production, you need to set a *Quality Control Point* on the Manufacturing Operation Type, as shown below. To create it, Go to :menuselection:`Quality --> Quality Control --> Control Points`, and click **Create**. If the check only applies to specific products, or product categories, you can specify these during the setup as well."
msgid "Regarding the reception of subcontracted products, instead of the Manufacturing Operation Type, you need to select the 'Receipts' Operation type. For the rest, the same principles apply."
msgid "By doing so, a quality check is automatically created each time a finished product is made and/or received. Note that several Quality Check *Types* can be chosen from the dropdown. Note also that several Quality Check Points can be set up for the same Operation Type."
msgid "A *semi-finished product*, also known as a *subassembly*, is a manufactured product that is used as a component in another product's bill of materials (BoM). Semi-finished products are used to simplify complex :abbr:`BoMs (Bills of Materials)` or to more accurately represent a manufacturing flow. A :abbr:`BoM (Bill of Materials)` that contains semi-finished products is referred to as a *multilevel BoM*, where the main *top-level product* and its subassemblies are distinguished."
msgid "To set up a multilevel :abbr:`BoM (Bill of Materials)`, the top-level product and semi-finished products must be configured. Therefore, the first step is to create the semi-finished products and their :abbr:`BoMs (Bills of Materials)`."
msgid "After the semi-finished products are fully configured, navigate to :menuselection:`Manufacturing --> Products --> Products`. Then, :guilabel:`Create` the top-level product. Configure the product's specifications as desired, and be sure to :guilabel:`Save`."
msgid "Once the top-level product is configured, click the :guilabel:`Bill of Materials` smart button on the product form, then click :guilabel:`Create` to make a :abbr:`BoM (Bill of Materials)` for the top-level product. Then, simply add the semi-finished products to this :abbr:`BoM (Bill of Materials)`, along with any other necessary components."
msgid "Semi-finished products are specifically used to manage manufacturable products with multilevel BoMs. If a BoM is being created simply to organize components or bundle sellable products, using :doc:`Kits <kit_shipping>` is the more appropriate option."
msgid "To automatically trigger manufacturing orders for semi-finished products after confirming a manufacturing order for the main product, there are two options:"
msgid "**Option 1 (recommended):** Create *Reordering Rules* for the semi-finished products and set both the minimum and maximum desired stock quantities to `0`."
msgid "**Option 2:** Activate the :guilabel:`Replenish on Order (MTO)` and :guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the semi-finished product's product form."
msgid "Option 1 is more flexible than Option 2 and is therefore recommended. Reordering rules do not directly link demand to replenishment, and therefore allow stocks to be unreserved and redirected to other orders, if necessary. The Replenish on Order (MTO) route creates a unique link between the semi-finished and top-level products, exclusively reserving quantities for the confirmed top-level manufacturing order."
msgid "To create a new *BoM*, go to :menuselection:`Manufacturing --> Products --> Bill of Materials` and hit create. Then, list the components your subcontractor needs to manufacture the product. For costing purposes, you might want to register all the components, even the ones that are sourced directly from the subcontractor."
msgid "To let your subcontractor know how many products you need, create and send them purchase orders (PO). To do so, go to the *Purchase* app and create a new purchase order. Be sure to send the PO to a vendor that is defined as a subcontractor on the *BoM* of these products."
msgid "Once the *PO* is validated (1), a pending receipt is created. When the products are received, validate the receipt (2), with the actual quantity received. As a result, Odoo does the following things for you:"
msgid "The *PO* is optional. If you create a receipt manually, with the right subcontractor, Odoo still performs all the moves. This can be useful if the subcontractor does not bill a fixed price per item, but rather the time and materials used."
msgid "Sending raw materials to your subcontractors (**A**) does not impact the inventory valuation, as the components are still valued as part of your stock. This is managed by making the *Subcontracting Location* an *Internal Location*."
msgid "Then, the vendor price set on the product C form has to be what has to be paid to the subcontractor for his parts and service time: **B + s**. The product cost has to be: **A + B + s**, how much the product is valued in the accounting."
msgid "If managing the replenishment of raw materials **B** at your subcontractor’s location is not needed, simply include the cost of **B** in the subcontractor’s price **s** and remove the products *B* from the *BoM*."
msgid "In case the received products from the subcontractor contain tracked components, their serial or lot numbers need to be specified during the receipt."
msgid "In that case, on the receipt of the subcontracted product, a *Record Components* button appears. Click on it to open a dialog box and record the serial/lot numbers of the components. If the finished product is also tracked, its serial/lot number can be registered here too."
msgid "Also note that in case flexible consumption has been selected on the subcontracted BOM for a non-tracked product, the record components option will also appear optionally on each move line, if you want to register more or less component consumption at your subcontracting location, when receiving your final product."
msgid "As you can see, the reception of both of these non-tracked products can either be executed by selecting the 'Set Quantities' Option or via the move line hamburger menus."
msgid "There are two ways to automate the supply of raw materials to your subcontractors when purchasing the final product. The chosen method depends on whether or not you want the materials to transit through your warehouse. Both of these methods are described as pull style mechanisms as their trigger is the inital PO to the subcontractor, which creates a need at the subcontracting location, for raw material."
msgid "If you are supplying your subcontractor with raw material from your own warehouse, you must activate the 'Resupply Subcontractor on Order' route as shown below. If this is a component that you buy from a vendor, the buy route should also be activated."
msgid "Now, if you want your vendor to resupply your subcontractor directly, you must choose the 'Dropship Subcontractor on Order' option instead. In order for this option to be active on the product form, you must first activate the dropship option from :menuselection:`Purchase --> Configuration --> Settings --> Dropshipping`. Once the PO to the subcontractor is validated, this route will create a dropship RFQ from your vendor to that subcontractor. You then just need to review and validate it."
msgid "Finally, if you want to track the stock of these raw materials at your subcontracting location(s), then you must activate *Multi-locations* in :menuselection:`Inventory --> Configuration --> Settings --> Storage locations`."
msgid "If you want to send components to your subcontractor at your own convenience, select the 'Resupply Subcontractor' Operation Type from the *Inventory* Module, and create a picking, specifying to which subcontractor you are delivering to."
msgid "Alternatively, you can also manually ask your vendor to resupply your subcontractor by creating a dropship type PO, with your subcontractor set as the delivery address."
msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save."
msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period."
msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like."
msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components."
msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button."
msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell."
msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross."
msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast."
msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment."
msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually."
msgid "Odoo Manufacturing allows for work orders to be carried out at specific work centers. When a manufacturing order is created for a product, any work orders listed in the :guilabel:`Operations` tab of the product bill of materials (BoM) will be automatically created as well and assigned to the specified work center. Work orders can be managed in the :guilabel:`Manufacturing` module by selecting :menuselection:`Operations --> Work Orders`."
msgid "In order to use work centers, the :guilabel:`Work Orders` feature must first be enabled. To do so, go to the :guilabel:`Manufacturing` module, select :menuselection:`Configuration --> Settings`, and activate the checkbox next to :guilabel:`Work Orders`. Work centers can then be created and managed by selecting :menuselection:`Configuration --> Work Centers`."
msgid "Within the :guilabel:`Manufacturing` module, select :menuselection:`Configuration --> Work Centers --> Create`. The work center form can then be filled out as follows:"
msgid ":guilabel:`Alternative Workcenters`: specify an alternative work center for operations to be carried out at if the main work center is not available"
msgid ":guilabel:`Time Efficiency`: used to calculate the expected duration of a work order at the work center; for example, if a work order normally takes one hour and the efficiency is set to 200%, the work order will take 30 minutes"
msgid "Using the :guilabel:`Equipment` tab, it is possible for specific pieces of equipment to be assigned to a work center. The following information will be displayed for each piece of equipment added:"
msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists."
msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out."
msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field."
msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form."
msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center."
msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:"
msgid "Configuring quality control points is a great way to ensure that quality checks are performed at routine stages during specific operations. However, quality issues can often appear outside of these scheduled checks. Using Odoo *Quality*, users can create quality alerts for issues that are not detected by automated processes."
msgid "A helpdesk user who is notified of a product defect by a customer ticket can create an alert that brings the issue to the attention of the relevant quality team."
msgid "To create a new quality alert, start from the :menuselection:`Quality` module and select :menuselection:`Quality Control --> Quality Alerts --> Create`. The quality alert form can then be filled out as follows:"
msgid "Odoo enables manufacturing employees to create quality alerts within a work order without accessing the *Quality* module. From the work order tablet view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner and select :guilabel:`Quality Alert`."
msgid "The quality alert form can then be filled out as detailed in the previous section. After saving the form, a new alert will appear on the :guilabel:`Quality Alerts` dashboard that can be found through the :menuselection:`Quality --> Quality Control` menu."
msgid "By default, quality alerts are organized in a kanban board view. The stages of the kanban board are fully configurable and alerts can be moved from one stage to the next by dragging and dropping or from within each alert. Additional options are available for viewing alerts, including graph, calendar, and pivot table views."
msgid "Filter alerts based on diverse criteria like date assigned or date closed. Alerts can also be grouped by quality team, root cause, or other parameters found under the :guilabel:`Filters` button menu."
msgid "Use **Odoo Quality** to control the quality of products before they are registered into stock, during picking operations, and when leaving the warehouse for a delivery order. By creating *quality control points*, manufacturers can set up quality checks that automatically trigger at specific points during production."
msgid "To create a new quality control point, go to :menuselection:`Quality Control --> Control Points --> Create`. Then, fill in the following form fields, accordingly:"
msgid ":guilabel:`Title`: give the quality control point a simple, but informative title so production floor and quality check teams can understand it easily"
msgid ":guilabel:`Operations`: determine which operations team(s) should perform the quality control check (e.g., `Manufacturing`, `Receipts`, `Delivery Orders`, etc.)"
msgid ":guilabel:`Work Order Operation`: for manufacturing operations, use the drop-down menu to indicate which type of work order the quality control point applies to: :guilabel:`Manual Assembly`, :guilabel:`Packing`, :guilabel:`Assembly`, :guilabel:`Testing` or :guilabel:`Long time assembly`"
msgid ":guilabel:`Company`: add the company that will implement the quality control point. Usually this will be the company that owns the Odoo database. However, a multi-company or vendor profile can be selected, as well, for cases where there are multiple manufacturing or engineering locations"
msgid ":guilabel:`Control Type`: using the drop-down menu, choose from :guilabel:`All Operations`, :guilabel:`Randomly` or :guilabel:`Periodically` to determine how often the control point should executed"
msgid ":guilabel:`Type`: using the drop-down menu, choose the control point type: :guilabel:`Instructions`, :guilabel:`Take a Picture`, :guilabel:`Pass - Fail`, or :guilabel:`Measure`"
msgid "Once a control point has been configured, a quality check will be automatically created and assigned when the specified operation or work order has been reached. Quality checks can be managed by selecting :menuselection:`Quality Control --> Quality Checks`."
msgid "To see all of the quality checks created by a control point, go to :menuselection:`Quality Control --> Control Points`, select a control point, and click :guilabel:`Quality Checks` in the top right corner."
msgid "To ensure that a product meets specific measurement requirements, select :guilabel:`Measure` from the :guilabel:`Type` drop-down menu. Selecting the :guilabel:`Measure` quality check type reveals three new fields: :guilabel:`Device`, :guilabel:`Norm`, and :guilabel:`Tolerance`. These fields can be configured so that only products within a certain tolerance will pass the check:"
msgid ":guilabel:`Tolerance`: select the range that a measurement can be within while still passing the check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to` 60.5 mm)"
msgid "When the quality control points form is complete, click :guilabel:`Save`. Now, this measurement-based test will trigger for products that were specified on the form."
msgid "When production of the specified product reaches the operation that requires a measure quality check, the manufacturing employee responsible will be prompted to record and validate the measured value in the tablet view. For products that measure within the values indicated in the :guilabel:`Tolerance` fields, the test will pass. However, for products that measure outside of those values, the test will fail. In that case, the worker who performed the check would create a quality alert from the tablet view. That quality alert can then be addressed by the quality management team."
msgid "**Odoo Purchase** helps you keep track of purchase agreements, quotations, and purchase orders. Learn how to keep track of purchase tender, automate replenishments and follow up on your orders."
msgid "If your company regularly purchases products, you have several reasons to track and analyze your performance. The insights gathered can help you to better forecast and plan your future orders. For example, you can assess if your business is dependent on particular vendors, and the data can help you negotiate discounts on prices."
msgid "Go to *Reporting* to access the purchase analysis. Simply by accessing the reporting dashboard, you can get a quick overview of your actual performance. By default, the reporting dashboard displays a line chart presenting the untaxed amount of your purchase orders per day, and below it, key metrics and a pivot table."
msgid "Odoo offers several default filters you can use and combine by clicking on *Filters*. When you select one or several filters, Odoo looks for all the orders that match at least one of the filters you have chosen and populates the chart, key metrics, and pivot table with the data. The pre-configured filters are:"
msgid "When you have to select a period, you can use multiple years, and, with at least one year selected, multiple quarters and the three most recent months."
msgid "If you use the *Order Date* or *Confirmation Date* filters, the *Comparison* feature appears next to *Filters*. It enables you to compare the period you filtered with the previous one."
msgid "Thanks to the 31 filtering options to choose from, the possibilities of your customizing your dataset are almost limitless. Go to :menuselection:`Filters --> Add Custom Filter`, specify the condition the filtering option should meet (e.g. *is equal to*, *contains*, etc.), and click on *Apply*. If you want to select orders matching several conditions simultaneously (*and* operator), repeat the process to add another custom filter. If you want to use the *or* operator, don't click on *Apply*, and click on *Add a condition* instead. Once you have added all the desired filtering options, click on *Apply*."
msgid "To avoid having to recreate custom filters every time, save them by clicking on :menuselection:`Favorites --> Save current search --> Save`. The customized search filter can then be accessed by clicking on *Favorites* or can even be set as the default filter when you open the reporting dashboard."
msgid "Before selecting what you want to measure, you need to decide whether you prefer using the graph view or the pivot view. By default, the dashboard presents both views. However, the measures you select won't be applied to both views. You can access each view separately by clicking on the icons at the top right of the dashboard."
msgid "You can transform the main graph in just a click by selecting one of the three charts: bar, line or pie. Fourteen different measures are available, but you can only use one at a time. However, you can group the measure using one or several of the 19 *Groups*."
msgid "For bar and line charts, the selected measure is your y-axis, and the first group you select is used to create the x-axis. Adding more group adds additional lines (line chart) or transforms your bar chart into a stacked bar chart. For pie charts, the more groups you select, the more slices are displayed."
msgid "The pivot table view enables you to explore your data in great detail. Unlike the graph view, the pivot table enables you to add several measures at the same time. By clicking on *Measures* or on the **+** sign in the *Total* column, you can add as many as you want, each assigned to a new column. By clicking on the **+** sign in the *Total* row, you can add *Groups*. If you click on a group's **+** sign, you can add a sub-group, and so on."
msgid "Blanket orders are long-term purchase agreements between a company and a vendor to deliver products on a recurring basis with predetermined pricing. Using blanket orders are useful when products are always purchased from the same vendor, but in different quantities at different times."
msgid "By simplifying the ordering process, blanket orders not only save time, they also save money, since they can be advantageous when negotiating bulk pricing with vendors."
msgid "To create blanket orders, the *Purchase Agreements* feature first needs to be enabled in the settings of the *Purchase* app. To do this, go to :menuselection:`Purchase --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase Agreements`. Doing so will enable the ability to create blanket orders, as well as alternative requests for quotation (RFQs)."
msgid "To create a blanket order, go to :menuselection:`Purchase --> Orders --> blanket orders`, and click :guilabel:`New`. This creates (and navigates to) a new blanket order form."
msgid "From this new blanket order form, different fields and settings can be configured, so there are pre-determined rules that the recurring long-term agreement must follow:"
msgid ":guilabel:`Purchase Representative`: is the user assigned to this specific blanket order. By default, this is the user who created the agreement; the user can be changed directly from the drop-down menu next to this field."
msgid ":guilabel:`Agreement Type`: is the type of purchase agreement this blanket order is classified as. In Odoo, blanket orders are the only official purchase agreement."
msgid ":guilabel:`Vendor`: is the supplier to whom this agreement is tied, either once or on a recurring basis. The vendor can be selected directly from the drop-down menu next to this field."
msgid ":guilabel:`Currency`: is the agreed-upon currency that will be used for this exchange. If multiple currencies have been activated in the database, the currency can be changed from the drop-down menu next to this field."
msgid ":guilabel:`Agreement Deadline`: is the date that this purchase agreement will be set to expire on (if desired). If this blanket order should not expire, leave this field blank."
msgid ":guilabel:`Ordering Date`: is the date that this blanket order should be placed on if a new quotation is created directly from the blanket order form. If a new quotation is created, this value will automatically populate the *Order Deadline* field on the :abbr:`RFQ (Request for Quotation)`."
msgid ":guilabel:`Delivery Date`: is the expected delivery date that the products included in an :abbr:`RFQ (Request for Quotation)` created directly from the blanket order form will be expected to arrive. If a new quotation is created, this value will automatically populate the *Expected Arrival* field on the :abbr:`RFQ (Request for Quotation)`."
msgid ":guilabel:`Source Document`: is the source purchase order (PO) that this blanket order will be tied to. If this blanket order should not be tied to any existing :abbr:`POs (Purchase Orders)`, leave this field blank."
msgid ":guilabel:`Company`: is the company assigned to this specific blanket order. By default, this is the company that the user creating the blanket order is listed under. If the database is not a multi-company database, this field can not be changed, and will default to the only company listed in the database."
msgid "Once all relevant fields have been filled out, click :guilabel:`Add a line` to add products under the :guilabel:`Product` column. Then, change the quantity of each product in the :guilabel:`Quantity` column (if desired), and set a price in the :guilabel:`Unit Price` column."
msgid "When adding products to a new blanket order, the pre-existing prices of products will not be added automatically to the product lines. The prices must be manually assigned by changing the value in the :guilabel:`Unit Price` column to an agreed-upon price with the listed vendor. Otherwise, the price will remain **0**."
msgid "To view and change the default purchase agreement settings for blanket orders directly from the blanket order form, click the :guilabel:`internal link (arrow icon)` next to the :guilabel:`Agreement Type` field where :guilabel:`Blanket Order` is listed. This navigates to the blanket order settings."
msgid "From here, the settings for blanket orders can be edited. Under the :guilabel:`Agreement Type` section, the name of the :guilabel:`Agreement Type` can be changed (if desired), and the :guilabel:`Agreement Selection Type` can be changed, as well. There are two options that can be activated for the type of selection:"
msgid ":guilabel:`Select multiple RFQ (non-exclusive)`: when a purchase order is confirmed, remaining purchase orders will ***not** be canceled. Instead, multiple purchase orders are allowed."
msgid "Under the :guilabel:`Data For New Quotations` section, the settings for how product lines and quantities will be populated on new quotations using this purchase agreeement can be changed next to the :guilabel:`Lines` and :guilabel:`Quantities` fields."
msgid ":guilabel:`Use lines of agreement`: when creating a new quotation, the product lines will pre-populate with the same products listed on the blanket order, if said blanket order is chosen on the new quotation."
msgid ":guilabel:`Do not create RfQ lines automatically`: when creating a new quotation and selecting an existing blanket order, the settings will carry over to the new quotation, but the product lines will not populate."
msgid ":guilabel:`Use quantities of agreement`: when creating a new quotation, the product quantities listed on the blanket order will pre-populate on the product lines, if said blanket order is chosen on the new quotation."
msgid ":guilabel:`Set quantities manually`: when creating a new quotation and selecting an existing blanket order, the product lines will pre-populate, but all quantities will be set to **0**. The quantities will need to be manually set by the user."
msgid "Once the desired changes have been made (if any), click :guilabel:`New` (via the breadcrumbs, at the top of the page) to navigate back to the blanket order form, and click :guilabel:`Confirm` to save this new purchase agreement. Once confirmed, the blanket order changes from *Draft* to *Ongoing*, meaning this agreement can be selected and used when creating new :abbr:`RFQs (Requests for Quotation)`."
msgid "After creating and confirming a blanket order, products, quantities, and prices can still be edited, added, and removed from the purchase agreement."
msgid "After confirming a blanket order, new quotations can be created directly from the blanket order form that will use the rules set on the form and pre-populate the new quotation with the correct information. Additionally, this new quotation will be automatically linked to this blanket order form via the :guilabel:`RFQs/Orders` smart button at the top right of the form."
msgid "To create a new quotation from the blanket order form, click :guilabel:`New Quotation`. This creates (and navigates to) a new :abbr:`RFQ (Request for Quotation)`, that is pre-populated with the correct information, depending on the settings configured on the blanket order form."
msgid "From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send by Email` to compose and send an email to the listed vendor; click :guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once ready, click :guilabel:`Confirm Order` to confirm the purchase order (PO)."
msgid "Once the :abbr:`PO (Purchase Order)` has been confirmed, click back to the blanket order form (via the breadcrumbs, at the top of the page). From the blanket order form, there is now one :abbr:`RFQ (Request for Quotation)` listed in the :guilabel:`RFQs/Orders` smart button at the top right of the form. Click the :guilabel:`RFQs/Orders` smart button to see the purchase order that was just created."
msgid "Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a vendor from the drop-down menu next to the :guilabel:`Vendor` field, and click :guilabel:`Add a product` to select a product from the drop-down menu in the :guilabel:`Product` column. Then, set the desired purchase quantity in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if desired."
msgid "Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item. Repeat these steps to add as many additional options as desired, including the :guilabel:`UoM` (Units of Measure) to purchase the products in, and the :guilabel:`Expected Arrival` date."
msgid "Before confirming the new quotation and creating a purchase order, click the drop-down menu next to the :guilabel:`Blanket Order` field, and type a new name for the new blanket order. This creates a brand new purchase agreement, and saves the information entered in the fields of the purchase order form, as well as the product information entered on the product lines."
msgid "From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send by Email` to compose and send an email to the listed vendor; click :guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once ready, click :guilabel:`Confirm Order` to confirm the :abbr:`PO (purchase order)`."
msgid "To see the newly-created blanket order purchase agreement, go to :menuselection:`Orders --> Blanket Orders`, and click into the new blanket order. From here, settings and rules can be changed, if desired."
msgid "Once a blanket order is confirmed, a new vendor line is added under the :guilabel:`Purchase` tab of of the products included in the :abbr:`BO (Blanket Order)`. This makes blanket orders useful with :doc:`automated replenishment <../../purchase/products/reordering>`, because information about the :guilabel:`Vendor`, :guilabel:`Price`, and the :guilabel:`Agreement` are referenced on the vendor line. This information is used to determine where, when, and for what price this product could be replenished."
msgid "Sometimes, companies might want to request offers from multiple vendors at the same time, by inviting those vendors to submit offers for similar goods or services all at once. This helps companies to select the cheapest (and fastest) vendors, depending on their specific business needs."
msgid "In Odoo, this can be done by adding alternative requests for quotation (RFQs) for different vendors. Once a response is received from each vendor, the product lines from each :abbr:`RFQ (Request for Quotation)` can be compared, and a decision can be made for which products to purchase from which vendors."
msgid "Sometimes referred to as a *call for tender*, this process is primarily used by organizations in the public sector, who are legally bound to use it when making a purchase. However, private companies can also use alternative :abbr:`RFQs (Requests for Quotation)` to spend money efficiently, as well."
msgid "To create alternative :abbr:`RFQs (Requests for Quotation)` directly from a quotation, the *Purchase Agreements* feature first needs to be enabled in the settings of the *Purchase* app. To do this, go to :menuselection:`Purchase --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase Agreements`. Doing so will enable the ability to create alternative :abbr:`RFQs (Requests for Quotation)`, as well as the ability to create *blanket orders*."
msgid "To save time on a *call for tender*, custom vendors, prices, and delivery lead times can be set in the :guilabel:`Purchase` tab on a product form. To do so, navigate to :menuselection:`Purchase --> Products --> Products`, and select a product to edit. From the product form, click the :guilabel:`Purchase tab`, then click :guilabel:`Add a line`. From the drop-down menu, choose a vendor to set under the :guilabel:`Vendor` column, and set a :guilabel:`Price` and :guilabel:`Delivery Lead Time` if desired. Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item."
msgid "Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a vendor from the drop-down next to the :guilabel:`Vendor` field, and click :guilabel:`Add a product` to select a product from the drop-down menu in the :guilabel:`Product` column. Then, set the desired purchase quantity in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if desired."
msgid "Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item. Repeat these steps to add as many options as desired, including the :guilabel:`UoM` (Units of Measure) to purchase the products in, and the :guilabel:`Expected Arrival` date."
msgid "Once ready, click :guilabel:`Send by Email`. This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send`. This turns the :abbr:`RFQ (Request for Quotation)` into a purchase order (PO), and sends an email to the vendor listed on the purchase order form."
msgid "Sending emails to each vendor can be useful when creating alternative :abbr:`RFQs (Requests for Quotation)`, because vendors can confirm if their past prices still hold today, which can help companies choose the best offers for them."
msgid "Once a :abbr:`PO (Purchase Order)` is created and sent by email to a vendor, alternative :abbr:`RFQs (Requests for Quotation)` can be created and sent to additional, alternate vendors to compare prices, delivery times, and other factors to make a decision from which vendors to order which products."
msgid "To create alternative :abbr:`RFQs (Requests for Quotation)`, click the :guilabel:`Alternatives` tab from the purchase order form, then click :guilabel:`Create Alternative`. When clicked, a :guilabel:`Create alternative` pop-up window appears."
msgid "From this window, select a new/different vendor from the drop-down menu next to the :guilabel:`Vendor` field to assign this alternative quotation to."
msgid "Next to this, there is a :guilabel:`Copy Products` checkbox that is selected by default. When selected, the product quantities of the original :abbr:`PO (Purchase Order)` are copied to the alternative. For this first alternative quotation, leave the checkbox checked. Once finished, click :guilabel:`Create Alternative`. This creates (and navigates to) a new :abbr:`PO (Purchase Order)`."
msgid "Since the :guilabel:`Create Alternative` checkbox was left checked, this new purchase order form is already populated with the same products, quantities, and other details as the previous, original :abbr:`PO (Purchase Order)`."
msgid "When the :guilabel:`Copy Products` checkbox is selected while creating an alternative quotation, additional products do not need to be added on the purchase order form unless desired. However, if a chosen vendor is listed in the :guilabel:`Vendor` column under the :guilabel:`Purchase` tab on a product form included in the purchase order, the values set on the product form carry over to the :abbr:`PO (Purchase Order)`, and have to be changed manually, if desired."
msgid "Once ready, create a second alternative quotation by clicking the :guilabel:`Alternatives` tab, and once again, click :guilabel:`Create Alternative`. This causes the :guilabel:`Create alternative` pop-up window to appear again. This time, choose a different vendor from the drop-down menu next to :guilabel:`Vendor`, and this time, *uncheck* the :guilabel:`Copy Products` checkbox. Then, click :guilabel:`Create Alternative`."
msgid "If an alternative quotation needs to be removed from the :guilabel:`Alternatives` tab, they can be individually removed by clicking on the :guilabel:`Remove (X)` icon at the end of their row."
msgid "This creates a third, new purchase order. But, since the product quantities of the original :abbr:`PO (Purchase Order)` were *not* copied over, the product lines are empty, and new products need to be added by clicking :guilabel:`Add a product`, and selecting the desired products from the drop-down menu. Once the desired number of products are added, click :guilabel:`Send by Email`."
msgid "This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send` to send an email to the vendor listed on the purchase order form."
msgid "From this newest purchase order form, click the :guilabel:`Alternatives` tab. Under this tab, all three purchase orders can be seen in the :guilabel:`Reference` column. Additionally, the vendors are listed under the :guilabel:`Vendor` column, and the order :guilabel:`Total` and :guilabel:`Status` of the orders are in the rows, as well."
msgid "Creating alternative quotations directly from a purchase order form under the :guilabel:`Alternatives` tab is the easiest way to create and link quotations. However, separate :abbr:`RFQs (Requests for Quotation)` can also be linked *after* the fact, even if they are created completely separately at first."
msgid "Once ready, click :guilabel:`Send by Email`. This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send` to send an email to the vendor listed on the purchase order form."
msgid "Then, click the :guilabel:`Alternatives` tab once more. Since this new :abbr:`PO (Purchase Order)` was created separately, there are no other orders linked yet. To link this order with the alternatives created previously, click :guilabel:`Link to Existing RfQ` on the first line in the :guilabel:`Vendor` column."
msgid "This causes an :guilabel:`Add: Alternative POs` pop-up window to appear. Select the three purchase orders created previously, and click :guilabel:`Select`. All of these orders are now copied to this :abbr:`PO (Purchase Order)` under the :guilabel:`Alternatives` tab."
msgid "If a large number of purchase orders are being processed and the previous :abbr:`POs (Purchase Orders)` can't be located, try clicking :menuselection:`Group By --> Vendor` under the search bar at the top of the pop-up window to group by the vendors selected on the previous orders."
msgid "When there are multiple :abbr:`RFQs (Requests for Quotation)` linked as alternatives, they can be compared side-by-side in order to determine which vendors offer the best deals on which products. To compare each quotation, go to the :menuselection:`Purchase` app, and select one of the quotations created previously."
msgid "Then, click the :guilabel:`Alternatives` tab to see all the linked :abbr:`RFQs (Requests for Quotation)`. Next, under the :guilabel:`Create Alternative` tab, click :guilabel:`Compare Product Lines`. This navigates to a Compare Order Lines page."
msgid "The Compare Order Lines page, by default, groups by :guilabel:`Product`. Each product included in any of the :abbr:`RFQs (Requests for Quotation)` is displayed in its own drop-down, along with all of the :abbr:`PO (Purchase Order)` numbers in the :guilabel:`Reference` column."
msgid "Additional columns on this page include the :guilabel:`Vendor` from which products were ordered, the :guilabel:`Status` of the quotation (i.e., RFQ, RFQ Sent); the :guilabel:`Quantity` of products ordered from each vendor; the :guilabel:`Unit Price` per product and :guilabel:`Total` price of the order, and more."
msgid "To remove product lines from the Compare Order Lines page, click :guilabel:`Clear` at the far right end of that product line's row. This removes this product as a chooseable option from the page, and changes the :guilabel:`Total` price of that product on the page to **0**. On the purchase order form in which that product was included, its ordered quantity is changed to **0**, as well."
msgid "Once the best offers have been identified, at the end of each row, individual products can be selected by clicking :guilabel:`Choose`. Once all the desired products have been chosen, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`."
msgid "Now that the desired products have been chosen, based on which vendors provided the best offer, the other :abbr:`RFQs (Requests for Quotation)` (from which no products were chosen) can be canceled."
msgid "Under the :guilabel:`Total` column, at the far right of each row, the orders from which no products were chosen have automatically had their total cost set to **0**. Although they haven't been canceled yet, this means that they can ultimately be canceled without repercussions, *after* the desired purchase orders have been confirmed."
msgid "To confirm a quotation that contains the chosen product quantities, click into one. Then, click :guilabel:`Confirm Order`. This causes an :guilabel:`Alternative Warning` pop-up window to appear. From there, either :guilabel:`Cancel Alternatives` or :guilabel:`Keep Alternatives` can be clicked. If this :abbr:`PO (Purchase Order)` should *not* be confirmed, click :guilabel:`Cancel`."
msgid ":guilabel:`Cancel Alternatives` automatically cancels the alternative purchase orders. :guilabel:`Keep Alternatives` keeps the alternative purchase orders open, so they can still be accessed if any additional product quantities need to be ordered. Once all products are ordered, :guilabel:`Cancel Alternatives` can be selected from whichever :abbr:`PO (Purchase Order)` is open."
msgid "To view a detailed form of one of the :abbr:`RFQs (Requests for Quotation)` listed, click the line item for that quotation. This causes an :guilabel:`Open: Alternative POs` pop-up window to appear, from which all details of that particular quotation can be viewed. Click :guilabel:`Close` when finished."
msgid "From the :guilabel:`Alternative Warning` pop-up window, click :guilabel:`Keep Alternatives` to keep all alternative quotations open for now. Then, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`."
msgid "Click into the remaining quotation(s) that contain products that need to be ordered, and click :guilabel:`Confirm Order`. This causes the :guilabel:`Alternative Warning` pop-up window to appear again. This time, click :guilabel:`Cancel Alternatives` to cancel all other alternative :abbr:`RFQs` linked with this quotation."
msgid "Finally, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`. The canceled orders can be seen greyed out and listed with a :guilabel:`Cancelled` status under the :guilabel:`Status` column at the far right of their rows."
msgid "Now that all product quantities have been ordered, the purchase process can be followed, and continued to completion, until the products are received into the warehouse."
msgid "In Odoo, the *bill control* policy determines the quantities billed by vendors on every purchase order, for ordered or received quantities. The policy selected in the settings will act as the default value and will be applied to any new product created."
msgid "To view the default bill control policy and make changes, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Here, there are the two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`."
msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill."
msgid ":guilabel:`Received quantities`: a bill is created only *after* part of the total order has been received. The products and quantities *received* are used to generate a draft bill. An error message will appear if creation of a vendor bill is attempted without receiving anything."
msgid "If one or two products need a different control policy, the default bill control setting can be overridden by going to the :guilabel:`Purchase` tab in a product's template and modifying its :guilabel:`Control Policy` field."
msgid "To complete an example workflow using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities`. Then, :guilabel:`Save` changes."
msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click :guilabel:`Create Bill`. Since the policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, without any products actually being received."
msgid "To complete an example workflow using the *received quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities`. Then, :guilabel:`Save` changes."
msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click on the :guilabel:`Receipt smart button`. Set the quantities in the :guilabel:`Done` column to match the quantities in the :guilabel:`Demand` column, and :guilabel:`Validate` the changes. Then, in the purchase order, click :guilabel:`Create Bill` and :guilabel:`Confirm`. Since the policy is set to *received quantities*, the draft bill can be confirmed *only* when at least some of the quantities are received."
msgid "Activating :guilabel:`3-way matching` ensures that vendor bills are only paid once some or all of the products included in the purchase order have actually been received. To activate it, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, click :guilabel:`3-way matching: purchases, receptions, and bills`."
msgid "When :guilabel:`3-way matching` is activated, vendor bills will display the :guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When a new vendor bill is created, the field will be set to :guilabel:`Yes`, since a bill can't be created until at least some of the products included in a purchase order have been received."
msgid "If the total quantity of products from a purchase order has not been received, Odoo only includes the products that *have* been received in the draft vendor bill."
msgid "Draft bills can be edited to increase the billed quantity, change the price of the products in the bill, and add additional products to the bill. If this is done, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`Exception`. This means that Odoo notices the discrepancy, but doesn't block the changes or display an error message, since there might be a valid reason for making changes to the draft bill."
msgid "Once payment has been registered for a vendor bill and displays the green :guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`No`."
msgid "The :guilabel:`Should Be Paid` status on bills is set automatically by Odoo. However, the status can be changed manually by clicking the field's drop-down menu inside the :guilabel:`Other Info` tab."
msgid "When a purchase order is confirmed, its :guilabel:`Billing Status` can be viewed under the :guilabel:`Other Information` tab on the purchase order form."
msgid "Below is a list of the different statuses that a :guilabel:`Billing Status` could appear as and when they are displayed, depending on the bill control policy used."
msgid "If you want to set up a vendor bill control process, the first thing you need to do is to have purchase data in Odoo. Knowing what has been purchased and received is the first step towards understanding your purchase management processes."
msgid "From the **Apps** application, search for the **Purchase** module and install it. Due to certain dependencies, installing Purchase will automatically install the **Inventory** and **Accounting** applications."
msgid "Creating products in Odoo is essential for quick and efficient purchasing within Odoo. Simply navigate to the Products submenu under Purchase and click create."
msgid "Products that are set as **Stockable or Consumable** will allow you to keep track of their inventory levels. These options imply stock management and will allow for receiving these kinds of products."
msgid "Conversely, products that are set as a **Service or Digital Product** will not imply stock management, simply due to the fact that there is no inventory to manage. You will not be able to receive products under either of these designations."
msgid "It is recommended that you create a **Miscellaneous** product for all purchases that occur infrequently and do not require inventory valuation or management. If you create such a product, it is recommended to set the product type to **Service**."
msgid "From the purchase application, you can create a purchase order with as many products as you need. If the vendor sends you a confirmation or quotation for an order, you may record the order reference number in the **Vendor Reference** field. This will enable you to easily match the PO with the the vendor bill later (as the vendor bill will probably include the Vendor Reference)"
msgid "If you purchased any stockable products that you manage the inventory of, you will need to receive the products from the Inventory application after you confirm a purchase order. From the **Inventory dashboard**, you should see a button linking you directly to the transfer of products. This button is outlined in red below:"
msgid "If you have a lot of awaiting orders, apply a filter using the search bar in the upper right. With this search bar, you may filter based on the vendor (partner), the product, or the source document (also known as the reference of your purchase order). You can also group the orders by different criteria under **Group By**. Selecting an item from this list will open the following screen where you then will receive the products."
msgid "When you receive a vendor bill for a previous purchase, be sure to record it in the Purchases application under the **Control Menu**. You need to create a new vendor bill even if you already registered a purchase order."
msgid "The first thing you will need to do upon creating a vendor bill is to select the appropriate vendor, since doing so will also pull up any associated accounting or pricelist information. From there, you can choose to specify one or multiple Purchase Orders to populate the Vendor Bill with. When you select a Purchase Order from the list, Odoo will pull any uninvoiced products associated to that Purchase Order and automatically populate that information below. If you are having a hard time finding the appropriate vendor bill, you may search through the list by inputting the vendor reference number or your internal purchase order number."
msgid "While the invoice is in a draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)."
msgid "Every time you record a new vendor bill, Odoo will automatically populate the product quantities based on what has been received from the vendor. If this value is showing a zero, this means that you have not yet received this product and simply serves as a reminder that the product is not in hand and you may need to inquire further into this. At any point in time, before you validate the Vendor Bill, you may override this zero quantity."
msgid "If the bill you receive from the vendor has quantities that do not match the quantities automatically populated by Odoo, this could be due to several reasons:"
msgid "The vendor is billing you for products that you might not have received yet, as the invoicing control may be based on ordered or received quantities."
msgid "In these instances it is recommended that you verify that the bill, and any associated purchase order to the vendor, are accurate and that you understand what you have ordered and what you have already received."
msgid "If you need to manage products based on ordered quantities over received quantities, you will need to belong to the group **Purchase Manager**. Ask your system administrator to enable these access on :menuselection:`Settings --> Users --> Users --> Access Rights`. Once you belong to the correct group, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**."
msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders. Odoo will add the additional line items from the purchase orders you select. If you have not deleted the previous line items from the first purchase order, the bill will be linked to all the appropriate purchase orders."
msgid "For certain products, it is necessary to ensure that there is always a minimum amount available on hand at any given time. By adding a reordering rule to a product, it is possible to automate the reordering process so that a purchase order is automatically created whenever the amount on hand falls below a set threshold."
msgid "Starting from the :menuselection:`Inventory`, :menuselection:`Manufacturing`, :menuselection:`Purchase`, or :menuselection:`Sales` module, navigate to :menuselection:`Products --> Products` and then click :guilabel:`Create` to make a new product. Alternatively, find a product that already exists in the database and click into it's product form."
msgid "Next, on the product form, enable reordering by checking the :guilabel:`Can be Purchased` option underneathe the :guilabel:`Product Name` field. Finally, set the :guilabel:`Product Type` to `Storable Product` under the :guilabel:`General Information` tab."
msgid "After properly configuring a product, a reordering rule can be added to it by selecting the now visible :guilabel:`Reordering Rules` tab at the top of that product's form, and then clicking :guilabel:`Create` on the :guilabel:`Reordering Rules` dashboard."
msgid ":guilabel:`Min Quantity` sets the lower threshold for the reordering rule while :guilabel:`Max Quantity` sets the upper threshold. If the stock on hand falls below the minimum quantity, a new purchase order will be created to replenish it up to the maximum quantity."
msgid "If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is set to `25` and the stock on hand falls to four, a purchase order will be created for 21 units of the product."
msgid ":guilabel:`Multiple Quantity` can be configured so that products are only ordered in batches of a certain quantity. Depending on the number entered, this can result in the creation of a purchase order that would put the resulting stock on hand above what is specified in the :guilabel:`Max Quantity` field."
msgid "If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple Quantity` is set to order the product in batches of `200`, a purchase order will be created for 200 units of the product."
msgid ":guilabel:`UoM` specifies the unit of measurement by which the quantity will be ordered. For discrete products, this should be set to `Units`. However, it can also be set to units of measurement like `Volume` or `Weight` for non-discrete products like water or bricks."
msgid "Reordering rules will be automatically triggered by the scheduler, which runs once a day by default. To trigger reordering rules manually, navigate to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-up window, confirm the manual action by clicking :guilabel:`Run Scheduler`."
msgid "To manage the reordering rules for a single product, navigate to that product page's form and select the :guilabel:`Reordering Rules` tab at the top of the form."
msgid "To manage all reordering rules for every product, go to :menuselection:`Inventory --> Configuration --> Reordering Rules`. From this dashboard, typical bulk actions in Odoo can be performed such as exporting data or archiving rules that are no longer needed. As well, the :guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form are available to search for and/or organize the reordering rules as desired."
msgid "When you purchase a product, it may happen that your vendor uses a different unit of measure than you do when you sell it. This can cause confusion between sales and purchase representatives. It is also time-consuming to convert measures manually every time. With Odoo, you can configure your product once and let Odoo handle the conversion."
msgid "A variety of units of measure are available by default in your database. Each belongs to one of the five pre-configured units of measure categories: *Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*."
msgid "To specify different units of measures for sales and purchases, open the Purchase app and go to :menuselection:`Products --> Products`. Create a product or select an existing one. Under the product's *General Information* tab, first select the *Unit of Measure* to be used for sales (as well as for other apps such as inventory). Then, select the *Purchase Unit of Measure* to be used for purchases."
msgid "Back to the first example, if you purchase orange juice from your vendor in **gallons** and sell it to your customers in **liters**, first select *L* (liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase Unit of Measure*, then click on *Save*."
msgid "Sometimes you need to create your own units and categories, either because the measure is not pre-configured in Odoo or because the units do not relate with each other (e.g. kilos and centimeters)."
msgid "If you take the second example where you buy curtains from a vendor in the form of **rolls** and you sell pieces of the rolls using **square meters**, you need to create a new *Units of Measure Category* in order to relate both units of measure."
msgid "First, create the unit of measure used as the reference point for converting to other units of measure inside the category by clicking on *Create*. Name the unit and select the units of measure category you just created. For the *Type*, select *Reference Unit of Measure for this category type*. Enter the *Rounding Precision* you would like to use. The quantity computed by Odoo is always a multiple of this value."
msgid "If you use a *Rounding Precision* inferior to 0.01, a warning message might appear stating that it is higher than the *Decimal Accuracy* and that it might cause inconsistencies. If you wish to use a *Rounding Precision* lower than 0.01, first activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings --> Technical --> Database Structure --> Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* accordingly. For example, if you want to use a rounding precision of 0.00001, set *Digits* to 5."
msgid "Next, create a second unit of measure, name it, and select the same units of measure category as your reference unit. As *Type*, select *Smaller* or *Bigger than the reference Unit of Measure*, depending on your situation."
msgid "Next, you need to enter the *Ratio* between your reference unit and the second one. If the second unit is smaller, the *Ratio* should be greater than 1. If the second unit is larger, the ratio should be smaller than 1."
