Integration with GLS shipping webservices. Documentation: http://gls-shipit.gls-group.eu/webservices/2_8_11/doxygen/WS-REST-API/index.html
Table of contents
To start using GLS, you need to configure two types of settings in Inventory - Configuration- Delivery or Inventory - Configuration - Settings which leads to the right section in inventory global settings. First you have the Carrier Account where you find account number and password then you also have Shipping Methods with other GLS parameters to configure such as contact ID, urls and return address. These 2 types of settings use "GLS" as delivery type. The contact ID corresponds to the sender which needs to be a contact in the GLS database. This determines the default return address, as well as the billing. You can also configure the tracking url that is used for each carrier.
For client integration tests you need to fill your credentials in the tests/common.py.
Create the packages on GLS which returns a tracking ID. If there is any kind of mistake (address, weight), it is possible to cancel it as long as it has not been scanned yet. If the package is not cancelled, it is invoiced even if it never ships.
When sending a picking, all products should be put in one or multiple packages. These packages need to have a GLS packaging either Parcel, Express, or Freight. These are already pre-configured in the module data.
The end of day report should be printed when the delivery takes place. At the last resort, this function should be called at the end of the day. If it had already run, it would have no impact. In case the delivery is delayed, the report should simply be kept for the next day, and provided with the next report if there is one.
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.
- Acsone
- Akretion
- David Beal @ Akretion
- Nans Lefebvre <nans.lefebvre@acsone.eu>
- Laurent Mignon <laurent.mignon@acsone.eu>
- Hughes Damry <hughes.damry@acsone.eu>
This module is maintained by the OCA.
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/delivery-carrier project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.