v 16.0 Third Party 7
Download for v 16.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Inventory (stock)
Sales (sale_management)
Discuss (mail)
Invoicing (account)
Community Apps Dependencies
Lines of code 7545
Technical Name shipment_advice_planner_toursolver
LicenseAGPL-3
Websitehttps://github.com/OCA/stock-logistics-transport
You bought this module and need support? Click here!

Shipment Advice Planner Toursolver

Beta License: AGPL-3 OCA/stock-logistics-transport Translate me on Weblate Try me on Runboat

This module extend the shipment advice planner engine to add a new planning method based on geo-localization. It uses the GEOCONCEPT solution called TourSolver to plan the shipment advices according to the location of the customers by calculating the best route according to the available resources.

Table of contents

Configuration

Before configuring this module, you must configure your account and your resources on the TourSolver website. Then you should be able to get your api key and paste it in the default backend. You can access to backends list under the setting menu of the inventory module.

The second step is to create the resources. You can add the properties you want TourSolver to use in its calculation of the best route.

For advanced planning, you can define your customer delivery windows. It will be considered in TourSolver calculation.

For more details about the properties you can use, please consult [TourSolver documentation](https://mygeoconcept.com/doc/6cc656Uv7gARvG6T/ts-cloud-doc/docs/en/toursolver-cloud-book/)

Usage

In the shipment planner you will see a new option added to the planning methods. If you select TourSolver, a TourSolver task per warehouse will be created for the pickings you want to plan.

The task will pass through different states by a dedicated cron and at the end of the process will create shipment advices according the returned result from TourSolver.

Known issues / Roadmap

At this stage, the TourSolver task is managed by a cron which will synchronize its status with TourSolver and get the result when it is ready. Another approach is available using queue jobs where the sync task will be rescheduled until it gets the optimization result.

Ideally, a webhook can be developed to be notified by toursolver when the result is ready. He will ensure that the result is obtained as soon as possible.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • ACSONE SA/NV

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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.

This module is part of the OCA/stock-logistics-transport project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.