User mistakes when introducing dates in different forms

We often find that users make mistakes when introducing dates and those mistakes are difficult to fix afterwards. For example, we find out:

  • Sales with the wrong sale date (which cannot be changed with sale_amendment). Having one or two sales in the future is a frequent mistake.

  • Customers phone asking for somebody to modify a shipment they introduced in the wrong date. The wrong date here affects stock and shipments cannot be undone, it is frequently a problem quite annoying to solve.

I wonder how others are solving those problems.

Would it be a good idea a warning raised when those documents have “rare” dates? We should, of course, agree on what “rare” means.

Other ideas?

Having wrong sale date for confirmed sale is no more a problem because it will no more be used.

A waiting customer shipment can be re-planned by going back to draft, change the planned date and set back to waiting.

A waiting customer shipment can be re-planned by going back to draft, change the planned date and set back to waiting.
[/quote]

The cases that we are referring are customer shipments and supplier shipments which are already done. For example common case when speaking about supplier shipments:

  • the user which receives the goods has to inform an expiry date to the product lot
  • the expiry lot date is 10/10/2025
  • after introducing the expiry date they introduce the effective date in the supplier shipment and finish the shipment, but the problem is that they have introduced 20/05/2025 instead of 20/05/2020.

After this point, there is no way back for the users.

Why filling the effective date? You can let the system put today automatically.
More over, we have now a confirmation for all non reversible actions but we need at some point have those actions.

Indeed there is no reason to allow stock move in the future so I filled Issue 9355: Prevent doing move in the future - Tryton issue tracker.