Cutoff
Potpone order preparation by 1 day if it has been validated after the partner or the warehouse cutoff.
This can be bypassed if commitment date is set.
Warehouse Calendar
Postpone delivery according to the warehouse calendar, if any.
Partner delivery window
Allows to define scheduling preference for delivery orders on customers, in order to select possible delivery windows to postpone deliveries to.
Table of contents
Usage
To use this, you have to configure a few things:
You may configure the cutoff by either:
setting the order cutoff preference to warehouse_cutoff, in order to use the warehouse cutoff.
setting the order cutoff preference to partner_cutoff, in order to use the partner cutoff.
By default, customer’s delivery window is set to anytime (default odoo behavior). It can also be set to working days or time window. If the latter is chosen, then time windows will have to be configured on the customer.
By default, warehouse working hours aren’t taken into account when computing the scheduled date. If you want to use this feature, just add a calendar on the warehouse, and enable the apply cutoff option.
Known issues / Roadmap
- The following modules (available in 13.0) has been merged into this module:
sale_warehouse_calendar
sale_cutoff_time_delivery
sale_partner_delivery_window
sale_partner_cutoff_delivery_window
The reason for that is that sale_warehouse_calendar overrides have to be executed between sale_cutoff_time_delivery and sale_partner_delivery_window, and there’s no other clean way to do that.
- However, there’s still a few things to deal with:
Clean tests
Clean code
Use TZ where it is not the case
Use calendar instead of time windows when delivery preference is working days
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Akim Juillerat <akim.juillerat@camptocamp.com>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Simone Orsi <simahawk@gmail.com>
Matthieu Méquignon <matthieu.mequignon@camptocamp.com>
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.
Current maintainer:
This module is part of the OCA/sale-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo14-addon-sale-delivery-date 14.0.1.1.0
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 | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_sale_delivery_date-14.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_sale_delivery_date-14.0.1.1.0-py3-none-any.whl |
Release files / odoo14_addon_sale_delivery_date-14.0.1.1.0-py3-none-any.whl
| Download URL | odoo14_addon_sale_delivery_date-14.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 56.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
836a6e150833eee4ecaffb0d0ad3e2e6e1082174e478ee4bf85790bd1a5c561d
|
|
BLAKE2b-256 checksum How to use checksums |
ced20c1f66ed4034e0e1f19840e30140254d00f7f3e90d500c40e2acd0517733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo14-addon-sale-delivery-date 14.0.1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.