odoo-addon-stock-move-not-merge-by-dest-moves 16.0.1.0.1

Do not merge stock moves that go to different destination moves

Stock Move - Do not merge by destination moves

This module extends the functionality of stock move merging to allow you to never merge stock moves if those moves will go to different destination moves.

Important

This is an alpha version, the data model and design can change at any time without warning. Only for development or testing purpose, do not use in production. More details on development status

Table of contents

• Use Cases / Context

  • Use case example:

  • Odoo Core VS. Module: Workflow comparison

• Usage

• Known issues / Roadmap

• Bug Tracker

• Credits

  • Authors

  • Contributors

  • Other credits

  • Maintainers

Use Cases / Context

This module was developed because sometimes we don’t want our stock movements to be merged if goes to different moves because:

• Sale free products that must be invoiced separatelly (for example, get 2 + 1 free)

• Use warehouse with 2 or 3 steps in Outgoing Shipments

• Use products with Invoicing Policy: Delivered Quantities

All of these conditions must be met for this module to be really useful.

Use case example:

We have an order with two lines of the same product that need to be weighed (kg) and the offer is “get 2 + 1 free”.

Each piece of Fish measures aproximately 1kg and we assume you know how many Fishes you need to take.

The lines of the sale would be like this:

• 2 pieces of Fish for aproximately 2kg in total.

• 1 piece of Fish for aproximately 1kg in total with 100% discount.

Odoo Core VS. Module: Workflow comparison

Odoo Core	With this module
The OUT step will not be grouped, so we will have 2 moves.	The OUT step will not be grouped, so we will have 2 moves.
The PICK step will be grouped into one line, telling you that 3 kgs must be demanded	Since we have 2 separate moves on the OUT step, we don’t want to merge moves in the PICK step. PICK step will tell you that 3kgs must be demanded into 2 separate moves.
When you measure the 3 fishes in the PICK step, we get 1.9kg for the 2 Fishes and 0.7kg for the free Fish. 2.6kg in total.	When you measure the 3 fishes in the PICK step, we get 1.9kg for the 2 Fishes and 0.7kg for the free Fish. 2.6kg in total.
Confirm the PICK step. When you reserve quantities on OUTGOING step, 2kg will go to the 2 Fishes and 0.6kg to the free Fish.	Confirm the PICK step. When you reserve quantities on OUTGOING step, 1.9kg will go to the 2 Fishes and 0.7kg to the free Fish.
Your invoice to the customer will be 2kg for the 2 pieces and 0.6kg for the free fish.	Your invoice to the customer will be 1.9kg for the 2 pieces and 0.7kg for the free fish.
This is not correct: The 2 pices of Fish should be invoiced for 1.9kg and the free fish should be invoiced for 0.7kg at 100% discount.	This is correct

If you also don’t want to have to reweigh in the last step if you exceeded the quantity demanded (Fishes weight 1.14kg each for example), you might be interested in this module:

• stock_rule_reserve_max_quantity

Usage

To use this module, you need to have activated sales module:

1. Activate sale module.

2. Go to Warehouse and activate 2 steps shipping process.

3. Create and confirm a sale with 2 lines: One with discount and one without discount with the same product.

4. Confirm the sale.

5. Check the first picking (PICK) moves is not grouped.

6. Set quantity done on each line that differs (below) the reserved quantity on PICK picking and confirm it.

7. Go to the OUT picking, and check how quantities are distributed correctly.

Known issues / Roadmap

• Receipts (second step quantities not correct)

  Symptom: After testing receipts, the quantities shown/propagated in the second step are not correct (they do not match what was processed in the first step, or the distribution per move is inconsistent).

  Source: Video “Moduon - Review Gelo [16.0][ADD] stock_move_not_merge_by_dest_moves #2014”. https://www.loom.com/share/416b1efb65d04c5d80acd9fac2bf4e0f?sid=8084079a-d28b-4b04-9839-cf3544cddc42

  Expected: The second-step document should reflect the quantities done in the first step, line by line / per destination move, without over- or under-allocation. Actual: The second-step quantities differ from the first step and/or are misallocated. Status: Under investigation.

• Sales (SO line changes not updated on picking)

  Symptom: After confirming a Sales Order, changes made on the SO line are not propagated to the generated picking.

  Source: Video “Moduon - Review Gelo [16.0][ADD] stock_move_not_merge_by_dest_moves #2014 sales”. https://www.loom.com/share/8dfe51327d6d435f8dbdcef4af9ce77b?sid=424232ef-c392-4903-8d42-0254da24c812

  Expected: Updates on the SO line (e.g., quantity/discount that affect downstream moves) should be reflected on the generated picking. Actual: The picking does not refresh after SO line changes. Status: Under investigation.

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

Authors

• Moduon

Contributors

• Eduardo de Miguel (Moduon)

• Rafael Blasco (Moduon)

Other credits

The development of this module has been financially supported by:

• Ulzama

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 maintainers:

This module is part of the OCA/stock-logistics-workflow project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.