Barcode Stock Partner Delivery Zone
This module is the bridge between delivery zones (partner_delivery_zone) and the warehouse app of the Barcode suite: the operations to process can be grouped and filtered by the delivery zone of the customer they go to, and an operation’s zone can be changed from the scanner.
partner_delivery_zone gives each contact a delivery zone and carries it onto the transfers made for it. This module brings that zone into barcode_stock’s operation lists and into the operation’s Information tab, without changing either module.
It installs itself as soon as both barcode_stock and partner_delivery_zone are installed.
Table of contents
Usage
Configure the delivery zones in Contacts > Configuration > Delivery Zones and set them on the customers (or their delivery addresses); their transfers get the zone automatically.
In the operation lists
Delivery orders open grouped by zone, so the operator works through one zone at a time. Operations without a zone are grouped under No zone. Receipts and internal transfers open as before; the grouping can be turned on or off for any list from the Group menu, and it is kept during the session.
The Filters menu has a Delivery Zone section: pick a zone, or No zone, to see only those operations. Like the status and date filters, it can be saved as the list’s default with the ★.
Each operation shows its zone, and typing a zone name in the search narrows the list to it.
In an operation
The Information tab shows the operation’s delivery zone and lets the operator change it from the list of zones; the change is saved at once, as in the back office (and reaches the sale order, through partner_delivery_zone).
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
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/barcode-interface 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-barcode-stock-partner-delivery-zone 18.0.1.0.0.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 | Actions Reset |
|---|---|---|---|---|
| odoo_addon_barcode_stock_partner_delivery_zone-18.0.1.0.0.3-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_barcode_stock_partner_delivery_zone-18.0.1.0.0.3-py3-none-any.whl |
Release files / odoo_addon_barcode_stock_partner_delivery_zone-18.0.1.0.0.3-py3-none-any.whl
| Download URL | odoo_addon_barcode_stock_partner_delivery_zone-18.0.1.0.0.3-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed5efe3f23b1fe93add82f208bb92d96f96965657565b814973b180b376f2387
|
|
BLAKE2b-256 checksum How to use checksums |
83dc97d42bc1c5c12ea986e0c9b21c89b2541877e7d4f58aea63c11b8394b449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-barcode-stock-partner-delivery-zone 18.0.1.0.0.3
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.
