<h1 class="title">Delivery Schenker</h1> <p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" 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.png" /></a> <a class="reference external" href="https://github.com/OCA/delivery-carrier/tree/14.0/delivery_schenker"><img alt="OCA/delivery-carrier" src="https://img.shields.io/badge/github-OCA%2Fdelivery--carrier-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/delivery-carrier-14-0/delivery-carrier-14-0-delivery_schenker"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/99/14.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p> <p>This module links the <a class="reference external" href="https://www.dbschenker.com">DB Schenker</a> booking and tracking APIs with Odoo delivery system.</p> <p><strong>Table of contents</strong></p> <div class="contents local topic" id="contents"> <ul class="simple"> <li><a class="reference internal" href="#installation" id="id1">Installation</a></li> <li><a class="reference internal" href="#configuration" id="id2">Configuration</a></li> <li><a class="reference internal" href="#usage" id="id3">Usage</a><ul> <li><a class="reference internal" href="#place-shipping-bookings" id="id4">Place shipping bookings</a></li> <li><a class="reference internal" href="#cancel-bookings" id="id5">Cancel bookings</a></li> <li><a class="reference internal" href="#get-labels" id="id6">Get labels</a></li> <li><a class="reference internal" href="#tracking" id="id7">Tracking</a></li> <li><a class="reference internal" href="#debugging" id="id8">Debugging</a></li> </ul> </li> <li><a class="reference internal" href="#known-issues-roadmap" id="id9">Known issues / Roadmap</a></li> <li><a class="reference internal" href="#bug-tracker" id="id10">Bug Tracker</a></li> <li><a class="reference internal" href="#credits" id="id11">Credits</a><ul> <li><a class="reference internal" href="#authors" id="id12">Authors</a></li> <li><a class="reference internal" href="#contributors" id="id13">Contributors</a></li> <li><a class="reference internal" href="#maintainers" id="id14">Maintainers</a></li> </ul> </li> </ul> </div> <a name="installation"></a> <h2><a class="toc-backref" href="#id1">Installation</a></h2> <p>This module depends on the <cite>zeep</cite> python library and the OCA/delivery-carrier <cite>delivery_package_number</cite> and <cite>delivery_state</cite> modules.</p> <p>The Schenker API doesn't provide delivery rating methods, so OCA's <cite>delivery_price_method</cite> is advised in order to use this carrier in a sales workflow.</p> <a name="configuration"></a> <h2><a class="toc-backref" href="#id2">Configuration</a></h2> <p>To configure a Schenker delivery method:</p> <ol class="arabic simple"> <li>Go to <em>Inventory &gt; Configuration &gt; Delivery &gt; Shipping methods</em> and create a new one.</li> <li>Choose <em>DB Schenker</em> as provider.</li> <li>Configure the service parameters according to your contract considerations.</li> <li>Choose a delivery product and a default packaging. This is mandatory for the booking request as it needs the packaging code.</li> </ol> <p>To make tests, set the carrier environment to test from the smart button. Don't forget to set it to production once you're ready to use the delivery method!</p> <a name="usage"></a> <h2><a class="toc-backref" href="#id3">Usage</a></h2> <p>These are the operations possible with this module:</p> <a name="place-shipping-bookings"></a> <h3><a class="toc-backref" href="#id4">Place shipping bookings</a></h3> <ol class="arabic simple"> <li>When the picking is validated, the shipping will be booked at Schenker.</li> <li>With the response, we'll receive the delivery tracking number and the pdf label in a chatter message and it will be kept as attachment to the document.</li> <li>You can manage packages number either with the proper Odoo workflows or with the package number field available in the <em>Additional Info</em> tab. You'll get as many labels as declared packages.</li> </ol> <a name="cancel-bookings"></a> <h3><a class="toc-backref" href="#id5">Cancel bookings</a></h3> <ol class="arabic simple"> <li>As in other carriers, we can cancel the shipping after the picking is done. To do so, go to <em>Additional Info</em> tab and click on the <em>Cancel</em> action on the side of the tracking number.</li> <li>We can generate a new shipping if necessary.</li> </ol> <a name="get-labels"></a> <h3><a class="toc-backref" href="#id6">Get labels</a></h3> <ol class="arabic simple"> <li>If by chance we delete the generated labels, we can obtain them again hitting the <em>Schenker Label</em> buttons in the header of the picking form.</li> </ol> <a name="tracking"></a> <h3><a class="toc-backref" href="#id7">Tracking</a></h3> <ol class="arabic simple"> <li>The module is integrated with <cite>delivery_state</cite> to be able to get the tracking info directly from the DB Schenker API.</li> <li>To do so, go to a picking shipped with Schenker. In the <em>Additional Info</em> tab you'll find an action button to <em>Update tracking state</em> so the state will be updated from the Schenker API.</li> </ol> <a name="debugging"></a> <h3><a class="toc-backref" href="#id8">Debugging</a></h3> <p>The API calls and responses are tracked in two special fields in the picking that can be viewed by technical users. You can also log them in as <cite>ir.logging</cite> records setting the carrier debug on from the smart button.</p> <a name="known-issues-roadmap"></a> <h2><a class="toc-backref" href="#id9">Known issues / Roadmap</a></h2> <ul class="simple"> <li>There's no dummy access key to test API calls so no tests can be performed.</li> <li>The test booking and shipping APIs databases aren't connected so it isn't possible to perform trackings on test mode.</li> <li>Only land shipping is implemented, although the module is prepared for extend to air and ocean just considering the mandatory request fields for those methods. Some additional adaptations could be needed (e.g.: origin and destination airport, port) anyway.</li> <li>Only volume is supported as a measure unit and with the limitations of Odoo itself. To enjoy a full fledged volume support, install and configure the OCA’s <cite>stock_quant_package_dimension</cite> module and its dependencies. The connector is ready to make use of their volume computations.</li> <li>It’d be needed to extend the method to support Schenker measure units such as loading pieces or pallet space.</li> <li>Some more booking features aren’t yet supported although can be extended in the future. Some of those, although the complete list would be really extensive:<ul> <li>Dangerous goods.</li> <li>Driver pre-advise.</li> <li>Transport temperature.</li> <li>Customs clearance.</li> <li>Cargo insurance.</li> <li>Cash on delivery.</li> </ul> </li> </ul> <a name="bug-tracker"></a> <h2><a class="toc-backref" href="#id10">Bug Tracker</a></h2> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/delivery-carrier/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 <a class="reference external" href="https://github.com/OCA/delivery-carrier/issues/new?body=module:%20delivery_schenker%0Aversion:%2014.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p> <p>Do not contact contributors directly about support or help with technical issues.</p> <a name="credits"></a> <h2><a class="toc-backref" href="#id11">Credits</a></h2> <a name="authors"></a> <h3><a class="toc-backref" href="#id12">Authors</a></h3> <ul class="simple"> <li>Tecnativa</li> <li>Studio73</li> </ul> <a name="contributors"></a> <h3><a class="toc-backref" href="#id13">Contributors</a></h3> <ul class="simple"> <li><a class="reference external" href="https://www.tecnativa.com">Tecnativa</a>:<ul> <li>David Vidal</li> </ul> </li> <li><a class="reference external" href="https://www.studio73.es">Studio73</a>:<ul> <li>Ethan Hildick</li> </ul> </li> </ul> <a name="maintainers"></a> <h3><a class="toc-backref" href="#id14">Maintainers</a></h3> <p>This module is maintained by the OCA.</p> <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>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>This module is part of the <a class="reference external" href="https://github.com/OCA/delivery-carrier/tree/14.0/delivery_schenker">OCA/delivery-carrier</a> project on GitHub.</p> <p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>