Which is the reason behind the stock_lot_sled not controlling the lot's expiry date?

Support User
#1

After using deeply the stock_lot_sled with several projects we came up with the previous question. The point is Tryton only checks the lot’s shelf life instead of checking both, shelf life and expiry time or date.

How the solve the situation where the company buys a product which has no shelf life but it does has expiry date? Why does Tryton allow to configure “None” in the shelf life state and “Required” in expiration state?
The majority of users configure their lots only with the expiration date required and the system allows them to produce with expired entries and serve expired goods.

Shall shelf life state be required when expiration is? Or should the expiry date be checked too after shelf life state when it is “None”?

#2

Because it is the shelf life that matters for stock management because it is by definition when the lot can no more be on shelve.

#3

I see we have “Fecha Caducidad” for the expritation_date and the term “Fecha Caducidad” is what is more used in Spain.
Do you think improving the translation may improve the usage from users?

#4

In terms of usage there are some companies which use the shelf life and expiry date for their products, for example, salt or other species which are sold in groceries and supermarkets. Those products have a shorter shelf life than their expiry date, because those products can’t be sold, when they are just one month ahead of their expiry date. Just like in supermarkets where you may display a product until a couple of days before of its expiry date, not closer. But you can “use” such product until the expiry date if you purchase it.

However, in the other hand, we have those commodities or production entries which have no shelf life, they only have expiry date. We conclude that it is the same date for both, shelf life and expiry date but why should we enter the same date two times? That is why I was asking if there is any option to manage both dates separately.

#5

It depends on what you want. If you want tryton to avoid moving goods that are before the date use the shelf life date. If you only need to track the date but do not check anything use the expiry date.

#6

Maybe using a formula to calculate the shelf life using expiry_date as a variable would be a good option. In this case you can define the shelf life = expiry_date as default on the product template. In the case of salt you can define the shelf life = expiry_date - 6 months.
Just an idea.

#7

That is not an option, because if we print labels we have to have different values and print a meaningful date for each one, shelf life and expiry date we can not tangle both and print the expiry date as a shelf life date because we will be missing the expiry date, which is mandatory.

#8

Absolutely, that could be an option.

#9

This is possible with the current implementation by enabling both dates on the product configuration and using the same days for both dates.
If there should be some delay, you just need to set diferent values for the time.

Of course, this will only work when creating new lots if the user needs to set custom values he should take care of setting the right values. This should not be a big issue as it can be easly customized by adding some on_change that computes the other date based on the diference of days between both.