<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> <a name="merge-sale-orders"></a> <h2>Merge sale orders</h2> <p>This module allows the sale employee to merge draft or confirmed orders from the same customer.</p> <p>When orders are merged, draft invoices and unprocessed outgoing pickings will be merged as well.</p> <a name="usage"></a> <h3>Usage</h3> <p>To use this module, you need to go to the main sale order that you want to merge with other sale orders. If there are any candidates, you will see a <em>Merge</em> button in the header of the sale order form. If you click on this button, a window will pop-up that has all mergeable sale orders preselected. Remove the orders that you do not want to merge, and click on the <em>Merge</em> button in the footer of the pop-up window. The main window will then refresh to the updated main sale order.</p> <p>The mergeability criteria are defined as follows:</p> <ul class="simple"> <li>Same customer, shipping address, warehouse and company.</li> <li>Orders must be in status 'Draft Quotation', 'Quotation Sent', 'Waiting Shedule', 'Sale Order', 'Sale to Invoice'.</li> <li>Once the order has already been confirmed, only draft orders or confirmed orders with the same invoice policy can be merged.</li> </ul> <p>The criteria can easily be extended in a custom module using method _get_merge_domain of model sale.order</p> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/167/8.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <ul class="simple"> <li>Orders with an invoice exception or a picking exception cannot be merged.</li> <li>If prepaid sale orders with confirmed invoices are merged, procurement will not be postponed until all the invoices are paid. Instead, it will start when the original invoice of the main order has been paid.</li> </ul> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/sale-workflow/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.</p> <a name="credits"></a> <h3>Credits</h3> <a name="images"></a> <h4>Images</h4> <ul class="simple"> <li>Odoo Community Association: <a class="reference external" href="https://github.com/OCA/maintainer-tools/blob/master/template/module/static/description/icon.svg">Icon</a>.</li> </ul> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Stefan Rijnhart &lt;<a class="reference external" href="mailto:stefan&#64;opener.amsterdam">stefan&#64;opener.amsterdam</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://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="https://odoo-community.org">https://odoo-community.org</a>.</p>