Comment 35 for bug 915568

Here are bits of documentation that I humbly propose for v8 when this lands into trunk, based upon this discussion.

"""
Near-real-time requirements
OpenERP expects you to manage your inventory in near-real-time.
For this reason, it will not let you enter stock moves and indicate a date in the past, because it would for example introduce errors in the price averages, and make inventory adjustments wrong.
Of course you do not have to enter stock moves in real-time - this typically require sophisticated inventory support hardware like RFID tags.
You must however enter every stock move in the same order as they really happened.
"""

"""
Inventory adjustments
Good practices and accounting rules dictate frequent inventories of important goods, and at least one global inventory control per fiscal year.
It is obvious that in the real world, not a single stock move should be made while the goods are being counted in the warehouse.
To help you with this, OpenERP will let you indicate which location is being controlled, and will forbid all stock move entry while the inventory is marked "in progress" in OpenERP.
When the inventory is done, OpenERP will adjust the stock levels at the date when the inventory was started.
This way, you can easily have a consistent inventory at a predictable date, which is crucial for end-of-year accounting operations.
Even though it may introduce stock moves in the past, this is consistent with the near-real-time requirement stated above.
"""