Hello @lubos. I think the inventory should get a close accounting period and recalculate algorithm should respect those dates. This would make it easier for users to understand, as the current lock date maybe lifted for some reason and when recalculated the previous costs may change.
This way you can also implement an automatic trigger of recalculate button (when recalculation is needed as you mentioned Manager knows when costs are incorrect and needs recalculations).
This approach would make the process more automated, ensuring that previous inventory values remain consistent even if any algorithm changes occur in future.
I see myself that mental model for inventory is not great at the moment and I’m exploring all the options how to present this in logical way.
This is something that worries me too.
And I see that lock date is not really the right way to constrain inventory recalculations because some businesses prefer to roll the lock date forward on daily basis. If they have negative inventory, then recalculation might not give accurate results which will create more confusion.
I’m not sure I can visualize what you are proposing but I’m interested to hear more.
Simply it is adding an Inventory Lock Periods screen under settings and making the recalculate algorithm to take the reference date from this screen rather than Lock accounting period screen. And instead of single date like Lock accounting period the date should be entered every period and the latest one will be used for Recalculations.
Let say i create a new closing period entry on 30 Jun 24, then the recalculate button would take that Date into consideration and will recalculate after 30 Jun 24. Then by adding another entry let say 30 Jun 25 Recalculation will be done after 30-jun-25.
Once a closing entry is created most businesses won’t need to delete that entry and with deletion a warning should be displayed showing inventory costs may change.
Here you mentioned why you can’t make this automated
By adding a separate lock period for inventory will solve that issue too.