OdooWiki OCA HUB

Barcode Stock Partner Delivery Zone

barcode_stock_partner_delivery_zone folder_open OCA/barcode-interface open_in_new
Inventory/Inventory License: AGPL-3

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.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Adds the customer's delivery zone to the warehouse barcode app: operations can be grouped and filtered by zone, the zone is shown on each operation card, and the operator can change it from the operation's Information tab.

This module connects delivery zones (from the contacts module) with the barcode warehouse app. It adds no new screens of its own; it extends the existing operation list and operation detail screens.

In the operation list: - A new "Delivery Zone" grouping level is added, placed first, so operations can be grouped by the zone of the customer they go to. Groups are sorted by zone name, and operations without a zone appear under "No zone". - A "Delivery Zone" section is added to the Filters menu, with options for all zones, "No zone", and each zone. Archived zones only appear while they are the selected filter. - Delivery orders (outgoing operations) open grouped by delivery zone by default, unless the operator has already chosen another grouping in the session. - Each operation card shows its zone with a small map icon, and the search also matches zone names.

In the operation's Information tab: - A "Delivery Zone" field shows the operation's current zone and lets the operator pick another one from a drop-down. The change is saved immediately and a confirmation message appears; if saving fails, the previous zone is restored.

If zones cannot be loaded, the list still opens without zone filtering, and operations whose zone could not be read are kept visible rather than hidden. The module touches stock.picking and partner.delivery.zone.

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/barcode-interface.

terminal Installation and usage

OCA documentation · Odoo 18.0

Usage

Source · Odoo 18.0

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).

No verified information in OCA: Installation, Configuration.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.