<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="pos-order-to-sale-order"></a> <h2>POS Order To Sale Order</h2> <p>This module extends the functionality of point of sale to allow sale orders creation from the Point of Sale.</p> <p>In the POS UI, buttons has been added to create a sale order and discard the current POS order.</p> <p>This module is useful in many cases, for example :</p> <ul class="simple"> <li>take quotations with a very simple interface</li> <li>take orders with a very simple interface</li> <li>allow clients to pay later</li> <li>if you have some customers that come every day in your shop, but want to have a unique invoice at the end of the month. With this module, you can create a sale order and deliver products every time he comes to keep your stock value correct and to create a unique invoice periodically.</li> </ul> <p>Four options are available:</p> <ol class="arabic"> <li><p class="first">'<strong>Allow PoS order</strong>'</p> <p>A PoS Order is the default type of order (opposed to sale orders). If you want to use only sales order, uncheck this option.</p> </li> <li><p class="first">'<strong>Allow Quotations</strong>'</p> <p>A quotation is a draft sale order. It can be changed and confirmed later from the backend. No payment can be taken with draft orders.</p> </li> <li><p class="first">'<strong>Allow Sale Orders</strong>'</p> <p>A confirmed sale order without picking. Useful if you don't manage stock or sell services otherwise use 'delivered picking'.</p> </li> <li><p class="first">'<strong>Allow Delivered Sale Orders</strong>'</p> <p>A sale order will be created and confirmed. The associated picking will be marked as delivered. Use this option if you delivery your customer frequently and bill him periodically</p> </li> </ol> <p>If multiple options are activated, buttons will appear on the payment screen.</p> <a name="configuration"></a> <h3>Configuration</h3> <p>To configure this module, you need to:</p> <ol class="arabic simple"> <li>Go to Point Of Sale / Configuration / Point of Sale</li> <li>Select the desired behavior by setting some of the checkboxes:</li> </ol> <blockquote> <ul class="simple"> <li>Allow PoS order,</li> <li>Allow Quotations,</li> <li>Allow Sale Orders,</li> <li>Allow Delivered Sale Orders</li> </ul> </blockquote> <a name="usage"></a> <h3>Usage</h3> <dl class="docutils"> <dt>In the PoS, on the payment screen, new buttons will appear according</dt> <dd>to options set in the configuration.</dd> </dl> <div class="figure"> <img alt="static/description/pos_order_to_sale_order.png" src="static/description/pos_order_to_sale_order.png" style="width: 800px;" /> </div> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/184/8.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="technical-notes"></a> <h3>Technical Notes</h3> <ul class="simple"> <li>Some hooks are defined in the JS file, to define custom behavior after having created the sale order (and the stock picking).</li> <li>Some prepare functions are available in the sale.order model, to overload the creation of the sale order.</li> <li>An additional, not displayed option, is to allow payment for sale orders. It requires an additinnal module (not yet written) to handle it correctly.</li> </ul> <a name="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <ul class="simple"> <li>Demo not ported yet. It was non functionnal before migration.</li> <li>Because of the poor design of the Odoo Point of Sale, some basic features are not available by default, like pricelist, fiscal position, etc ... For that reason, unit price will be recomputed by default, when creating the sale order, and the unit price of the current bill will not be used. We could imagine to create an option 'Use Pos Order Unit Price' in a setting.</li> </ul> <p>For more information about that point, you could check pos_pricelist OCA module. (same repository).</p> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/pos/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 smash it by providing detailed and welcomed feedback.</p> <a name="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Sylvain Le Gal (<a class="reference external" href="https://twitter.com/legalsylvain">https://twitter.com/legalsylvain</a>)</li> <li>Raphaël Reverdy (<a class="reference external" href="https://github.com/hparfr">https://github.com/hparfr</a>)</li> </ul> <a name="funders"></a> <h4>Funders</h4> <p>The development of this module has been financially supported by:</p> <ul class="simple"> <li>GRAP, Groupement Régional Alimentaire de Proximité (<a class="reference external" href="http://www.grap.coop">http://www.grap.coop</a>)</li> <li>Akretion</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>