|
5 | 5 | Inbound and outbound flows
|
6 | 6 | ==========================
|
7 | 7 |
|
8 |
| -There are several ways to handle how a warehouse receives products (receipts) and ships products |
9 |
| -(deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse |
10 |
| -size, and the amount of daily confirmed receipts and delivery orders, the way products are handled |
11 |
| -when coming in and out of the warehouse can vary a lot. Different settings can be configured for |
12 |
| -receipts and deliveries; they do not have to be configured to have the same number of steps. |
| 8 | +Configuring inbound and outbound flows in Odoo is key to optimizing efficiency, traceability, and |
| 9 | +cost. Warehouse managers must balance speed and control, choosing between a streamlined process or |
| 10 | +added checkpoints. |
13 | 11 |
|
14 |
| -.. seealso:: |
15 |
| - - `Using Routes (eLearning Tutorial) <https://www.odoo.com/slides/slide/using-routes-1018>`_ |
16 |
| - - `Push & Pull Rules (eLearning Tutorial) |
17 |
| - <https://www.odoo.com/slides/slide/push-pull-rules-1024>`_ |
18 |
| - |
19 |
| -Choosing the right inventory flow to handle receipts and deliveries |
20 |
| -=================================================================== |
| 12 | +Odoo offers one-step, two-step, and three-step flows, with more steps providing greater control but |
| 13 | +increasing operations. The best setup depends on quality checks, packaging, and warehouse size. |
21 | 14 |
|
22 |
| -By default, Odoo handles shipping and receiving in three different ways: in one, two, or three |
23 |
| -steps. The simplest configuration is one step, which is the default. Each additional step required |
24 |
| -for a warehouse for either the receiving or shipping process will add an additional layer of |
25 |
| -operations to perform before a product is either received or shipped. These configurations depend |
26 |
| -entirely on the requirements for the products stored, such as performing quality checks on received |
27 |
| -products, or using special packaging on shipped products. |
| 15 | +This guide helps businesses determine the most suitable configuration. |
28 | 16 |
|
29 | 17 | One-step flow
|
30 |
| -------------- |
| 18 | +============= |
31 | 19 |
|
32 |
| -The receiving and shipping rules for a one-step configuration are as follows: |
| 20 | +The *one-step inventory flow* is the simplest option, with minimal handling steps and the least |
| 21 | +traceability. In this setup, products move directly from vendors to stock or from stock to |
| 22 | +customers, with Odoo only tracking when items enter or leave the warehouse. This makes it ideal for |
| 23 | +businesses with high-volume, low-risk products or fast-moving operations where additional validation |
| 24 | +steps aren’t necessary. |
33 | 25 |
|
34 |
| -- **Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock |
35 |
| - occur, such as a transfer to a quality control location. |
36 |
| -- **Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping |
37 |
| - occur, such as a transfer to a packing location. |
38 |
| -- Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First |
39 |
| - Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies. |
40 |
| -- Receipts and/or deliveries are handled quickly. |
41 |
| -- Recommended for small warehouses with low stock levels, and for non-perishable items. |
42 |
| -- Items are received or shipped directly into/from stock. |
| 26 | +- **Receiving**: Products go directly into stock. |
| 27 | +- **Shipping**: Products ship directly from stock. |
| 28 | +- **Best for**: Small warehouses, low stock levels, and non-perishable items, where minimal |
| 29 | + processing is needed before products are stored or shipped. |
43 | 30 |
|
44 | 31 | .. seealso::
|
45 | 32 | :doc:`daily_operations/receipts_delivery_one_step`
|
46 | 33 |
|
47 | 34 | Two-step flow
|
48 |
| -------------- |
| 35 | +============= |
| 36 | + |
| 37 | +A *two-step flow* adds an input or output area for processing products before storage or shipment. |
| 38 | +Incoming goods can be unboxed and inspected before shelving, while outgoing shipments are sorted and |
| 39 | +consolidated before dispatch. This setup improves efficiency by assigning storage teams to picking |
| 40 | +and stocking, while dedicated teams handle unboxing, (possibly) packing, and final verification to |
| 41 | +reduce order fulfillment errors. |
49 | 42 |
|
50 |
| -The receiving and shipping rules for a two-step configuration are as follows: |
51 |
| - |
52 |
| -- **Input + stock**: Bring products to an input location *before* moving into stock. Products can be |
53 |
| - organized by different internal storage locations, such as various shelves, freezers, and locked |
54 |
| - areas, before being stocked in the warehouse. |
55 |
| -- **Pick + ship**: Bring products to an output location before shipping. Packages can be organized |
56 |
| - by different carriers or shipping docks before being shipped. |
57 |
| -- Minimum requirement to use lot numbers or serial numbers to track products with a |
58 |
| - :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or |
59 |
| - :abbr:`FEFO (First Expired, First Out)` removal strategy. |
60 |
| -- Recommended for larger warehouses with high stock levels, or when stocking large items (such as |
61 |
| - mattresses, large furniture, heavy machinery, etc.). |
62 |
| -- Products received will not be available for manufacturing, shipping, etc., until they are |
63 |
| - transferred into stock. |
| 43 | +- **Receiving**: Products move to an *input* area before being transferred into stock. |
| 44 | + |
| 45 | + - Until transferred, received products are not automatically reserved for manufacturing, shipping, |
| 46 | + or other operations. |
| 47 | + |
| 48 | +- **Shipping**: Products move to an *output* before shipping to allow for :doc:`sorting or |
| 49 | + consolidation <picking_methods>`. |
| 50 | +- **Best for**: Large warehouses, high stock levels, bulky items, and workflows that separate |
| 51 | + receiving from storage to improve organization and efficiency. |
64 | 52 |
|
65 | 53 | .. seealso::
|
66 | 54 | :doc:`daily_operations/receipts_delivery_two_steps`
|
67 | 55 |
|
68 | 56 | Three-step flow
|
69 |
| ---------------- |
70 |
| - |
71 |
| -The receiving and shipping rules for a three-step configuration are as follows: |
72 |
| - |
73 |
| -- **Input + quality + stock**: Receive products at the input location, transfer them to a quality |
74 |
| - control area, and move the ones that pass inspection into stock. |
75 |
| -- **Pick + pack + ship**: Pick products according to their removal strategy, pack them in a |
76 |
| - dedicated packing area, and bring them to an output location for shipping. |
77 |
| -- Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, |
78 |
| - First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal |
79 |
| - strategy. |
80 |
| -- Recommended for very large warehouses with very high stock levels. |
81 |
| -- Required for any warehouse needing to perform quality control inspections before receiving items |
82 |
| - into stock. |
83 |
| -- Products received will not be available for manufacturing, shipping, etc., until they are |
84 |
| - transferred into stock. |
| 57 | +=============== |
| 58 | + |
| 59 | +A three-step flow builds on the two-step process by adding a quality check and packing area, |
| 60 | +enforcing stricter processes and improving oversight. |
| 61 | + |
| 62 | +.. important:: |
| 63 | + While this setup enhances process control, separating picking and packing requires validation at |
| 64 | + each step. If the same person handles both, it may cause redundancy and slow operations. |
| 65 | + |
| 66 | + Quality checks and packing do not require a three-step flow. Enable :doc:`quality control points |
| 67 | + <../../quality/quality_management/quality_control_points>` separately or activate the |
| 68 | + :ref:`Packages feature <inventory/warehouses_storage/enable-package>` in Odoo to incorporate |
| 69 | + these processes without adding extra transfer steps. |
| 70 | + |
| 71 | +- **Receiving**: Products follow a structured process: *input area* → *quality control* → *stock*. |
| 72 | +- **Shipping**: Products are *picked*, *packed*, and then *shipped*, ensuring proper handling and |
| 73 | + organization. |
| 74 | +- **Best for**: Very large warehouses with strict quality control requirements, dedicated picking |
| 75 | + and packing workflows, and a need for clear traceability across multiple handling stages. Suitable |
| 76 | + when multiple teams manage different steps before products are stocked or shipped. |
85 | 77 |
|
86 | 78 | .. seealso::
|
87 | 79 | - :doc:`daily_operations/receipts_three_steps`
|
88 | 80 | - :doc:`daily_operations/delivery_three_steps`
|
89 | 81 |
|
| 82 | +Add-ons |
| 83 | +======= |
| 84 | + |
| 85 | +To optimize each flow, Odoo provides additional features that can enhance the process. |
| 86 | + |
| 87 | +Storage |
| 88 | +------- |
| 89 | + |
| 90 | +To organize and store products efficiently, use: |
| 91 | + |
| 92 | +.. cards:: |
| 93 | + |
| 94 | + .. card:: Putaway rules |
| 95 | + :target: daily_operations/putaway |
| 96 | + |
| 97 | + Guide products to specific storage locations based on predefined rules |
| 98 | + |
| 99 | + .. card:: Storage categories |
| 100 | + :target: daily_operations/storage_category |
| 101 | + |
| 102 | + Set item or weight limits to prevent overstocking at the location and ensure proper |
| 103 | + organization |
| 104 | + |
| 105 | + .. card:: Consignment |
| 106 | + :target: daily_operations/owned_stock |
| 107 | + |
| 108 | + Keep track of products owned by third parties |
| 109 | + |
| 110 | +Delivery |
| 111 | +-------- |
| 112 | + |
| 113 | +Tailor the outgoing shipment process to fit the business needs. Picking methods and removal |
| 114 | +strategies control how products are reserved for orders, while cross-docking and dropshipping |
| 115 | +determine how they move. Configuring these options in Odoo ensures visibility into product movement |
| 116 | +and confirms that items reach customers efficiently. |
| 117 | + |
| 118 | +.. cards:: |
| 119 | + |
| 120 | + .. card:: Cross dock |
| 121 | + :target: daily_operations/cross_dock |
| 122 | + |
| 123 | + Receive products and immediately transfer them to another warehouse without storing them |
| 124 | + |
| 125 | + .. card:: Dropshipping |
| 126 | + :target: daily_operations/dropshipping |
| 127 | + |
| 128 | + Coordinate with vendors to deliver orders directly to customers, bypassing internal stock |
| 129 | + |
| 130 | + .. card:: Picking methods |
| 131 | + :target: picking_methods |
| 132 | + |
| 133 | + Optimize picking operations using piece, batch, cluster, or wave picking techniques |
| 134 | + |
| 135 | + .. card:: Removal strategies |
| 136 | + :target: removal_strategies |
| 137 | + |
| 138 | + Use FIFO, LIFO, or FEFO strategies to automate the selection of products for delivery |
| 139 | + |
| 140 | +Customization |
| 141 | +------------- |
| 142 | + |
| 143 | +Odoo's flexible framework enables businesses to tailor workflows to match specific operational |
| 144 | +needs. |
| 145 | + |
| 146 | +.. cards:: |
| 147 | + |
| 148 | + .. card:: Custom routes |
| 149 | + :target: daily_operations/use_routes |
| 150 | + |
| 151 | + Define tailored receiving or delivery workflows to meet specific business needs |
| 152 | + |
90 | 153 | .. toctree::
|
91 | 154 | :titlesonly:
|
92 | 155 |
|
|
0 commit comments