<img alt="License" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> <a name="purchase-transport-addresses"></a> <h2>Purchase - Transport Addresses</h2> <a name="description"></a> <h2>Description</h2> <p>This module - together with <strong>Stock - Transport Addresses</strong> (<cite>stock_transport_multi_address</cite>) and <strong>Sale - Transport Addresses</strong> (<cite>sale_transport_multi_address</cite>) - manages in a coherent way the following addresses in the standard Odoo workflows:</p> <ul class="simple"> <li>origin address</li> <li>destination address</li> <li>consignee</li> </ul> <a name="delivery-addresses-management"></a> <h3>Delivery addresses management:</h3> <p>This module adds a delivery address to the purchase order, which is automatically propagated to a corresponding field in the generated picking.</p> <p>Some of this logic was present in the core, but is not functioning properly. More specifically, in the core, a dropshipping purchase order has two fields: partner_id is used for the supplier, and dest_address_id contains the address of the customer. This works, except that the address is not visible because of odoo/odoo#2950).</p> <p>On the other hand, the picking has only one field: the partner_id. By default, it takes the delivery address of the PO if there is one, or else the supplier. The stock.move also has a partner_id field that is filled with the same partner. To make things even more confusing, in v7 the partner_id of the move is the supplier, while the partner_id of the picking is the customer address.</p> <p>This means that in v8 with core modules, we do not clearly see the supplier and the customer address of a picking. Those two fields are important to handle dropshipping.</p> <p>With this module, in dropshipping mode the generated picking will have the supplier in the partner_id field, and the customer address in the new delivery_address_id field.</p> <a name="credits"></a> <h2>Credits</h2> <a name="contributors"></a> <h3>Contributors</h3> <ul class="simple"> <li>Alexandre Fayolle &lt;<a class="reference external" href="mailto:alexandre.fayolle&#64;camptocamp.com">alexandre.fayolle&#64;camptocamp.com</a>&gt;</li> <li>Leonardo Pistone &lt;<a class="reference external" href="mailto:leonardo.pistone&#64;camptocamp.com">leonardo.pistone&#64;camptocamp.com</a>&gt;</li> <li>Yannick Vaucher &lt;<a class="reference external" href="mailto:yannick.vaucher&#64;camptocamp.com">yannick.vaucher&#64;camptocamp.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h3>Maintainer</h3> <a class="reference external image-reference" href="http://odoo-community.org"><img alt="Odoo Community Association" src="http://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="http://odoo-community.org">http://odoo-community.org</a>.</p>