Delivery State
This module adds additional functions that will be needed for the carrier developments. It provides fields to be able to contemplate the tracking states and also adds a global field so it can have generic states in addition to the ones carrier gives us.
Table of contents
Configuration
A scheduled action for automating the tracking update for these pickings can be configured going to Settings > Technical > Scheduled Actions and then choosing Update deliveries states. It will update the pending delivery states for the pickings with service providers with tracking methods configured, and in pending state (not delivered or cancelled).
In order to send automatic notifications to the customer when the picking is customer_delivered:
Go to Inventory > Configuration > Settings.
Enable the option Email Confirmation (customer delivered).
Choose the template “Delivery: Picking delivered by Email”.
Usage
Depending on the delivery service provider, the state tracking could be more or less complete, since it could have or not the necessary API calls implemented.
With regular methods (fixed, based on rules):
Go to Inventory / Operations and open an outgoing pending picking.
In the Additional Info tab, assign it a delivery carrier which is fixed or based on rules.
Validate the picking and you’ll see in the same tab the delivery state info with the shipping date and the shipping state.
If enabled, an automatic notification will be sent to the picking customer.
When service provider methods are implemented, we can follow the same steps as described before, but we’ll get additionally:
In the Additional Info tab, we’ll see button Update tracking state to manually query the provider API for tracking updates for this expedition.
Depending on the stated returned by the provider, we could get these states (field Carrier State):
Shipping recorded in carrier
In transit
Canceled shipment (finished)
Incident
Warehouse delivered
Customer delivered (finished)
In the field Tracking state we’ll get the tracking state name given by the provider (which is mapped to the ones in this module)
In the field Tracking history we’ll get the former states log.
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
Contributors
Trey:
Roberto Lizana <roberto@trey.es>
-
Zahra Velasco <zahra.velasco@factorlibre.com>
-
Pedro M. Baeza
David Vidal
Víctor Martínez
Marçal Isern <marsal.isern@qubiq.es>
Maintainers
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-delivery-state 18.0.1.2.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_delivery_state-18.0.1.2.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_delivery_state-18.0.1.2.2.3-py3-none-any.whl
| Download URL | odoo_addon_delivery_state-18.0.1.2.2.3-py3-none-any.whl |
|---|---|
| Size | 41.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08308f46528017cb65e72b628c6e18a07480428a53054c87ebeef72f72975dc2
|
|
BLAKE2b-256 checksum How to use checksums |
cdabf089c16b6c73b09807a0ea126cb9c7c1819131e39ccbc43fab8d8e917ee7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
