Ir al contenido
Menú
Se marcó esta pregunta
2 Respuestas
859 Vistas

Hello


We have the following question for a company that has multiple clothing shops with an own warehouse and those shops need to be resupplied from a main warehouse.

The main problem that we are having at the moment is with cross-docking. The flow should be as followed:


There is a need of certain products in their shop in Ghent (WHGENT). This need has to be fulfilled by the main warehouse (WHMAIN). When WHMAIN does not have enough stock, or there is no stock in general then these products need to be purchased from the supplier.

When the supplier delivers the products, it will be delivered to the main warehouse. The products are not taken into stock but it has to go from the incoming location to the outgoing location with the cross-docking route.

At the moment, we had some recommendations from Odoo Support top set-up a flow but with these flows we need to cancel one operation and also change another operation from picking to cross-docking and this is something that we want to prevent doing (too error sensitive).


Anyone that has a flow similar to this one and can help us out?



Avatar
Descartar

Might need a bit more details on the current routes and locations (single / multi step delivery, receipts, location etc) setup in each WH (main and shop). 

Additionally what triggers these procurement routes on each of the WHs? (resupply, replenishments or inventory operations etc)

Autor

Hi Jaideep

At the moment there are 2 warehouses, WHMAIN en WHGENT. More Warehouse will be added but we want to get the flow first before setting up the other ones.
WHMAIN will be the warehouse were all purchase are done. the other warehouses will be warehouse used for the shops and these warehouses need to be replenished by WHMAIN.

WHMAIN has 2-step for receiving and delivering (because we need this for the cross-docking) and other warehouses only have the 1-step for receiving and delivering.

We will be working with re-ordering rules in the shops so that the replenishment can be done. When there is a need of products in the shops, we will need to look at the stock of the WHMAIN first. 

  • If there is stock, then we send the stock from WHMAIN to WHGENT. 
  • If there is stock, but not enough, then we send the available stock to the shop and order the remaining units from supplier. These products don't come in the stock of WHMAIN but should be delivered to WHGENT with cross-docking.
  • If there is no stock in WHMAIN, then we order the units from supplier and then we also don't take the units into stock of WHMAIN but also work with cross-docking to send it to WHGENT.


Mejor respuesta

Thanks for details, the expected outcome is clear. However, there are no details of your route configuration.


Do let me know if these assumptions are correct.. 1. you are on V18+ where multi-step routes are configured with push rule 2. The standard re-supply warehouse route is triggered for re-order/ replenishing stores (WH) 3.You have created a Push rule WHMain/Input to WHMain/output for cross-docking.


  • Modify the resupply route - specifically modify the rule Pull from WHMain stock to WHMain Output by modifying supply method to "Take from stock, if unavailable trigger another rule"


In the above configuration for a resupply trigger the below operations would be triggered


a. A 'PICK' from WHMain/Stock to WHMain/Output - this would be for 'ALL' of the demand qty and available qty would be reserved in the operation


b. Available qty is picked WHMain/ Stock to WHMain/Output - NO backorder needs to be created. Alternately demand qty can be changed by 'unlocking' Pick operation


b. For the unavailable qty in WHMain/Stock an RFQ would be triggered with a receipt operation. Vendor to WHMain/Input


c. On validation of Receipt Cross-dock operation is triggered WHMain/Input to WHMain/OUtput


d. On validation of both PICK and (or) cross dock operations delivery operation is triggered


This is in line with your desired outcome, as the 1st step is always to check availability in WHMain stock location which triggers the Pick operation followed by cross dock operation. This provides the flexibility to choose between stock qty and buy qty. The 'demand' qty on the Pick operations can be modified by 'unlocking' the operation.


If the need is to always trigger cross-dock then you could configure route as illustrated in the below post


https://www.odoo.com/forum/help-1/what-should-i-do-if-i-need-to-use-the-cross-dock-route-in-version-18-2-275548


Further, if your need is flexibility to choose between cross-dock and stock you could check the below configuration


https://www.odoo.com/forum/help-1/how-can-i-configure-cross-dock-if-i-have-the-space-otherwise-hold-inventory-in-stock-aka-flexible-cross-docking-272810

Avatar
Descartar
Autor

Hi Jaideep

Thanks for the extensive explanation. For answering your question about the routes. All routes are all default configured routes from Odoo itself. We changed them now because of the feedback Odoo gave us but it is all still in staging so we can redo the flow with some changes.

We are currently running Odoo on v18 and multi-step routes are indeed active. The default replenishment route is indeed triggered when we do a replenishment for WHGENT.

We have not yet set a new push-rule from input to output because of the following:

When we order the products for WHMAIN, a transfer from Supplier to Input is created and also a transfer from input to stock.
Cross-docking is not automatically triggered. What we have to do (from feedback Odoo Support) is to cancel the transfer from input to stock. Then we have to look for the picking transfer (Stock --> Output) change the operation type from picking to cross-docking.

The explanation from Odoo in following video: https://drive.google.com/file/d/1pWPvsrC30lPONl_XEBVQP2lVGs2Ri6hn/view

Hi, thanks for sharing the details.

Yes, there are multiple ways to configure/ achieve the objectives.

The common thread here is a Pick and a transfer operation that is auto created requiring manual modifications (change of qty or cancellation and change of Location) In many ways this is essential as a decision and control point while planning each fulfillment. Furthermore these plans (manual inputs) can be made in advance (at time of planning) to these operations. The operator at the time execution would just follow the said operation.

>>> When we order the products for WHMAIN, a transfer from Supplier to Input is created and also a transfer from input to stock.<<<<

2 operations are created as the receipt operation has been configured as 2 step. If your current receipt is single step, then I would suggest to keep it as 1step. In this configuration a single receipt would be created vendor to Stock. For cross docking, change the destination location from WHMain/stock to WHMain/ output. Again this wouldn’t take away the Pick operation which would require manual modifications as well.

Suggesting / recommending a solution has a lot to do with nature of business, volume of transactions, skills and training required on the ground while balancing current processes.

Also, do consider the example here is of 1 product with no availability in WHMain. In practice I would believe WHGent would request multiple products which might have varying availability in WHMain and balance fulfilled by more than 1 vendor (PO).

Hope this helps explain that each case is unique.

Mejor respuesta

Hi,


Please take a look at the following for Cross-Docking.

* https://www.youtube.com/watch?v=hsc-Ky6c2fk

https://www.cybrosys.com/blog/how-to-optimize-inventory-flow-with-cross-docking-in-odoo-18

https://www.odoo.com/documentation/18.0/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.html 


Hope it helps

Avatar
Descartar
Autor

@Cybrosis

This is a normal cross-docking flow which is completely clear to us, but the cross-docking needs to happen between 2 warehouses of the same company and that flow is not optimal in the default cross-docking flow.

Publicaciones relacionadas Respuestas Vistas Actividad
2
may 23
3351
1
abr 24
3192
0
oct 22
3382
2
ene 25
1295
0
sept 24
1381