Comment 5 for bug 1192115
Revision history for this message
| Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote Re: [7.0] carrier information not propagated from sale order to pickings | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Hello Amit, the problem is not in the invoicing part. I understand that part, thanks for the clear explanation. The problem is when handling the logistics.
Imagine an e-commerce company offering an expensive express shipping (using carrier UPS) and a low cost slow shipping (using carrier Chronopost). The Chronopost truck comes around once a week on wednesday to pick up the products, and the UPS truck comes once a day. The invoicing is made on sale order, and the orders are prepaid, so the customer says 'I choose the Chronopost delivery method' and gets invoiced for the amount related to this carrier. So we are using your scenario 1 (in comment #4).
Now, for the people working in the warehouse, things get complicated : they need to group the orders they prepare based on the delivery method (carrier_id), so that the process the UPS delivered sale orders in priority each day on the one hand, and make sure that all the orders shipped by Chronopost are ready on wednesday. However, since we are using "invoice on sale order" (which the logistics people don't care about), they don't have the information available on the stock.picking objects.
Is this explanation clearer?
Regards,
Alexandre