|
| 1 | +========================================== |
| 2 | +Create and process transfers with barcodes |
| 3 | +========================================== |
| 4 | + |
| 5 | +The *Barcode* app can be used to process internal transfers for all types of products, including |
| 6 | +transfers for products tracked using lots or serial numbers. Transfers can be created from scratch |
| 7 | +in real time using an Odoo-compatible barcode scanner or the Odoo mobile app. |
| 8 | + |
| 9 | +For a list of Odoo-compatible barcode mobile scanners, and other hardware for the *Inventory* app, |
| 10 | +refer to the `Odoo Inventory • Hardware page <https://www.odoo.com/app/inventory-hardware>`_. |
| 11 | + |
| 12 | +Enable Barcode app |
| 13 | +================== |
| 14 | + |
| 15 | +To use the *Barcode* app to process transfers, it must be installed by enabling the feature from the |
| 16 | +settings of the *Inventory* app. |
| 17 | + |
| 18 | +To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down |
| 19 | +to the :guilabel:`Barcode` section, and click the checkbox next to the :guilabel:`Barcode Scanner` |
| 20 | +feature. |
| 21 | + |
| 22 | +Once the checkbox is ticked, click :guilabel:`Save` at the top of the page to save changes. |
| 23 | + |
| 24 | +When the page has refreshed, new options are displayed under the :guilabel:`Barcode Scanner` |
| 25 | +feature: :guilabel:`Barcode Nomenclature` (with a corresponding drop-down menu), where either |
| 26 | +:guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. The |
| 27 | +nomenclature selected changes how scanners interpret barcodes in Odoo. |
| 28 | + |
| 29 | +There is also a :guilabel:`Configure Product Barcodes` internal link arrow, and a set of |
| 30 | +:guilabel:`Print` buttons for printing barcode commands and a barcode demo sheet. |
| 31 | + |
| 32 | +.. image:: transfers_scratch/transfers-scratch-enabled-barcode-setting.png |
| 33 | + :align: center |
| 34 | + :alt: Enabled Barcode feature in Inventory app settings. |
| 35 | + |
| 36 | +For more on setting up and configuring the :guilabel:`Barcode` app, refer to the :doc:`Set up your |
| 37 | +barcode scanner </applications/inventory_and_mrp/inventory/barcode/setup/hardware>` and |
| 38 | +:doc:`Activate the Barcodes in Odoo |
| 39 | +</applications/inventory_and_mrp/inventory/barcode/setup/software>` documentation pages. |
| 40 | + |
| 41 | +Scan barcodes for internal transfers |
| 42 | +==================================== |
| 43 | + |
| 44 | +To create and process internal transfers for products in a warehouse, the :guilabel:`Storage |
| 45 | +Locations` and :guilabel:`Multi-Step Routes` features **must** be enabled. |
| 46 | + |
| 47 | +To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down |
| 48 | +to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` |
| 49 | +and :guilabel:`Multi-Step Routes`. |
| 50 | + |
| 51 | +Then, click :guilabel:`Save` at the top of the page to save changes. |
| 52 | + |
| 53 | +Create an internal transfer |
| 54 | +--------------------------- |
| 55 | + |
| 56 | +To process existing internal transfers, there first needs to be an internal transfer created, and an |
| 57 | +operation to process. |
| 58 | + |
| 59 | +To create an internal transfer, navigate to the :menuselection:`Inventory app`. From the |
| 60 | +:guilabel:`Inventory Overview` dashboard, locate the :guilabel:`Internal Transfers` card, and click |
| 61 | +on the :guilabel:`0 To Process` button. |
| 62 | + |
| 63 | +Then, click :guilabel:`Create` in the top left of the resulting page. This navigates to a new |
| 64 | +:guilabel:`Internal Transfer` form. |
| 65 | + |
| 66 | +On this blank form, the :guilabel:`Operation Type` is automatically listed as :guilabel:`Internal |
| 67 | +Transfers`. Under that field, the :guilabel:`Source Location` and :guilabel:`Destination Location` |
| 68 | +are set as :guilabel:`WH/Stock` by default, but can be changed to whichever locations the products |
| 69 | +are being moved from, and moved to. |
| 70 | + |
| 71 | +.. image:: transfers_scratch/transfers-scratch-internal-transfer-form.png |
| 72 | + :align: center |
| 73 | + :alt: Blank internal transfer form with source location and destination location. |
| 74 | + |
| 75 | +Once the desired locations have been selected, products can be added to the transfer. On the |
| 76 | +:guilabel:`Product` line under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and |
| 77 | +select the desired product(s) to add to the transfer. |
| 78 | + |
| 79 | +Once ready, click :guilabel:`Save` at the top of the form to save the new internal transfer. Once |
| 80 | +saved, click the :guilabel:`Detailed Operations` icon (four lines, at the far right of the |
| 81 | +:guilabel:`Product` line) to open the :guilabel:`Detailed Operations` pop-up window. |
| 82 | + |
| 83 | +.. image:: transfers_scratch/transfers-scratch-detailed-operations-popup.png |
| 84 | + :align: center |
| 85 | + :alt: Internal transfer detailed operations pop-up window. |
| 86 | + |
| 87 | +From the pop-up, click :guilabel:`Add a line`. |
| 88 | + |
| 89 | +Then, in the :guilabel:`To` column, change the location from :guilabel:`WH/Stock` to a different |
| 90 | +location, where the products should be moved. |
| 91 | + |
| 92 | +Next, in the :guilabel:`Done` column, change the quantity to the desired quantity to transfer. Once |
| 93 | +ready, click :guilabel:`Confirm` to close out the pop-up window. |
| 94 | + |
| 95 | +Scan barcodes for internal transfer |
| 96 | +----------------------------------- |
| 97 | + |
| 98 | +To process and scan barcodes for internal transfers, navigate to the :menuselection:`Barcode app`. |
| 99 | + |
| 100 | +Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different |
| 101 | +options is presented. |
| 102 | + |
| 103 | +To process internal transfers, click on the :guilabel:`Operations` button at the bottom of the |
| 104 | +screen. This navigates to an :menuselection:`Operations` overview page. |
| 105 | + |
| 106 | +.. image:: transfers_scratch/transfers-scratch-barcode-app.png |
| 107 | + :align: center |
| 108 | + :alt: Barcode app start screen with scanner. |
| 109 | + |
| 110 | +From this page, locate the :guilabel:`Internal Transfers` card, and click the :guilabel:`# To |
| 111 | +Process` button to view all outstanding internal transfers. Then, select the desired operation to |
| 112 | +process. This navigates to the barcode transfer screen. |
| 113 | + |
| 114 | +.. note:: |
| 115 | + When using the *Barcode* app without the *Inventory* app (**only** if using a barcode scanner or |
| 116 | + the Odoo mobile app), the barcodes for each transfer of a corresponding operation type can be |
| 117 | + scanned to be processed easily. |
| 118 | + |
| 119 | + Once scanned, the products that are part of an existing transfer can be scanned, and new products |
| 120 | + can be added to the transfer, as well. Once all products have been scanned, validate the transfer |
| 121 | + to proceed with the stock moves. |
| 122 | + |
| 123 | +From this screen, an overview of all products to process within that specific internal transfer |
| 124 | +(**WH/INT/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add |
| 125 | +Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if |
| 126 | +the whole operation should be validated at once. |
| 127 | + |
| 128 | +.. image:: transfers_scratch/transfers-scratch-receipts-overview.png |
| 129 | + :align: center |
| 130 | + :alt: Overview of receipts in transfer to scan. |
| 131 | + |
| 132 | +Then, scan the barcode of the product to process the internal transfer. |
| 133 | + |
| 134 | +Or, to process and scan each product individually, choose a specific product line. The |
| 135 | +:guilabel:`+ 1` button can be clicked to add additional quantity of that product to the transfer, or |
| 136 | +the :guilabel:`pencil icon` can be clicked to open a new screen to edit that product line. |
| 137 | + |
| 138 | +In the product's pop-up window, the product and the units to process is displayed with a number pad. |
| 139 | +Under the product name, the :guilabel:`Quantity` line can be edited. Change the number in the line |
| 140 | +to the quantity listed to be transferred on the internal transfer form. |
| 141 | + |
| 142 | +.. example:: |
| 143 | + In the internal transfer operation `WH/INT/000XX`, `50 Units` of the `Transfer Product` is |
| 144 | + moved from `WH/Stock` to `WH/Stock/Shelf 1`. `[TRANSFER_PROD]` is the :guilabel:`Internal |
| 145 | + Reference` set on the product form. Scan the barcode of the `Transfer Product` to receive one |
| 146 | + unit. Afterwards, click the :guilabel:`pencil icon` to manually enter the transferred quantities. |
| 147 | + |
| 148 | + .. image:: transfers_scratch/transfers-scratch-product-line-editor.png |
| 149 | + :align: center |
| 150 | + :alt: Product line editor for individual transfer in Barcode app. |
| 151 | + |
| 152 | +Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract |
| 153 | +quantity of the product, and the number keys can be used to add quantity, as well. |
| 154 | + |
| 155 | +Below the number keys are the two :guilabel:`location` lines, which read whichever locations were |
| 156 | +previously specified on the internal transfer form, in this case `WH/Stock` and `WH/Stock/Shelf 1`. |
| 157 | +Click these lines to reveal a drop-down menu of additional locations to choose from. |
| 158 | + |
| 159 | +Once ready, click :guilabel:`Confirm` to confirm the changes made to the product line. |
| 160 | + |
| 161 | +Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), |
| 162 | +click :guilabel:`Validate`. The receipt has now been processed, and the *Barcode* app can be closed |
| 163 | +out. |
| 164 | + |
| 165 | +.. tip:: |
| 166 | + The *Barcode* app can also be used to scan products in internal transfers containing unique lot |
| 167 | + numbers and serial numbers. |
| 168 | + |
| 169 | + From the barcode transfer screen, scan the barcode of a lot or serial number, and Odoo |
| 170 | + automatically increases the quantity of the product to the quantity recorded in the database. If |
| 171 | + the same lot or serial number is shared between different products, scan the product barcode |
| 172 | + first, then the barcode of the lot/serial number. |
| 173 | + |
| 174 | +Create a transfer from scratch |
1 | 175 | ============================== |
2 | | -Create a Transfer from Scratch |
3 | | -============================== |
4 | 176 |
|
5 | | -To create a transfer from the *Barcode* application, you first need to |
6 | | -print the operation type barcodes. To do so, you can download the |
7 | | -*Stock barcode sheet* from the home page of the app. |
| 177 | +In addition to processing and scanning barcodes for existing, previously-created internal transfers, |
| 178 | +the *Barcode* app can also be used to create transfers from scratch, simply by scanning a printed |
| 179 | +operation type barcode. |
| 180 | + |
| 181 | +.. admonition:: Did you know? |
| 182 | + |
| 183 | + Odoo's *Barcode* application provides demo data with barcodes to explore the features of the app. |
| 184 | + These can be used for testing purposes, and can be printed from the home screen of the app. To |
| 185 | + access this demo data, navigate to the :menuselection:`Barcode app` and click :guilabel:`stock |
| 186 | + barcodes sheet` (bolded and highlighted in blue) in the information pop-up above the scanner. |
| 187 | + |
| 188 | + .. image:: transfers_scratch/transfers-scratch-demo-data.png |
| 189 | + :align: center |
| 190 | + :alt: Demo data prompt pop-up on Barcode app main screen. |
| 191 | + |
| 192 | +To do this, first navigate to the :menuselection:`Barcode app`. Once inside the *Barcode* app, a |
| 193 | +:guilabel:`Barcode Scanning` screen displaying different options is presented. |
| 194 | + |
| 195 | +From this screen, when using a USB or bluetooth barcode scanner, directly scan the product barcode. |
| 196 | + |
| 197 | +When using a smartphone as the barcode scanner, click the :guilabel:`Tap to Scan` button (next to |
| 198 | +the camera icon, at the center of the screen). This opens a :guilabel:`Barcode Scanner` pop-up |
| 199 | +screen that enables the camera of the device being used. |
| 200 | + |
| 201 | +Face the camera toward the printed operation type barcode to scan it. Doing so processes the |
| 202 | +barcode, and navigates to a barcode transfer screen. |
| 203 | + |
| 204 | +From this screen, an overview of all products to process within that specific internal transfer |
| 205 | +(**WH/INT/000XX**) is shown. Since this is a new transfer created from scratch, however, there |
| 206 | +should not be any products listed on the page. |
| 207 | + |
| 208 | +To add products, scan the product barcode. If the barcode is not available, manually enter the |
| 209 | +product into the system by clicking the :guilabel:`Add Product` button at the bottom of the screen, |
| 210 | +and add the products and product quantities that should be transferred. |
8 | 211 |
|
9 | | -.. image:: transfers_scratch/transfers_scratch_01.png |
10 | | - :align: center |
| 212 | +Once ready, click :guilabel:`Confirm` to confirm the changes made to the product line. |
11 | 213 |
|
12 | | -Once done, you can scan the one for which you want to create a new |
13 | | -document. Then, an empty document will be created and you will be able |
14 | | -to scan your products to populate it. |
| 214 | +.. image:: transfers_scratch/transfers-scratch-blank-product-editor.png |
| 215 | + :align: center |
| 216 | + :alt: Blank product editor in scratch internal transfer. |
15 | 217 |
|
16 | | -.. image:: transfers_scratch/transfers_scratch_02.png |
17 | | - :align: center |
| 218 | +Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), |
| 219 | +click :guilabel:`Validate`. The internal transfer has now been processed, and the *Barcode* app can |
| 220 | +be closed out. |
0 commit comments