Community mailing list archives

Make to order business case design problem V8

OpenERP Master
- 12/13/2014 02:50:31
My customer does a make to order sales order over 70% of the time, meaning that they sell product that they do not carry stock. They order this product from the manufacturer after the customer pays. Once it is received it is shipped to the customer.

At first I praise the new procurement design over previous versions, now I think it could be trouble. See the following business case for V8.

Customer orders item A at 3 quantity (make to order)
Different Customer orders item A at 2 quantity (make to order)
*Note the order in which the orders were placed, this is important

quotation purchase order is created for 5 quantity. Business confirms they need 5 units to fulfill both orders.

Vendor only sends 2 quantity.

in Odoo, when we received the 2 sent quantity it is assigned to the first order (FIFO) (Customer ordered 3), but this is not sufficient quantity to fulfill the order, however the second order placed the quantity would be sufficient.

This business wants to ship what can ship complete, not necessarily what came in first.

Problem: There appears to be no way to support assigning product to a delivery order based on its ability to completely fulfill. Furthermore, the delivery becomes split into 2 lines. the 2 quantity that is available as reserved, the other quantity of 1 as waiting other operation. I do not like this behavior.

Secondary problem: The business wants to cancel the availability on the delivery order that Odoo assigned the inventory to and assign it to the order that can be fulfilled complete (Qty 2). This appears not possible. If you cancel the reservation, there is no way to assign the availability to the other order without clicking force availability. IMO, even if it is a M2O, and there is sufficient stock and a user requests an availability check, it should check the warehouse for available inventory.

Additionally, once you cancel the availability on a received make to order, it never reassigns availability, and subsequent requests to check availability or running schedulers does not re-assign the canceled inventory. The only way to get past this is to force availability. IMO there is a pretty big issue here, but these are some case scenarios perhaps not many people have.

Looking for some feedback.