OdooWiki OCA HUB

Delivery Preference Glue Stock Picking Group

delivery_preference_glue_stock_picking_group folder_open OCA/wms open_in_new
Hidden License: AGPL-3

This module fixes a conflict between the two modules delivery_carrier_preference and stock_picking_group_by_partner_by_carrier, that makes the function release_available_to_promise loose the carrier set by default on stock picking for the backorder left by the release.

A customer has a favorite delivery carrier that is set on his sales orders and the related stock pickings. The company can have some preferred carrier based on the weight of a shipping. When a stock picking is partially released the quantity that can be shipped should have the corresponding company preferred carrier (if applicable) but the backorder quantity should keep the customer favorite carrier.

The grouping done by the module stock_picking_group_by_partner_by_carrier breaks this functionality by recreating procurement groups during the release.

auto_awesome What this module does

AI-generated from the code · Odoo 14.0

Automatically keeps the customer's preferred delivery carrier on backorder pickings after a partial release, instead of losing it when pickings are grouped by partner and carrier.

This is a hidden glue module that fixes a conflict between two other modules: one that sets a customer's favourite delivery carrier on sales orders and stock pickings, and one that groups pickings by partner and carrier. Without this fix, when a stock picking is partially released (only part of the quantity is available to ship), the backorder created by the release could lose the carrier that was set by default from the customer.

The module extends the stock.move model and overrides the release_available_to_promise method. It only acts on outgoing moves whose picking is flagged for preferred-carrier recomputation. After the normal release process runs, it looks at the sales orders linked to those pickings, finds the pickings that still need to be released, and resets their carrier to the carrier stored on the related sales order.

In practice, users do not see a new menu or button. The change is automatic: the shipped quantity can still get the company's preferred carrier based on weight, while the backorder keeps the customer's favourite carrier. This keeps delivery information consistent on backorders without manual correction.

Models and fields (1)
  • stock.move · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 14.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: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

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.