Comment 29 for bug 915568

Thanks Quentin for this honest explanation.
We should not introduce features in v7 that we won't be able to port to v8 so we'll have to live with it for now.

So here's what I propose for the core v8:
- if there are conflicting stock moves (ie. move.date > inventory.date), refuse to confirm the inventory.
- if there are no conflicting moves, compute the stock difference at inventory.date and insert the stock moves at the same date.
The error message MUST give users the list of locations/products/lots with conflicts. Then they can re-count the goods, change the date of the inventory and confirm.
This is probably acceptable by most SME with no-too-complex warehouse structures.

Now, for those with more complex warehouses like ourselves, we have developed additional features to secure the inventory :
- indicate the impacted locations BEFORE we open the inventory
- forbid all stock moves on the impacted locations during an inventory
Our has been in production on v6 for ~1 year and we've just finished porting it to v7: Loïc will be making a merge proposal to OCA's WMS project soon, possibly this afternoon.

So in the end, users get the choice to either allow moves during inventory and let the manager clean up the mess, or enforce data integrity from the get go.

Either way, we have to accept that all stock moves must be entered in the correct sequence, and as close to real-time as possible.