1. Yep, have it on the product and checked.
2. Have tried at the warehouse level and product level.
3. Not new, just that I wanted to see it in Inventory Overview. Using Internal Transfer. Or trying to at least if the transfer would ever create.

I tested on V16 and have also tried in other versions and it creates the transfer and reserves the products. There isn't any other configuration to it either. If you using runbot to test maybe I could share the one I used to configure this rule

Once the products are moved to QC bin are they available in that location? Inventory > Reporting > Locations group by location. Just to be certain the products are indeed available to trigger the rule.

Yep, tried in this runbot: https://22447968-15-0-all.runbot109.odoo.com/

Receipt in P00017 for Product QC Test.
Here is what I see: https://www.loom.com/share/59cb2241f9db4cf59e88c1571826c9c6

Thanks for sharing, I tried to make
1. an internal transfer from stock to stock/QC and this triggered the creation of an internal transfer from stock/qc to stock. -- works as anticipated

2. On the receipt operation created a transfer to Stock/QC (on the operation) and provided stock/qc in the detailed operation. This too created the internal transfer from stock/qc to stock -- works as anticipated

3. When the location was stock on receipt operation while in detail operation stock/qc is selected. The system overrode the detailed operation to Stock (WH/IN/00018).

4. When location is stock/qc on operation, it does not allow for some quantities to be sent to Stock. Push rule is triggered

5. Location is WH/Stock on operation, in detailed operation some qty sent to Stock and some quantity Stock/QC. The transfer goes through and product available in location but push rule not triggered. This is your use case which seems to fail.

I tried the above failed case (5) in V16, and in the detailed operation Stock/QC location changed to Stock on validation.

https://22432797-16-0-all.runbot174.odoo.com (your test has been on V15)

It seems it is not possible to split the qty of a product to multiple locations in 1 operation. Essentially all quantities would be moved to QC or all quantities received in Stock followed by an internal transfer of partial quantity to QC

Thanks for Confirming. On #5, which is the use case, any idea why that is? Isn't that what the push rule says it will do? "Why product arrives in X, transfer created to Y." Why does it matter how the product is arriving in X? Trying to better understand route and rules, thanks.

Yes, I would agree, the push rule should have triggered the next operation, irrespective of how the product arrived.

@Jaideep - thanks for confirming at least. Maybe someone else will add something how to get it to work. Thanks.

You might want to consider an alternate process to make it easier on operational.

1. If all your receiving are scanned for QC examination then maybe choose 2 step receiving. Essentially, Pull & Push rule. You could modify the move to be automatic, if you wish the process be accomplished with just 1 operation. The products not validated will remain in receiving location for QC examination.

2. If the QC examination isn't routine, then suggest the use of Internal transfer to QC location to trigger additional operation.

Also, do validate the version you are using as V16 does not allow disparity of location between picking and detailed operation

@Jaideep, thanks for your thoughts. I know there are additional steps that can be done to manually do this, the client receives hundreds of products a day so adding additional operations add a lot of work for something that should be easy.

What do you mean by "V16 does not allow disparity of location between picking and detailed operation". You can still very much receive to different locations on a PO receipt in the detailed operation.

Do try your use case (#5) in V16, it didn't allow the transfer to stock/qc location for me. The runbot you had used last week was V15

I did not try a QC bin, but I can always put products in different bins. I have never seen it not allow that. This was in a v16 runbot. https://www.loom.com/share/95c3b269fefe48c99a3c6c474faf3954

But doesn't really matter. The client for this is for is v15 actually. But not seeing a difference for v15 to v16 on the push rule, does not work in either version when splitting a receipt.